Monday, 18 November 2024

Looking forward to Consequences

Next week, I’m off to Consequences, the freeform larp convention. I went last year, and you can read about that here.

I’ll do a post-con report after Consequences, but I thought I’d start things off with a pre-con preview covering some of my thoughts, hopes and fears. Hopefully, there won’t be spoilers.

Consequences this year in the Lakeside Holiday Park in Chichester. So there’s a bunch of logistics in getting there that I’m not covering here. I’m just talking about the games.


So the games, in order.

Thursday

Spellbound (Bjergtaget)

Written by Maria & Jeppe Bergmann Hamming and run by Mo Holkar, Mike Snowden and Quinn D.

According to the organisers, “Spellbound (Bjergtaget) is a non-verbal black box larp for 10-30 participants. The participants play either humans or creatures of the Underground. Through symbolic gestures and movement to music, a night in the world of the Undergrounders is played out. The humans are lured by and bonded to an Undergrounder, and in a series of scenes, the relation between the human and the Undergrounder is explored. Through workshops the participants learn the symbolic gestures and how to move to the music, before we all enter a world of magic and myth.”

I really have no idea what to expect. It’s a long way outside my comfort zone I have no sense of whether I will love it or hate it. (Tune in next time to find out!)

Happily, there are no costuming requirements, other than comfortable clothing with pockets. They suggest wearing contact lenses rather than spectacles, but given that if I wear contacts, then I need reading glasses to read anything, I suspect I’ll just stick with glasses. Or maybe I won’t – I haven’t decided yet.

Friday

Three games today. There’s a risk that’s too many, but I’m running the first one (and I find running games less tiring than playing them), and the middle game doesn’t need any prep.

The Stars our Destination

Written and run by me!

This is part 5 of my first contact saga (is currently called The Dark Forest). I’ve got everything printed out and ready to go, I just need to remind myself of what’s going on before I get started. (I’ll do that a couple of days beforehand.)

This is its second run – the first was online, back in June. As it’s the second run, that means it’s Timeline 2 (as I think of it), which means some of the things that were true in the first run are not true in this run. (For example, this timeline has vat-grown host bodies for one of the aliens!)

I haven’t really talked about The Stars our Destination here yet. I’m not sure why. I suspect I’ll have more to say after this run.

All You Need is Love

Written and run by Laura Wood and Ruth Trenery-Leach.

I had originally planned to have a break in this session, but this game was struggling to fill, and it didn’t look like it needed a lot of homework (or costuming), so I thought I’d give it a try.

“The larp will explore themes of music, fame, and relationships of all kinds. The setting is an alternative 1960s without sexism or queerphobia. If you have any 60s-inspired accessories, feel free to wear them, but they’re not required.  On the day, you’ll be able to choose from skeleton characters, which we will workshop together before we begin.”

So it’s another larp that’s outside my usual comfort zone (skeleton characters and workshops), but it does involve singing Beatles songs, so that’s a plus.

The Koenig Dead

Written and run by AJ Smith and Tony Mitton.

Phew – a “regular” freeform with 20 pages of detailed background and character stuff and 13 other characters with their own agendas.

This is part of a series of games set aboard a spaceship in a universe that seems suspiciously similar to Joss Whedon’s Firefly. I’m playing Alix Orban, the captain of the freighter Kestrel. I fought on the losing side in the war, which makes me Mal from Firefly. Except I’m not, there’s more to it than that.

In The Koenig Dead, we’re taking the Kestrel to the Koenig base where, hopefully, I can get my uncle the medical attention he desperately needs. What could go wrong?

Interestingly, I haven’t been given character objectives/goals – instead, I have a list of suggestions to roleplay my character, help others have fun, have fun myself (and then two game-specific suggestions – one a GM note and the other a reminder that I need to get my uncle the medical attention he needs). Was that a spoiler? I don’t think so, as my uncle’s condition is not a game secret.

The Koenig Dead follows The Linfarn Run, which is the first in the series featuring the Kestrel and many of the same characters. I’ve not played The Linfarn Run, and the character pack (character background, recent events, basic history) felt a little disjointed as it referred to events in that game before explaining them properly. I’m sure if I had played in the previous game, it would make more sense.

I notice this sort of thing because I’m taking a similar approach with my first contact series (such as The Stars our Destination, above). Hopefully, my character sheets flow – but I’m not the best person to judge. (Nobody has mentioned it as an issue, but that doesn’t mean I’ve got it right.)

