Showing posts with label Chase Scenes. Show all posts
Showing posts with label Chase Scenes. Show all posts

Thursday, February 23, 2017

Mos Philos

In Night’s Black Agents, every PC has one MOS. This stands for Military Occupational Specialty, which, while delightfully jargonized, is a little misleading. It doesn’t necessarily have anything to do with the Military or your character’s official occupation. In a nutshell, an MOS is a once-per-session* automatic high-level success. You pick a single skill that you can absolutely rely on to save your bacon once per night*.



*: Recommended House Rule: The rules say MOS is once per session, but I’ve found that once per MISSION works much better, especially with larger groups. Once per Op means the players have to be a little careful not to just blow their MOS on something trivial, and in turn that frees up the GM to really make those MOS activations knock everyones socks off. The best reason to go with once-per-Operation instead of -per-session is that this discourages players from dragging things out. Someone metagaming the refresh system of a Gumshoe game like NBA can actually wreck your campaign. You never want a situation where the best play is to turtle up and do nothing until the end of the night because next week the PCs will all be back at full strength if they just stall out the clock. For my own campaigns I’ve moved all the end-of-session refreshes and processes to happen at end-of-mission instead, and I find it’s a strong improvement. Ops rarely last more than a second session back-to-back anyway, because all those MOS activations and Cherry benefits generally allow the PCs to shoot for the moon and stick the landing on any plan in just a session or two. About the only situation where I would consider moving things back to a per-session basis would be if I was running a campaign with just 1 or 2 players.  

I’ve seen three main philosophies or schools of thought for player MOS. Having seen them all in play, I think all are equally valid, though it took me a little while to get to that. Here’s three ways to pick an MOS:

1) Use it to strengthen the skill you plan to spend the most frequently. This is the obvious play for a super-shooty assault specialist. Putting your MOS in a skill you plan to lean on heavily provides you the freedom (and safety) of being able to blow all the points you want on every roll, knowing that even if you bottom out your best ability in a protracted conflict you still have one helluva trick up your sleeve.

Though I mentioned shooting, this approach actually works super well for non-combat skill MOS assignments. The notion of “master of disguise” is a very fitting one for the genre, but it can be very point-intensive in this game. You may feel that Disguise alone isn’t good enough, and before long your core concept is eating up your General Ability budget with the smorgasbord of Cover, Network, Infiltration, and Surveillance. Covering all the aspects of “master of disguise” can leave you feeling stretched thin, and those points all feel a little wasted when the current Op is some unsubtle smash-and-grab. Putting your MOS into one of those Abilities is a great way to ease that pain. You can then afford to specialize in just the Ability levels needed to score the most appealing Cherries, and know that a timely MOS will cover any oversights or point deficits.

Aligning your MOS with your best (or one of your best) skills feels very fitting, and makes good sense in- and out- of-character. There is no rule forcing you to pick an MOS in your best skill though, or even in a skill you've got any points in at all. Let's look at some other philosophies and options for MOS selection...

2) Use it to shore up a critical weakness. Here you’ll take a MOS in some action skill that you are otherwise incapable of using. The first time a player in one of my campaigns picked an MOS they didn’t have more than a point or two in, I was very apprehensive. On some level, it felt almost like an abuse of the system. But now I’ve seen it in action, and I’m a full convert.

One of the PCs in my current campaign took a Weapons MOS and basically no other combat skills. Once per mission* she can get the drop on someone and beat them into submission with a frying pan, but if faced with a protracted battle she’s more properly motivated to surrender and gather intel as a prisoner. It works out pretty well. She gets fun spotlight moments in the occasional fight despite being otherwise a non-combatant. That is all kinds of cool. The MOS mechanic allowed her the freedom to play a quirky civilian in a setting where that might otherwise be a lethally bad idea.


3) Use it to hand-wave past your least-favorite part of the genre. The entire point of Gumshoe is to cut out the tedious die-rolling and related frustrations that can wreck a mystery scenario… so there’s no reason you can’t apply that principle to any skill or type of scene that just doesn’t excite you.

For the sake of the argument, let’s say you just hate car chases. Maybe it’s the chase mechanics never live up to your imagination and expectations. Or maybe you’re bus-bound in the real world and couldn’t give a damn about cars. Whatever the reason, you’ve decided that you can’t stand car chases and don’t want to play that minigame. It may be counter-intuitive, but in that situation an MOS in Driving would be a great investment. It would allow you to short-circuit any chase or tailing sequence you want by just invoking your MOS to escape/catch-up/ram the opposition. If there’s someone else at the table that absolutely loves car chases, you can expect that there will be the occasional twice-in-one session chase scene extravaganza, but at least you only have to suffer through the second half of the double-play.  
(EDIT/afterthought: Depending on just how much your fellow players enjoy a car chase, you may find it fairest to instead suffer through a few minutes of it in the early part of a session, and then invoke your MOS if the scene really starts to drag or if a second car chase crops up in the same session. Your mileage may vary.)

