| « home | Browsing all comments (spoilers: on | off) (info: on | off) | next 25 |
 |
<Tom 7> Hilarious. I can hear the MIDI guitar shredding. <Tom 7> (SPOILER) Added speedrun: 243 moves (old: 367). speedrun ;) <Swivel Maste> 'e1m1' uploaded by Swivel Maste: More of a joke. I just had to. |
 |
<Beaman> this is my favorite one yet nice job |
 |
<Alois> (SPOILER) Added speedrun: 24 moves (old: 26). <Gil Anthony> '107 pm 5/18/07' uploaded by Gil Anthony. |
 |
<Gil Anthony> Isn't that something? no pun |
 |
<mm> (SPOILER) Hi Tom - I did download the solutions - and so I do have 3 "bookmarks": my solution, the speedrun and the original. In the "directories-list" it picks the speedrun instead of mine, so it indicates (green): Solved! (613 moves) |
 |
<Tom 7> (admin) Automatically moved to minor leagues. (Difficulty: 0.8 Style: 2.1) |
|
|
<Tom 7> (SPOILER) (I marked your comment as a spoiler.) A cook just means an unintended solution, generally one that circumvents a puzzle. In this case I definitely think it makes the first puzzle easier, even if it takes a bit longer, since the time is spent just walking back and forth. My own opinion is that unintended solutions are usually bad. Even though I think my favorite part of playing this game (and others) is outsmarting level creators by finding cooks, I usually rate a level in which I can't find cooks more highly... it's harder to create such levels and there's something satisfying about such compositions. But it's up to you... sometimes it's hard to fix a level, and sometimes it's better to offer an "advanced" version where you must employ the cook, and sometimes the cook is too trivial to bother fixing. Sometimes someone else might do it for you. ;) In chess puzzle competitions (where the terminology 'cook' comes from) they don't even allow puzzles that have more than one solution! <Rubric> (SPOILER) Oh I see. I was assuming that a cook, by definition, meant the solution time was faster. If it just means that you solved it in an unexpected way, then you're right. I guess I should have put more holes and/or rough around the lasers to prevent alternate uses for the gray blocks. Or is that desirable? What is the prevailing opinion as far as fixing cookable levels? I suppose it varies from level to level. In this case, the cook seems undesireable because it is (a) easier to figure out than the intended solution (except for me, apparently), and (b) it takes more moves. |
 |
<wowei> (SPOILER) Added speedrun: 249 moves (old: 255). |
|
|
<Eric119> (SPOILER) Added speedrun: 613 moves (old: 617). |
 |
<wowei> (SPOILER) Added speedrun: 180 moves (old: 194). |
|
|
<Eric119> (SPOILER) Added speedrun: 617 moves (old: 637). <Tom 7> (SPOILER) Yeah, I only meant that it seems like an unintentional way to circumvent the puzzle there (i.e., a cook), which is not necessarily the same as a speedrunning technique. =) <Rubric> (SPOILER) Added speedrun: 637 moves (old: 652). Here is the 637 time. I guess I couldn't upload it because I hadn't downloaded the level. <Rubric> (SPOILER) Actually, Tom, I think it's faster without using the 0/1 button more than twice. I watched mm's solution, and saw that the way I was losing so much time was on the right side of the board, where I was doing it a silly way. Once I used mm's method on the right, and my method on the left side, I got the time down to 637 moves. I would upload the solution, but ctrl-u is telling me that I can't upload a "non-validating solution" or some such. I'm having a great time with this game, by the way. <Tom 7> (SPOILER) True, though there's already a level that uses that as its main "trick." <mm> (SPOILER) That could become quite a nice mod! <Tom 7> Also, I agree, a nice first level! <Tom 7> (SPOILER) Cook: My solution was a lot like mm's, the main cook being using a grey block to allow the 1/0 button to be pushed as many times as we like. <mm> (SPOILER) Added speedrun: 652 moves (old: 686). This is fun to run! Nice first level! <mm> (SPOILER) Added speedrun: 686 moves (old: 707). <mm> (SPOILER) Added speedrun: 707 moves (old: 765). |
| « home | Browsing all comments (spoilers: on | off) (info: on | off) | next 25 |