Hacker News new | ask | show | jobs
by jsnell 4233 days ago
A few bits of feedback:

- There's no list of rules anywhere. If you forget any rule, you need to go through the tutorial again.

- Is the tutorial missing a rule? (It has the "no two identical rows" rule, but it seems like you also can't have two identical columns).

- The endgame needs work. Right now it's simply highlighting every square that's wrong, rather than just telling which rule was broken. This is absolutely ridiculous, since at that point the player can simply flip every highlighted square and pass (and score the full points?).

There are two alternatives I can think of:

a) Instead of telling which squares are wrong, find an instances of the rules being broken. So for example highlight two rows that are equal, or a column of 3 identical squares, etc.

b) End the game when the board is full, but dock points for incorrect spaces, rather than force the player to go through the busywork of just toggling all squares that were wrong.

6 comments

I have to agree with (a) here. Upon reaching the end of a 6x6, as far as I could tell no rules were broken, yet the solution was not valid.

I'm wondering if multiple solutions can exist and the game will only accept one.

Same here. Can't see what i'm doing wrong. Nice to have the rules on the side or a button to press to show them.
Yeah everything in this 10x10 seems right and I have looked over every single row and column to confirm that I haven't broken any rules but it still tells me that 8 random tiles are incorrect.
You should take a screenshot. See if anyone else can find something you might have missed, or can confirm that you found a winning solution.
here is a 4x4 that naively seems like it should be a legal solution, but isnt:

    1010
    1010
    0101
    0101
same number of 0s as 1s per row same number of 0s as 1s per col no rows or cols with run of 3 of same value

edit: oh - "no two rows are the same". fail. disregard this. must have clicked past that in the tutorial.

That's the point of having a clear set of rules somewhere because most people skipped that part of the tutorial. (I did too) I had to be stuck somewhere, quit the game and redo the tutorial very slowly just to see if there's a rule I didn't see ;)

Another way to find the rules is to use the "eye" on every turn in a 6x6 or 10x10.

Same here. It took me a while to notice that there were two identical vertical rows.
Hi, I'm Martin, the author. Thanks for analyzing the game and the recommendations. I was actually working on your solution a already. So it will be coming up shortly. Also, for those who were suggesting to put it on iTunes and the Play Store, it already is. Enjoy playing! - @mrtnkl
You should put a link to the app in the app stores on the website.
Thanks for not requiring my home address and current blood-sugar levels to install the android app!
I have nothing much to contribute, but I want to say that this is really well done, I'm having a lot of fun with it, and thanks for making an iOS app for it. Now I just need to train my brain to notice rows determined by the "identical row" rule....
I actually appreciate the sense of discovery in the way the rules are presented. It felt like someone was actually watching me play and stepping in once they saw I was stuck.
I had trouble with the "no two identical rows" rule as well. I didn't see it in the tutorial and on the 10 x 10 it was a key piece of logic to solve the puzzle.

Enjoyed the game play and the graphics are very smooth and clean.

Yes, it's pretty easy to maximise your points-per-second simply by clicking everything once to red, then correcting the ones that the endgame says are wrong.
Yes, I believe it is missing a rule. If columns don't need to be identical than this 10x10 puzzle won't have a unique solution: http://i.imgur.com/ZQ8pkfm.png
I get the same problem with valid solutions that don't match whatever it's comparing as the "right" one. It would be better to instead do a goal test after the final square has been filled? Seems to me this wouldn't be too hard to implement instead of comparing with a key.
Nope, there's just one: look at column 1 and 4, so far they are the same.
That's the point.

The rules don't explicitly say that columns need to be unique (only rows).

Within the stated rules there are (as best I can see) 2 valid solutions to that puzzle. It is the introduction of the unstated unique column rule that resolves it.

The author is not a native English speaker, but it seems obvious that the row rule should apply to columns.