That was fun until I got to the point where no progress could be made and I had to undo a whole bunch of times to get to a workable configuration. Perhaps add a notification of some kind that I've gotten myself in that situation, rather than letting me kill a bunch of time solving an unsolvable puzzle. Still, very enjoyable!
maybe a percentage chance of solving puzzle tracker that updates a bit randomly slow so you don't necessarily know right away that you made a mistake, although it would have to be a bit weird, for example when you start you are not at 100% of solving puzzle.
lmao same. actually a really cool fun/concept it's definitely wordle popularity caliber, but once i got to the last 3 words and ended up in this scenario and the hint button said that i was like -_- owned.
not sure what the right game experience would be for that. a notif that says "You can still solve more words but you'll never solve them all!" doesn't quite work here, because it's sort of saying "there's only one _right_ way to win, but good luck figuring out the right order". Still, it would be better than me finding that out at the very end.
it would probably be pretty important to design levels so that the unwinnable states can't happen early in the game, but it's getting a little abstract to think about at this point. sort of brings me back to that unblock it game from the old ipod touch days.
Fun! On first thought, I'd prefer knowing when I'm in an unwinnable state instead of having to keep clicking the hint button.
Also, the site worked for me in Chrome but doesn't work in Firefox (145.0.2). Do `window.cookieManager = ...` (or even `var cookieManager = ...`) instead of `const cookieManager = ...`. This goes for all variables in the global lexical scope you intend to share across source files.
Fantastic work, very fun !
I actually only ran into the dead end scenario right until the last few words so not a frustrating first experience. But reading other comments maybe a setting to prevent the player to take a route that ends up unsolvable would be great. Kinda like the "Normal" and "Expert" Modes in worldle
Very nice. Easy to accidentally cheat, however. Shift a word to an invalid position, but right click instead of letting the mouse up event fire. Then shift the word back to the original position: win!
Was a bit disappointed when I almost "solved" it but couldn't solve the last 2 words, finally clicked the hint and it told me to undo 12 times.. would have preferred if there was a warning earlier.
Seems like the same idea as treating your LLM as a compiler.
When you write code in Rust and user your compiler to produce an x86 binary, you don't maintain the binary. If you want to make a change, you toss away the old binary, change your Rust code, and recompile.
This is really, really cool. I think telling me how many moves I have to go back in the hint was absolutely a must-do, and shouldn't cost two hints... Second-guessing every single move I made would be insane, but knowing I had to go back seven, and pick something different than the last thing I restored, that worked fine.
It's easy to assume making a word disappear is always the right choice, but you forget it changes the word it leaves behind as well. Very clever.
It does have the same quirk Wordle had that bugged me: Treating browser storage as useful in our multidevice world.
> It's easy to assume making a word disappear is always the right choice, but you forget it changes the word it leaves behind as well. Very clever.
It's also easy to make the opposite assumption, that the goal is to change the other word. I initially felt weird about changing from a letter at position 3 to the same letter at position 1, but eventually realised that the goal is just to slide the word around, not necessarily to make a new word.
not sure what the right game experience would be for that. a notif that says "You can still solve more words but you'll never solve them all!" doesn't quite work here, because it's sort of saying "there's only one _right_ way to win, but good luck figuring out the right order". Still, it would be better than me finding that out at the very end.
it would probably be pretty important to design levels so that the unwinnable states can't happen early in the game, but it's getting a little abstract to think about at this point. sort of brings me back to that unblock it game from the old ipod touch days.
I didn't like that it's possible to leave the underlying word unchanged by dragging the word containing a letter twice to the second occurence.
Also, the site worked for me in Chrome but doesn't work in Firefox (145.0.2). Do `window.cookieManager = ...` (or even `var cookieManager = ...`) instead of `const cookieManager = ...`. This goes for all variables in the global lexical scope you intend to share across source files.
The only thing that felt a bit weird was being able to change the word to the same word, if the slid word had the same letter twice.
When you write code in Rust and user your compiler to produce an x86 binary, you don't maintain the binary. If you want to make a change, you toss away the old binary, change your Rust code, and recompile.
Haven't yet really tried the full level but really liked the tutorial, and the quality of the build
update - wow the actual level is better ;)
It's easy to assume making a word disappear is always the right choice, but you forget it changes the word it leaves behind as well. Very clever.
It does have the same quirk Wordle had that bugged me: Treating browser storage as useful in our multidevice world.
It's also easy to make the opposite assumption, that the goal is to change the other word. I initially felt weird about changing from a letter at position 3 to the same letter at position 1, but eventually realised that the goal is just to slide the word around, not necessarily to make a new word.