Driving was merely the low-hanging fruit there, and the same principle can be applied to nearly any type of scene you don’t like if you just target the skill most likely to shortcut it. Hate shopping and planning scenes? A Preparedness MOS will get you the right tool for the job with no advance notice.  Can’t talk your way out of a wet paper bag? An Infiltration MOS will get you past the security check point and on to the fun parts behind enemy lines. Completely bewildered by technology, or bored to tears by hacking scenes? Digital Intrusion MOS cuts those down to a quick montage and a bare minimum of jargon.

The MOS mechanic is one of the great innovations of Night's Black Agents, and it does an amazing job of empowering the player to not just customize their character, but also tailor their gaming experience just the way they want it. That's a win for everyone.


Thursday, September 4, 2014

Dissecting Psi*Run

Psi*Run is a great little pick-up game that requires no prep work from the GM (other than printing 2N+1 single page documents for the group of N participants to reference mid-game). The PCs have partial amnesia, mysterious powers, and are being pursued. That’s it. Everything else is determined by the players during the game. I do mean players, because, (like Urchin) it’s a game that intentionally takes some of the power usually reserved for GMs and distributes it around the table.

It's a game about an extended chase. You could use the system to tell tales along the lines of Bourne Identity, Logan’s Run, or The Terminator, anything where pursuit is a huge part of the plot. In practice (because there’s no default setting, it’s all improvised, and relies on collaborative story telling) I find you tend to get things more like a gonzo, trippy, four-color version of the X-files. A wild ride, to be sure. The mechanics push you towards this sort of story, with flashy misfiring powers going haywire in nearly every scene.

It’s mostly awesome, but sometimes strains disbelief or kinda fails to come together in the third act. There’s a couple of recurring pitfalls inherent to the system, stemming from the odd mechanical structure and the lack of a single guiding hand at the narrative wheel.  Here’s the problems as I see them:
  • Powers cannot be subtle.
  • The 2nd Act Slump.
  • Die-assignment paralysis.
  • Passive GMing.
Nothing that can’t be overcome with a bit of forethought, but I’d like to discuss them here to aid anyone who’s looking to run the game in the future. The solutions are for the most part fast and easy, and I really like the game overall.


Powers Cannot Stay Subtle.


The most common Psi*Run problem is thankfully a minor one. Despite not being a huge issue, it has come up in at least 4 of the 5 sessions I’ve run, so it deserves some attention. I’m talking about the problem of low-key, non-threatening, and/or passive powers. When someone’s making their Psi*Run character, sometimes they’ll describe a power that doesn’t do much, or shouldn’t realistically endanger anyone, or (going the other direction) is just one giant enigma beyond their faintest understanding.

If the power doesn’t do much, or is _completely_ outside the PC’s control, then they won’t get to roll as many dice and won’t have as much of the spotlight. That part of it is a self-correcting problem, in that most players will quickly figure out that they’ve got to start triggering their own ability… but once you’ve started arbitrarily dictating that your power “randomly” kicks on in the middle of actions, you tend to use it in every single action. “All the time” is better than “none of the time”, but either is missing out on some of the depth of the system. A player who chooses “none of the time” is basically choosing to have a boring game, and missing out on at least half the fun of the setting. Don’t let them do that, GM.  Encourage them to take a more active power, and tell them that the game will run better for everyone if they do.

A related problem (really the second half of the first problem) is what happens when you have one of these low-key or passive powers, and then proceed to assign a “1” die to the Psi category during play. When the dice are arranged in that way, it’s supposed to be lethal and destructive on a grand “would make national news” style. Every single power has the potential to go horribly awry. In recent memory, I’ve seen this happen with powers like “my hands glow different colors” or “I have a 12-foot tongue”. How do those kill dozens? As a GM, I’m willing to roll with it and narrate a crazy overblown moment. Turns out your glowing hands are just the warning lights of a much more deadly power, or your prehensile tongue doesn’t know it’s own (super)strength. Oopsie!

