| « home | Browsing all comments (spoilers: on | off) (info: on | off) | next 25 |
 |
<Tom 7> (SPOILER) I thought it was going to be a regular dodgeball match, but it turned out to be quite elegant. |
 |
<Tom 7> (SPOILER) Note to self: do not save hugbot |
 |
<Tom 7> (SPOILER) Added speedrun: 236 moves (old: 314). If I recall, the beginning of this is fairly well-optimized (perhaps even not what jason intended), but it gets pretty sloppy towards the middle and end. |
 |
<Tom 7> I can put it back in triage if you want... but I figured it was meant to just be a regression test. It's almost hard NOT to win! <Adam> You deleted my first level! I tried to make the 2nd part fun <Tom 7> Since this is a regression test for developers, I moved it to the deleted collection and added it to CVS instead. |
 |
<Tom 7> As usual, it's up to the puzzle composer to make good levels! (That might mean making use of what little hidden information is possible.) I'm just lamenting the fact that sometimes making the game more like I "meant it to be" can damage some subversive levels that I do like. <Max> (SPOILER) Well, Tom, the screenshot also gives away "What's Going on Over There?", as does the ability to zoom during gameplay with "[" and "]". So, in a sense, screenshots of levels themselves have the opportunity to be spoilers. I think there should be a decision as to the extent to which a level that relies on hidden information is undesirable. In the case of "WGoOT?", it is quite possible to reason about the setup of the hidden part of the level through trial and error. Similarly, on this level, after realizing that the blue sphere puzzle is impossible, the only option left is to try pushing the button until something happens. (Of course, this is probably cute at best and obnoxious at worst.) Anyway, I do agree that in general there should be as little hidden information in escape as possible... |
 |
<Joshua Bone> (SPOILER) Added solution "Original." |
 |
<bpotetz> (SPOILER) Added solution "Original." <bpotetz> (SPOILER) Aw, nine kilomoves is not THAT much. Well, at least I'll have a copy. I'll try anyway. <Tom 7> (SPOILER) On second thought, that might not work because there's a limit on the size of a solution that's not the smallest (I don't want to fill up the database!). Oh well... <Tom 7> (SPOILER) Brian, you could save max's solution by doing this: Download his to your computer Rename it ("Max's Crazy Solution") Upload your own solution ("Original") Upload max's solution (not as speedrun) |
|
|
<Tom 7> (SPOILER) No insert key? Yikes! Well, you'll be able to use ctrl-i too in the next version, but by then solution playback should be done. All new levels store the original solution, but I don't think that includes this one. They're uploaded as non-speedruns, so they don't get deleted. Generally, I'd like to keep for each level (1) the "intended solution" (2) the fastest known solution (set as speedrun, so it is deleted when a faster one is uploaded) (3+) any substantially different and interesting cooks So, if you're uploading an "intended solution" (for an old level) or cook, don't mark it as a speedrun. (But then describe it in the comment field!) |
|
|
<bpotetz> (SPOILER) Wow, Max - that is some solution. It's pretty different from mine. I'm curious how you went about solving it. My general approach was to choose a set of atomic "moves" that made predictable changes to the board, and then plot out a path to the goal state on paper. I had to use longer & longer atomic moves before I got it to work. I could probably do it a lot faster if I tried again, now that I see your approach. Definitely I suffered from the false mindset where I had to put the grey spheres over the inner panels. I would like to upload my solution, but then yours would be gone. |
|
|
<bpotetz> (SPOILER) I wish I could have seen your original solution. Tom just told me about using insert to see everyone else's solutions. But then I discovered that most of the keyboards I have kicking around don't have insert keys anymore. Go figure. And on top of that, your original solution is gone now since it was only a speed run. Tom - didn't you mention you had all the original solutions stored someplace? It would be neat if the originals were always available for download. I think that is the coolest use of solution managers, since it helps you decide about cooks and rigidity. |
 |
<Tom 7> (SPOILER) I didn't solve this one yet, but jason, if you have a wire free at the end to position the sphere, why not use the wire to just push the button directly? |
 |
<Tom 7> (SPOILER) Oh, that makes sense. ;) <Tom 7> (SPOILER) Added speedrun: 525 moves (old: 999999). Damn, that was a speedrun? |
 |
<Provost Zakh> (SPOILER) Added speedrun: 66 moves (old: 68). I just tried to complete the level. I wasn't reaching for a speed record. |
|
|
<jcreed> Hahaha. |
 |
<Tom 7> (SPOILER) Added speedrun: 24 moves (old: 26). hah! |
|
|
<Tom 7> (SPOILER) Unfortunately (?) the screenshot sorta gives it away... <Max> I realize that this level was annoying enough for some the first time around. Well this is for the rest of you! |
 |
<Max> (SPOILER) Added speedrun: 222 moves (old: 224). Heh heh ;) |
| « home | Browsing all comments (spoilers: on | off) (info: on | off) | next 25 |