There are some nice ideas in the background – I particularly like the idea of warp sinks, which affect FTL and make it harder to travel away from some stars. I have no idea if it’s inspired by anything, but I like it. (I’m pretty sure it’s not in Firefly, although it has been many years since I’ve watched that.)

I haven’t worked out costuming yet. I think I just need to look different, and captain-y.

Saturday

Two games today – I can have a lie in! (As if; I bet I’m awake at 6 am as usual.)

Do You Hear The People Sing?

Written and run by Alex Helm.

Remarkably, I think this will be the first time I’ve played in one of Alex’s games – and I’m playing in two of them this year. Alex often writes games set in the Warhammer 40K universe, and while I gather they are splendid games, I don’t know anything about 40K, and it doesn’t really appeal.

Do You Hear The People Sing is not a 40K game. Far from it – it’s a mashup of Noises Off and Les Miserables (and inspired, I gather, by this year’s West End Lullaby, where Alex played Javert.) It sounds fabulous.

I’m playing Frankie Jackson, who plays Monsieur Thenardier in Les Miserables. So I get to perform some great songs as Thenardier – but I’m also playing several minor characters and get to perform other songs as well.

The game takes place both backstage (where the character stuff happens) and on stage (where the performances happen – miming or karaoke or whatever). I’m not sure how the balance is maintained between the two (if, indeed, balance is the right word), but I’m looking forward to finding out.

Do You Hear The People Sing has the best advice on gender, race and age I’ve seen. In short, none of the actor characters are gendered – everyone chooses their gender. And the in-game amateur dramatic society’s casting policy means that anybody can play any role regardless of gender, race or age. So that means we will have a crazy range of people just playing the parts – and that will be great.

Batukh Hungers!

Written and run by Alex Helm. 

Two Alex Helm larps in one day! In Batukh Hungers, devoted followers of Batukh the Hungering God gather to conduct the holy rites and ensure their deity is appeased for another year. But times are hard for this dark cult – membership is falling, willing sacrifices are ever harder to come by, and internal plotting and divisions could spell the end. And if Batukh is not satisfied, the current age of humanity will end in blood and flame.

I’m playing “Coyote” (we all have code names), and from what I can see, it’s going to be interesting choosing a sacrifice.

Sunday

And two games to finish off. The closing ceremony happens shortly before my second game – and Sunday evening is spent unwinding.

Hillfolk

I’m running a game of DramaSystem – it could be Hillfolk, it could be Hazelwood Abbey or even Success2Soon. I’ll let the players decide.

Hopefully I’ll remember my revelation about dramatic poles!

The Roswell Incident

And finally, I’m running The Roswell Incident. This will be its third outing and will be the start of Timeline 3. (So if all goes well, next year I will run All Flesh is Grass, and the year after that, Children of the Stars, and so on. So that’s me committed to Consequences for the foreseeable future!)

Interestingly, a couple of players who have signed up for Roswell have played in later games (in Timeline 2 last year). I suspect there has been enough of a gap for it not to matter, but I am looking forward to finding out how that worked for them.

Monday

And on Monday I drive home.


Monday, 11 November 2024

Adventure Crucible: Review

Adventure Crucible: Building Stronger Scenarios for any RPG is a Kraken chapbook by Robin D Laws.

Physically, Adventure Crucible is a 52-page A5 booklet with very thin covers. (I’m keeping mine in its plastic cover.)


Adventure Crucible
concentrates on “trad” RPGs – it excludes “story games” (which in this case seems to mean anything that isn’t trad). But that’s okay; it keeps the book focused.

Adventure Crucible looks at five common RPG scenario structures: the Dungeon, the Mystery, the Chain of Fights, Survival and Intrigue. (Two others, Picaresque and Drama are lightly touched on.) I’ll be honest, I hadn’t even realised there were so many different scenario structures – but that’s probably because, for me, some of them are almost indistinguishable from each other.

Obstacles

But before we get to that, one key element of the book is the obstacle, which is broken down as follows:

Dilemma: The expression of the obstacle

Choices: The choices the players are presented with.

Consequences: The consequences of those choices.

Rooting interest: Why the players should care. (“Rooting interest” doesn’t feel like a helpful name to me.)

All RPG scenarios have obstacles with choices and consequences, and Adventure Crucible recommends that scenario designers ensure their obstacles offer meaningful choices with consequences that the players care about. Well, yes.

Scenario structures

So, the scenario structures. Below, I go into the basic structures in more detail. They can, of course, be mashed together (and often are, as a dungeon becomes more compelling when mixed with a mystery).

Dungeons

In dungeon scenarios, the characters explore a discrete physical space; obstacles are monsters, traps and physical hazards.

