2020 MIT Mystery Hunt, Part 3: Points of Contention

(This is a recap/review of the 2020 MIT Mystery Hunt, which happened this last month. Puzzles and solutions can currently be found here. This recap may contain spoilers.)

I haven’t managed to find time to blog recently, which is unfortunate because when I envisioned this third post, the main purpose was to encourage discussion, and I’m not sure people are going to be that excited to opine a month after Hunt. But better late than never, I hope.

[Since I also haven’t had time to post about other puzzlehunts, let me mention that I thought My Little Pony: Puzzles Are Magic was quite good! It had too much MLP-specific content for my tastes (you’d think that’s to be expected, but the FAQ was misleading in that respect), but the puzzles were fun, and the story took some twists and turns in a “GPH Lite” sort of way. Also be on the lookout for Cryptex Hunt 2020, which starts on Leap Day (much like the Revs season) and is apparently a novel.]

Before I totally run out of mental fuel to talk about this year’s Mystery Hunt (and the state of Hunt moving forward), I want to ask some questions that I think I have subjective answers. I have my own answers to them, which I’ll provide in some cases, and some of you may have answered them in your own way in the post-Hunt feedback form, but I think it’s often useful for solving teams to know what other solving teams think, and for teams to know what teams think about what teams think, etc. (Though everybody should keep in mind that the vast majority of Mystery Hunt teams are fairly casual and may not be reading a sparsely updated puzzlehunt blog. Hunt is for them too, so don’t assume any consensus reached here reflects the community ethos!)

I’ll number questions below so that it’s easier to refer to them in the comments.

Q1: Are there too many puzzles?

I loved most of the puzzles and metapuzzles I encountered in Hunt this year and thought the quality and polish was really solid on all of them… but there sure were a lot of them. It felt like a big jump in quantity, although comparing the number of puzzles to 2019, my back of the envelope calculation from a few weeks ago showed there wasn’t actually that much of a difference. Of course, I didn’t solve 2019, so maybe people felt the spike then, and I didn’t notice it from constructing HQ. I did think the average puzzle this year was harder/more involved than the average 2019 puzzle, but again, I don’t have the solver perspective. More teams finished “on time” this year than in 2019 by infinity percent, though teams in 2019 seemed more logjammed by metas, and I feel like in 2020 our team was never stuck for long on metapuzzles.

The traditional discussion in this realm is “when should the coin be found?” People have varying opinions about this: an earlier first finish means more teams will get to see the entire Hunt, but some will have a truncated experience, and a later finish means fewer teams will get a satisfying conclusion. But even if you agreed on a target, anyone who’s constructed Hunt can tell you this is something that isn’t purely a function of number of puzzles, and also something you’ll never be able to completely control. Actual Hunt teams are impossible to accurately replicate/simulate in testing, and I’ve helped write Hunts were the coin was found much earlier than intended and much later.

In any case, you can probably guess from my Part 1 post that I would have liked Hunt to be a round or two shorter so that my team could finish. I probably would have endorsed aiming for fewer puzzles in 2019 too, except that the structure we chose needed a lot of puzzles to support it… having metas split between rounds isn’t interesting unless you have a lot of connectivity between the rounds. Structural innovations are something valuable that set Mystery Hunt apart from other puzzlehunts for me, and sometimes those innovations require a large size. But at the same time, a long stretch of Hunts with many many puzzles is inevitably going to lead to an increase in average team size. And that’s something that (a) may not be sustainable on a campus of fixed size, and (b) makes it hard for casual student teams to get involved, and given that Hunt lives off of MIT resources, they’re the teams we owe the most to. More on that in a bit.

Q2: Should every team see every puzzle?

When we designed the “Santa curve” for 2019, one of our goals was that every team, regardless of progress, should have every puzzle unlocked at least an hour or two before close of HQ. We made pretty steady progress this year, and as a result I didn’t realize until afterward that (as far as I’m aware) Left Out didn’t time-release rounds*. This meant a team that didn’t solve a lot of puzzles early probably never saw the Outer Lands and missed a large chunk of story and innovation.

*[Edited to correct myself: As Wei-Hwa points out in the comments, my “as far as I was aware” statement was incorrect, and rounds were in fact time released. I think the main reason I gathered they weren’t is that three of the four largest rounds were batch-opened at once right around when the coin was found, so the isolated bits of information I heard from teams well behind the curve was that they got an impression of “Okay, folks, competitition’s over, now the rest of the Hunt is open.” I would still argue that given the size of these rounds, opening them at 1pm on Sunday makes it impossible for those teams to see all of the content in them, and opening them all at once diminishes the discovery effect, so the Q2 debate is still relevant to this Hunt. But I apologize for my false assumption above.]

There’s certainly a debate to be had about this, and the big unknown variable is trying to predict what will make casual teams happiest: focusing on early meaningful goals, or getting to solve whatever they want. There’s an easy argument that if you give teams all the puzzles eventually, they can make this decision for themselves. But there’s a counterargument that teams that are only solving a few puzzles may be overwhelmed/dispirited to have a pool of 100+ puzzles to wade through. Some constructors would probably like to encourage those teams to solve a meta (maybe their first ever!) and keep them in the shallow end so they can do that. On the other hand, some constructors probably want as many teams as possible to see what they’ve written, especially if they wrote the last puzzle released in the last round…

My own opinion on this probably varies based on the Hunt structure. When a new round or concept is revealed on the Hunt website, I get an endorphin rush, and I want every team to get that rush. So for this year, my preference would have been to have the round openings time-released to teams. (Maybe this did happen, but I gather it either didn’t, or it happened very late.) Within each round, you had to solve puzzles to unlock other puzzles, which means even as a strong team, some puzzles were never opened to us. I don’t object to that. I’d like teams to be able to see what the whole structure looks like by the end of the weekend, but I’m not fixed on everybody seeing every single puzzle. We did that in 2019, but due to the linear release structure, getting everybody every round wasn’t that different from getting everybody every puzzle.

Q3: Where do you put the story?

This is a nitpick, but 2016 and 2020 were the two Hunts I can remember that conveyed major story elements through videos isolated on the website. I take a lot of interest in the Hunt theme and story, but in both of these years, I never felt particularly driven toward the video page. As a result, these were probably the years that I felt least engaged in the story. This is, of course, my own fault, since I could have watched the videos if I wanted to (and the 2020 videos in particular, I discovered later, were adorable). But my interactions with the website and puzzles never really encouraged me to do that.

I also get the sense that a lot of story/theme/aura was conveyed to the people who went to squish pennies after each meta solve. I didn’t go to any of these, and the people who did didn’t tell us much else than that they got pennies. On a large team, a lot of members won’t end up going on any of those trips, especially since some team members like to volunteer for multiple pick-up missions. There was a nice skit when we opened the Outer Lands, and I appreciated that that skit happened in our HQ so that as many people could see it as possible. But it was something we watched rather than something we did, and the plot didn’t have a whole lot of urgency (especially once we established that the park was no longer closing).

I don’t want to send the message that I didn’t like the story or theme this year… I thought the kickoff (even after the wedding) was creative and well-written, and the theme park “lands” structure was intuitive enough that you didn’t need to follow the story to understand how the puzzles fit together. If you don’t care about story, the website and puzzle design made it easy to ignore the story and solve the Hunt. But as someone who does care, it was too easy for me to ignore it too. To paraphrase an argument I remember making to someone on another team I constructed with, Mystery Hunt is a set of puzzles with a story layered onto it, not a story with some puzzles, and so the story will (and should) always take a back seat. But I think it’s worth discussing narrative strategies to immerse solvers in that story as much as possible (without obscuring the puzzles).

Q4: Is phoneless answer confirmation the way of the future?

I dropped a question about this at the end of my Part 1 entry, and a lot of people already commented (as they did on Reddit). I think the question is fairly well-understood, so I won’t restate the problem, but it’s certainly an open question, so I’m including it again here.

I will say this: Virtually all of the people/teams I’ve heard who didn’t like losing the phones are Hunt veterans… I was concerned with the effect on newer teams, and they don’t seem to have had a problem, though by definition they wouldn’t have anything to compare to. And a lot of the veteran complaints have been along the lines of, “We expected to do X and have done X in the past, and we were bummed that we didn’t get to do X,” whether X is using the phone calls to keep team members aware when progress is made, or to check in with HQ, or to make wisecracks. Maybe some more advance notice might have been useful to smooth the transition, and I would encourage PPPGTPPP to let teams know in advance what to plan for next year.

I might get kicked off Setec for saying this, but I actually think the online submission is mostly better (and I especially loved the sound tags on solves). But there was one related issue that might be a dealbreaker. I’ll meet you at Q5.

Q5: How much guessing is too much guessing?

If you’re a regular reader (at least as much as I’m a “regular” poster), you probably remember my ranting about backsolving and THE WOLF’S HOUR in 2019. (I hope THE WOLF’S HOUR will join BE NOISY and RECTION in the die-hard Hunter’s inside-joke file.) I am by no means the most opposed person to backsolving/guessing, but I’m certainly not the least. That said, the captain of teammate wrote a great blog post about their Hunt experience that contained this little nugget: “during the minutes before the hunt started I encouraged everyone to submit a guess as long as they were >10% sure that it could be the right answer.”

The next paragraph begins, “I realize that this aggressive guessing strategy seems horrifying to some teams”… And I would like to confirm that YES, IT DOES. I realize this isn’t how it’ll happen in practice, but “more than ten percent sure” suggests that a team may expect to call in nine or ten answers per puzzle. With no live phones, that’s no longer something that’s going to jam up the lines and prevent other people from confirming answers. But the same post also includes this very relevant graph:

