The aliasing or whatever on the gridlines is causing that moire effect optical illusion for me and making it hard to enjoy looking for more than a few minutes.
Something to be aware of is to use integer math where possible when dealing with canvas coordinates and drawing. I found I ran into similar issues when I allowed fractions to get into my system.
Nice game, was able to play it for a bit, got 8 right tops.
It seems like the density of bombs is much larger than a regular minesweeper? Or I've just been playing on easy mode in other times...
Do not trust other people's flags though as they can be wrong - possibly intentionally.
> Do not trust other people's flags though as they can be wrong - possibly intentionally.
Yes, this is intentional. I want to see how people start collaborating across very limited channels. Or how they start playing against each other :)
One quick suggestion on the scoring.
Currently scoring favours quantity over quality so the best strategy is to just find the big empty areas rather than thoroughly clearing around bombs. If the score also factored in the adjacent bomb count for each revealed position it would make that a more viable strategy.
1. Do not debug in production (console.log ...)
2. Secure the session (do not display the session ID in high-scores)
3. This is not infinite (in64 * in64) square + weird border :)
4. Balance the score for big discovered area
5. For the new players start the position on an playable area
6. Limit the total of high-scores returned by the ws
7. Limit the ws data as much as possible
...
Thanks and sorry :)
3: 64 bits are close enough to infinity :)
4: Good idea. Maybe something like a logarithmic curve on the number of discovered fields would be good.
5: Also a good point. I'll try to build that
