Classic Slitherlink (Full Version)

All Forums >> [PUZZLE FANS] >> Puzzle Support


kovukun -> Classic Slitherlink (12/1/2012 8:29:40 AM)

This is my first hard slitherlink I've ever tried, and I'm kinda proud that I made it this far. I had help here and there with the "show errors" option, but I never used it to help make a guess. When it showed a mistake, I undid the wrong line, and use logic to find out why.

But it sucks that I've gotten THIS far, and am just stuck. I have a hunch that the next step lies somewhere in the 2 or 3 in the middle there...


As for the help... I don't want someone just saying "Oh, put a line here" and don't explain why. ^^; I'm here to find the next logical step, not to cheat and have someone fill in the answer. XD

Thank you for your help!

opnismry -> RE: Classic Slitherlink (12/1/2012 8:26:46 PM)

Here's my logic process. I look around for "unstable" situations and say, 'well if there was a link here, then does anything bad happen?'. Similar is looking at when there isn't a link somewhere. Or consider all the possible combinations (when there are few such combos) and see if there's any similarities.

I noticed this...

Edit: there's also an X'd path that is in common with those two.


kovukun -> RE: Classic Slitherlink (12/2/2012 7:06:26 PM)

Can you please explain the logic behind the second diagram, in regards to the red line in my picture?


It turns out when I tried it out, it immediately came up wrong. That red line shouldn't be there, and I'm curious as to why you thought it should. Turns out your first diagram was correct. The one you thought was wrong. :/ That red line that you say should be there, shouldn't. (As it turns out, with a bit more logic, I was able to figure out the correct position of the lines, by ruling out the other positions, like you said. The correct layout is in blue. I'm still just confused as to why you think that red line should have been there. ^^; )

Anyways, thanks for your help, the two green lines you did offer did in fact help!

opnismry -> RE: Classic Slitherlink (12/3/2012 4:55:45 AM)

oh i put a red line to denote that a lane can't go there.

Boodle -> RE: Classic Slitherlink (12/6/2012 10:44:53 PM)

Hi kovukun,

The line in red cannot exist, as it would mean the number 3 next to it is unable to have 3 sides.
Therefore the line in green is the only correct option.

Then one can see that the pink line must not exist, for if it did the yellow line would have to exist aswell and it has nowhere to go on the left hand side.


Ichneumon -> RE: Classic Slitherlink (1/14/2013 7:14:12 AM)

A technique that be very powerful and extremely effective when you're otherwise stuck is what I call the "inside/outside" method. It's based on an algorithm in geometry which determines if a point is inside or outside of a (possibly very complex and convoluted) polygon, by counting whether a line drawn from the point to a point known to be outside the polygon crosses an even or odd number of edges (if even, it's outside the polygon, if odd, it's inside the polygon). This works because if you're inside and cross one line, you're now outside, and vice versa.

Since the final solution in Slitherlink is a closed loop, it too is a polygon, and any square on the grid is either inside or outside the loop. This fact can be used to deduce whether two adjacent squares must (or must not) have a line between them in the final solution.

Consider your partially solved puzzle as I've marked it up here. Look at the column near the middle which has colored dots on it. The red dot at the very top is clearly in a cell that is outside the loop, as there is no line above it. Moving down, since we crossed a line, the cell below it (which has the "3" in it) has to be inside the loop, so I've marked it with a blue dot. Moving down again, we cross another line, so the cell below that has to be outside the loop, and I've marked it with a red dot (it's also pretty obviously outside the loop since you've completed the area up and to the left of it which leads to the edge of the puzzle). The cell below *that* one we reach by crossing a "definitely no line here" boundary, so it too must also be outside the loop like the one we just came from (so a red dot again). And so on downward, flipping between inside/outside each time we cross a known line, and remaining with our current inside/outside status each time we cross a "no line here" boundary. When we reach the "maybe a line?" area surrounded by the turquoise box, we stop for a moment as we don't yet know if that's going to end up a line or a "no line".

Now we move to the bottom and repeat the process moving upwards. The lowest cell is clearly inside the loop since there's a line on the bottom of the puzzle dividing it from the "outside" area of the puzzle -- blue dot. As before, we move up the puzzle, marking each cell as inside (blue) or outside (red) based on whether we crossed a line to get there. Again we run into the "don't know" turquoise box area.

Note that we now know that the cell directly above the turquoise rectangle is *outside* the loop (since we red-dotted it), while the cell directly below the turquoise rectangle is *inside* the loop (since we blue-dotted it). Two immediately adjacent areas that are of opposite "sideness" (one outside, one inside) MUST be separated by a line lest they "run into" each other and create a contradiction. Thus we KNOW for a fact that a line belongs in the area marked by the turquoise rectangle. QED.

In this case it happened that we could do this exercise in a straight-line clear across the puzzle, but often things aren't that neat. But we can "go around corners" if necessary. If we didn't have the lower half of that dotted column complete enough, we could have done something else. Look at the cells marked with orange dots a little to the left. The lowermost one was clearly an "outside the loop" cell. From there I "walked" up the "also outside" region (not always in a straight line, but always crossing a "no line here" X'ed divider so we know we're still in the "outside" region. Look at the green dot just to the right of the uppermost orange dot -- we know it must be an "inside" cell since there's a known line between it and our "outside orange" dot. Lines separate insides from outsides.

Also note the other green dot on the "3" cell -- we know it must be an "inside" cell since we had to cross a line to it from the red (outside) dot just to the right of it (which we knew was outside due to coming down from the top of the puzzle before). Now consider the "is it a line?" area between the two green dots. It MUST NOT be a line, otherwise it would divide a known inside cell from a known inside cell, which is a contradiction. Adjacent inside cells, and also adjacent outside cells, have no line between them, they are part of the same region. So we can safely "x" that location and proceed solving as usual.


Ichneumon -> RE: Classic Slitherlink (1/14/2013 7:30:53 AM)

Sometimes a simpler way to invoke the same technique I just described is to realize that a necessary consequence of the "crossing rule" is that *every* column and *every* row in a Slitherlink puzzle *must* have an *even* number of lines in the completed solution (0, 2, 4, 6, etc.).

In the partial solution here, the column with all the red and blue dots has seven known lines (e.g. the lines you cross as you move all the way down the column from top to bottom), and one "unknown" line (one place where we don't yet know if a line is there or not), the area marked with the turquoise rectangle.

Since a column *must* have an even number of lines, it's easy to see that the unknown area *must* have a line in it so that our column's line count finishes out to be an even number (8) instead of the uneven number (7) it would be if we did not draw a line there.

Other times this can be used to determine that, say, two remaining unknown "lines?" in a row/column must be completed with only a single line (as opposed to possibly 0 or 2 lines), something that can also provide clues to aid in solving the puzzle.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.5.5 Unicode