GM Guidelines

From Chrome Company Wiki
Revision as of 11:09, 11 September 2022 by Dartosc (talk | contribs) (Created page with " Note the following are not rules, merely guidelines. The GM Head will explain when and how specific situations vary if a decision is handed down. ==Rewards== When possible, it is often better to give less immediate reward and instead create the promise of future reward (ie. "delayed" rewards, if you will). For example, instead of giving the players a discount on an expensive or rare item, give them a business card for a contact who will help them obtain it later...afte...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Note the following are not rules, merely guidelines. The GM Head will explain when and how specific situations vary if a decision is handed down.

Rewards

When possible, it is often better to give less immediate reward and instead create the promise of future reward (ie. "delayed" rewards, if you will). For example, instead of giving the players a discount on an expensive or rare item, give them a business card for a contact who will help them obtain it later...after doing just one more favor for them. Not only does this reduce reward inflation, but it makes the obtaining of those rewards more memorable.

Expectations

  • Players should have fun. We’re fundamentally here to play games together and have fun, and as the GM you have a lot of control over how the game goes; with that great power comes great responsibility, and the responsibility is to try to make sure people have a good time.
  • If you have a major obstacle, know the rules related to that obstacle. If a big part of the run involves a car chase or a host dive, you should have a good grasp of the rules related to car chases or host dives (or whatever the obstacle is).
  • Try to limit railroads and definitely try to avoid "Rocks Fall" scenarios. Generally goes without saying, but Shadowrun can be amply dark without succumbing to the temptation of Deus ex Machina unavoidable situations.
  • Stay within reasonable expectations. It may be fun for a character to get milspec armor from a ganger in the barrens on a low-threat run, but it really cheapens the experience of the player who slogged through the amazon to pry that same armor off a super-soldier during a prime run.
  • Play with the players, not against them. Challenge and risk can make for a great and memorable experience -- but don’t make the game you vs. the players. Assume competence, and don’t try to catch players in “gotchas” -- competent runners might make a mistake or forget something if they’re pressured for time or under fire, but it’s good practice to give them the benefit of the doubt when they aren’t.
  • Balance that with risks and challenges. Players are allowed to fail, make mistakes, make their situation work, or trigger escalation. If particularly dire consequences are about to drop, make sure that you have foreshadowed them and given players ample opportunity to discover and avoid the upcoming problems where feasible. This particularly applies to Prime class runs, which are generally unforgiving of character (or player) mistakes, but should be kept in mind at all tiers of difficulty. Even in the most grim of scenarios, players should have a way out (and it shouldn't take Moriarity to figure out that it's possible), but there is no onus to hand them answers unless it fits your story.

Assumed Competence

There are a lot of trivial decisions -- that is, decisions with a clear best choice and no downside -- that shadowrunners routinely make. These are things like wiping an astral signature, infiltrating in disguise, wearing a mask in a firefight, setting up a DNI before the meet, running silent while hacking, and turning off SINs before committing crimes. In general it’s best to assume that players do these things unless they say otherwise (or some kind of constraint -- like time -- prevents them). Exactly what assumed competence covers is a matter for debate, should be discussed with the players at your table in the event it comes up and should be written in style document what is assumed competence.