And I’ll be honest, I can’t imagine anything worse. I’m not a big fan of dungeon-crawling board games, but at least they have the decency to be a board game.

Tellingly, Laws opens this section with “People who tire of the Dungeon format can tire of it hard.” I don’t ever remember actually liking the format. For me, dungeons lack one of my three key pleasures of roleplaying: a plot.

Chain of Fights

In a chain of fights, characters fight a series of enemies (the obstacles). For me, there’s such an overlap between this and Dungeons that it hadn’t occurred to me that they might be different. (But then, I’ve never felt the need to run Feng Shui.)

As far as I can tell, the main difference between the dungeon and a chain of fights is that in the latter, each fight contains a clue leading to the next one. (Rather than just going into the next room, as in a dungeon.) At least chain of fights does have a plot, which is a step up from a dungeon.

Survival

In a survival scenario, the characters encounter dangers while defending something or someone, which is kind of a backwards chain of dights. Obstacles include getting whatever it is the group needs to survive.

I don’t have much to say about dungeons, chain of fights, or survival structures because I don’t find them interesting to play. They’re basically adventures about combat, and if I wanted to do that, I’d play a miniatures war game. (And I don’t enjoy miniatures games either…)

Mysteries

In mysteries, the characters investigate something.

My favourite type of RPG scenario activity is the mystery. That’s probably because Call of Cthulhu was one of my early RPGs, and Cthulhu is all about the investigation. I also create a lot of scenarios, and as an author, I find mysteries the most satisfying type of scenario to create.

Obstacles are finding clues and, in a horror game, mental distress from experiencing the supernatural.

Adventure Crucible spends longer on mysteries than any other type of scenario structure, claiming that they are the hardest to write. That’s probably true, and I’m currently wrestling with an investigative scenario that seems to be causing more problems than it really should. They certainly seem to have more moving parts than other types of structures. For example:

  • You need a villain with a plan. Adventure Crucible notes that players (and GMs running the scenario) expect the bad guy’s plan to make sense – which isn’t always as easy as it sounds.
  • You need to know what they want, and what they are planning to do if the PCs don’t get involved. (So a countdown clock or timetable.)
  • You need to know what the antagonist has done so far, so you can seed clues for the PCs.
  • And depending on how you write your adventure, you need locations and NPCs where clues may be revealed. (The book doesn’t really mention this, but clues don’t have to be fixed in any one location. A clue can pop up anywhere.)

The climax or resolution of an investigation can often be the trickiest section to write and run. Mysteries don’t always suit a pitched battle as a finale – PCs who are good at investigating aren’t necessarily going to be strong in combat. And if you want your villain to react to the PC’s actions, it can be difficult to pinpoint exactly where and when the resolution takes place.

Intrigues

In an intrigue, the characters vie for influence and power. Obstacles are getting favours or stuff from other characters, usually at a cost.

Games of Amber and Vampire are described as intrigues – along with something described as “Gloranthan Freeforms.” But I’m not sure how many freeforms (Gloranthan or otherwise) Robin Laws has played, because while I would agree that some are intrigues, many are not.

I don’t really know how to write a pure intrigue scenario (unless we are talking about freeforms, in which case I’ve written a book about that), and I’m not sure Adventure Crucible explains it properly. I happily add factions and hidden agendas to characters to create an element of intrigue, but that’s often overlaid onto a mystery (see my Perfect Organism scenario for ALIEN).

Picareseque and Drama

Two more adventure structures are mentioned in Adventure Crucible but are only lightly covered:

Picaresque, in which the characters amble around and cause trouble. (Sounds like sandbox murder hobo-ing to me. Also not my style.)

Drama, which appears to be an excuse to cram a reference to Hillfolk into the book. I’m not sure you can write a scenario for Hillfolk, as it's so player-driven.

As an aside, when I look at what I like in roleplaying games and the scenario structures presented in Adventure Crucible, I seem very limited in my enjoyment of what makes a good game. But that’s because I think most scenarios (especially one-shots) are mysteries: there’s usually something going on, a plot of some sort.

And because I find combat dull, that rules out the first three structures.

Building stronger scenarios

So has Adventure Crucible helped me build a stronger scenario? I’m not sure it has, but it’s made me reflect on some scenarios that didn’t really work and why that might have been.

Where I have struggled to engage with scenarios (and this isn’t always me running them) is often where the core activity isn’t clear. If you’ve heard Robin D Laws speak, you’re probably familiar with the term “core activity” – it’s what players do in the game: “You are X, who do Y”.

When that’s not clear, scenarios can stumble.