The problem here is that the player may actually want to play someone with subtle low-key powers. If so, they need to never put anything less than a 3 in “Psi” so that nothing over-the-top gets narrated… and that’s really hard to pull off for an entire session unless you’re willing to let something else horrible happen (or willing to never succeed at your goals and never regain lost memories). Player, it’s on you. If you want a subtle power, you just have to accept that the story is going to get dark in other ways. You’re going to fail and you’re going to get hurt, because you don’t have “Psi” available as a place to dump your lowest dice. Subtle powers either become outrageous over time, or they successfully remain understated while everything else bad happens to you all at once. There’s really no other alternatives (unless the dice are abnormally kind). The GM should mention this early on, preferably during character creation, so there’s no unpleasant surprises during play.


The 2nd Act Slump.


The other major problem the game sometimes runs into is a 2nd or 3rd Act slump. The first Act always opens up strong, with character introductions amidst a flaming wreck, and mysterious pursuers right behind you. There’s built in dramatic tension, and we’re all still experimenting with the mechanics, so that first part is golden. Sometimes (2 out of the 5 Psi*Run one-shots I’ve done) the players will, instead of experimenting, just click on the supposed “optimal” plays or get freakishly good rolls. Some people always play to win, even if it’s an RPG.

If you’ve always got 5’s and 6’s to stick in “Harm”, “Chase”, and “Goal”, the PCs can quickly shoot out to 5 or more locations ahead of the chasers. At that point the dramatic tension diminishes significantly. The notecard system clearly tells us exactly where the conspiracy has gotten to, and with no injured characters your dice will probably continue to extend the lead, so things kinda slow down. The players spend a ton of time discussing options at this stage, which is sad because it’s not really a game with a “right answer”.  If there's anything that can ruin a game of Psi*Run, it's the second act slump, but in practice I find even the slumpy games have such good starts that you don't regret playing at all.

There’s three ways to get out of this slump, should it happen during your game.
  • Player “sabotage”
  • Remote villainy
  • Cheating the chase tokens

Player "Sabotage"


The best way is for a player to ‘intentionally sabotage’ the PC’s progress, by sticking low numbers in “harm” or “psi”. The GM has less power in this system than most, so it’s hard for them to create tension or steer the plotline. Players, by putting their dice in “sub-optimal” parts of the resolution sheet, can rapidly change the tone of the game. As a player, if you feel things are starting to slow down, you should grab the reigns, and intentionally screw up. It will rescue a game that’s starting to get away from the GM.

Even if the game has given no indication that things are going wrong, it can be very helpful (to the narrative) if someone purposefully fails or causes trouble from time to time. It helps keep the game tense, and sometimes amazing scenes develop from it.

Remote Villainy


The second best option is for the GM to introduce a subplot about the Pursuers conducting some act of evil at an off-site location. Give the PCs a reason to leave the safehouse they found, and start heading towards an enemy stronghold. If anyone’s Questions implied a friendly NPC is out there, put that NPC in danger. If not, then think big, and engineer things so that the PCs are the only ones who know about the villain’s planned coup or terrorism. If they do dive into the heart of evil, the lack of tension from having such a huge lead on the Chasers may make it anti-climactic, but at least with them rolling dice there’s a chance things will go south. It only takes one bad die roll to suddenly make the game interesting again.

Getting the reaction you want is hard when you’ve got limited narrative windows, and an inability to dictate the danger level. The PCs might call your bluff, and there’s really no consequence if they do so. The Crossroads system in the end game will usually let them hand-wave a solution to your impending apocalypse even if they ignored it all session. GM, don’t restrict yourself to only in-character motivations. Tell the players “I think we’ll probably have a more enjoyable session if you put yourselves back into dangerous situations.” You’ve escaped, caught your breath, and time has gone by. What would your favorite movie heroes do next? Vengeance? Justice? Infiltration? Pick one and do it.

Cheat It


The third option is untested (by me, anyway). That would be to just cheat the chase tokens. There’s no official mechanism by which the GM can ever control the rate of the pursuer’s advance. Officially, the players set the bad guys pacing, and their location on your trail is public knowledge. You really couldn’t get away with suddenly moving the pursuit token 3 or 4 spaces along the trail just to make the game interesting again. Doing so would break the rules, and more importantly it would make the players feel like their previous decisions (about where to go and what dice to assign to various boxes) were meaningless.

What you could do without breaking immersion or rules, is just decouple the Pursuit token from the narration. The Chasers are officially 5 spaces behind you, but that just means the bulk of their forces (enough to turn “Chase” into “Capture”) are trailing that far back. Instead, you introduce scouts or advance units that are much closer. They can’t capture any one, but they provide immediate danger (forcing players to add the “harm” die to every roll) and keep the plot rolling. This still runs a tiny risk of generalized “our actions were meaningless” perception, but certainly less of it would come from arbitrarily moving the markers around. Again, the players could call your bluff and just ignore the scouts with only minimal consequence. As with the “Remote Villainy” option, you may have to get a little meta and ask the players to please try to work with the plot, since they’ve already proven they can beat the mechanics.



