Well hey guys, i thought i might wanna make a topic about this project for if someone ever gets interested

so what i'm making is a binary puzzle game (look up: binary puzzle OR binairo)

so what i've got so far:

- premade levels -working
- number placement -working
- solution validator -working

planned features:
- main menu
- stage select (select size of puzzle (6*6 , 8*8 , ...))
- level select (select level of stage (probably 100 or more per stage))
- automatic level generator (if you don't have enough with premade levels)
- win/lose screen
- save progress

any more ideas?

interested in a piece of code?


btw: rewriting my whole program now, for function ordening, for better track of vars, more comments in code, to include the screen states, to use the special 1-touch function instead of the CurrentTouch )which is always on the state of 'ended' after release of the finger, which could lead to some code being ran more than once

Here are two more ideas:
- simple error indicators (that say when a row or column is definitely wrong, for example the no-3-in-a-row or the counting rules are broken)
- a tutorial mode, using next-step suggestions with explanation for why that step can be made (I know my own implementation of it doesn't do an especially good job at the explanation, but it's something, and at least it can get you unstuck)

The first one is trivial to implement, but might not be as useful.
The second is hard to implement, but useful, and when you've implemented it you can build level-select on top of it (by banning hard steps at low levels and by calculating how hard a puzzle is in total so you can "aim" for a certain range of hardness for each level)

Here are two more ideas:
- simple error indicators (that say when a row or column is definitely wrong, for example the no-3-in-a-row or the counting rules are broken)
- a tutorial mode, using next-step suggestions with explanation for why that step can be made (I know my own implementation of it doesn't do an especially good job at the explanation, but it's something, and at least it can get you unstuck)

The first one is trivial to implement, but might not be as useful.
The second is hard to implement, but useful, and when you've implemented it you can build level-select on top of it (by banning hard steps at low levels and by calculating how hard a puzzle is in total so you can "aim" for a certain range of hardness for each level)

about the error thing: yeah for 3 in a row thing i could indicate, but that's about it... like 2 identical rows... should i indicate them as well?

for the tut: i'll implement that one later, i'm gonna keep it in mind and code my app so that i can add it later on

well i'm gonna see about that later should i do it like this: if user has filled it in right, say it, or only tell them they won after pressing some validation button?

no, i'm doing it like this: 2 buttons, '1' and '0' and a 'square' around the selected cell

btw: just tested my own button class, and it works great