For example, I once played in a very short Star Wars game that didn’t make it past the first session. I can’t remember what characters we created, but they weren’t the usual Star Wars characters – they weren’t rebels or bounty hunters. Our core activity was never defined, and the game collapsed when we didn’t react the way the GM expected us to. While we really could have used a proper session zero, the lack of a core activity for Star Wars didn’t help.

Some games don’t have a single core activity (RuneQuest, Traveller), making things more complicated. For example, I don’t really know what a typical Traveller adventure is. (Unlike a typical Call of Cthulhu or Liminal investigation, which I can easily imagine.)

Other London

In terms of Other London, so far, my scenarios have all been mysteries with a hint of intrigue. (Faction power plays are happening in the background – the PCs focus on the mystery.) 

One reason faction splatbooks aren’t on the horizon is that I’m not sure what the core activity of other factions would be.

For Desk 17 it’s clear: you are police detectives investigating supernatural crimes.

But for a fae court? Or a vampire gang? Or the Custodians of the Echo? I’m not sure, and until I can figure that out the fae, the vampires, and everyone else are staying as NPCs.

Overall

So overall, while I’m not sure it’s made my scenario writing any stronger, I found plenty of food for thought in Adventure Crucible.

Monday, 4 November 2024

The Haunter of the Dark: a first impressions review

The Haunter of the Dark is Paul Baldowski’s guide to writing Cthulhu Hack investigations using Lovecraft’s story of the same name as an example.

Physically, the book is a lovely 76-page A5 book that feels like the right size for a roleplaying supplement. While written for Cthulhu Hack, the ideas and process for creating an investigation work for any investigative game. (This is the only Cthulhu Hack book I own, so I can’t tell if other adventures also use this advice.)

The Haunter of the Dark is split into four parts: Hacking at the Darkness, Horrible Abysses, Random Tables, and The Haunter of the Dark.

Hacking at the Darkness

This is the book’s introduction and explains the basic principle, which is to take a story and create an investigation around it. Hacking at the Darkness explains the basic Cthulhu Hack investigation structure:

Fascination: Hooks that lead the PCs into the investigation.

Discovery: Uncovering clues and working out what’s really going on.

Conflict: Conflict isn’t only fighting – it includes reaching hard-to-find places, or tracking down clues. It happens in parallel with Discovery.

Resolution: The final scene, where the investigation is resolved. 

Coda: The last bit of the story – a moment to reflect. (Sadly, this isn’t expanded on in the book, but I’ve found getting the players to describe what their characters are doing in an “end of credits scene” is a good way to capture the spirit of a coda.)

The introduction also covers annotating the original text of your source material. The book uses different colours of highlighter to differentiate the different types of annotation:

  • Information – revealed by a Flashlight roll
  • Stories – revealed by a Smokes roll
  • Threats
  • Unsettling imagery to repurpose
  • Background and motivation
  • Seeds and hooks

Horrible Abysses

Horrible Abysses, is the meat of the book. This is a sample (outline?) investigation that follows the events in The Haunter of the Dark. The hook is that Robert Blake has been found dead (as per Lovecraft’s story), and the investigators are investigating.

So Horrible Abysses takes the structure above, details various locations and shows how you might add clues that lead to a resolution where the investigators face the Haunter!

Locations include Blake’s apartment, Federal Hill, the Providence Journal, the police station, the library, city hall – and, of course, the sinister church where Blake found the Shining Trapezohedron.  The resolution, however, happens elsewhere – the Haunter has moved.

As for the Haunter itself, Lovecraft doesn’t say, and five entities are suggested: an avatar of Azathoth, insects from the void, a proto-shoggoth, an avatar of Shub-Niggurath, or a Mi-Go weapon. 

Unfortunately, the investigation doesn’t feel easy to run. (I’ve only read it, I’ve not tried to run it.) While it’s a great example of the thought processes that you might use when creating an investigation based on a story, I would need to do a fair bit of work to bring it to the table.

Random tables

Following Horrible Abysses are eight pages of random tables – contents of a desk drawer, things found halfway up a staircase, newspaper names. 

These feel a little unnecessary. There are some lovely entries in the tables, such as “Oddly arranged formula set down in soft pencil: won’t add up,” or “Ring with a dozen keys, all snapped off bar one.”). But for me, they would be better in an investigation so they can be rolled at the appropriate time.

The Haunter of the Dark

This section reprints Lovecraft’s The Haunter of the Dark, highlighted and annotated to indicate gameable sections.

The Haunter of the Dark, annotated

