Welcome to Follow-Up Friday!
By this time, you know the drill. Follow-Up Friday is a chance for us to revisit the subjects of previous posts and bring the PuzzleNation audience up to speed on all things puzzly.
And in today’s post, I’d like to follow up on last week’s murder mystery post.
In the previous post, I gave you some of the backstory and logistics of our in-office murder-mystery event, and today, I wanted to discuss the event itself.
Our murder happened Monday night — the fictional J. Augustus Milverton Puzzlenationo would breathe his last breath near the photocopier — so Tuesday morning marked the official start of the game.
And since we’re an office full of puzzlers, the morning began with something of a logic puzzle, as the players were given a list of passcodes used to enter the building, but they needed to figure out who had used them and at what time.
You see, someone’s passcode being used at a certain time didn’t necessary mean that person was actually entering the building at that time. Someone could’ve used another player’s code. (Information involving times and identities was scattered throughout emails to all 10 participants, so it would take a fair amount of cooperation to unravel this.)
But since all of the players were suspicious of each other — which was wise, given that several “solvers” were actually following my orders throughout the event to fulfill certain tasks — the first day didn’t involve as much cooperative solving as I’d hoped. (That would come the next day out of necessity, as alliances began to form and more information was shared.)
As I fielded questions from players asking for further details — and several clues were discovered and analyzed — the first of several complications for the players was revealed: a fellow player was “killed.”
This not only upped the stakes for the players, but led to one of my favorite moments in the game. You see, when a fellow player stumbled upon the body, he wasn’t sad that his coworker was dead…he was sad because he couldn’t ask him any questions. (Though, intrepid solver that he was, he asked if a Ouija board was out of the question.)
For the rest of the day, I was fielding all sorts of instant messages and emails from players, asking for information, cashing in Holmes Tickets, clarifying things, and trying to fit the pieces of the puzzle into place. Early theories emerged. Some were wild guesses, and some were surprisingly close to the truth.
Our event played out in real time, so the players were aware that things could happen outside the workday that would impact the game. People seemed reluctant to leave, just in case they missed a clue.
Day Two opened with another red herring — punny threats sent to three of the players, delivered in envelopes that pointed to another player (a gambit by the killer to put the spotlight on someone else) — and a few secrets had already come out.
Players openly offered information to each other in a group email, which helped resolve some red herrings and put other pieces into place. More clues were uncovered, but the murder weapon remained elusive.
Lunchtime was orchestrated to be a tipping point. Not only would another murder occur, but other plans and clues would come together. I gave one of my collaborators two missions to accomplish while the players were away from their desks. Hopefully, she’d be able to accomplish both, but at the very least, she had to accomplish one of the tasks.
There were a few of these open-ended narrative moments written into the story where the players had the chance to surprise me with what happened and what didn’t. Not only did those moments make the game more fun for me to run, but it gave other players chances to really inhabit their characters and get into the performance side of the gameplay.
Lunchtime allowed for more group theorizing — something that the workday hampered, as you might expect — but the real fireworks awaited players upon their return.
A trap was sprung, and another player died unexpectedly. Although some chaos did ensue, most of the players realized this latest death was the work of another party, and several of the players solved it quickly before returning their attention to the first two murders.
In the midst of all this, two real-world complications arose on Day Two.
The first involved a player dropping out due to a mix of time constraints (she felt the game was distracting her too much from work) and general frustration with the format of the game (which, for someone unfamiliar with immersive storytelling like this, is totally understandable). I was sad to see her go, and adjusted the story accordingly, recovering a clue from her and redistributing it to an active player.
The second involved the pace of the game itself. I’d hoped to run it over the course of Tuesday and Wednesday and have it wrapped up that second day. But between the elaborate unfolding plot and the difficulty in balancing gameplay with, you know, actually getting our work done, things were progressing more slowly than expected.
That darn workday. Such a nuisance.
So the game rolled into Day Three, and players could sense the end was near. Most of the puzzle pieces were there for the taking, and several compelling theories emerged. (Honestly, one of them was better than the story I’d actually written, which was both funny and a little humbling.)
To add a bit of drama, I set a deadline of mid-afternoon. If the murders hadn’t been solved by then, the killer would escape scot-free.
Things finally steamrolled to their conclusion when the murder weapon was revealed — in the hands of a thief who had been woven into the plot — and one of the players came close enough to cracking all three murders that I declared the mystery solved. (And our ace detective did so before the deadline, so no escape for our dastardly murderer.)
It was different from any murder-mystery event I’d run before, and everyone seemed to enjoy it. There were certainly flaws in execution, as there are in any first attempt, but I learned some valuable lessons in this play-through that will make other such events in the future smoother, more satisfying, and more engaging.
Although…I hadn’t considered the potential consequences of the event on workdays going forward; everyone seems a bit more wary of each other. (And there are a few vengeful “spirits” lurking about, hoping to avenge themselves in future games.)
Thanks for visiting PuzzleNation Blog today! Be sure to sign up for our newsletter to stay up-to-date on everything PuzzleNation!
You can also share your pictures with us on Instagram, friend us on Facebook, check us out on Twitter, Pinterest, and Tumblr, and explore the always-expanding library of PuzzleNation apps and games on our website!
Pingback: It’s Follow-Up Friday: 2016 Countdown edition! | PuzzleNation.com Blog