>=D=> >=D=> >=D=> GT >=D=> >=D=> >=D=> (yes, I am going to write that differently every time instead of looking up how to type a damn airplane symbol) is certainly a team to be reckoned with… They have great solvers, and I’ve loved all three Galactic Puzzle Hunts, and I was honestly rooting for them to win (sorry, Palindrome, I know you’ve been waiting) this year. But I find it very troubling that the two teams that guessed answers the most aggressively were two of the first three teams to finish, and in particular, in the first year without phones (and thus without a construction team potentially getting annoyed about answer spamming), the two most aggressive guessing teams had a notable increase in performance. I’m not sure that’s entirely a coincidence.

So here’s the thing. I think it’s up to the constructors to decide what parameters they think are reasonable for solving teams. On one hand, I think those standards should be communicated better to teams, and on the other hand, if teams know the precise standards, it could encourage some teams to engage in “unacceptable behavior minus epsilon.” And I suspect Trendsetters will have a pretty loose attitude about this given their own solving style. But I encourage all Hunt writers to consider that allowing teams to guess aggressively will encourage any team that wants to win to guess aggressively. And that will cause a lot of puzzles to fall more quickly. Which may cause constructors to feel obligated to write more puzzles. At which point I refer you to Q1.

Q6: How should non-student participants (and teams) approach Mystery Hunt?

This question is here for two reasons. The first is that the late-night-visitors-on-campus policy this year was a major event in Hunt history, and it’s worth discussing. The second is that I spent a lot of time before and after Hunt ranting at people on various social media platforms, and I want to collect those thoughts here for the record.

I did not state the question as something like, “What resources should MIT provide to non-students?” because no one creating or participating in Mystery Hunt ultimately has control of that (though the evolution of Puzzle Club is probably the best thing that has happened in years in terms of giving Hunt a stable voice on campus). MIT doesn’t have any obligation to support or continue Mystery Hunt, and they certainly aren’t required to host a large number of visitors on campus for the event. Yet they allow Hunt to use a large number of rooms, both for solving teams and the constructing team, and they also partially fund the event through various avenues.

Based on some of the posts I saw elsewhere and flipped out about, this relationship between Hunt and MIT is not fully understood. People suggested that Mystery Hunt is a vital part of MIT’s educational mission. It’s not. People suggested that Mystery Hunt is one of the biggest events of the year on campus. It’s not. People suggested that Mystery Hunt is a large enough event that Boston and Cambridge should be aware of it and provide support. It’s not. I think it’s a wonderful part of MIT culture, and it’s one of the most important events of the year to me (and has played an outsized role in my development as a human being). But it serves a niche audience, and we should not let ourselves believe the world revolves around that audience.

People also suggested that MIT is paying attention to the event design throughout the year, and so any policy changes they make are through some fault of the construction team. That’s not how this works. If anyone still believes any rule changes for late night HQs this year were because of Left Out, please understand that, in fact, the reason so many rules eventually were left unchanged were because of diligent work by Left Out and the Puzzle Club. I am very grateful for everything they did, especially in the last week when there are a million other things to worry about.

If you are not an MIT student–and I’m including myself in this even though I paid MIT four years of tuition back around the turn of the century–any resources, classrooms or otherwise, that MIT provides you are a gift. The Institute is not perfect (I refer you to a lot of other blogs and news outlets for more information on that), but they are doing the Mystery Hunt community a big favor. The best way to ensure that this favor continues to be done is to remember that, whether you donate to Hunt or not (and please consider doing so), you are a guest on campus. Enjoy the event within whatever constraints are put into place, don’t be entitled, and trust that the people who interact with MIT are doing what they can to include as many solvers as possible.

Sorry to end this post on such a ranty note, but Q6 has been a touchy subject for me this year. With that, I’m going to close the book on 2020 Mystery Hunt posting. If you have thoughts on any of the questions above (or other Hunt thoughts that you don’t have a convenient place to deposit), please respond below, and I’ll see you in the comments.

2020 MIT Mystery Hunt, Part 2: Some Puzzles I Remember

(This is a recap/review of the 2020 MIT Mystery Hunt, which happened this month. Puzzles and solutions can currently be found here. This recap may contain spoilers.)

[Before I start, if you’re seeing this shortly after I post it on Sunday, you may have time to drop by Left Out’s AMA on the Mystery Hunt subreddit. And even if you’re seeing this later, I’m sure the Q&A there will still be interesting to look at after the fact!]

It’s more standard for me to start by talking about structure, since that tends to be my favorite thing about a new Mystery Hunt, but I expect I’ll have more complex things to say about that, so I’m going to start with a rundown of some puzzles I remember solving (or not) and have something to say about. They don’t necessarily represent my favorite puzzles that I did, and certainly not my favorite in the Hunt as a whole since I still haven’t seen everything!

The Ferris of Them All

This was my first instance of following Setec’s planned “casual approach” to this year’s Hunt; this released very early, and while abstract logic puzzles often get devoured very quickly on our team, Jackie and I decided to print out our own copies regardless of what everybody else was doing. (The team explicitly mentioned solving puzzles in parallel as a way to make sure we didn’t finish first… in practice, when one group finished a puzzle, everyone else usually stopped, and if a group didn’t let other folks know what they were doing, feelings sometimes got hurt, so we’re still working out the kinks.)

Some steps of the puzzle were harder than others; I think on Step 2 we realized too late that looking ahead to Step 3 would have eliminated some options, and so on Step 3, I used some constraints from Step 4. Jackie and I mostly worked independently and then combined forces when we got stuck. If I’d known we were going to be struggling to finish the Hunt a couple of days later, I would have approached this (and probably some other early puzzles) very differently.

Star Maps

Star Maps was probably the puzzle I put the most time into solving, and it’s another case where if we were trying to win, I probably wouldn’t have focused it for so long; but it was very satisfying, so I’m glad I stuck with it. I joined the puzzle after the jigsaw had been assembled, at which point we needed to decide where to place the red dot pieces. We briefly pursued a red herring–surely a puzzle called “Star Maps” with fifty nodes would have something to do with connectivity of the 50 states–but Alaska and Hawaii eliminated that option, and as we got some dots placed that seemed to match up, we realized each edge seemed to pass through one graph. The more dots we placed, the easier remaining ones were to place, which led to a nice solve flow. We didn’t do ourselves any favors by setting the puzzle up in a room with poor lighting; between that and the small printing, we eventually had to use flashlights to finish solving.

For the graph identifications, we ID’d about 15 out of 50 properties (I’ve never taken a course in graph theory but I used to dabble for fun), and once it occurred to us to assume the 5’s at the ends were all “graph,” that gave us enough letters to wheel-of-fortune the first 40 out of 50 letters of the clue phrase. For the last ten, we got stuck with T???PL?????, and even once we guessed that the PL?? might be PLUS, we didn’t know what the T??? could be. With some more ID’s, we got to TW??PLUSO??, still perplexed by the four letters before PLUS; finally somebody suggested TWON (it was actually K, and I still don’t know what a snark is), and we were able to draw the answer. It was a loooong process, but it got more approachable a bit at a time, and it was very rewarding to make it to the end.

Looking at the solution, I can tell you we never wrote the properties on the intact sheet, and therefore I had no idea until now that the properties were alphabetized on the sheet. And don’t get me started about the easier-to-read erratum that came out after we solved the whole thing.

Peak Adventure (and Ox and Chairiot Races and Penny Park Guide, etc.)

I’m a fan of the sort of puzzle that is actually a little suite of variety puzzles; it provides a lot of ahas, and if any of them are unusually hard to approach, you can usually solve them from a large subset of solutions. (This should not be surprising… I like puzzlehunts enough to have a poorly updated blog about them, so of course I’m going to like puzzles that are little puzzlehunts.) I’d say the only real drawback to this kind of puzzle is that it’s time-consuming to write, so I have no idea how Left Out wedged a whole bunch of them into their Hunt.

The one I interacted with the most successfully was Peak Adventure. Clicking around the puzzles in Cascade Bay at a time that most of our power solvers were hammering away at the Safari metas, I found a nice little collection of a dozen mountain-themed puzzles. Checking our solving spreadsheet, I saw people had spreadsheetified a lot of data, but only about four of them had been solved, so I started bouncing around completing partial solves and getting a few ahas myself. In the last stage, Jackie and Josh Oratz and I figured out which three winter weather words could be combined with nonconsecutive substrings of our answers (well done by the author in making the set enumerations similar so that you needed most answers to start placing things confidently), and we worked out a final answer.

Ox was the puzzle of this type I heard the most positive feedback about on social media; I didn’t look at this during the Hunt, but Jackie and I cosolved a bunch of the subpuzzles after Hunt (I’d already spoiled myself on the extraction) and they were fun and creative, though I was sad that the sound file link was broken. There were at least two more mini-suites that proved too hard for us overall; I was sitting next to the group working on Penny Park Guide, and there was a lot of cool stuff going on, but in particular there was a lot of it, and by the time they solved it (still forward, I believe!) I believe we had solved the metapuzzle for that round and had all the other answers. I did work on Chairiot Races, and after hours of solving and many people looking, I don’t think we solved half of the subpuzzles… which was a shame since reading the solution after the fact, the end step seemed really cool. I think the pieces of this last puzzle suite were probably miscalibrated in terms of difficulty, and I’d be curious to hear how many teams solved it as intended.

Spaghetti Western

I almost included this in the mini-suite catchall section, but this one was inherently different, since the individual puzzles overlapped by four inputs, which means the main first goal was to solve for those inputs by comparing ALL of the minipuzzles, and then eventually completing each one independently. I’ve certainly played Spaghetti on Eric Berlin’s social media before (in fact, I was unexpectedly the author of the weirdest example “solution” when he presented it as an exercise at a recent NPL Con), so I appreciated the reference, and I thought the flow of solving was a lot of fun… just like in Star Maps, making progress in one area made everything else a little bit easier, so there was a gradual and satisfying acceleration toward the final answer.