As I hadn’t read The Haunter of the Dark in about 30 years, I was pleased to read it again.

Overall

I do like seeing how someone might use a short story to create an investigation. It’s not quite how I would do it, but that’s ok. (I am more likely to take the broad strokes of the story and transplant them somewhere else – but I already know how to do that!)

It’s interesting to compare this with Graham Walmsley’s Stealing Cthulhu. The two work well together, as while Stealing Cthulhu takes a big-picture look at adapting Lovecraft’s work for gaming, The Haunter of the Dark takes a more detailed look at a specific investigation.

However, the one thing that I felt is missing is a final investigation that a Keeper can run with minimal fuss. In my mind, Horrible Abysses is too much of a proto-scenario; a fair bit of work is needed to get it to the table. I would have liked to have seen a final, tightly written investigation stripped of the discussion and options. To keep to the existing page count, this could replace the random tables.

So that’s The Haunter of the Dark. A lovely look at how you might adapt a story into an investigation.

Wednesday, 30 October 2024

Monday, 28 October 2024

Dramatic poles in Hillfolk one-shots

I’ve run five or six sessions of one-shot Hillfolk/DramaSystem now, and I’ve never given dramatic poles much attention. 

Mechanically, they don’t do much. Their interaction with the rules only occurs at the end of a session.

According to the rules: 

At the end of each episode, each player in turn (in seating order) makes a brief statement, highlighting how he entertainingly brought out his character’s dramatic poles over the course of the episode, in relation to the episode’s theme.

Any story with a theme inherently includes the opposite of that theme. A story about war is also about peace; a story about hunger is also about nourishment; and a story about love also threatens the possibility of lost love. Therefore, you can describe your character as either reinforcing or undermining the theme.

You might describe yourself moving from one pole to the other, or bringing both poles into your characterization at different points.

All participants then vote, ranking the other players in order, with #1 the best score, #2 second best and so on. The argument is just a reminder: voters base their rankings on how well the players brought out their dramatic poles in relation to the theme, not how skillfully they made their cases. Moving from one pole to another in the course of an episode is a good thing. Vote against players who, episode in and episode out, stress a particular pole and ignore the other. Players do not rank themselves. No one ranks the GM, who never gets bennies. The GM votes, too, ranking all of the players.

The GM then totals each player’s vote tally. The number of drama tokens a player has in hand is then subtracted from this number. 

The two players with the lowest scores gain one bennie each.

Bennies are the campaign currency, and are kind of like super drama tokens. In a one-shot they’re worthless, of course. 

And so, as a result, I hadn’t paid dramatic poles much attention.

However, I now think that was a mistake.

DramaSystem and Furnace

A couple of things happened at Furnace when I ran Success2Soon, my pop group playset.

First, Paul Baldowski was playing and joked that he felt that Robin Laws specialised in designing RPGs that fixed things in gaming that didn’t need fixing. In Hillfolk’s case, it’s challenging players who say, “My character would never do that.”

Second, at the end of the game, I asked the players to highlight how they brought out their dramatic poles over the course of the session. And we voted on them, with the person with the most votes “winning”.

That was interesting, and worth doing again. But next time I run a DramaSystem game, I’m going to emphasise dramatic poles even more.

Because they help roleplaying.

“She’s rich…”

The example I always use of a dramatic scene is in Star Wars (as I still think of it), or to give it its full title, Star Wars Episode IV: A New Hope.

We’re on the Death Star, and Artoo has just told Luke that Leia is in the detention centre. Luke tries to persuade Han to help him rescue Leia. It’s a dramatic scene – Luke is the petitioner, and Han is the granter.

Luke initially fails, but eventually succeeds by appealing to one of Han’s dramatic poles: money (paying off the bounty on his head). Han’s other dramatic pole at this point is loyalty to his friend, Chewbacca. 

(Luke’s dramatic poles, on the other hand, are duty [responsibility to his uncle and aunt] versus adventure [running off with Ben to join the rebellion].)

My character would do that

Dramatic poles help explain why characters do things that appear to be against their self-interest (like sneaking into the detention centre in the heart of the Death Star).

And that’s why there’s space on the character sheet for other character’s dramatic poles. It means you can use them when petitioning, and help create the drama.

And another thing: procedural scenes

While I’m on the subject of Hillfolk, I stumbled across this AMA on Reddit. To save you the effort of wading through the questions, I found an interesting point about the design of Hillfolk’s procedural system (which seems clunky written down, but works fine in practice).

