zakarya/puzzles
1
0
Fork 0
mirror of git://git.tartarus.org/simon/puzzles.git synced 2025-04-21 08:01:30 -07:00
Code Issues Packages Projects Releases Wiki Activity

Slant uses the same generation strategy as Solo, despite not having

Browse Source 
the property which devel.but claimed to be the reason why that
strategy works. A bit of thought revealed what the _real_ reason is
why this strategy works in some puzzles and not others, so I've
rewritten the paragraph to be more accurate.

[originally from svn r6158]
This commit is contained in:
Simon Tatham
2005-08-03 11:06:16 +00:00
parent 727a18a5a0
commit c212a1b5eb
1 changed files with 16 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
devel.but
View File

@ -3293,19 +3293,22 @@ is next to a three}, which can depend on the values of up to 32 of
the 56 squares in the default setting!), so this tweaking strategy the 56 squares in the default setting!), so this tweaking strategy
would be rather less likely to work well. would be rather less likely to work well.
A more specialised strategy is that used in Solo. Solo has the A more specialised strategy is that used in Solo and Slant. These
unusual property that the clues (information provided at the puzzles have the property that they derive their difficulty from not
beginning of the puzzle) and the solution (information the user is presenting all the available clues. (In Solo's case, if all the
required to fill in) are inherently interchangeable; therefore a possible clues were provided then the puzzle would already be
simple generation technique is to leave the decision of which solved; in Slant it would still require user action to fill in the
numbers are clues until the last minute. Solo works by first lines, but it would present no challenge at all). Therefore, a
generating a random \e{filled} grid, and then gradually removing simple generation technique is to leave the decision of which clues
numbers for as long as the solver reports that it's still soluble. to provide until the last minute. In other words, first generate a
Unlike the methods described above, this technique \e{cannot} fail random \e{filled} grid with all possible clues present, and then
\dash once you've got a filled grid, nothing can stop you from being gradually remove clues for as long as the solver reports that it's
able to convert it into a viable puzzle. However, it wouldn't even still soluble. Unlike the methods described above, this technique
be meaningful to apply this technique to (say) Pattern, in which the \e{cannot} fail \dash once you've got a filled grid, nothing can
clues and the solution occupy completely different spaces. stop you from being able to convert it into a viable puzzle.
However, it wouldn't even be meaningful to apply this technique to
(say) Pattern, in which clues can never be left out, so the only way
to affect the set of clues is by altering the solution.
(Unfortunately, Solo is complicated by the need to provide puzzles (Unfortunately, Solo is complicated by the need to provide puzzles
at varying difficulty levels. It's easy enough to generate a puzzle at varying difficulty levels. It's easy enough to generate a puzzle