In Space, No One Can Hear You Sing

I believe I was the first on our team to open this puzzle and see that I should submit the word KARAOKE and come do a thing, and if you know me at all, you know you don’t have to tell me to do this twice! We did, on the other hand, have a hard time finding a second person to go… eventually when leadership asked the room, “Seriously, we need someone to go to this thing with Dan,” Jenn Braun said, “Okay, I’ll do it. What is it?” When somebody volunteers for karaoke without realizing it’s karaoke, it’s useful if that person happens to be, like me, a former president of the MIT Musical Theater Guild.

We were happy to see some of our good friends from Attorney (I’m calling them that from now on, see Part 1), and since we’d been told HQ would be able to (and was strongly encouraged to) watch our karaoke game show, I Slacked the room that there would be Rhode/Anand content, and Tanis was very pleased. Erin unfortunately got stuck with a set of songs she didn’t recognize (Rich Bragg had to tell her to stop reading the entire list, as it made the puzzle potentially easier, at least if you hadn’t spotted the aha), and so from now on I will assume that Lady Gaga’s “Diamondheart” is an avant-garde spoken word number. For some reason, I tried to pick my song very quickly once the options came up, thinking that would help(?), and I ended up doing a mediocre down-one-octave rendition of “Feel It Still.” I only actually remember processing the middle two songs on my list of four, and choosing the one I did because I liked it much more than the other. In retrospect, based on the puzzle mechanic, I think “X’s and O’s” by Elle King was likely on my list, and I regret not choosing it because I think it suits my vocal range better. None of this was the point of the puzzle, of course.

Weakest Carouselink

This was the other game show I volunteered to go play, shortly after I woke up Saturday morning when few of our team members were awake. Apparently few teams in general were awake, as we (Todd McClary and I) ended up playing a game designed for eight people with only four. The organizers handled this by giving us four “ghost” players, which made things… anticlimactic? No, antibeginningic, since in the first four rounds, no matter what we answered right or wrong, a ghost was eliminated each time. I survived to the last round of two people, in which we tied on questions answered (I think zero each), and I got eliminated simply by virtue of order placement. Again, as above, not the point of the puzzle.

The point of the puzzle was to take the correct answers to the questions and link them into chains. Todd and I had fun trying to link the answers partially from memory and partially from the cards on our way back to HQ, so when we got there we already knew half of what we needed to do. We got stuck on extraction, but Scott Purdy walked by and noticed there was consistently one overlap that was shorter… I thought this was a bit of a stretch until I processed that the short overlap was literally “the weakest link,” and we read off the clue phrase and answer shortly afterward.

Dance Party

I didn’t get involved in the HQ step of solving this, but I was recruited when the invite to the follow-up interaction heavily implied there would be DDR. As it happens, I didn’t actually play any of the DDR, as Philip Loh came with me, jumped on the dance pad first, and never really needed to leave.

The last step of the multi-phase interaction involved placing a gibberish handout on a turntable in front of a strobe light, which highlighted the answer letters in a very cool effect. Our experience here was slightly awkward because one of the two turntable setups had broken down right before we arrived, and so our handlers were extremely paranoid about our doing anything to break the one version that remained. This led to a frustrating dynamic where they were clearly encouraging us to touch the turntable, but not do this, or this, or this… I voiced my annoyance at this and was probably unfairly impatient, since I can imagine how panicky I would be running this station with two instances suddenly becoming one. Eventually they reminded us they’d told us to bring our handouts but took all the no-longer-relevant ones away from us, which was a nice way to narrow the search space and get us to the near effect (and, of course, clear the room so other teams could play).

Wolf and Rat

Both of these were fairly straightforward, and I co-solved each of them during a period where HQ was a bit slow and we needed more answers to plug into the Safari Adventure metas. Rat was one of the first puzzles I tackled Sunday morning, and a crostic was a good thing to wake up my tired brain without requiring too much creative thinking. Wolf appeared to be a food pyramid puzzle (somehow my eye picked out the relevant lines for that amidst the others) and turned out to be a food-and-two-other-pyramids-I’d-never-seen puzzle. We didn’t get the ordering mechanism at first, particularly since the first batch of letters we extracted was anagrammable without a mechanism, but the last step was cute once we grokked it.

Film Clips

I did nothing to help with this task-then-puzzle until the end. When I arrived in HQ on Sunday morning, the emoji meta had been solved in my absence (and worked much more satisfyingly than I’d expected when I went to sleep, since I’d been finding single-digit changes in the hex codes for the emojis) and there were a handful of backsolved emoji listed on the board next to our unsolved puzzles, one of which was an envelope. There was also an envelope marked FILM CLIPS taped to the board, which we’d received after making a movie trailer and which apparently no one particularly wanted to solve. I suggested that we try the envelope emoji for Film Clips, just in case the puzzle resolved to something like “What this puzzle came in.” We did, and it did.

Magic Railway

Or as we called it, the Harry Potter Konundrum. I have a fairly established rule not to solve konundrums (or generally immersive direction-following puzzles) for my Hunt teams, because I usually get annoyed by them. So it’s a testament to the quality of this one that after glancing at a bunch of the cause-and-effect instructions, I thought it actually looked fun, and I would happily participate as long as I could be Professor Ophidian. After all, my crossword grid nameplate on my office door does contain the hidden micro-bio, “Math Snape.” Anyway, I did enjoy the interplay between characters, but I was kind of disappointed when after two actions aboard the train, I got off the train, and I never got back on. I know from experience that writing these can be exhausting, but I would have been happy for this to go about twice as long… I felt like our group had finally found a good rhythm in interpreting the instructions, and then all of a sudden we were extracting stuff. But it’s rare for me to want there to be MORE stuff in someone else’s konundrum, so compliments to the chefs.

Water Slides

This was a chutes and ladders wordplay grid variant we solved in a group of four that was very straightforward to solve, given its placement. I want to bring it up to say three things about it: (1) Given that the constructors didn’t get to pick the locations of the chutes and ladders (they were taken from the original game board), the grid fill was very impressive to me. (2) While my teammates saw immediately that the player banter referenced the clued words, I initially thought they’d reference the pictures of kids doing things on the originaly published game board. This means I spent way too much time finding a hi-res version of that image, and also that I can attest that those kids are doing weird stuff. (3) In reference to this being a pretty easy puzzle near the end of the Hunt, after Hunt someone on Left Out mentioned that they’d put some easy puzzles right near the end in order to give people a smooth landing. If this was intentional, oy, please don’t do this, constructing teams. I get this principle in the design of, say, mixtapes or calculus exams, but in a Mystery Hunt where you have to unlock earlier puzzles to open later ones, the end of the Hunt is the last place you want to bottleneck teams. If Cascade Bay and Cactus Canyon had opened their puzzles in a different order, we might have had a fighting chance to reach the endgame.

TEAMWORK TIME: Various Subtitles

I was asleep for the first few of these, so I think my first participation was Tug of War, when only five or six of us were awake, and therefore at least three of our players had to be Philip running separate instances on his computer. Anyway, I think these were fun, and whenever they occurred at a time I was awake, somebody yelled out, “Teamwork Time!” and most of the team participated. I’m told these were similar in nature to the Whistle Stops from a recent Microsoft Puzzle Hunt, and whomever you want to credit for the innovation, I think it was a cool social element for Hunt. Based on some of the interactive features in recent GPH’s, I hope/suspect Six Planes Two Words will do something similarly inspired. Though if it could not require me to work out a set of English words that adds up alphanumerically to 851, that’d be swell.

First You Visit…

This parody/loving tribute to First You Visit Burkina Faso unlocked while I was asleep, and I woke up to see everybody poking Ben Monreal (the author of the original, who was remote this year) on Slack. Sadly, I’m not sure we ever solved this, and I don’t actually know if we even cracked the pop culture reference that I now see the puzzle revolved around. Given how significant the original was in the battle between the top two teams in 2019, I think sending it up this year was great, and the particular mechanic used was ingenious. I apologize to Mark and Gaby that you didn’t get to see our team solve this, as I’m sure it would have been the highlight of your entire weekend. (Nothing else significant happened to the two of you during Hunt, did it? Well, other than the release of the Radiohead Public Library, which I’m sure caused Mark’s head to explode.)

Next time: Structure and Big-Picture Design! What was different about this Hunt compared to other Hunts? What worked? What didn’t? You decide! (Well, it’s my blog, so I quasi-decide first, then I let y’all weigh in in the comments. Speaking of comments, what puzzles did you particularly like from this year? Opine below…)

2020 MIT Mystery Hunt, Part 1: Coping With Anticlimax

(This is a recap/review of the 2020 MIT Mystery Hunt, which happened this month. Puzzles and solutions can currently be found here. This recap may contain spoilers.)

As usual, I expect to devote multiple blog posts to the premier puzzlehunt of the year. But for the second year in a row, the Brown schedule is such that there’s no buffer week between Hunt and my teaching responsibilities, so I’m about to become quite busy. As a result, Hunt posts may be spread out, though I’ll try to keep things a bit more together than I did with Miskatonic. I’ll open with a post about what I’m feeling right now a day after Hunt and address content/structure/length/policies/what-have-you later, and if there are particular topics you think should be discussed here, feel free to bring them up in the comments.