Question: Hillfolk is a game I have been wanting to play for a long time now, as soon as I can find the right group for it. The procedural resolution rules seem to be quite a divisive subject among players. Were there any particular design considerations that led you to implement the system the way that you did? What kind of impact do you feel that replacing the procedural resolution rules with rules from another system (as many people seem to do) would have on Hillfolk's overall gameplay?

Robin’s answer: The procedural system is designed to do what it needs to do without pulling focus from the central feature of the game, the dramatic scenes.

Because drama is more about dealing with the repercussions of disaster than chalking up wins, the system also imposes a much higher failure rate than you'd tolerate in the procedural-focused games we're all used to.

So if you replace it with a rules system you find aesthetically alluring and like to play around with, you'll likely:

a) call too many procedural scenes

b) succeed too often at them

(Remember that if everyone wants to succeed, you just say you did, with narration, and then get back to the interpersonal interactions.)

Which I found interesting. Hillfolk’s procedural system is harder because in a dramatic game, failure is more interesting than success. I wish the rules actually said that.

Next time on Hillfolk

So next time when I run Hillfolk I will:

  • Make sure dramatic poles get the emphasis they deserve.
  • Stress that the procedural system is tough because failure is more interesting than success.

(And next time will probably be at Consequences, at the end of November.)

Monday, 21 October 2024

Furnace 2024

A couple of weekends ago I attended Furnace, the RPG convention in Sheffield. As usual (previous reports here), I ran one game and played in three others.

Furnace is a lovely, friendly convention and would be the highlight of my gaming calendar if it wasn’t for all the other lovely events I go to.

Anyway, here’s what I played and ran.

Kids on Bikes

Fergus ran Swallows and Elder Things, an investigative scenario for Kids on Bikes where we played WW2 refugees sent to the country to stay with our uncle. (We were effectively Enid Blyton’s Famous Five – including a dog. I played Bea, nine years old and the youngest.) We uncovered dark secrets of an expedition to the Antarctic where our uncle had brought back something he shouldn’t. And thanks to some bad rolls, we all died in the climax to the ancient creature we really shouldn’t have reawakened…

Lots of lovely details (tongue sandwiches, ribbons, throwing sticks for Tommy the dog) – and everyone leaned into their characters. In fact, we had so much fun roleplaying kids that the scenario overran the slot a little – but it didn’t matter. Neither did the TPK ending.

DramaSystem (ie Hillfolk)

After lunch, I ran Success too Soon, a game for DramaSystem (ie, Hillfolk). My four players played members of a successful pop band who had reached the end of their first tour. We created the characters as usual in DramaSystem, and then their manager told them their record company wanted them to sign the next contract tonight, which kicked the game off.

While the band argued about what to do with the contract, I raised the stakes by introducing a parent who wanted to remortgage the house (and was relying on their income), and a music journalist looking for a scoop. We ended up with the band fracturing and one member going their own way.

This was the first time I had run this playset and it seemed to go well. As ever when I’m running a DramaSystem game, I felt drained at the end of it – I find it a very intense game.

Anyway, I’ve now put the playbooks on Itch.

Liminal

Elaine ran The Forgotten Station, a Liminal investigation into an old book which led us to a forgotten underground station and a dangerous magical ritual. I played Morgan, one of the Hidden, those who are easily overlooked (and inspired, I think, by Neverwhere).

As always, Liminal was a lot of fun. Lots of inventive London magic by our geomancer, and plenty of in-character chat, which I always like to see. We ended with a climactic battle against the forces of darkness (we won) and finished pretty much on the dot.

Mouse Guard

For my last game of Furnace, Guy ran Mouse Guard, where we had to track down a grain peddler who was suspected of being a spy. We faced terrible hazards including rain and a mink. I played Lillye, an enthusiastic guard mouse. (It’s fun being given an enthusiastic character – you just volunteer for everything!)

This was my first time with Mouse Guard. I had the book a while ago (a rare raffle win from a previous Furnace – it’s not the sort of thing I would normally buy), but I never got it to the table because it didn’t really make sense. And although it made some sense when Guy ran it, I felt the lack of system mastery when it came to the challenges – we were nearly defeated by the rain, and in the final battle, when two of us went up against a mink, we lost. I’m not regretting getting rid of Mouse Guard, but I’d like to play it again.

As for our adventure, we had a nice time, although it would have been nice to have a bit more time for some character stuff - we were all done a couple of hours or so.

Until next year

And that was Furnace 2024 for me.

There are other conventions at The Garrison (see them all here), but they are all too close to other gaming weekends, so I give them a pass.

Next on my calendar is Consequences, the freeforming convention in November.


Monday, 14 October 2024

