So, a third game I ran at Big Bad Con was Locus. Locus has intrigued me for a while because it plays around in the Silent Hill inspired space that I enjoy so much. It is definitely a passion project built by someone who I genuinely believe played it a lot.
In this instance, I used the sample scenario provided with the game. The premise of Locus is that locations have souls based on their reputation or historical providence. It’s possible for people to wound these souls by doing things that ruin or tarnish a location’s essence. Having been wounded the location falls into a kind of violent depressed angry slump that sucks in everything around it. In short, it’s a Haunted House game.
In this case the Locus was The MFV Mulligan, a large fishing vessel known for being lucky. The captain plotted with the ship’s owner to scuttle the ship for the insurance money. The captain brought the ship’s engineer into it who hesitated at the last minute but the ship ended up impaled on a damaged oil rig. Half the crew was thrown overboard and killed in the collision, the other half mutineed and killed the engineer and then were killed when monsters started manifesting because of the Locus going evil.
The game’s prep procedures are very clear. The GM basically prepares a toybox consisting of the following:
- The Locus. This is mostly about the backstory that led to it going bad. This game definitely believes in maps, although not as detailed as one might find in a D&D-style scenario.
- Set Pieces. These are little prepared events. Some of them might be placed in specific places but a lot of them are things that could happen anywhere at any time. Two examples from this scenario.
- The corpse of the engineer around which can be heard the sounds of his murder. This one is in a fixed location on the map.
- A ghostly conversation between an older sailor and a younger anxious sailor in which the older sailor assures the younger one that The Mulligan’s good luck will protect them. This is one that can happen anywhere.
- Spot Effects. These are similar to Set Pieces except they target specific players. In Locus all the player characters have something emotionally weighing on them. In its violent depression the haunted location starts manifesting these emotions. These are all written to happen anywhere, anytime at the GM’s choosing.
- One of the characters in the game I played had caused a woman to lose custody of her child. The scenario lists one of their Spot Effects as seeing the woman’s silhouette walking about the ship.
- Clues. These are anything that reveal the backstory of the location. Again, some have fixed locations like the correspondence between the owner and ship’s captain plotting over the insurance scam is located in the captain’s quarters. But most are free floating like the word Mulligan written over and over on a wall circling the word Lucky which is scratched out. The GM is told simply to bring these up whenever they want.
- Monsters. Monsters are not placed on the map like you would in a dungeon exploration scenario. They are to be fielded whenever and wherever the GM wants. Monsters have three sources.
- The Locus Itself: This is kind of a “boss monster” that represents the wounded angry soul of the location. However, fighting and killing it is not ideal as the result is the total destruction of the location. It’s very much the “and then the haunted house burned to the ground” outcome. In this case that’s The Scylla which looks like a floating, chained up mermaid with a harpoon through her.
- Any NPCs Trapped In The Locus. In this case that’s just the captain. The Piscator which looks a bit like a fishing net of tentacles wearing a rain slicker and cap.
- The PCs Themselves: The GM is supposed to derive one unique monster type from each PC. This game had two so that meant The Neglect which is a kind of fungus that grows on safety equipment and The Toll, a kind of spider-like monster made of flesh stretched over machine parts.
- Finally, the GM is supposed to have some idea about how the location could be healed. This is the better option than killing the boss monster. In this case there is a giant gaping hole in the ship (a literal wound) that needs to be repaired and the ship started again.
When I was looking over all this I noticed two things. Positively, none of this is organized into a “plot”. There are no scenes. The clues don’t point anywhere specific. It’s just a collection of stuff about the location.
However, I also note that much of it is of limited interactivity. The monsters exist primarily to fight or run from. Everything else is inert or recorded memories. It’s purely experiential and informational. What exactly am I, the GM, playing?
One take is that I’m playing exactly one entity: The Locus. The Locus is in pain and is lashing out both in anger and as a cry for help. Set Pieces, Spot Lights, Clues and Monsters are its methods of communication. In some ways I’m reminded of the board game Mysterium in which one player is trying to communicate something to the other players but is only allowed to do so by selecting from a hand of cards with paintings on them.
But does that just add up to the ghost of Bobby G? A sort of time release panama canal? I was hoping to find out by playing this and… I kind of didn’t because of what actually happened.
Thankfully, the game does not frame the player characters as a team of “location healers” or anything like that. It’s pretty clear that the player characters are to be built as ordinary people attuned to the subject matter suggested by The Locus. In this case, the PCs are tugboat operators who receive a distress call from The Mulligan. They are told that the tugboat operation is in dire straits financially and that if they can salvage The Mulligan and rescue any survivors they’ll get a substantial cut of the insurance money which is necessary to keep the business afloat. Their livelihoods depend on it.
This was the very last slot of the convention, so it was unsurprising that I only had two players. One was the tugboat’s engineer who had previously caused injuries with lax safety inspections and a deckhand who had caused a woman to lose custody of her child.
The two men board The Mulligan while their own captain stays behind. They head straight to the bridge tower where they find a young deckhand named McKay who tells them about the mutiny and they discover the correspondence between the captain and the owner about the insurance scam. They also find a newspaper article about The Mulligan’s unusually lucky past.
They also witness several ghostly events. They see ghostly images of the first mate ransacking the captain’s quarters. They see a figure that flickers in and out of existence at the ship’s wheel. The deckhand sees the silhouette of the woman he wronged walking along the deck of the ship. They see ghostly figures through a skylight wandering around in the ship’s kitchen below.
And then they encounter their first monsters. They come across some patrolling Piscators and that’s when they decide to NOPE out of there. They engage in a fighting retreat back to the tugboat.
On the tugboat they discover that their captain has locked himself in the console room and appears to be bound up by a fungus growing out of a dead cat. They also can’t find McKay, who they had sent back to the ship first. They decide they’re going to cut the tugboat loose, go into the lower deck, tear open the engine and try to override things to get it started and just hope someone picks them up out at sea.
Below deck, they encounter The Toll and fight their way past it to the engine room. While the engineer tries to start up the tugboat, the deckhand searches for McKay but only catches little glimpses of him here or there but is never able to fully find or interact with him.
The engineer finally manages to start the engine and they pull away from The Mulligan. At this point I asked the players if they had any problem ending the session early and they were both fine with it. So I just said, “The tugboat heads out into the eerie sea, and you are never heard from again.” (More on why I said this in a bit). They both laughed and said, “Yeah, that makes sense.” The whole game lasted 90 minutes.
Here’s the thing I want to focus on about this particular play experience. I think some people would consider this session a failure. They didn’t solve the mystery or solve the problem. But I argue that it was incredibly successful because every moment of play was very genuine and sincere. There was an incredible and palpable sense of authenticity underlying the whole thing.
These two guys were completely committed to the idea that they were playing two blue collar guys sent to do a job. And when that job turned out to be full of monsters, something they are not used to, they decided to flee. They even had the conversation about the insurance money and the tugboat’s financial problems and landed on: they can find another job, they can’t find another life. They aren’t heroes.
So why the bummer ending of, “they are never heard from again”? On the surface, that can look like punishing the players for failing to engage the scenario but it’s actually a function of the rules. You see, Locus takes into account that the players might try to run or even end up in a kind of “lie down and give up” state.
There’s one other thing the GM is supposed to prepare when building a Locus. The Layers. Generally there are three layers. These layers are basically like sub-dimensional versions of The Locus each one progressively more haunting and weird than the previous. It’s like literally sinking into depression. So when you’re going over your map, you’re supposed to write three descriptions of each area, one for each layer. For example, the hole in the ship goes from just being a hole on Layer One to an actual bleeding, fleshy, infected wound on Layer Three.
Now, here’s the thing, there are things that can only happen on certain layers. Deckhand McKay can only be found on Layer One. Monsters don’t show up until Layer Two. The Captain and The Scylla only exist on Layer Three. Most importantly escape is only possible from Layer One. When the players started the tug boat they were on Layer Two.
How do the players move from Layer to Layer? Over the course of the game, the players draw playing cards from an ordinary deck. When all the players have 4+ cards they are on Layer Two and when all players have 7+ cards they are on Layer Three. Falling below those thresholds moves them up a Layer.
Players draw cards when they encounter Set Pieces, Spot Effects, Monsters, act according to their character’s Vice and every hour of real-time play. Players automatically discard any cards whose suit matches the suit of their Virtue and they can discard other cards by acting in accordance with any of the four Virtues available in the game.
When I saw how little interactivity the GM prep typically has, I began to wonder where the opportunities to act virtuously were supposed to come from? My own guess was confirmed by this play: by taking action toward each other.
The players actually did manage to discard a couple of cards while engaging The Piscators. They really demonstrated they had each other’s backs. They were going to make it out alive and they were going to make it out together. They waited for each other and they defended each other. One of the virtues is about community solidarity and they were able to discard a couple of cards. For a minute, I thought maybe they were going to make it back to Layer One. But alas, they didn’t quite ditch enough cards and picked up a couple more when they saw the captain and fungus cat and encountered The Toll back on the tugboat.
So that’s why they were never found again. They basically ended up in the “stalemate” condition where they neither truly escape nor heal or destroy The Locus. The game specifically calls this condition out and says the characters become forever lost in the sub-dimensions.
I kind of want to play this again with a Locus of my own design and characters of the players own making.