Regardless of how good the content of this Hunt was (and I think it was very very good), it will be hard not to remember this year as both the first Mystery Hunt where I explicitly didn’t want to win, and the first Mystery Hunt where my team didn’t solve all of the metas. I realize the latter might be surprising, since the vast majority of Hunt participants don’t see the end of the Hunt before HQ shuts down, and so expecting to finish is admittedly somewhat entitled. But here’s a brief summary of my Mystery Hunt experience:

  • 1998: Hunted with Setec, reached the coin location at the same time as Iliaphay, who found it during their turn in alternating shifts in the elevator
  • 1999/2000: Won with Setec, wrote with Setec
  • 2001/2002: Won with Setec, wrote with Setec
  • 2003: Hunted with ACRONYM, and we were informed during the first phase of endgame that the coin had been found
  • 2004/2005: Won with Setec, wrote with Setec
  • 2006/2007: Won with Evil Midnight, wrote with Evil Midnight
  • 2008/2009: Won with Evil Midnight, wrote with Evil Midnight
  • 2010: Hunted with Attorney (A Team That Obstinately Replaces Names Every Year), solved the last meta while HQ was open, but they didn’t have resources to run endgame
  • 2011: Hunted with Attorney, finished the Hunt
  • 2012: Hunted with Attorney, finished the Hunt
  • 2013/2014: Hunted with Attorney, wrote with Attorney [Alice Shrugged]
  • 2015: Hunted with Setec, finished the Hunt (though I slept through the endgame)
  • 2016/2017: Won with Setec, wrote with Setec
  • 2018/2019: Won with Setec, wrote with Setec

Which brings us to 2020. After writing in 2017 and 2019, the leaders of Setec Astronomy polled the team, and we pretty much established we didn’t have the time/energy/interest to run a third (well, sixth) Hunt in 2021. So we basically said we would approach the Hunt in a more casual way. We said it would be okay to solve puzzles in parallel, people should feel free to get as much sleep as they wanted to, and people brought board games, though I’m not sure any of them actually got played.

In practice, the extent to which people took their foot off the gas probably varied from solver to solver. Early on when the first logic puzzle came out, Jackie and I solved it independently even knowing another group was working on it, but other than that I thought I was going pretty much my normal speed, especially once I started to suspect how big the Hunt was, as I really didn’t want to miss out on completing the endgame. After talking to Jackie, there are still ways in which I gave less than 100%… I slept a few hours more than normal per night (especially from Saturday into Sunday), and there were a few occasions where I sunk a lot of time into one puzzle, and in a more competitive environment, I probably would have abandoned ship and looked for things that were closer to an answer. (I am glad I got to see Star Maps through to its conclusion, but man was it a time sink, and I didn’t even help people assemble the jigsaw.)

As time went on, I became more sure we weren’t likely to finish by 5pm, but I didn’t think we were doing much more slowly than usual, so I was worried we were going to enter an awkward stage; if Hunt passed 5, we couldn’t finish without winning, and I wanted to finish but we were not willing to win. This became a moot point when PNGTOPN (plane noise Galactic Trendsetters other plane noise] officially won, but now we had a race against time to try to finish our last two rounds.