Traveller’s Wrath of the Ancients: First Impressions review, part 3

This is part 3 of my long review of Mongoose Traveller’s Wrath of the Ancients. This will make more sense if you read part 1 and part 2 first.

If you can’t face reading part 1 and 2, well, the TL;DR is that I think Wrath of Ancients isn’t great. It’s overwritten, badly structured and formatted and makes excessive use of lazy coincidences, signposts and information dumps. Worse, I think it would be hard work to run.

In the last two posts I went into the plot in some detail. This time I'm thinking about railroads and presenting an alternative campaign idea that fits my idea of what an Ancients campaign could be.

Riding the railroad

Wrath of the Ancients doesn’t want to be thought of as a railroad.

Which is odd, because a railroad is exactly what it is. You can see that from the signposts I’ve mentioned - each scene has a signpost leading to the next one. Sure, the PCs may take slightly different routes between the scenes, but it’s still a railroad.

At one point, Wrath even says, “The Referee should not railroad them in any direction...” Except that if the PCs don’t follow the big flashing “here’s the adventure” signpost, the GM has to work overtime trying to get them back on track.

(To be fair to Wrath, it does have a couple of pages of signpost ideas to get the PCs back to the plot. But that only signals its railroad-y nature.)

But if you are worried about your campaign being a railroad, write it so it isn’t! Don’t write a railroad and then lecture the GM about it not being a railroad!

Avoiding a railroad isn’t hard:

  • Provide a timetable of events and write the villains so we know what their plans are, and how they and other parties (Imperials, Omicron, Zhodani and others) react.
  • Write scenes and set pieces flexible enough that they can be located wherever necessary.
  • Give clues to the players so they can decide in what order to investigate them – and at some point make sure they know what the bad guy’s plan is so they can work out how to foil it.

There - a non-railroad campaign.

(And frankly, it’s not the end of the world if your campaign is a railroad. As long as the players are having fun and are making their own decisions, railroads are fine.)

Let’s not upset the boat

One thing I found disappointing about these campaigns is that they don’t really rock the boat. Chartered Space isn’t really changed by what happens. I would have been much happier if, during the campaign, the Ancients had gone on the rampage, carving up large chunks of Chartered Space.

So what would I do?

So, given I don’t think much of Mysteries/Wrath, what would I do?

First, I’d probably keep Secrets of the Ancients entirely separate. Secrets is great and stands on its own. Mysteries and Wrath use the same Ancients canon as Secrets (ie, the Final War isn’t over yet), but they don’t really play well together.

So, some options.

The classic campaign

One option is to go back to Adventure 3: Twilight’s Peak and drop information and ideas into an existing campaign. Work it like Twilight’s Peak, with rumours leading to the Ancients’ base.

And that might be enough - I might never use Wrath of the Ancients.

The Omicron campaign

One of the challenges of writing for Traveller is designing adventures that suit any party. (You can see that in some of the gymnastics that start some adventures.)

But why do that at all? Why not assume that the PCs are members of Omicron Division, seeking evidence of the Ancients. This way, the PCs could visit Research Station Gamma and the blockade at Andor, and meet the Ancient Hunters all before things start kicking off.  

And then it’s easy to give the PCs clues pointing them towards Twilight’s Peak and the rise of Tsyamoykyo.

(And with the PCs involved, I’d make Omicron less inept.)

The Ancient Hunters campaign

For this version, get the players to create Ancient Hunters during character generation. Give the PCs links to other Ancient Hunters, and make them interested in anything to do with the Ancients. This might be more like the standard Mysteries of the Ancients campaign - but give them several clues to follow at once, rather than just giving them the next clue.

Agents of Seven

And if you’ve already run Secrets, then the PCs may be agents of the Ancients and part of the Final War. They’ve got an incentive to follow up leads to other Ancients’ sites like Twilight’s Peak and can get involved that way.

The rise of Tsamoykyo

But what is Tsamoykyo doing? In Wrath of the Ancients, he doesn’t really get started. He supposedly has the goal to do great (but unspecified) works and to meet God (as the creator of the universe) to understand why the universe is the way it is. But the campaign ends before he gets started, which I think is a shame.

So let’s give him a preposterous plan: Tsamoykyo wants to create an Undoing to summon the Creator. To do this, he’s going to rip a huge section of Chartered Space into a small pocket universe and collapse it into a giant black hole, which will then punch back through into the real universe, creating an anomaly that will force the Creator to appear.

