Much to my frustration, I am a month late. I would have really liked to finish the MP update this month but it's obviously not going to happen.
The main reason is that it blew out of proportion as I noticed more and more things that I would like to change. It was originally going to be Humanity + Fiends rework and the removal of Character Feats/Role Techs. Now nearly every class has had some fun/balance issues fixed, I've added more alternate rules to compensate for the loss of customization with the removal of Character Feats, I've written a bunch of advice for players and GMs alike... It's honestly kind of ridiculous but I'm really happy with how it has turned out for the most part. I don't plan to add any more content, so we're on the final stretch in this regard. I've got a couple pages of advice left to write and then there'll be a lot of reviewing to go through it all looking for mistakes but that's all.
Also it's summer and it's always a miserable experience full of nothing but bad news so maybe it could've been possible to finish things up last week or the one before that but the random events table for this season is the worst.
I'm gonna have to talk about all the mechanical changes at some point, but for now I just want to share some of the advice I've been writing. First, Chapter 1 is getting the "Going Independent" section that was at the back end of the book after the introduction of all the factions. Second, at the end of Chapter 2 I'm adding a page of advice for playing PCs of each faction (including independent ones). Third, I'm adding campaign ideas for each faction using them as either protagonists or antagonists in the GM section between the survival rules and NPC creation.
I'm going to post some of those now, they range from the classic "save the world" epics...
The Order is preparing to launch a satellite called the Angelsong. This satellite is a mass brainwashing device powered by countless human brains. The siren’s call of the Angelsong will convert humans into fervent believers, instantly winning the war wherever it strikes. The PCs must attack the various facilities that are key to the completion of the Angelsong. This includes the factory producing the satellite parts, the brain extraction facilities, the brainwashing program control station and perhaps the launch base itself. The climax is a large-scale battle between the PC’s faction and the Order’s forces in which the Strike Team must self-destruct the Angelsong from the inside to destroy it once and for all.
...to the gameplay gimmicks...
The Valkyrie Unit, a stealth airship with a couple dozen Raptor suits, is staging hit and run attacks on the PC’s home base. The PCs are part of a response team designed specifically to catch these enemies that a large force would struggle to keep up with. Can they predict where the enemy will show up and successfully whittle them down until landing a killing blow? And how will they deal with the Valkyrie Unit when they in turn adapt and start setting up traps of their own to bait the PCs? What if the Valkyries decide to prioritize eliminating the PCs and attempt to assassinate them by blowing up their sleeping quarters? This one is a bit tough since the players must design their team in a way that they can all deal with long-range flying threats, but that’s what makes it an interesting departure from the norm.
...to the just plain ridiculous.
The earth rumbles as the mountain-sized terapede DaiOhMukade stirs in its sleep. The creature is largely harmless outside of causing tremors every few weeks or so, as it has spent most of its life preserving its strength in stasis, like a dormant volcano who could erupt any moment but most people now take for granted it won’t. The PCs are tasked with protecting the massive arthropod and keeping others from disturbing it, less it cause a cataclysm when it wakes up. The problem lately is that a lot of Gaian teams are coming around to try and not just wake it up but also bring it to their side of the war. DaiOhMukade has no intelligence whatsoever and is probably impossible to communicate meaningfully with. Its awakening would probably destroy not just the PC’s home but also doom the rousing Gaians themselves. Stop these deluded fools by whatever means necessary.
There's something for everyone here and I'm glad that I took the extra time to write them, because it's either gonna come in handy or be an interesting read at the very least.
Until next time, Gimmick Out.
Jan 27, 2019
Jan 6, 2019
Monsterpunk has Skill Challenges now
Today I want to talk about what is one of my favorite low-key mechanics in Monsterpunk: Group Tests. One of the things I'm doing is upgrading them from a sidebar suggestion to a proper full page of rules.
The idea is basically as follows: Multiple PCs cooperate to resolve a sufficiently complex task using Skills and Techs, with success and failure being determined not by individual performances but rather the performance of the group as a whole.
Mechanically, each PC participating in a Group Test contributes with a certain amount of Progress, with each task requiring a specific amount to solve it. The most basic form of contribution is through Skill Tests, as follows:
Comparing both ways to contribute: Skill Tests are available to everyone, they have a lower ceiling and a higher floor, but are random. Features and Techs are more reliable, but there's less of them and they are individually more niche in use, so you can't always count on having an applicable one around.
Between Skill training, Features, Techs and just plain being lucky, you can assume that most groups will get at least 1 Progress per PC and half of them will get 2. This means that the average PC contributes 1.5 Progress to any given Group Test. So how far does that get them? Well, there are three difficulty settings for Group Tests, but on average the results are as follows:
Progress Lower than the Number of PCs: As a Twist.
Progress Exactly the Number of PCs: As a Success with Twist.
Progress Over the Number of PCs: As a Success.
Double or More Progress than the Number of PCs: As a Success with Bonus.
The regular Skill Test rules lean towards Success with Twist being the most common result, with regular Successes and then Twists behind (remember that Advantages twist the odds towards higher numbers). Group Tests however lean towards Success being the most common result, not just because 1.5 Progress per PC means you'll land solidly there on average, but also because Success with Twist is really unlikely to happen, even less so than a pure Twist. Interestingly, Success with Bonus is much more likely in regular Skill Tests, thanks to a combination of Advantage stacking and Tricks that let you autoroll 10 once per day, but in Group Tests getting a Success with Bonus requires multiple people to be very lucky or having so many applicable Features and Techs that it should be obvious at a glance there's no real chance of failure here and you shouldn't even bother rolling dice.
This means you could arguably powergame the narrative rules by getting the group to work in tandem most of the time, so that you're always rolling Group Tests and minimizing chances of failure. It's exploitable, but is that a bad thing? Not really. Or at least not meaningfully. Consider that this kind of exploit is one that requires involving everyone in the story and working together, rather than making one person hog the spotlight constantly. Sure, it might make the game too easy, but if your problem is that the PCs are always cooperating and using their special talents to help each other out all the time... Well, that's a great problem to have, honestly. Even then you can always just use the provided rules to make Group Tests harder so it's not a super huge deal.
It is also preferable to what happened in old versions of these rules: They were much harder, leaning towards Success with Twist and making it possible to take away from the group's Progress with bad rolls. The end result of this subsystem was that people would rather sit out than risk undoing everyone else's work and that really sucks considering that the entire point of Group Tests is to make all the PCs participate in advancing the story.
And I think they serve a very important function in doing that. We've all been in games where one or two PCs end up doing more than the others just because they speak up more, their skillsets can solve most problems, or the GM just doesn't know how to make challenges that involve everyone. Group Tests are a formalized, simple and effective way to guarantee that - at least for one Scene - everyone does something of relevance. Or makes the attempt and fails, I guess, but, er, at least they tried?
I really like Group Tests. I've found myself using them more and more in playtesting and fine-tuning them until they became a core part of the rules. They're not flashy or fancy but they're fun and facilitate cooperative storytelling. And hey, those are two of my favorite things!
I really can't wait to get them out the door so that others can start playing with them.
The idea is basically as follows: Multiple PCs cooperate to resolve a sufficiently complex task using Skills and Techs, with success and failure being determined not by individual performances but rather the performance of the group as a whole.
Mechanically, each PC participating in a Group Test contributes with a certain amount of Progress, with each task requiring a specific amount to solve it. The most basic form of contribution is through Skill Tests, as follows:
Note that you can't substract Progress by rolling badly. You can opt out of rolling a Skill Test, but there's no point to doing so since the worst you can do is not add any Progress at all. Also a single PC can contribute with only one Skill per Group Test... Unless they fail and try again using a different Skill, but even then they're still rolling once per attempt. Point is, no one can roll multiple Skills at the same time and everyone should be rolling their most applicable Skill here.
PCs can also contribute 'passively' through Features, Support or Trick Techs that apply without having to roll anything. These add +1 Progress each and, in truly exceptional cases where your Techs can cover for multiple PCs, +2 Progress each. For example: The PCs must infiltrate an enemy facility and reach the VIP area without raising an alarm. Making yourself invisible is an automatic +1 Progress, but the ability to make yourself and all the other PCs invisible would be +2 Progress instead and you can still roll Stealth, Electronics, Negotiation or whatever other suitable Skills you've got on top of that.
Between Skill training, Features, Techs and just plain being lucky, you can assume that most groups will get at least 1 Progress per PC and half of them will get 2. This means that the average PC contributes 1.5 Progress to any given Group Test. So how far does that get them? Well, there are three difficulty settings for Group Tests, but on average the results are as follows:
Progress Lower than the Number of PCs: As a Twist.
Progress Exactly the Number of PCs: As a Success with Twist.
Progress Over the Number of PCs: As a Success.
Double or More Progress than the Number of PCs: As a Success with Bonus.
The regular Skill Test rules lean towards Success with Twist being the most common result, with regular Successes and then Twists behind (remember that Advantages twist the odds towards higher numbers). Group Tests however lean towards Success being the most common result, not just because 1.5 Progress per PC means you'll land solidly there on average, but also because Success with Twist is really unlikely to happen, even less so than a pure Twist. Interestingly, Success with Bonus is much more likely in regular Skill Tests, thanks to a combination of Advantage stacking and Tricks that let you autoroll 10 once per day, but in Group Tests getting a Success with Bonus requires multiple people to be very lucky or having so many applicable Features and Techs that it should be obvious at a glance there's no real chance of failure here and you shouldn't even bother rolling dice.
This means you could arguably powergame the narrative rules by getting the group to work in tandem most of the time, so that you're always rolling Group Tests and minimizing chances of failure. It's exploitable, but is that a bad thing? Not really. Or at least not meaningfully. Consider that this kind of exploit is one that requires involving everyone in the story and working together, rather than making one person hog the spotlight constantly. Sure, it might make the game too easy, but if your problem is that the PCs are always cooperating and using their special talents to help each other out all the time... Well, that's a great problem to have, honestly. Even then you can always just use the provided rules to make Group Tests harder so it's not a super huge deal.
It is also preferable to what happened in old versions of these rules: They were much harder, leaning towards Success with Twist and making it possible to take away from the group's Progress with bad rolls. The end result of this subsystem was that people would rather sit out than risk undoing everyone else's work and that really sucks considering that the entire point of Group Tests is to make all the PCs participate in advancing the story.
And I think they serve a very important function in doing that. We've all been in games where one or two PCs end up doing more than the others just because they speak up more, their skillsets can solve most problems, or the GM just doesn't know how to make challenges that involve everyone. Group Tests are a formalized, simple and effective way to guarantee that - at least for one Scene - everyone does something of relevance. Or makes the attempt and fails, I guess, but, er, at least they tried?
I really like Group Tests. I've found myself using them more and more in playtesting and fine-tuning them until they became a core part of the rules. They're not flashy or fancy but they're fun and facilitate cooperative storytelling. And hey, those are two of my favorite things!
I really can't wait to get them out the door so that others can start playing with them.
Gimmick Out.
Subscribe to:
Posts (Atom)