Log in

No account? Create an account
21 January 2013 @ 02:40 pm
Too Big to Solve?  
Not my tagline, but a good description for the Mystery Hunt that just happened. One line of dialogue after last year's Hunt that I led with in my wrap-up was a question of when is too soon for a Hunt to end. I said, in this era of a few competitive teams trying to grow to get over the winning hurdle, constructors aiming bigger was a mistake. The Hunt ending after 36 hours (Midnight Saturday) is fine if that makes the solving experience stretch over the weekend for everyone else. I won't comment generally on this year's effort but it seems a great example to point back to of too much ambition by too many people towards the further militarization of the size of Hunt so that by 2025 the team "The whole of new USA" can go after the coin against "USSReunited" for at least a month. The sense of "puzzle" versus "grindy work" is also a discussion I have every year and I don't choose to repeat myself. I've felt since 2008 that the Mystery Hunt is far from an event I'd regularly attend in person although I'm glad to have finally been onsite to play with Team Luck with whom I've been a "free agent" now for three years.

I had a good solving year as things go relatively, but it was mostly demoralizing personally. I soloed Palmer's Portals, for example, but spent many hours after basically solving 8/10ths with a need to tweak a very small and underconstrained set of things to get from that hard work state to a finished state. At some stage I told the team "I'm going to solve Portals and the Feynman meta and then go sleep" and I met this goal but in many times the expected time when I gave the statement. I led the solve of both Danny Ocean (with zebraboy stating the most necessary last bit to get my work over the cliff) and Richard Feynman (with Jasters). I obviously co-solved lots of the logic puzzles and other puzzles, and gave various finishing help to a range of things too. I think I did this best for "Kid Crossword" once when he had spent a lot of timing mastering the hard steps of a crossword/scrabble puzzle -- and could quite impressively fast rewrite out the set of steps I wanted him to do about the puzzle -- and the follow-up steps were not obvious but I led the killing of the beast. This was too often the feel for these puzzles, and my assassination rate was far lower than I wanted. My Sunday was spent earning 3 puzzle answers by actually going to an event, and then falsely believing the power to buy some answers would let me finish solving the Indiana Jones mini-metas -- where I had already mostly soloed Adventure 2's snakes with 5/8 answers, but then killed myself dead on #1/Ouroboros for the rest of the day for so long solving, as many solvers will say in hindsight, the puzzle that was meant to be in one of a dozen ways and not the puzzle it was. Let me state here as I did for hours with my team, the phrase "I'm not cut out for this" is horrible flavor. It implies both cut this out and, in a different way, also don't cut this out. This makes you want to cut it out, which takes a lot of time, but also to not invest too much time in cutting it out, so as to save the wasted time of doing a task you are being told not to do. Other wordings are far safer, and implied negatives within positives is one of the five worst flavor failure modes in my opinion. Puzzle editing and flavor text is an art and is certainly the biggest variable from year to year and constructing team to constructing team.

So yeah, Mystery Hunt happened. And there were the usual share of overwhelmingly incredible Aha moments. Endgame seemed very fun and I wish all teams could do just that for the weekend or at least a lot more things like that. More of that, and more sleep, would have both been some good choices this year. If only the puzzles solved on schedule.

ETA: And as I added far below around comment #300, as a solver who was both frustrated yet had fun in this Hunt, I do want to thank everyone on Sages for the incredible effort they put in. Making a Mystery Hunt is a gift for all solvers whether it matches expectations or not, and as a mostly thankless job I do want the constructors and editors and software engineers and graphic designers and cooks and phone center workers and everyone else to know I appreciated all you did over the last weekend to give us several days together for puzzling.

Further, as I was asked to write a larger piece elsewhere that has given me personally a lot more attention as the face of the criticism, and as I use the phrase "My team" a lot in general as solving forms this kind of bond, I want to be very clear: since Bombers broke up after 2009 I have been a free agent. I have solved recently with Team Luck but am not a core part of their leadership and these opinions I state are my own. I intend to form my own team next year to go after the coin again, and if you have a problem with what I have said anywhere on the internets, please hate me for it. I believe in my posts I have been offering constructive criticism, but even what I have said is without all the facts of what went on inside Sages so I could easily be speaking from ignorance a lot of the time.

EFTA: Thanks to tablesaw for pointing out this chronologic feature of posts. If you want to see all the additions to this post in time sorted order, go here http://motris.livejournal.com/181790.html?view=flat. We're on page 14 at the moment.
nameelectricshadow4 on January 25th, 2013 09:35 pm (UTC)
For Mergers, the reason Codex (or at least the people I was working with) never got anywhere was because there were too many choices and too few places for confirmation in the middle of the puzzle. We had a few of the ones in the solution on our spreadsheet, but also a bunch of merges that weren't the ones used.

The two puzzles from the past it feels similar to were http://web.mit.edu/puzzle/www/12/phantom_of_the_operator/functions/ and http://web.mit.edu/puzzle/www/10/puzzles/1752/string_maze/ . Both of which have a similar branching factor, but both have more confirmation steps in the middle.

Having something like "each level of the tree has a different color for a different type of merger" or even "here are the 5 types of mergers we use, and we use each of them 3 times" would have made it easier to ensure that the solver is on the right track.

Also, the Aardvark+King->Arthur and Arthur+Cheetah->Chester associations seem a bit rough. Perfectly fair if they're clued or if there's some reason to believe those go together, but it doesn't jump out the way it should if you're picking 2 from a list of 10. Similarly, at the top, it's quite a leap to get to "copper + tin", and there's no real confirmation before that point.

Also, as a general note, for a lot of puzzles, there's a bit of "if we didn't have 50 other puzzles open we might have looked harder and broken through". The overwhelming mass of "too many puzzle-hours" puzzles means that even puzzles which would have been fine on their own might have been too complicated here.
Alisonlandofnowhere on January 25th, 2013 09:45 pm (UTC)

I did get the impression your final paragraph was what was happening in general with the puzzles I haven't heard much about.

And I did push for more intermediate-stage confirmation on Mergers (the original version had no tree), but we ended deciding that this version was good enough, possibly because we were running out of time.
Cody B.: contemplationcodeman38 on January 26th, 2013 03:46 am (UTC)
Listing the types of mergers would indeed have been useful on Mergers--because otherwise, there are just too many ways to get unanticipated mergers out of some of the term pairs.

Some of the Codexians might have heard me shouting out that "Mac OS X" and "King" should totally be given a missing-link merger to get "Lion"...which, of course, turned out to not even be one of the merger types that was used.