Tsamoykyo has already run a trial (on a smaller scale) that has shown great promise. 50 years ago, a mysterious black hole appeared out of nowhere in Reft Sector. (When they become aware of it, astronomers will want to charter a ship to visit the black hole [where there may be clues] and also travel to where they can observe it appear in real-time [ie, overtaking the light emitted by the event].)

The eye of God?

With a successful trial under his belt, Tsamoykyo puts his plan to create a huge pocket universe into effect. So he will take a huge chunk of space - let’s say a 25-parsec radius around Andor (so taking out the Darrians, Sword Worlds, a corner of the Zhodani Consolate and a large chunk of the Third Imperium) and pull it into a pocket universe.

(Centring it on Andor explains why Tsamoykyo has to rescue the Droyne.)

The new pocket universe will only be a parsec or so across, and compressing all those systems into a tiny space will create an enormous black hole which will punch back into normal space. So that’s the plan.

So why is Tsamoykyo doing this now? (Rather than, say, a thousand years ago, or 200 years in the future?) Because of Twilight’s Peak. 

Tsamoyko stored his pocket universe-creating device at Twilight’s Peak, and when he learned that the base had been disturbed, he sent an agent (Tellsadiu – from Mysteries of the Ancients).

Tellsadiu teleported the device back to Tsamoykyo and began to warm up the base.

A timetable

With that as a rough idea, here’s my (equally rough) timetable:

984: Twilight’s Peak is disturbed (121 years ago, during the Third Frontier War) by Mercedes and her crew. The alarm is triggered.

1050: Tellsadiu arrives at Twilight’s Peak and returns the device to Tsamoykyo.

1052: Tsamoykyo creates a test black hole in 1052 (in the middle of Reft, where light will take 30+ years for the black hole to be noticed in the Third Imperium).

1060-1105: Tsamoykyo starts setting up ship teleporters at the edge of his planned area. He needs 30 (say). These will all be in deep space, placed there by his ships, and will be networked.

1080+: The mysterious black hole is observed in Reft from the Third Imperium.

1106: Twilight’s Peak is destroyed (as per Mysteries of the Ancients)

1108: Tsyamoykyo takes secret Droyne cache on Andor.

1108: Tsyamoykyo establishes a forward base at a location on the edge of the rip where he expects the Creator to arrive.

1109: Tsyamoykyo triggers the Undoing, creating a monstrous black hole brimming with exotic energies.

1110: Tsyamoykyo meets the Creator!

Okay, this is a bit rough and ready, and I suspect needs fixing in places. But it’s a start.

I haven’t really worked out how the device works, but I think it needs teleporters to be “around” the area to be pinched off. They then become portals into the universe. And the bigger the bit of the universe you are pinching off, the more portals you need. (Ideally, I want the PCs to use the teleporters to zip quickly around the map.)

One thing this does is highlight Tsyamoykyo’s arrogance. He considers the Third Imperium and other empires utterly beneath him and can’t conceive of them interfering with his plan. That’s his mistake…

Other factions

I also need to think about potential other factions that might be involved. They include:

  • Omicron Division
  • Imperial Navy
  • Zhodani Consulate
  • Other aliens – such as the Darrians and Sword Worlds
  • The friendly Droyne from Mysteries of the Ancients
  • Seven and/or Grandfather (if I bring them in)

They all have their own objectives and will react accordingly. (I might even need a timetable for each.)

Getting the players involved

I can see several entry points, depending on what sort of campaign I’m running. Some ideas:

  • The PCs are recruited to investigate the black hole. There they uncover signs of Ancient technology, leading them to investigate further.
  • The PCs are asked to investigate mysterious signals coming from deep space and discover a portal in deep space.
  • The PCs are drawn to Twilight’s Peak as per Adventure #3.
  • The PCs get involved in the adventure on Callia (in Mysteries) and are drawn into the Ancients that way.

As part of the campaign, I want the PCs to discover Tsyamoykyo’s plan and understand how they may foil it. So I’ll need clues – maybe captured intelligence from enemy Droyne, information from friendly Droyne or Omicron, theoretical research from a scientist studying the black hole, or even decoded messages from Ancients’ artefacts.

I also like the idea of the PCs having to convince the Imperial authorities to take action. If they’re successful, maybe we’ll see fleet action against one of the teleporters.

And we can end with a final confrontation in Tsyamoykyo’s pocket universe as before. (Although it’s been pointed out to me that Wrath of the Ancients and Secrets of the Ancients have very similar endings, so perhaps we should do something different.)

Return of the Ancients

So I think that’s what I’d do with Mysteries/Wrath of the Ancients.

That’s assuming I do anything with them – it’s much more likely they’ll just stay on my bookshelf, unplayed.