![]() I mean much more than mere UI or design choices, but the actual quality of generated boards. My goal was to create a NG version, but I quickly discovered that NG versions can quickly become quite complicated (see (2) below), and I had made a poor choice of language for my project (Javascript), which meant I would have to manually write some pretty complicated algorithms that are part of established libraries in other languages.īut mostly, I stopped coding because my version was playable, and I like to play it. The clone I wrote features guess scenarios, because I have effectively abandoned the project. The meta-knowledge we get - that there must be a solution - makes puzzles easier.īesides all of the above, there are a couple other reasons to play versions that might include guessing scenarios:Įase of use, other features, requested permissionsīasically, design choices and privacy concerns. That is, because we know the solution can be deduced, we can know that certain cells must be safe, even if we do not actually have enough information to truly deduce that. The thing is, this can actually reduce the difficulty of certain puzzles. So with a NG board we know there is a solution, so whenever we face a puzzle we cannot immediately solve, we know we need only slow down a little as there is a solution. The ambiguity of not knowing if you need to guess or not (this is obviously more of a beginner issue). a cell which is safe and all of its adjacent cells are safe). Good implementations provide a guaranteed safe initial click, and truly good implementations (on my view) offer a zero-start (i.e.
0 Comments
Leave a Reply. |