Die-Assignment Paralysis.

I’ve noticed that some players take a lot of time agonizing over which dice to assign to which box on the resolution sheet. Sometimes, it feels like the only way to get exactly the result you want is to run a dozen different ordering around in your head and compare them. I understand that, and am known for a bit of analysis paralysis myself in other games. In practice, though, agonizing over the dice in Psi*Run does you no good. It just slows things down for everyone. Also, I find that every time someone has spent a lot of time and energy moving the dice around, they _always_ screw up who gets first say on at least one of the dice. Which means that the thing you just spent 5 minutes silently envisioning won’t actually play out at all like what you pictured.

My advice is to move those dice around fast and not worry too much about the exact numbers.
  1. What’s the most important thing you wanted to accomplish with this roll? It’s usually going to be Goal or Chase/Capture/Disappear, (but sometimes it will be Reveal or Harm instead in certain circumstances) and you’ll generally know which one before you’ve rolled the dice. Slide your highest die onto that first. If nothing calls out to you, just move on to the next step.
  2. Next, look for the 1’s in your remaining dice. You get to ignore one of them (unless you’re impaired) so just set it aside. If there’s any 1’s left over, put them somewhere other than Harm or Chase/Capture/Disappear; most people find that Psi or Reveal is a good sink for that. 
  3. The remaining dice can pretty much be put anywhere and you’ll be equally happy most of the time, so I recommend just move each of them to the box nearest where that die stopped. It’s quick and easy.

A little less than half the dice in the game won’t actually affect the narration at all, so don't sweat it. No matter where you put dice, you will eventually experience a roll where some else getting first say on a single die completely derails what you were trying to do. That’s okay. The game is actually at its best when the unexpected is suddenly happening out of nowhere. Don’t overthink it, just play the dice where they lay. The only thing you’ll ever actually regret is if you put a “1” in the wrong place at the wrong time, so if you get your ones solved the rest can be arbitrary.



Passive GMing.

This is the most minor of the flaws to this game, but I don’t really have a good solution for it. Passive GMing might not be the right word, perhaps it’s more accurate to call it “GM’s feeling of powerlessness”. It's not that you can't or don't do anything as GM, it just feels like that's the case.

Like Urchin, the GM in Psi*Run has very little narrative power. You get to set up the original crash, and cobble together your badguys from the things implied by the PC’s descriptions and Questions. After the game starts, you’re down to just narrating side effects and the degree of success, with the occasional physical description thrown in for flavor. If you try to force a plot, the players will ignore it.  If you try to establish background detail, the players will contradict it when they answer Questions.

If you’re the GM who loves to run taut mysteries or large casts of NPCs, Psi*Run will seem like you don’t have enough to do. If you’re the sort of person who loves GMing more than Playing, Psi*Run is going to feel weird to you. If you’re the inverse - a person who would rather Play than GM, or who likes describing combat scenes colorfully but is intimidated by the idea of generating entire plots - then Psi*Run is right up your alley as a game to break out whenever it’s your turn to provide the evening’s entertainment.

The hardest part of being the Psi*Run GM is choking back the answers you want to give to everyone’s Questions. Only players answer Questions, so the GM never gets a say in anyone’s backstory or mysteries.  I’ve considered changing the “Reveal” box so a 3 result lets the GM answer a Question, but I think that would speed up the game too much for long-term play. For a one-shot it’d probably be fine, you’d use 5 or 6 Questions per player instead of the truncated 4 per player currently recommended for Con games. Perhaps more interesting would be to use the “1” result not the “3” for GM reveals, but in the process encourage the GM to narrate the most punishing Answer they can dream up when those 1s do happen. That would make Reveal much less of a safe die sink, and I haven’t played around with it enough to know if that’s a good or a bad idea. Next time, I guess.


Despite That, It's A Really Good Game


These are small problems with wordy solutions, but not much needed in terms of house-rules. I've run the game 5 times total, with 3 of them being brilliant and the other 2 hitting the second act slump mentioned above but still being mostly solid. It's an easy game to run when you don't have time to prep something more involved, and it's a great icebreaker game for conventions or strangers.

Psi*Run. It's cheap. It's easy. It's fun. Check it out. Link to publisher.




Wednesday, January 20, 2010

Creeping up on sentries

We all make mistakes while gaming. I've made plenty. There are times where craziness happens, or where one mistake leads to another. Hindsight is 20/20, and sometimes all you can do about it is learn not to make the same mistakes next time.

