Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(21 edits)

Ah so more or less,, (bit of a technical breakdown, sorry in advance) when making the boards it does the following steps:

  1. Random fill
  2. Generate labels based on fill
  3. Solve the final board solution based on the labels. This ends up with filled, crossed out, and ambiguous(!) cells
  4. Test ambiguous cells to see if they're really "abiguous" by filling and crossing and seeing if both solve nicely (if one doesn't, then it's state is the other one!). This step is currently what messes up as, for 20+ rows/columns mainly, even when it places and tests it doesn't solve completely!
This means that after you place one or two onto the so called "ambiguous" cells, they're not actually ambiguous in the final solution and thus you get the weird "mostly crossed out" bug and the game doesn't treat it as an error as it doesn't know (thinks it's ambiguous)!! (some form of recursive test is whats needed to fix this directly but that fairly computation intensive so....)

The broken ones usually look like this (as you might’ve encountered!):

Anyways, thank you so much for playing and having fun with it!! :)

Thank you for the breakdown! That makes sense and i get why it's not that easy to fix