Move to the square indicated below the board without moving to a square the queen can capture and without capturing the queen. Once accomplished a new square will be indicated. Repeat until all possible squares are done.
Well, it's the one thing the directions didn't actually say: The goal of the game. I'd be shocked if anyone went to that site and could figure out what to do.
You need to have /some/ experience playing chess to realize and understand chess notation.
And no, vague and indirect "move to every square in order" located separately from the chess notation is not good information. Also, no, tiny nomenclature for ants on the board is not good information.
Have to raise my hand then to shock you.. what else should the coordinate that is also indicated on the axes mean?
> to every square in order, right to left, top to bottom
Added to that immediately.
shrug But yeah as the title says, one realizes quickly that knight moves pretty strange so got bored after 5 targets and did something more exciting: wrote a Python script that prints me the moves from and to any coordinate (:
Have to raise my hand then to shock you.. what else should the coordinate that is also indicated on the axes mean?
Yeah, but it's not clear that the instructions text is talking about that symbol, *because it doesn't say so* explicitly.
Sometimes a small level of information redundancy is good for communicating with humans, instead of forcing them to make the correct inferences in place.
Maybe we were pushing the programmer a little too hard for changes if they felt compelled to continue working on their project while showering. (Remember folks: using a computer, or any other electric appliance, in the shower is a bad idea!)
no, you just have to use your brain implant's wireless connection to make changes. what kind of 21st century lame-os are you that have to worry about electric connections to the computer?
ohmuhgawd, that's gotta be the darkest thing i read all day and caused me to literally lol (so that device would let me type it) so hard i spilled a bit of my old fashioned.
No, they say to move in every place, while you're expected to to move to a specific place in every step. f8 is the first for me, but I did not understand that was supposed to be the target, since it seems arbitrary.
I thought it meant "goto the bottom left corner" or "goto the top left corner then goto the bottom left corner." or "mark all legal tiles visited".
There's no hint in the help that you're suppose to goto the tile coordinate specified by the little box in the bottom left corner. I'm not even technically sure that's what the "f8" at the beginning is for since the help doesn't mention it.
Like move the Knight to every square on the board, in a certain order, but skipping some. I didn't notice the "f8" at the bottom until I read the comments.
They wouldn't have to write any instruction nor add letters and numbers around the board (they are missing) if they marked the goal square. Even after I read your instructions I equivocated where f8 is. I actually moved to f1, then realized that's a long time since I looked at a chess diagram.
A demonstration of how a little detail can ruin a project.
Honestly I read this the first time and thought you were making a suggestion as to how the game should be changed. I love the idea but the design and explanation is just awful.
I think the text is useful for describing the ultimate goal, but agree that visual suggestions would make it easier to figure out what the problem is about.
For example, I read this as a variation of the knight's tour but was confused as to why they didn't highlight the visited squares. (Answer: it isn't a knight's tour since each square will be visited more than once.)
Another example, the description itself didn't quite make sense since it mentioned a sequence but didn't really say that certain squares must be skipped. (In retrospect, the answer is obvious. The queen makes certain squares invalid destinations, along with being invalid intermediate steps to that destination. But it won't be obvious to some people upon initially reading the instructions.)
Finally, the purpose of the square shown in the completion gauge isn't explained at all. Since it is not explained, I did not link it to the description of the goal.
> I think the text is useful for describing the ultimate goal
No, text is not needed if the next target block is marked - after the first three acquisitions of the first three target blocks, the game is very clear.
Thank you! Once I saw this comment, very satisfying puzzle. At first I was fumbling my way through randomly, but around halfway I started to visualize the board as two "sets" of connected paths and grokked how to switch between them using the lower-right quadrant.
> Thank you! Once I saw this comment, very satisfying puzzle. At first I was fumbling my way through randomly, but around halfway I started to visualize the board as two "sets" of connected paths and grokked how to switch between them using the lower-right quadrant.
Exactly this - I used the upper right quadrant to switch lanes, but the idea is the same: if you cannot reach the target in the current lane, switch lanes and try again.
here's a script that will highlight previously visited squares as red. as a nice bonus it replaces the instructions with more accurate ones
// Get all square elements
squareElements = [...document.querySelectorAll("[data-testid='white-square']"), ...document.querySelectorAll("[data-testid='black-square']")];
// create array of elements that have been landed on
// these need to be set to red every time because the board resets every move
let modifiedElements = [];
observer = new MutationObserver(function (mutations) {
mutations.forEach(function (mutation) {
if (mutation.addedNodes.length > 0) {
mutation.addedNodes.forEach(function(addedNode) {
key = addedNode.getAttribute('data-testid').split('-')[1];
if (!modifiedElements.includes(key)) {
modifiedElements.push(key);
}
for (let i = 0; i < modifiedElements.length; i++) {
el = squareElements.find(e => {
return e.getAttribute('data-squareid') === modifiedElements[i]
})
el.style.backgroundColor = 'red';
}
});
}
});
});
// observe all square elements
for (let i = 0; i < squareElements.length; i++) {
observer.observe(squareElements[i], { childList: true, subtree: true });
}
// replace instructions with more accurate instructions
instructions = document.querySelector('section p')
instructions.innerHTML = 'Move to the square indicated below the board without moving to a square the queen can capture and without capturing the queen. Once accomplished a new square will be indicated. Repeat until all possible squares are done.';
A short note about how the coordinates work would also be helpful, or just highlight the target square, because not everyone knows chess notation by heart. I tried two different interpretations (both wrong) before finally resolving to google for it.
I am going to agree, and hopefully clarify the point with a slightly different example. While I know how the notation works, I cannot figure out where a particular square is at a glance. This meant a lot of time squinting at the tiny, low contrast labels at the edges of the board. It made the problem a lot harder to solve since my concentration was constantly being disrupted by figuring out where the next destination is, rather than focusing upon the pattern of the knight's moves.
I'm not seeing the letters. I see the numbers and vaguely knew enough about chess to know which way the numbers go. Honestly, I really only know about the board location designations because of the puzzle under the word scramble in the paper that asked you to accomplish something on the example chess board. The answers to the previous challenge were written (upside down to prevent accidental spoilers) in the standard(?) chess notation.
I did not see those markings at all - nor did I see the label indicating the square to jump to, until quickthrower2's explanation cued me to look for it!
(I see now that the target-square notation is much more prominent if you stretch the window horizontally, but I habitually use portrait-mode windows, where it's very small.)
Kind of makes you appreciate the amount of work most games put into UI design. This game mechanic is very simple and it still needed documentation... And the documentation wasn't enough! Immensely complex games these days are so good at providing hints and player feedback that many often don't need their tutorial levels.
Sure. It's a different facet of the same problem. There's a damn good reason that professional software development organizations hire designers and technical writers, and while many developers like to think so, it's not merely to save them time. Developers often suck at making docs for other developers; reasoning about communicating to people one step removed from that gets even dicier. As a developer before I learned good design principles, I often fell into the trap of assuming my being able to assemble something in code gave me sufficient understanding of why it was designed that way. Ah, the hubris of inexperience.
Perhaps it's me but had absolutely no trouble interpreting the 'help' meassage. Before I did though, for at least some time, was trying to capture the queen :)
Man, I was losing it on mobile since a) I didn't get that it tells you the next field below the board, then b) the labels in the squares are too low contrast to be visible on my phone, and c) 9 out of 10 times the browser would start scrolling instead of starting to drag the knight.
The fact that it doesn't highlight where you've moved already makes it no fun.
Edit: the directions weren't super clear. I see that you're actually supposed to go to every square in a specific order (first G8, then F8, E8, etc), not just visit them all in any order. That means you have to do a bunch of laborious trips around the queen to go to certain squares since you won't have enough room to maneuver directly there.
That's how I took it as well. Everyone talks about highlighting stuff but you don't get highlights in real games. I got more comfortable with knight manouvers and chess notation thanks to this puzzle.
It should definitely have some visual tutorial for people to understand how it works though.
It depends upon what you are trying to visualize. If you are trying to visualize the pattern of the knight's moves, e.g. how to reach a specific square using a sequence of moves, then highlighting the target would be more valuable. The displacement matters, not the absolute positions. The absolute positions are more of a hindrance since it makes it more difficult to generalize the sequence of moves.
yes, i have an algebraic mind, and I find it easy to visual where the squares are, and if you say "N-KP4", I'm Johnny-on-the-spot! now, what's this a-b-c stuff?
Still doesn't make it sense from a UX perspective. You can make it an option to highlight the square or just show coordinates and cater for both crowds.
I mapped out the structure of the board as a graph of which squares you can get to from which other squares. It's surprisingly stringy without all the squares forbidden by the queen placement.
Hah, you beat me to it! I drew this very same board by hand, after noticing that many positions were dead ends, and that the options for moving around the top-left were quite limited.
Thanks for generating this! I struggled quite a bit getting to a few squares, and the graph shows they were indeed far apart from each other and that I wasn't missing something obvious.
This is a good advertisement for the approach I came up with eventually: if you don't see a trivial way to the next square, find a sequence that will lead to it that starts in the lower right quadrant, then go to that quadrant and get to that square. (The lower right quadrant is the center ring in this diagram.)
I'm used to a version with pawns that involves less backtracking, so it took me a little while to stop trying to be "smarter" and just be okay with continually returning to home base.
It's really cool (quite a bit harder) but on the phone it's frustrating that a fat finger can result in a diagonal move (e.g. b6 to a7 instead of a8) and instantly lose the progress.
It seems like in this version / webpage, you're allowed to revisit squares however. It'd be nice if it highlighted what squares "Counted", because the words are quite ambiguous. A graphical representation of what is being counted / not counted would be very helpful.
----------------
EDIT: Ah, I got it. The location on the left is the next spot you're supposed to go to. The puzzle is quite easy once I understood the interface.
The interface needs a "Next square: h5" or something. I really didn't get it for the longest time.
I found that to be the middle ground between "you still have to plan" versus the amount of energy I was spending trying keep track of the forbidden squares
This took me 14:02 on the first try. Definitely got faster as time went on but I found myself getting stuck on a few squares for no good reason. Starting from the destination and working toward the source helped.
It has text now? "Move the knight to every square, right to left, top to bottom. Don’t land anywhere the queen can take you, and don’t take the queen."
It might not be obvious, but the specified squares are "all the squares in the order right to left, top to bottom without those the queen can attack" as the text instructs.
I didn't actually realize the goal of the game was to do it all in order! The help text just says "Move the knight to every square, right to left, top to bottom."
The knight move in chess seems a bit strange at first, but it makes sense when you realize that the knight can move to squares that lie on a circle around it.
That is fun! It's interesting, the solution is presented here[1], but I'm pretty sure it's wrong (off by 19) due to not taking into account the possibility for the pawn to move two squares on its first move.
> Note: If you counted the pawn moving forward two squares with its initial move as distinct from its moving two individual squares, then there are 160 paths. Feeling generous, I gave full credit for either approach.
If you drop the sequential restriction, this becomes a pretty neat shortest path problem, essentially the same as LeetCode 847, but the simple dynamic programming approach does not work here (too much memory needed). It can be transformed to TSP, though, which gives an optimal solution (using Concorde) of just 46 moves:
http://directory.iit.bme.hu/~salvi/archive/snippets/knight/k...
For me the instructions are pretty clear: every square "right to left, top to bottom" - except don’t land anywhere the queen can take you, and don’t take the queen. (i.e. somehow move to the upper-right, then one to the left and so forth going through the rows and columns backards and down, like reading right to left down a page.)
I gave up after 4 minutes. It's really tough and I only got partway through the second row. I play OK chess (slightly above average on lichess) but it is a really tough visualization exercise.
for anyone who did it to completion, how long did it take? did you speed up by the end?
Took me a few minutes to understand what exactly I was supposed to do but once I figured it out I reset and did it in 13:15. Pretty neat game. I'm not sure I could do it faster a second time, just because my approach is a bit trial-and-error. Some patterns were surprisingly elusive this way.
I actually think I would enjoy it more if the UI helped a bit more, like by marking the squares that were forbidden because of the queen.
Thanks. Regarding marking forbidden squares, apparently the whole point of the game is to develop visualization skills for chess (under Help, it references a grandmaster who recommends this exercise), so if it marked forbidden squares it would defeat the purpose a bit, I think!
After a couple tries got it done in 16 minutes or so. Probably laughably bad for anyone good at chess but it was a fun and enlightening challenge. About midway through I had a sudden click and figured out the pattern to hit the right squares. I don’t know how to put it into words but I believe there’s a three move combo that helps you move off of one set of squares and onto the other set. And my intuition got a lot better towards the end, even getting the last squares almost by accident. Funny how that happens
That sort of clicked for me too, then I decided to take a break from fumbling through it and draw out the graph.
I ended up visualizing as two sets of loops connected to each other in the bottom-right, top-right and bottom-left quadrants, with some dead ends branching out:
Instead of just giving the next square you're supposed to jump to, how about just highlighting all the squares on the board that you already visited? I think that would make the game both easier to understand and give the player an incentive to complete it (the "gotta catch em all" effect)
Right? Where’s the fun in that? I blame YouTube for explaining the bejeezus out of everything and spoilering everything else. Don’t get me wrong, it has its value. I’ve saved hundreds on refrigerator repairs.
Yes, start with the end square and work your way backwards. It is often only a single path that leads you there for the final steps. Once you develop the path close enough back to where you are then it’s easier to see how you can get onto it. Then just follow it.
Incidentally, this is also a good strategy for planning and breaking down goals in real life: begin with the end goal, then work your way backwards.
I think this is basically the same strategy I stumbled onto. It feels binary in nature, like you're either on circuit or off circuit within the target areas, and there's only that one degree of freedom within the small quadrants. If off circuit it seems like you have to go to one of the larger quadrants to get on the right circuit again and hit the target.
Same here. By the end, I was just reflexively moving back to the bottom right hand quarter, doing my 3 point turn, and then taking the circuit back to the destination.
In case anyone else goes nuts trying to write a program for a knight's tour with the additional queen constraint from this game: you can't get to B7. Obvious if you actually look at the board.
Took me ages. What finally helped me was to work backwards from c8. What squares can get to c8? Which of those squares can I eliminate (e.g. because to get there I'd have to be on a square covered by the queen) and so on.
Took me ~25 minutes which was annoying. As I type this, my brain is worried that the individual keys I type are not knight’s moves away from each other.
Move to the square indicated below the board without moving to a square the queen can capture and without capturing the queen. Once accomplished a new square will be indicated. Repeat until all possible squares are done.