Advice for the next time you're creeping up on the sentries around an enemy camp:
  • Don't split up the party if you don't have to. If you do split up, don't get impatient and head away from your agreed rendezvous point without permission.
  • If you happen to know that your groups Tank / Fighter is prone to wandering off and stirring up trouble, and you see him wander off, follow him. Don't do your own thing instead.
  • If the sentries are of a race that has infravision, your stealth precautions need to be more significant than putting out your torch, and carrying the smouldering remains of it with you. This goes doubly so if the system in question doesn't put a limit on infravision range, it just says "Goblins and Orcs suffer no penalties for darkness".
  • If you don't know the total numbers of the enemies at the camp, dispatch their sentries with something silent, like a knife or a bow, not an area-effect stunning spell.
  • If you do use the area-affect stunning spell on the two sentries you can see, arrange the area-of-effect so that it includes both of them.
  • After you use your area-affect stunning spell, and it alerts a huge crowd of orcs to chase after you, if you can cast it again, do so. Don't spend several actions standing around trying to make a persuasion roll against the two dozen orcs that are charging you. They're not listening.
  • When the resulting chase lasts so long the GM asks for a Vigor roll to resist fatigue, AND you roll double-ones on it, use your last bennie to reroll that. Don't save it for "if things get really dire later". Double ones on your Fatigue-resisting roll when dozens of orcs are chasing you is dire.
In the end, all the PCs survived, but extricating themselves from the situations this caused took over 6 more hours of play, and a lot of die rolls. It was ugly.

Tuesday, January 29, 2008

Mountain/Forest Chases

This is for use with the Chase System from 7th Sea. It's intended to compliment (and be used just like) the Street Chase, Riding Chase, Rooftop Chase, and Carriage Chase charts on pages 171-172 of the 7th Sea GM's book.

For a Chase through dense woods and steep hills, each person must roll Finesse+Sprinting. For every 5 full points you win by, you may add or subtract 1 ChaseRaise from the distance between you. If the result for a turn is 0 modification, then roll 1d10 on the chart below:

1-2: The hunted is able to duck beyond cover, such as behind a bush, tree or hill.
The chaser must roll Panache+Tracking or Shadowing vs TN 20 or Wits+Ambush vs TN25.
Failure results in 4 ChaseRaises being added to the distance of the chase as the hunted is able to alter course and surprise the chaser.
A successful roll still results in 1 ChaseRaise being added, as it takes a moment for you to figure out where they went.

3-4: A dirt slope gives way, causing both hunted and pursued to face great peril. Each must roll Finesse+Balance vs TN:20. Failure sends you tumbling.
If you fail, you fall 2 Levels Soft. If you take any damage, you must roll (the lower of Finesse or Resolve)+Sprinting for the remainder of the Chase Rolls.
If one person fails and the other succeeds, then 2 ChaseRaises are added to the distance between hunted and chaser, regardless of which fell.
If you succeed, you may continue rolling Finesse as normal.

5-6: First the hunted, and then the chaser, must cross or avoid an obstacle such as small ditch or large boulder. Each may choose which of the following roll to make:
Brawn+Leaping, TN:25
Finesse+Footwork, TN:15, but you are slowed by 1 ChaseRaise as you avoid the obstacle.
Failure to succeed at your roll results in 3 ChaseRaises being applied as a penalty to you.

7-8: The hunted foolishly plows into a thicket or bramble. They suffer 2k1 fleshwounds in the collision, but continue on their way. The chaser may choose to suffer the same injuries, or relinquish 1 ChaseRaise to skirt around the thornbush.

9: The hunted has run to the edge of a cliff - they must make a stand here or jump off the ledge. If they stand their ground and fight, they start off on higher ground at the beginning of the battle. If they consider jumping you must roll 1d10 to determine height & landing surface.
1-2: 2 Levels of Height, Soft Surface
You must roll Finesse+BreakFall vs TN:20 or be knocked Prone.
Getting up from Prone costs 1 ChaseRaise.
3-8: 4 Levels of Hieght, Hard Surface
You must roll Finesse+BreakFall vs TN:30 or be knocked Prone.
Getting up from Prone costs 1 ChaseRaise.
9-10: 8 Levels of Hieght, into the water, a Soft Surface
You must roll Finesse+Swimming vs TN:20 or be disoriented upon surfacing
Recovering from disorientation costs (5 minus Panache) ChaseRaises.

10: The hunted has reached a dead end. They must double back or at least take a overly sharp corner that costs time and ground. Remove 4 ChaseRaises from the distance between them and the chaser.