Running The Sprawl: First impressions

Yesterday I had my first (gameplay-)session of The Sprawl, as a Game-Master.

Even though I feel very comfortable with Powered by the Apocalypse (PbtA) games, I am having a hard time with The Sprawl, and my players do, too.
I will not say too much about the mission I gave my players for now:

  1. The mission hasn't ended yet. If I spill secrets, and one of my players stumbles on this post, they would have knowledge they should not have.
  2. I will create a mission-based story-log/diary-thing. Somewhat for me, to not forget what happened (my notes only include crucial things like "X owes Y a favor!"), but also for you guys to read.

The mission was a very normal first mission for the players though:

  • Get a call by the client.
  • Meet the client in some shady place.
  • Here's your job: Please steal a robot-prototype from corp X.

But here is where the trouble starts. This is a PbtA game, thus I'm playing to find out.
Rewind 3 days: I'm planning for an hour, what to do with the players. They couldn't tell me, because they did not have any interaction with the world before, so I had to prepare something:

  • What? (Ended up being 5 lines)
  • Where? (Also about 5 lines)
    • This implied a: How? (Bad mistake planning this!)
  • Complications?
    • The team is a bunch of weirdos:
      • Pusher – Talker with a vision, to destroy a Mega-Corp
      • Fixer – Peoples-Person, running from a Mega-Corp
      • Driver – Hunted by a machine cult
      • Killer – Included in … Cyber-Greenpeace?
    • One of these things is not like the other hums
    • Inserting hooks, and making everything personal cost me another 12 lines.
  • The GM has to prepare 5 Mission-Directives, which dictate, at which point the players gain XP.
    • An example: "When you deliver the prototype, mark XP."
    • This by nature is very rigid, and actively opposes playing to find out.
      • What if the players don't want to deliver to prototype? They're not getting paid, yeah … But they're not getting XP, either!
  • The GM is also adviced to prepare states for the Action-Clock and the Legwork-Clock.
    • These are basically 10 short sentences describing what happens if the players make X amount of noise.
    • An example: "Action, 1800 - A guard in front of every department door."
    • Again, very rigid. What if the players never go anyway near the department, and find another way?
      • Should you ignore what you prepared, and make something fictionally appropriate up? Great job wasting my time with useless preparation.
      • Or should you make it easy on them, negating all the tension which would be introduced by the clocks? This feels like I am making it too easy for the players.

All this preparation leads to another problem: What if the players say, they do not want to do the job, the GM gives them? Unless the GM planned 3 other missions, the session would be over. Not playing to find out, again!

Since this is a mission-based game, where you have to prepare stuff beforehand, you are playing hide-and-seek with information. Give the players enough information, but not too much.
There is a move, to be done, at the beginning of the mission: Get the job

This move encompasses all the discussion, banter, bartering, and so on, you would see in games like Shadowrun, when talking to Mr Johnson. It's all abstracted in a roll. Don't tell the players too much at the meeting.
Additionally there is a mandatory Legwork-Phase, meant for the players to get the information they need.
This very much shouts: Do not give the players too much information at the beginning. They will skip Legwork completely, if you do.

This gets very problematic, because it is easy to skip important information the players should have.
They will either figure them out immediately, by rolling well. That is only mildly interesting.
Or they will roll badly, and the Legwork and eventually Action-Clocks tick up.
This in turn is bad, because it means the players don't get information they need, and the mission only gets harder.
Advancing clocks means you are not telling the players what they did wrong, and where to go next. You are just telling them BAD! go, somewhere else! A recipe for disaster.

For now I will only tick the clocks if up fiction seriously demands it, or if the players pick a "Something attracts attention" drawback on a 7-9.

None of the problems I encountered are talked about in the book, sadly. I got some great feedback from my players though.

Next mission I prepare will include a basic, very risky plan to tell the players. Focusing more on the what, mostly ignoring the how.
The Legwork-Phase then should be used to defuse the plan. Let's see where this leads.

Post Note: As it turned out: The Sprawl wasn't so good at all. Some of these problems changed, some of them stayed. Also see my The Sprawl Review.