We didn’t, and at the end of the Hunt, we still had 4-6 puzzles in each of those rounds we hadn’t even unlocked. I spent most of the last hour of Hunt desperately trying to contribute to Cascade Bay by backsolving one of two missing answers that would have to fit into both Lazy River and Coast Guard, apart from about 25 minutes where we had a teamwork time open and I had to learn to speak Beale. At the time, I didn’t think we had a chance at finishing on time, though I thought we definitely could wrap things up given another five hours or so. But having been to wrapup, I actually think we should have been able to get in under the wire, given three things I discovered today:

  • Our theories on how to solve the two remaining metas were pretty much exactly correct, but we just needed more inputs (in particular, for the Cascade meta, most of our answers had different lengths and didn’t pair up, and we had almost all of the PH halves and very few of the answers that actually provided meta letters.
  • My Cascade backsolving was handicapped by the fact that we hadn’t put HELICOPTER DROP into the grid yet, and so I had been trying to fill an answer in where two went.
  • At breakfast I discovered that one of my teammates had guessed a pun answer for Cactus Canyon based purely on the flavortext, but never called it in. It was correct. (Given our goal of not winning, I wouldn’t have wanted to skip an entire round while the coin was still active, but once Galactic found the coin, I desperately wish I’d known we had a guess, because if we’d been able to focus on Cascade Bay for three hours, I think we could have wrapped things up.)

I shouldn’t be frustrated about missing endgame; I had a great weekend solving well-written puzzles with people I like. But I have a perhaps unhealthy habit of characterizing myself based on accomplishments over time, and it’s hard to cope with the fact that I’ll never again be able to say I have a perfect record of finishing Mystery Hunts. But all things must come to an end, and so maybe it’s good to rip off this band-aid and not have to worry so much about getting to endgame next year, though I certainly hope we will.

In any case, the end of the 2020 Hunt was very anticlimactic for me, and I’m still strangely uneasy, but I suspect I’ll get over it in a few days, and then I can evaluate the Hunt from a more rational perspective. So I’ll check in again when I’ve chilled out.

In the meantime… answer checking without phones! Loved it? Hated it? Did the world end? Setec had a lot of members expressing displeasure about it, but for me, it was actually fine. I did wonder (once others brought it up) whether it made Hunt less welcoming for newb teams.

Recap: Miskatonic University Game, Part 6

(This is a recap/review of the Miskatonic University Game, which happened on August 15-18. Puzzles and solutions are not fully online, but some of them are posted here. This post will likely contain spoilers.)

I wanted to finish up this recap before the end of the calendar year, and it’s three days until Christmas (last time I said, “hopefully soon doesn’t mean December,” but it definitely did), so let’s try to wrap things up. The main things holding me back have been (a) having a busy semester with a new course prep for the first time in years, and (b) the fact that the last phase of Miskatonic University was almost certainly my least favorite part of the event.

That second thing is almost certainly not a function of event quality, though I noticed that, much like in the Famine Game, the last wave of puzzles didn’t include much in the way of plot advancement, which made things less immersive. A much more significant factor was sleep deprivation. Apart from the hour of sleep I got at the overnight location (right before the Eyeglasses Nightmare of 2019) I hadn’t managed to nap at all, and it was finally catching up to me big time.

Jackie, my usual first-choice puzzling partner (and life partner) didn’t join us for Miskatonic because she values sleep, and she asked me several times why these events don’t have sleep breaks. I think there are multiple reasons for this in a Game-style event, including the fact that having a place to sleep increases cost and logistical complications, and that people who fly in want to get the most puzzle bang for their buck. But I’m getting too old for extreme all-night puzzling, and I have to admit that a longer event with an overnight sleep stop sounds more appealing to me.

I should note that in 2001, when Palindrome declared that the Mystery Hunt was going to have an overnight break where HQ would close and no puzzles could be confirmed or unlocked, I was among the many community members who were infuriated. Lest I sound inconsistent now, I want to point out first that the Mystery Hunt is very different in that it’s a competitive event where no one is skipped forward, and so not being able to unlock puzzles while other people catch up to you is a big problem; and second, that I was literally half my current age at the time, and forgoing sleep was way less of a problem back then.

We were warned that once we parked for this phase, we’d be on foot for the rest of the time, which is again probably logistically necessary, but is arguably the worst time to be away from your van from an extended period of time, since when I really needed a nap, I didn’t have a place to take it. This was even more of an issue for our team, because (as you might remember from Part 1 of this recap posted about nine years ago) we had an oversized van, and as a result we had to park in a lot farther away from things than the intended garage, so going back to rest in the van was even less feasible. Probably the only thing that could cause me to be even less comfortable would be if when we left the van I forgot to bring my daily acid reflux medicine that prevents me from having heartburn when I eat or drink. So guess what I did?

Anyway, all of the above left me in a crankiness spiral where I wasn’t a very pleasant teammate, and I probably didn’t process the puzzles well enough that it makes sense to do a full blow-by-blow recap. So let me just mention some of the puzzles I remember liking most, and then I’ll summarize the endgame…

I already skipped over describing the puzzle we had to solve en route to Boston, which was one of the only puzzles we actually solved in the van. This was also one of the times we might have needed a laptop, since we had a bunch of Lovecraftian Christmas carol parodies on a USB, but our van had about eight places to plug in a USB, and one of them came on over the car stereo. I took the very important role of music box cranker, and while I didn’t find the carols as funny as some people did, I did enjoy IDing the melodies.

We were given a magnetic white board to use for some of the remaining puzzles, which was really convenient given that we had a lot of jigsaw-style puzzles coming up. I worked on one based on the Greenway labyrinth that was clever but a bit frustrating, and the one I enjoyed more was a “brick by brick” puzzle where we had to build a grid to accommodate a bunch of phrases with the word FISH in them. The concept of that one was not groundbreaking, but it hit a good level of difficulty for my weary brain. The other half of our team was working on a much harder puzzle at the time, and when we went to help them finish, I could see why they took longer… they definitely drew the short straw.

Puzzles from there included a Jenga puzzle (with very large provided Jenga bricks!) where we messed ourselves up by trying to construct the tower from the wrong end… a Harry Potter/Cthulhu mashup spelling bee where the text of the puzzle was funny enough to make the actual puzzle solving anticlimactic… and a letter weaving puzzle and another listed on the website that I honestly don’t remember. We then got to solve one more meta presented by a man dressed as the Gorton’s Fisherman (a joke I’m sure he only heard two or three thousand times). I remember this involved phrases associated with GOLD, SILVER, and BRONZE, and nothing else. We finished the meta early enough that we were told we’d be off for 90 minutes before the final puzzle. Most of the team went to lunch, but I was afraid eating was going to cause me pain (I still hadn’t recovered my meds) so I hung out in Boston Common and strongly considered catching a train home. Like I said, this was not a pleasant morning for me, and if the commuter rail schedule had been more cooperative (and if not for the fact that I’d need to drive to Jenn’s later and collect my stuff from the van), I might have jumped ship early. Though Jackie reminded me over the phone that if I missed the end I’d probably have serious FOMO regret later on, so I rejoined the team after lunch.

The final confrontation was a very elaborate large-scale Survivoresque physical challenge involving solving one face of a Rubik’s cube to spec and winning a game of very loosely adjudicated Simon Says. And then repeating this over and over again. As much as I wanted to fight for humanity (this was where we discovered that some of us had been assigned to support humans and some the Cthulhu cultists, though I didn’t know until later that we were sorted by inkblot puzzle answer), there was no way in hell that I was going to drag my half-asleep body into a Simon Says game, so I, along with most of my team, decided to watch. Humans won anyway. This is not a good metaphor for presidential elections. Participate when things are important, kids… don’t just expect everybody else to do the work for you.

While all of this was going on, a member of Here Be Dagons heard me whining about my acid reflux plight and gave me a Zantac. Not a permanent solution, but very helpful for the moment, and the second time somebody on another team proved to be my hero. In the alternate-timeline version of this endgame where I had both heartburn and broken glasses, I might have just wandered out on the field and started punching cultists.

After all of this, there was actually a puzzle! For most teams. We were one of two teams who didn’t get a copy, because apparently some teams took too many copies. And from what I heard, when they asked teams to surrender extra copies if they had them, somebody saw a solver hide an extra copy. That’s coming third-hand, but if you’re reading this, and you did that, thanks for being a massive jerk. Then when we did get a secondhand copy of the puzzle, it didn’t include instructions that said we should submit once we had an initial collection of words that clearly wasn’t an answer, so we spent a bunch more time trying to “solve” those words, and I think I should stop talking about this puzzle before it makes me angry.

Anyway, this was an appropriate capper to what was for me a rough seven hours at the end of an otherwise great event. Most of the roughness was my own fault, though I think taking teams far away from their mobile HQ during the period when they’re most likely to be exhausting is something construction teams should consider. (I don’t remember having the same problem during the Famine Game, but again, I was younger then.)

I feel bad that I’m ending this six-part series with my crankiest reaction, and I hope any organizers reading this note that when one of six posts is notably negative, that means the other five are mostly positive. I’ve written eight Mystery Hunts, two BAPHLs, and three NPL Con extravaganzas, and in all of these I’ve had a ton of fun creating puzzles and an overarching structure, while most of the most significant stress I’ve experienced has been tied to logistics and protecting against every problem that can occur. I feel like Game running is even more tipped toward the latter than the Mystery Hunt is (even though it involves fewer solvers), and I cannot express enough admiration to Sarah and her minions and their ability to track dozens of independent vans darting around New England and keep things from falling apart. I’ve criticized some elements of the event, and any opinions are my own; I hope my perspective is useful to anybody who runs a Game in the future, and I hope those who ran this one don’t let the negative feedback eclipse the positive.

I don’t think that last paragraph tied everything together very eloquently, but writing this entry has somehow caused me to feel sleep-deprived all over again, and thankfully I don’t have to sleep in a van or on my glasses tonight. Happy holidays, y’all. See you at Hunt.

Recap: Miskatonic University Game, Part 5

(This is a recap/review of the Miskatonic University Game, which happened on August 15-18. Puzzles and solutions are not fully online, but some of them are posted here. This post will likely contain spoilers.)

Real talk, folks. It’s been a long time since Miskatonic, and as it gets farther away, my memories become less focused and less useful. So as much as I want to document everything in exquisite detail, I’m going to try to go faster so I can reach the end. (Besides, this is the point in our journey where I was starting to get extremely sleep-deprived, so about half of the details I remember were probably hallucinated anyway.)

Side note: While I was being an absent puzzlehunt blogger, Puzzle Boat 6 happened! It was great even if it did take a perennial Mystery Hunt theme contender (unchosen finalist in 2009 and 2014) off the table. Grab some friends and sign up for lots of puzzly goodness.

Frat party? Frat party.

Frat party!

When we last left our heroes, they were feeling all smug that they had managed to surge past all the other teams, not knowing this was because they’d been skipped past a puzzle (the only puzzle we wouldn’t see all weekend). As it turned out, arriving to this multi-puzzle location in the fake lead was a big advantage, as a lot of the puzzles were in small rooms/areas that we initially had to ourselves, and later they were super-crowded.

The first and frattiest puzzles took place in a cafeteria area, as we arranged a collection of solo cups in beer pong formation to spell out beer names and then solved a nifty physical maze on the surface of a wooden hazing paddle. Teams were apparently sent to the remaining puzzles in this round in different orders (I am delighted that I did not have to work out the logistics of this). The other puzzles were mostly upstairs and did not feel particularly fraternity or university themed. I’m thinking that the idea was that the party was downstairs, but once you snuck upstairs you got access to all the creepy supernatural stuff that the frat bros were really up to.

We next went upstairs to solve a nice non-rectangular grid puzzle on a whiteboard, which could be erased quickly for the next team. This was one of the times we were grateful to be early, since there were stations set up for four teams to work at once. We were the only team in the room and thus we could shout out answers as loud as we wanted… I think this would have been more frustrating with other teams present, as I’m hypersensitive to overhearing unintentional spoilers.

The next puzzle involved going outside, and I’m grateful it was served to us next, because a terrifying and thematic rainstorm was rolling in. We had to grab a multicolored cryptogram from a box on a bench, and then transcribe Morse Code from a whole bunch of blinking eyes. Transcribing Morse is not easy in real time, and it’s harder in the dark, and even harder when you’re under time pressure because it’s starting to rain. Some of our data seemed wonky, but we fled into the lobby with what we had, and it was enough to finish solving inside. Meanwhile, we saw several poor souls run outside into what was now a torrent, run outside and run back in soaked with a wet piece of paper, asking, “We don’t need anything else from out there, do we?” Bad news for you.

We got shuttled between four more frat party stations, the coolest of which by far was a Ouija board with a paddle that moved automatically when you spoke a word to it (or more accurately to the data inputter listening nearby). The puzzle itself was essentially just word mastermind, but this was the sort of visually impressive set piece that I look for in a Game versus a typical puzzlehunt. We also tackled a very challenging but eventually pretty cool puzzle based around a gallery of paintings of tentacled creatures, a set of jars of mutilated stuffed animals communicating in both Braille and genetic code, and a puzzle box where the box was unintentionally open when we first arrived, and which was closed by the organizers and then didn’t open without assistance when we did the right thing. I heard positive feedback about this puzzle from others, so hopefully we just had a dud box.

Next stop: metapuzzle! We were told to proceed outside (thankfully the rain had passed) to find a dark and creepy path leading to the back of a truck. The truck contained a pretty cool padded room with words drawn on the walls and meandering paths all over the walls connecting various letters. This was yet another case where getting there early was a boon, as we had the truck to ourselves and could write down all of the paths pretty effectively. But we got stuck for quite a while on what to do with our puzzle answers and the words on the walls, until we remembered a sign on the outside saying something like “What do you fear most?” All of the items on the walls had phobia names that could be linked to our puzzle answers, yielding a meta answer.

This led to the best plot twist of the weekend; we were confronted by an excellent actor playing a stern psychiatrist in a very nicely understated performance, telling us that, in the spirit of some disturbing episodes of Buffy the Vampire Slayer and Community, everything we’d been doing so far was imagined and that we were actually in a mental hospital. It was a particularly nice touch that when he asked where we really were, and I incorrectly said, “Arkham Asylum,” without missing a beat and without breaking character, he patiently explained to me that that was a fictional location from the Batman universe. Here’s to you, creepy psychiatrist guy.

We were ahead of the curve at this point, so we were fed a non-meta bonus puzzle. I’d been carting around my laptop all weekend for no reason, and this was the one time I used it; not only did we have to speed up some super-slow recordings, we had to know exactly how much we’d sped them up, so having Audacity was a godsend. Once we finished this puzzle (which was honestly kind of tedious) we were told other puzzles weren’t ready for us, and that we’d be paused for about an hour. So we squatted in the room we’d solved that puzzle in, turned off the lights, and attempted to take a nap.

Bad morning!

When I woke up, I encountered the most horrific moment of the weekend. In trying to fall asleep, I’d tried a lot of positions including a few in which I slumped onto my bag on the table. My glasses were also on the table, and presumably at some point I had put my bag, and all of my head weight, onto the glasses. So when I put them on, they had been bent and mangled to the point where I could not place them on my head in a position I could see. This was really distressing, and thankfully one of the people around when I was freaking out about this was brave enough to carefully bend them back into position. I don’t remember who you were, glasses repair guy, but you kept me from having a panic attack, and thus you occupy an echelon even higher than creepy psychiatrist guy. I still had trouble getting past how jarring this experience was, and much to my team’s dismay, I proceeded to tell this story to everyone I encountered for several hours.

Before departing for breakfast, we had another quick interaction where we established we were consciously choosing madness (as opposed to exposing the charade of Evil John Hodgman, making this officially more like Buffy than Community), and we solved an inkblot-themed puzzle, folding sheets of paper to yield the phrase THAT WAY LIES MADNESS. As we’d find out after the event was over, this was one of two possible answers to this puzzle, which was integrated into the event in a surprising way that we wouldn’t fully appreciate until much late.

For breakfast, we finally took the van to another location, where before entering the main room, we were whisked off into a small room where we were told there was a humans-versus-cultists war brewing, and we were on the human side. Given the general dark undertones of the event, I assumed we were being led to believe we were helping the humans, but that we would actually secretly be helping Cthulhu. But in fact, based on the answer we’d found to the inkblot, we had legitimately been assigned to oppose Cthulhu. This is pretty cool in retrospect, but in the moment, it was just confusing.

The breakfast room had two puzzles. The first involved viewing a whole bunch of crayon drawings of monsters around the room and determining a complex monster naming convention, which we would then use to draw our own monster. Jenn drew a fantastic picture of Thaathlog that you can appreciate here, then stood in a long line only to be told it was close but not right. So we spent a long time re-studying the pictures to figure out what was wrong, and then eventually decided to re-check the exact same picture, whch was then ruled correct; apparently there was a mistake in the way the judge was interpreting the language rule. There was a second wordplay puzzle involving monster bags in monster bags in monster bags, but I don’t think I appreciated it due to being annoyed that we had been held up looking for a nonexistent error.

Once we finished these puzzles, we were given an old-timey music box, a collection of audio files, and directions to park in Boston for the final phase of Miskatonic. Which I’ll describe in the final part of my Miskatonic write-up, coming soon. Hopefully soon doesn’t mean December.




Recap: Miskatonic University Game, Part 4

(This is a recap/review of the Miskatonic University Game, which happened on August 15-18. Puzzles and solutions are not currently online but should be posted eventually, likely here. This post will likely contain spoilers.)

I was just ranting on a Slack about how online things related to puzzlehunts should be posted as soon as possible after the event, because as time goes by, constructor willingness to deal with the event decreases exponentially. Then I realized that applies to me as a blogger as well, and I should get back to Miskatonicking ASAP.

Obligatory me update since I don’t have a non-puzzlehunt blog to speak of: September is busy as always, since my job for the math department includes a ton of administration and placement advising that peaks when a ton of first-year students arrive at once. Looking forward to my first lull in mid-October after my first round of exams. Also hoping the Revolution have limped into the playoffs by then (currently 7th of 7 playoff teams, with control of their own destiny but not a lot of room for error).

The next stop after the solve-by-sulking puzzle I mentioned last time was a bit more on-theme; if we were going to playing an occult game north of Boston, surely we’d be seeing some witch trial sites, and we were directed to the Witchcraft Victim Memorial in Danvers. The first wordplay stage of this puzzle gave us a message telling us to “peel” the cards, and we discovered that one side of the cards could be removed (not easily, which was presumably so people wouldn’t discover this by accident), revealing white lines that could be arranged to form a path. We got very stuck on this stage for a long time; we couldn’t decide what letters, if any, to place on the path, and we did consider trying to peel the other sides of the cards, but it clearly didn’t work. After a while, constructor Joe wandered over to check on us and asked what we’d done, and he suggested that no, we weren’t done peeling the cards… and if you think one side was hard to get off, don’t get me started about the other side. The other peeled side had some delightfully subtle vanished letters, and finally we had letters to spell an answer word.

Onward to… wherever we wanted for dinner, as we were given a jigsaw puzzle to take with us and solve at the location of our choice. As noted earlier, everybody else on the team had scoffed at my mention of McDonald’s earlier, and yet here we were at one for the second time, mainly because we figured it would be a good place to be able to claim some space and leave whenever we were ready. This was one of those artisan jigsaw puzzles with pieces that fit together unusually and custom-sea-creature-shaped pieces (which had been sneakily removed). The actual image was simply of NATO flags, which are mostly solid colors, so it was difficult to assemble. It was even harder to assemble on the table we chose, which had weird flashing colored lights and was likely intended to entertain children while they ate their McNuggets. It also entertained this adult while he ate his McNuggets.

Fortunately, we didn’t get dessert at McDonald’s, partially because even I think McDonald’s dessert is wretched (hey, McDonald’s, sponsor my blog [insert awkward pause while I have a Mandela Effect moment and double check whether “McDonald’s” has an apostrophe… yes it does, I’m not crazy, you’re crazy) and partially because our next stop was Richardson’s Ice Cream, a huge ice cream stand in Middleton. (This place looked super-familiar, and I just confirmed that Jackie and I went there with my brother and his soon-to-be-wife a few years ago.) The puzzle at this location was a set of three rolling block mazes with convoluted and amusing shared rules. Concerned we might still be running behind the pack leaders, we decided to replace our initial puzzles-then-ice-cream plan by splitting up into Team Go Get Ice Cream and Team Solve The Damn Puzzle. I ended up with the first of three puzzles, and teammates took the second and third. Each puzzle spit out letters as you advanced far enough through the maze, and my maze had the most (three) but it also branched the least and was probably intended to be the tutorial. By the time I got two out of three letters (CH_) we’d pulled one out of two letters on each of the others (C_) and (E_), and we chose the correct option out of several words that could have fit that pattern. We submitted the answer right as ice cream reinforcements were arriving. You can tell Richardson’s is a quality ice cream vendor because a “small” cup contains enough ice cream to feed the population of Kazakhstan.

The next stop was one of the more immersive locations, a police-taped-off crime scene showing outlines of dismembered Scooby Doo characters (in the parking lot of the local NRA chapter– ick). I have no idea how quickly Todd ID’d that those were the relevant characters, but it happened before the end of a quick phone call to Jackie, and I think it would have taken me at least another hour. There was another nice aha here, as the letters that were spelling the names of famous dancers helped us realize that we were assembling “Dancing Men” cipher figures. I don’t remember much about the subsequent stop except that the puzzle was given to us in a milk carton, we split up a Gashlycrumb Tinies diagramless by having half of us solve it top-down and the others bottom-up, and we were driven into our van to solve this because the location was overrun by mosquitoes. It is a miracle that I don’t have EEE.

The next location was built out of a retired train car, although the car itself was full, so we opted to solve on some benches outside (again, how do I not have EEE?). The first puzzle we were given was a constraint-based 3-D jigsaw, which was not easy to parallelize, so some of our team members spent the time chatting with Here Be Dagons (they changed it from Dragons in the spirit of Lovecraft) members on a nearby bench. This puzzle was quite challenging, and while it took us a while, I think we did well with it. [This is where I look at the solve times and… yeah, not so well after all.] We next unlocked the metapuzzle, and this is when we were unwittingly skipped past a bonus puzzle. We’d stopped at a Whole Foods a puzzle or two ago for the benefit of those that didn’t stuff their face with McDonald’s, and it appears that we were seven minutes short of being allowed to tackle the bonus puzzle. Next time, no eating. Anyway, the metapuzzle was nice. I don’t vividly remember it now, but I must have understood it at the time, because we tied for fastest team to solve it, and a few hours later Sarah had me hint a team on it.

We were told that our next location was the “overnight location,” another hub where we’d be solving a bunch of stuff. This was thematically the invite-only frat party, and we were the first team to arrive. At the time, this made us feel like badasses, because we thought we’d finally passed everybody. In fact, we’d solved one puzzle less than The Gray Old Ones, who walked in a few minutes later. GOOs, if we looked smug, know that we now know our place. But I’m glad we got there early, because one of the puzzles at this location was outside, and there was a massive storm brewing. Would we solve the puzzles? Would we keep the partially unearned “lead”? Would we make it out alive? Tune in next time! (Spoiler: I am alive.)

Recap: Miskatonic University Game, Part 3

(This is a recap/review of the Miskatonic University Game, which happened on August 15-18. Puzzles and solutions are not currently online but should be posted eventually, likely here. This post will likely contain spoilers.)

Happy Labor Day! Two days ago, Jackie and I won the prize division of this year’s Labor Day Extravaganza, the Revs salvaged a tie, and I have not, to date, died of a mosquito-borne disease. Decent Saturday.

So before I continue with the Miskatonic recap, let me comment on two big picture things. At the end of Part 2, I mentioned that we were surprised to be solving yet another puzzle in Newburyport; all of the puzzles happening within walking distance were feeling a lot like a BAPHL (or DASH or DCPHR for those of you who don’t live in Boston). The structure of this Game did seemed like it was based primarily around a handful of BAPHL-like robust locations (the Castle Friday night, Newburyport Saturday morning, the overnight location I can’t remember the name of right now, and then downtown Boston on Sunday) with a smattering of one-puzzle locations between the big nodes.

On one hand, I totally understand the advantages of that setup from a construction perspective; there are probably only so many locations that can accommodate many teams, so you want to make use of those locations as much as possible if you have them, and it’s also probably easier to skip teams past puzzles when the puzzle after the next puzzle is within walking distance. On the other hand, as a New Englander who’s spoiled by having 2ish local walk-around hunts in my backyard every year, it felt weird to spend both money and sleep to do a bunch of them in a row. We weren’t in our van nearly as much as any of us expected, and that took the “adventure” feeling down a few notches. That said, running these things is a logistical nightmare, and I support design decisions that mean less stress for the saints that are organizing.

Another thing I want to comment on, as alluded to above, is “skipping”… unlike in most puzzlehunts, teams in the Game are traditionally skipped past puzzles without explicitly being told it’s happening. In this Game, the puzzles fit into metas, so you might discover you skipped something when, after solving six puzzles, you reach a meta and are provided a list of eight answers, two of which you might not have seen before. There also aren’t explicit standings during or after the event (at least I didn’t think so, but more on that later), so what’s the motivation to solve quickly? I can think of at least three reasons: (1) Keeping up with the top teams makes it less likely that you’ll skip a puzzle. (2) Arriving at locations early makes it more likely that the locations are comfortable and have good solving space. (3) I just think solving puzzles with the goal of finishing quickly is fun.

In any case, we were trying to go at high speed throughout, and since we were never fed an unearned meta answer, we were put on “pause” due to not having puzzles available a couple of times, and we even earned one explicitly bonus puzzle, we were pretty confident that we got to see everything. So imagine our faces when data/statistics were released to teams last week, and it turns out we DID skip a puzzle! Dagnabbit. I blame the ^#%$^@ boats. We were one of five teams to solve 45 out of 46 puzzles; congrats to the Burninators and The Gray Old Ones for being the only teams to move fast enough to see everything. (The GOOs is Brent Holman’s team, and I knew they were the only ones to see one puzzle in the Famine Game, so this was not a surprise; and I didn’t see Wei-Hwa Huang from Burninators at most of the Saturday stops, so they were clearly staying ahead of us.)

This could be a post by itself, but I really need to keep making progress while I still remember some of what happened, so:

Saturday, continued

The last stop in Newburyport was a pond (lake?) where we were given a tiara and handout shaped like the tiara (which, fun fact, I didn’t notice at first). The person giving out puzzles also recommended we choose a place “near one of the birdhouses,” which was doubily useful because I don’t think I would have noticed one birdhouse, much less that there was more than one. We needed to gather info from birdhouses all around the pond (lake?), and we sent a couple of team members to go looking… But our team mojo was still not at maximum function, and instead of suggesting that the teammates text us info as they got it, we waited for them to do a full lap. Which took a while, because it was a big pond (LAKE?). Once we had the necessary info, all of which was pre-existing but some of which the constructors had to rebuild at the last minute when a birdhouse disappeared, we drew some lines and solved a puzzle and left with a tiara (possibly being worn by Princess Tanis at the time).

Now we finally got to drive somewhere (forgive me for forgetting where) and it wasn’t totally clear from the instructions whether we’d need to solve something on site or if someone could pick up something to bring back for solving in the van. So we sent Scott into the park initially, and he came back to confirm that, no, he could not bring the display of sixty boxes with him. This was my kind of puzzlehunt puzzle, in that there was an immediate task you could sink your teeth into (taking lots of superimposed sets of letters and figuring out what words they represented) but still having a nice aha to work out (the numbers on the sides of the boxes indicated the lengths of *adjacent* words in clues, and stringing the words together to form clues was a satisfying challenge). This was one of many puzzles in the weekend where I collected a bunch of data and wrote it down in handwriting half the team couldn’t read, which slowed us down, but it felt like we picked up some time on the teams we were competing with, though the data dump suggests that wasn’t really the case.

Next stop: Georgetown, MA, where some boards with photos connected by colored strings, conspiracy-theory-style. (These puzzles were starting to feel not-very-Lovecraft-themed.) It didn’t take us too long to notice the pictures were cluing MA towns (it helped that half of us were local and one of the images was, well, Georgetown), giving us a bunch of sequences of towns and no idea what to do with them. This location was extremely sunny as well, so our brains were being fried as we stared at our town lists.

I had plugged my phone in to charge in the van, and for reasons I won’t get into, I couldn’t go back to get it. So I was suggesting things we might want to look up (without being able to do it myself) leading to a testy exchange with a teammate. This caused me to storm off and stand under a nearby tree with my copy of the town lists, which was a blessing in disguise, because by abandoning all possible outside reference options, I tried just pulling letters from each name, and noticed I could spell one of the town names with letters from town names. I returned to the group, and we were able to work out a town-name-to-letter cipher to produce seven town names and thus seven letters, which we anagrammed to form an answer. I still don’t know if there was supposed to be a less haphazard way to decide which letter to pull from each town (rather than just a constrained cryptogram) but we definitely banked “send Dan off to sulk” as a potential solving technique for the future. This was another stop where it felt like we made up time, but the solve data suggests that if we did it was minor. These stats are super-interesting, but also very ego-deflating. Maybe those are both good things.

This is a completely random place to interrupt the narrative, but it’s getting late here and tragically it is no longer the season in which academics can sleep in. I may have to speed this recap up in future chapters.

Plug: Mark Halpin’s Labor Day Puzzles 2019

I’m still in the middle of blogging the Miskatonic University Game, but as it’s the Saturday before Labor Day, I would be derelict in my duties if I didn’t remind you that Mark Halpin’s annual Labor Day Puzzle Suite is premiering today at 1pm Eastern. This is traditionally one of my favorite online puzzlehunts of the year, as Mark’s puzzles are usually very challenging but elegant and fair. Solve, enjoy, and tip!

This will also be my first puzzle-soccer-conflict day in a while, as the Revs play at home tonight at 7:30, so under non-puzzle circumstances we would probably show up to tailgate by 5 (and I doubt we’ll be done solving by then). On the other hand, my region of Massachusetts is currently beset by lethal EEE-infected mosquitoes, so I’m not sure I ever want to go outside after dark again. Off to the drug store now to buy all of their insect repellent.

Recap: Miskatonic University Game, Part 2

(This is a recap/review of the Miskatonic University Game, which happened on August 15-18. Puzzles and solutions are not currently online but should be posted eventually, likely here. This post will likely contain spoilers.)

Friday at the Castle

Hammond Castle did not disappoint as a thematic setting; when we arrived, Chancellor Red welcomed us to the Activities Fair and ushered us across an honest-to-goodness drawbridge and into a stone basement with lots of art and antique displays. We were also given an envelope full of puzzles, and while no time limit was announced, we had a self-imposed urgency based on sleep. Once we finished, we’d need to travel for an hour and get as much sleep as possible before traveling another hour. (That second hour would theoretically be a good time for bonus sleep, but it’s tough to nap when you’re geared up to start a puzzlehunt.)

I think we finished relatively early compared to the pack, though two things slowed us down. One was team strategy; even though 5/6 of us are on Setec Astronomy, we’d rarely solved together as a unit and didn’t have much of a rhythm. We divvied up puzzles and went our separate ways immediately, when we probably would have benefitted from giving every puzzle a first look as a group so that each subgroup would move forward with the wisdom of the whole team. (Speaking of the team, I don’t think I’ve formally mentioned who I solved with: my Mystik Spiral teammates included my Famine Game allies Eric Berlin and Scott Purdy, plus college-and-beyond friends Tanis O’Connor and Jenn Braun, and one of the most pleasant human beings on earth, Todd McClary.)

So for example, I went off on my own with half a list of scavenger hunt items and quickly found one, a green statue of a nude person with a fig leaf. I was hoping once I figured out what area of the castle the puzzle referred to, the rest of the items would fall quickly, but it turned out the puzzle referenced items throughout this floor of the castle, and walking around with one of two pages was not particularly efficient. I also noticed while wandering around that a bunch of people were gathered around a table full of flags in one room, and I figured one of our puzzles would eventually send us there.

The second slow-down factor came from something we were warned about in advance, the lack of cell signal and wi-fi in most of the puzzle area. Essentially we had to walk upstairs or outside to get any internet, and even then both signals were inconsistent and unreliable. This was pretty rough given that (a) some puzzle required research, (b) answer submission was online, and (c) hints were sporadically distributed online. It was annoying to have to venture out of the castle just to see if there might be a hint, and to not be able to instantly check suspected answers.

While I floundered on my art studies, two teammates were making steady progress on a sheet-music-based puzzle, and I think they solved the whole thing modulo a nudge on the extraction from teammates once we re-merged. I passed on the art runaround to teammates who were more patient and thorough at searching, and instead did something I was better at by providing an extraction aha for the sports puzzle others were working on. At some point I also realized that our web app (hard to access inside, remember) referenced four puzzles instead of three; the flag table was not something that would be pointed at by something in our packet, but in fact it was a self-contained puzzle we had not been paying attention to.

Some of us started getting data on that new puzzle, which involved a list of crossword clues and a lot of information on flags, while others found enough art pieces to extract a message telling us to request a copy of the MU humor magazine. Scott pulled me aside to work on the Jumble puzzle we’d been given (I think the two of us also worked together on the awesome pro wrestling Jumble in the 2018 Mystery Hunt) and we discovered the “humor magazine” was actually about humors, a very nice touch. From there, we proceeded fairly smoothly (once we found a 4G spot outdoor to bring up the Wikipedia article on humorism).

As we solved that, the sports puzzle fell as well, leaving the flags. Our two biggest obstacles on this puzzle were not noticing early enough that the clues on a handout were also on the flags themselves (giving us a clue-to-flag correspondence that we were working without for a long time) and not being able to interpret the hints, which told us there was another thing in the castle that applied to this puzzle. The hint said we needed something “besides the table,” but I misread this as “beside the table” and was focused on the flag room itself; it turned out we needed to go back to the biggest hall and apply the puzzle data to ten colored banners hanging from the ceiling. Once we had all the inputs, this puzzle involved some very pretty wordplay, and solving the fourth and final puzzle gave us access to the The Freshman Facebook meta upstairs. Actually, let’s just call it the Freshman Facebook meta, it’s cleaner.

Teams had been asked to send a photo of each team member (with a gimmick that varied by team) to facilitate construction of this puzzle, and each of the puzzle answers (HEADGEAR, PROJECTILE, etc.) referred to items that might or might not appear in a given photo. We were presented with a large array of these photos with a “major” listed under each one. We briefly considered things like connecting dots, binary, Braille, etc., but enough of the majors started with vowels that we suspected we’d be reading off an acrostic, either by answer or overall across the grid. We got enough letters to wheel-of-fortune out the answer, and at this point our teamwork was functioning better than it did at the beginning of the evening, as we entered after another team had already started work on the meta and left before they were done.

Our team was asked to send pictures featuring our favorite number, and while my picture appeared in the puzzle (unlike a couple of my teammates), my number was cropped out. I’m not surprised by this, because the number-related answer was PRIME, and my picture featured the number 511 formed from two soccer jerseys with the numbers 5 and 11. Since 5 and 11 are prime but 511 is not, I can see how this would have confused the hell out of people if the photo wasn’t edited. Sorry, organizers!

The trip back to Dedham was much less trafficky than the rush hour trip to Newburyport. As we disembarked and half of us headed to a nearby hotel, we noticed that a tentacle holding a pencil (now on my refrigerator) had been added to the MU logo on the side of our van when we weren’t looking. I thought these might eventually become puzzle content, but they were just a neat thematic touch. That night I got as much sleep as one can get on an air mattress the night before an event one is excited about. Which is to say, not very much.

Saturday morning in Newburyport

The trip to Newburyport was also straightforward, with a brief breakfast stop at McDonald’s en route. Side note: Leading up to the event, our team had some internal debate over whether we should bring food for meals or just for snacks. We eventually settled on snacks, with a majority of the team suggesting we plan to get meals on the road. I said something about stopping at places that would be quick like McDonald’s, and the response I got could be paraphrased as, “Ha ha ha, we are adults! Unlike you, we do not eat garbage.” Well, we stopped at McDonald’s twice on Saturday, and it was not my idea either time.

Our team sat down at a table in the first location to find an exam book, since college always has exams on the first day, right? Once things got started, we found that the exam book was one of three active puzzles, with a Horology puzzle based around the exam book, a Math puzzle based on a Power Point presentation that the organizers had some difficulty starting, and an Anatomy puzzle based on a timed appointment that was more than an hour away.

Once the presentation got started, my instinct to write stuff down was defeated by other people’s instinct to photograph/video the slides, which was definitely easier to work with. The puzzle involved solving some straightforward “D in a W = 7” style puzzles with an extra snag of determining what base the right-side numbers were expressed in. Meanwhile, other team members had discovered (likely in part due to the throngs of people that had assembled near the back of the room) that the clock opposite the presentation screen was changing every few seconds. This data was even harder to collect, but we split into data collection and semaphore-deciphering, and applying the resulting message to the cities and letters in our exam book got us to an answer.

With the two available puzzles solved and our Anatomy appointment still some time away, we unlocked Cartography, an overlapping map jigsaw puzzle requiring us to walk around the surrounding town and retrieve letters missing from photos. We assembled the map and then walked around as a unit collecting letters. We were able to wheel-of-fortune the answer from a little over half of the inputs, which was perfect timing as we got the solution as we were walking back for Anatomy. While walking, we also noticed what appeared to be a puzzle distribution stop, so we knew there was likely to be at least one more puzzle in Newburyport.

Anatomy was an extra-large game of Operation that was not that much different than playing regular Operation; in fact, the Operation step felt kind of like busywork, since we only needed to know which items were at which body part, which we could tell by looking at the board. (If we set off the buzzer on an item, we had to drop it and try again, but doing that wasn’t that different from a continuous try… This activity might have been more interesting if buzzing forced us to immediately hand the “tweezers” over to someone else on the team.) Having collected the data, we were also handed a bag of all the things we extracted–which we never used, so this felt like a waste of organizer money, although I imagine it would have been necessary if a team’s data recording was flawed. We considered a few wordplay ways to use the body parts and items, and one of our early theories was correct. This sent us to the station we’d observed earlier, and despite the fact that we’d already passed it, we still got a bit lost en route.

The next puzzle… oy, the next puzzle. The web app suggested we should get lunch during this puzzle if we hadn’t already, and it’s a good thing we did, because we were stuck on it for over an hour, and at least we were stuck on it for over an hour with pizza. The puzzle had two steps: photographing a set of mosaics of sailboats along the river, and then matching pieces of construction paper to irregular tiles, after which we’d connect the holes punched in the tiles to form letters. Our main problem was that we repeatedly assigned the right letters to the wrong mosaics since their tile shapes were very similar, and even given enough hints to know how the entire extraction worked, we could not reassign enough letters to squeeze out an answer phrase. After struggling on this forever, we finally decided we should start from scratch and re-check all of the data, and I think we had to revisit every mosaic before getting an answer. Leaving the exam room we thought we were among the fastest teams, but we definitely squandered any lead we had on what I would refer to for the rest of the weekend as the ^#%$^@ boats.

Each of the answers to our puzzles so far was the title of a textbook, and at our next stop (still on foot) we were given covers to all of those textbooks, with dotted lines along which to cut them apart. The resulting pieces had some letter overlap, and we combined them into a frankentextbook with our metapuzzle answer. Having spent hours walking around Newburyport, we were ready for closure and a change of scenery, and so we eagerly consulted the web app for our instructions to go to… another on-foot stop in Newburyport? Come on.

Even though that next puzzle was still within walking distance, it was part of a new “round,” so we’ll pick up with that in the next post.

Recap: Miskatonic University Game, Part 1

(This is a recap/review of the Miskatonic University Game, which happened on August 15-18. Puzzles and solutions are not currently online but should be posted eventually, likely here. This post will likely contain spoilers.)

You didn’t need any posts in June or July, did you? I’ve been doing a lot of traveling this summer, including two weeks in France to see the knockout rounds of the Women’s World Cup, five days in Colorado to get a nasty stomach virus during the National Puzzlers’ League convention, and most recently half a week in North Carolina, my first visit to the state since living there for three years in the early 2010s… the casual racism is still embarrassing but the biscuits are still delicious.

So far the puzzle highlights of August have been the Melbourne University Maths Society Puzzle Hunt (MUMS), which my team unexpectedly won, and the long-awaited Miskatonic University Game in the Boston area. I was going to cover them chronologically, but MUMS solutions still aren’t up (and there are a lot of questions I need answered about that metapuzzle before I talk about it) so Miskatonic gets first honors.

A couple of things to note before I start writing: One is that I’m not going to try to document every puzzle we encountered, because there were a whole lot of them. Word is that they’ll be posted online in the near future, and Matt Gruskin, showing far more patience than I possess, put together a marvelously detailed blow-by-blow writeup here. (Two of my teammates also wrote reports on their perspectives, if you’d like to hear from Eric and Todd.) I’ll comment on some of the more interesting, memorable, and/or problematic puzzles, but there will be an emphasis on my team’s experiences, both during and between the puzzle solving.

The second point I want to make is that no puzzlehunt is perfect, and so I am certain that I’ll have critical things to say; but overall, this was a really fun event, and so my nitpicking should not be read as lack of appreciation. The Game is almost certainly the most difficult puzzle event to produce (the Mystery Hunt requires more content creation and testing, but I can’t even wrap my head around the site procurements and legal red tape necessary to host an event at more than a dozen locations in one weekend), and just because I have isolated complaints doesn’t mean I don’t have immense respect and gratitude for all the work invested by Sarah Leadbeater, her puzzle Nathans (Fung and Curtis), and the rest of her eldritch minions in order to make this event happen.

Disclaimers processed? Cool. Let’s roll.


As new Miskatonic University students, before our classes started on Saturday morning, we had a freshman orientation to attend in Gloucester, MA on Friday night. (At least our orientation was Friday; the organizers added in an alternate session on Thursday that allowed them to accommodate more teams.) Based on the number of people they said they could fit in, some participants on the escape room Slack I frequent had hypothesized that the orientation would be held at Hammond Castle, so I was surprised when we were told to show up to a random fraternity hall. That is, I was surprised until we were told we would be eating at that location and then proceeding to another, which I correctly assumed would be the castle.

Despite being advised to spend Friday night at a location near Newburyport, my half-local team had decided to spend the night in the Boston area, since it formed roughly a temporal equilateral triangle (one hour per side) with Gloucester and Newburyport. Or at least I thought it did, but after making plans, it occurred to me to check travel time during Friday rush hour, which was when I discovered we’d want to allot 2-3 hours for the first travel leg. Oof.

Speaking of “Oof,” I arrived at Jenn’s (our Boston homebase) to be immediately told, “Don’t freak out.” Despite her confirming with Budget two weeks earlier that they would have our van, confirming with Budget four days earlier that they would have our van, and BUDGET CONFIRMING WITH HER two days earlier that they would have our van, Jenn had gotten a call an hour before pickup that they did not have our van, and was that okay? No, it was not. Budget Rental Car Denham doesn’t have a Yelp page, but if anyone’s considering renting from them and accidentally stumbles upon this article (and has read this far for some reason), RUN AWAY AS QUICKLY AS POSSIBLE. Jenn and her husband started calling every rental place in town, and thankfully Adventure Vehicle Rental in Allston had a van available day-of. In fact, it was way nicer (and according to our two drivers, easier to drive) than I expected. They do have a Yelp page that’s actually riddled with negative reviews, but our experience was delightful, especially considering the alternative.

The one real drawback to our new van was that the built-in GPS made extremely poor decisions about our route to Gloucester, so after driving straight through Boston during rush hour, we got to the first location after dinner was already being served. The volunteers handling registration seemed a bit testy after having dealt with lots of other teams… we kind of wanted to grab food before submitting waivers, but they insisted on having the waivers first, presumably in case the pizza toppings were poisonous. However, when we explained one of our team members was parking the van, they didn’t seem to understand why that meant we couldn’t yet hand them six signed waivers. But once the initial chaos resolved, we received nifty non-name-specific student ID cards, collectible plastic MU cups, and some tasty pizza. We also got a car mirror hanger designed to remind us that due to our van’s excessive height, we would not be able to park in a garage near the end of the event (we were reassured an alternative lot would be provided) but that unlike many unprepared college freshmen, we could survive a trip down Storrow Drive if necessary.

I realize I haven’t even gotten to any of the puzzles yet, and they awaited at Hammond Castle after a run-down of the rules and instructions on how to use the event website. But the clock just struck midnight here, and since there’s no Game going on, I’m actually going to sleep. More solving-relevant content to come.