GM Core
Chapter 1: Running the Game
Running a Session
Source GM Core pg. 10
During a session, you're in charge of keeping the game's action moving, managing the different modes of play, fielding questions, and making rules decisions. You'll also want to keep a rough eye on the time, so you can end when most convenient for the group.
You're the interface between the rules and the imagined universe you and the other players share. They will ask you questions, and they'll act based on their own assumptions. It's up to you to establish what's true in the game, but you don't do this unilaterally. You're informed by the setting's backstory, your preparations, and the suggestions and assumptions the other players bring to the table. Keep in mind that until you announce something, your own plans are subject to change. For example, if you originally intended the bartender of a cantina to be kindly and wellintentioned, but a player misreads her and invents an interesting conspiracy theory regarding her intentions that sounds fun, you might convert the friendly bartender into an agent of evil after all.
You'll also determine when PCs and foes need to attempt checks, as well as the consequences of those rolls. This comes up most often outside of encounters, as encounters are more regimented about when checks happen and how they are resolved. In an encounter, a player can usually determine their own character's turn, with you chiming in only to say whether an attack hits or if something in the environment requires a character to attempt a check.
You're the interface between the rules and the imagined universe you and the other players share. They will ask you questions, and they'll act based on their own assumptions. It's up to you to establish what's true in the game, but you don't do this unilaterally. You're informed by the setting's backstory, your preparations, and the suggestions and assumptions the other players bring to the table. Keep in mind that until you announce something, your own plans are subject to change. For example, if you originally intended the bartender of a cantina to be kindly and wellintentioned, but a player misreads her and invents an interesting conspiracy theory regarding her intentions that sounds fun, you might convert the friendly bartender into an agent of evil after all.
You'll also determine when PCs and foes need to attempt checks, as well as the consequences of those rolls. This comes up most often outside of encounters, as encounters are more regimented about when checks happen and how they are resolved. In an encounter, a player can usually determine their own character's turn, with you chiming in only to say whether an attack hits or if something in the environment requires a character to attempt a check.
Pacing Game Sessions
Source GM Core pg. 10
Most sessions should have lulls in the action punctuated by challenges such as intense encounters, puzzle-based exploration, and investigation. Presenting players with a variety of such obstacles can help them feel more engaged at the table. Information flow matters, too. If the group meets a large number of NPCs in short order, that can make it harder for them to remember individuals. It helps to break things up into smaller scenes and memorable moments.
Knowing when to end a session takes practice. About 20 minutes before a play session is scheduled to conclude, it can be beneficial to figure out how you'd like to end. It can be memorable to end with a cliffhanger—a moment so curious and abrupt it raises questions about what happens next. Examples include ending play before combat, when the PCs find vital information, or as they discover treasure. Doing so can inspire the PCs to discuss the game between sessions. Note anything that could be satisfying to resolve over media, such as email. This could include divvying up treasure, leveling up, roleplaying casual character interactions, or completing downtime tasks.
Knowing when to end a session takes practice. About 20 minutes before a play session is scheduled to conclude, it can be beneficial to figure out how you'd like to end. It can be memorable to end with a cliffhanger—a moment so curious and abrupt it raises questions about what happens next. Examples include ending play before combat, when the PCs find vital information, or as they discover treasure. Doing so can inspire the PCs to discuss the game between sessions. Note anything that could be satisfying to resolve over media, such as email. This could include divvying up treasure, leveling up, roleplaying casual character interactions, or completing downtime tasks.
Starting a Session
Source GM Core pg. 11
Once everyone is ready, get everyone's attention and cover the following topics. These are in a rough order that you can change based on your group's style or a session's needs.
- Recap what happened during the previous sessions.
- Establish where the characters are at the beginning of this session. Have they been resting since their last challenge? Are they in a deserted hangar, preparing to break through the airlock into a derelict shuttle? Tell players whether their characters had time to rest or recover since the last session.
- Remind players that they each have 1 Hero Point at the start of the session.
- Establish goals. The players should have an idea of what they want to do next. Reestablish any goals the group already had, then let the players weigh in on whether these goals still apply, and on whether there's anything else they hope to accomplish in this session.
- Commence adventuring! Decide which mode of play you're going to start in, then lead off with a verbal prompt to get the action started. You might ask a question related to a particular character, have everyone immediately roll initiative as a monster attacks, or briefly describe the environment and sensations that surround the player characters, allowing them to react.
The Spotlight
Source GM Core pg. 11
As you run the game, keep track of who has the spotlight. It can be easy to keep attention on the most outgoing player or character, but you need to check in with all the players. If a player hasn't contributed in some time, stop and ask, “What's your character doing at this point?” If the player's not sure, add a detail or nonplayer character to the scene that the player might find interesting.
Stakes and Consequences
Source GM Core pg. 11
A GM should always convey a clear picture of the stakes and consequences of the PCs' actions or inaction. What horrible things will happen if the PCs fail? What can they achieve if they go beyond what's expected of them? A well-constructed adventure conveys the stakes at the outset, but it's also important to remind the players of those stakes throughout play. A game where the stakes are extremely high all the time cuts out the opportunity for low-key scenes, and can be overwhelming or even monotonous. In most games, players enjoy having some scenes where their characters can relax and socialize with low stakes as well.
Consequences should be specific and evocative. Don't just tell the players what happened after success or failure; let their characters witness it in the game universe. Are they treated as celebrities or pariahs? Does the reactor deep within the derelict ship stutter and ignite, exploding as the PCs escape? Does a failure lead to the death of an ally and a somber funeral? It's usually best if the PCs can foresee the consequences, at least in a general sense. If a villain demonstrates their intention to attack a planet, and the PCs don't stop them, then the planet is invaded by imperial troopers or hired guns. It's okay if you have an idea for an interesting subversion occasionally, but keep those to a minimum or the chain of cause and effect will become too muddy.
Consequences should be specific and evocative. Don't just tell the players what happened after success or failure; let their characters witness it in the game universe. Are they treated as celebrities or pariahs? Does the reactor deep within the derelict ship stutter and ignite, exploding as the PCs escape? Does a failure lead to the death of an ally and a somber funeral? It's usually best if the PCs can foresee the consequences, at least in a general sense. If a villain demonstrates their intention to attack a planet, and the PCs don't stop them, then the planet is invaded by imperial troopers or hired guns. It's okay if you have an idea for an interesting subversion occasionally, but keep those to a minimum or the chain of cause and effect will become too muddy.
Failing Forward
Source GM Core pg. 12
Unexpected failure can bring the game to a halt, particularly during exploration. “Failing forward” means finding a way to progress the story instead of saying, “That didn't work.” This doesn't mean the group can't fail, or that the PCs should get what they wanted despite failing. Rather, it means that a failure might still impart more information, reveal a way to improve their chances next time, or even cause unforeseen difficulties. Doing so means the player's choice to attempt a check mattered, even if the results weren't what they wanted. Allowing the PCs to fail forward means fewer dead ends and perfunctory checks. It's important, however, not to put unnecessary pressure on yourself to do so all the time. Sometimes you won't know immediately how a PC can fail forward, and in those cases, it's usually best to just move on.
Improvisation
Source GM Core pg. 12
As a GM, you often make things up on the fly. You can find tips for improvising rules within Adjudicating Rules. When an issue seems to pertain to the story instead of the rules, ask yourself the following questions.
You might not have a good answer for every question, but asking them can inspire useful solutions. If what you need to invent is significant in the storyline or setting, there's nothing wrong with asking the group to take a little break while you fill in the gap. You can even ask players to invent details. If it's not particularly significant and you can't come up with anything more compelling, it's also okay to say “Nothing happens” and move on.
Often, a player will ask, “What happens when I do that?” This is a good indicator that the player expects that what they've done will draw a reaction from an NPC or the environment. Unless the player is way off base, provide an ingame response, even if it's minor. The player has telegraphed what matters to them, and the perceived importance of their action can draw them into the game.
- Does something already established in our story so far tell me what should happen here?
- What would the NPC's personality lead them to do?
- What does the player expect to happen?
- What would best fit the themes of our story?
You might not have a good answer for every question, but asking them can inspire useful solutions. If what you need to invent is significant in the storyline or setting, there's nothing wrong with asking the group to take a little break while you fill in the gap. You can even ask players to invent details. If it's not particularly significant and you can't come up with anything more compelling, it's also okay to say “Nothing happens” and move on.
Often, a player will ask, “What happens when I do that?” This is a good indicator that the player expects that what they've done will draw a reaction from an NPC or the environment. Unless the player is way off base, provide an ingame response, even if it's minor. The player has telegraphed what matters to them, and the perceived importance of their action can draw them into the game.
Special Circumstances
Source GM Core pg. 12
The player characters in your group will at times attempt tasks that should be easier or harder than the rules or adventure would otherwise lead you to expect, such as a PC Gathering Information on their home world. In these cases, you can just apply a circumstance bonus or penalty. Usually, this is +1 or –1 for a minor but significant circumstance, but you can adjust this bonus or penalty to +2 or –2 for a major circumstance. The maximum bonus or penalty, +4 or –4, should apply only if someone has an overwhelming advantage or is trying something extremely unlikely but not quite impossible.
You can also add traits to actions. Let's say that during a fight against a security robot in a mechanic's garage, Obozaya Interacts to give the blades of her doshko an electric charge using jumper cables and a nearby hovercar. You could add the electricity trait to her next Strike so Obozaya can take advantage of the security robot's weakness to electricity. A PC getting an advantage in this way should usually have to use an action to do so, so Obozaya would get the benefit for one attack, but to do it again she'd need to use the jumper cables once more.
You can also add traits to actions. Let's say that during a fight against a security robot in a mechanic's garage, Obozaya Interacts to give the blades of her doshko an electric charge using jumper cables and a nearby hovercar. You could add the electricity trait to her next Strike so Obozaya can take advantage of the security robot's weakness to electricity. A PC getting an advantage in this way should usually have to use an action to do so, so Obozaya would get the benefit for one attack, but to do it again she'd need to use the jumper cables once more.
False Information
Source GM Core pg. 13
A critical failure to Recall Knowledge can result in you needing to convey false information, requiring some improvisation. If you aren't careful, this information can be perceived by the PCs as too silly or could derail the game. For example, if a PC misinterpreted text about the god of war, Damoritosh, telling them that they now believe the god is an incompetent coward who rewards the underhanded might be too far-fetched. Similarly, if they incorrectly believe Damoritosh will reward their strength with immortality if they defeat four prominent warrior priests on different planets of the Veskarium, this could send them on a tangent.
Providing false information can cause the PCs to make mistakes, but the consequences should typically be immediate rather than continual or far in the future. Avoid dispensing false information that might not be used for hours or entire sessions after the check is forgotten. If you're unsure, the safest form of false information is information that's wrong but not in a way that causes major consequences. Remember that a critical failure says you get incorrect information, not that you get important-seeming false information. Erroneously believing Damoritosh's symbol is a sword instead of the blades of a doshko might lead to a miscommunication, but one that's not dangerous, easy to clear up, and only a little embarrassing for the PC.
Providing false information can cause the PCs to make mistakes, but the consequences should typically be immediate rather than continual or far in the future. Avoid dispensing false information that might not be used for hours or entire sessions after the check is forgotten. If you're unsure, the safest form of false information is information that's wrong but not in a way that causes major consequences. Remember that a critical failure says you get incorrect information, not that you get important-seeming false information. Erroneously believing Damoritosh's symbol is a sword instead of the blades of a doshko might lead to a miscommunication, but one that's not dangerous, easy to clear up, and only a little embarrassing for the PC.
Secret Checks
Source GM Core pg. 13
During play, you roll some checks in secret instead of allowing the player to do so, as explained under Secret Checks. This rule helps ensure that a player remains uncertain at times when their character is unsure of how a situation may resolve, immersing the player in their character's perspective. It can be handy to keep a list of the PCs' modifiers on hand to help you roll secret checks more quickly. At least, you should record each player's Perception modifier, their saving throw modifiers (especially Will), and the skill modifiers of any skills they often use to Recall Knowledge. Check in anytime the PCs level up, and consider asking the players to update you when any of these modifiers change.
You can still have the players roll the checks even if an action has the secret trait. This is usually best done when the results are going to be immediate or when stakes are low, like when the PC is trying to recall something during downtime that they'll see is false through the course of their research. You can instead have the players handle all their rolls, secret or otherwise. This works best when the group is interested in leaning into the dramatic irony of knowing a PC is wrong and playing up their characters' mistakes.
You can still have the players roll the checks even if an action has the secret trait. This is usually best done when the results are going to be immediate or when stakes are low, like when the PC is trying to recall something during downtime that they'll see is false through the course of their research. You can instead have the players handle all their rolls, secret or otherwise. This works best when the group is interested in leaning into the dramatic irony of knowing a PC is wrong and playing up their characters' mistakes.
Metagaming
Source GM Core pg. 13
Knowledge the players have that their characters don't is often called “metagame knowledge,” and using it to influence characters' decisions is called “metagaming.” Some metagaming results naturally from play and is wise to disregard. The witchwarper aiming corrosive haze precisely enough to include three enemies in the very edge of the spell's area is probably unrealistic, but isn't that disruptive to play. Things get more questionable if the player says something like “That's a cybernetic zombie, so don't get too close because they self-destruct” regardless of whether their character has encountered a cybernetic zombie before or identified the creature. Each group is different, and the assumption of what the characters know varies. If metagaming starts to get out of hand, you might use some gentle reminders, like “I'm not sure your character's aware of that” or “Can you explain your character's thinking when they do that?” If the problem persists, see the guidelines mentioned in the Problematic Players section.
Roleplaying NPCs
Source GM Core pg. 14
Although the PCs are the stars of the game, NPCs make the universe around the PCs vibrant. They can become a part of the campaign, sometimes for years, weaving into the story right alongside the PCs. Portray NPCs however it works best for you. Some GMs keep it simple, describing the NPCs simply by their looks or their hook (see below). Others go into more detail, using accents, mannerisms, or acting.
Because NPCs have smaller roles than PCs, imparting enough information to convey their identities while they interact with the party can be challenging. When you create an NPC, start by integrating a single “hook” into their concept: a retired space pirate, a refugee from a war in distant space, or a contemplative who constantly asks awkward questions. Each hook hints at a backstory but is easily described in a synopsis. If the NPC continues to interact with the party, you can then add to their backstory later.
NPCs from adventures and other sourcebooks often include basic information about their personality, gender, and role in the game. Important NPCs often include more in-depth roleplaying tips, personal edicts, anathemas, and more.
Because NPCs have smaller roles than PCs, imparting enough information to convey their identities while they interact with the party can be challenging. When you create an NPC, start by integrating a single “hook” into their concept: a retired space pirate, a refugee from a war in distant space, or a contemplative who constantly asks awkward questions. Each hook hints at a backstory but is easily described in a synopsis. If the NPC continues to interact with the party, you can then add to their backstory later.
NPCs from adventures and other sourcebooks often include basic information about their personality, gender, and role in the game. Important NPCs often include more in-depth roleplaying tips, personal edicts, anathemas, and more.
NPC Limitations
Source GM Core pg. 14
Always remember that the PCs have the greatest role in your story. Avoid including allied NPCs who could easily solve any problem the PCs encounter. An extremely powerful NPC should be engaged with matters beyond what the PCs are tasked with or have some limitation that necessitates the PCs' involvement. Remember that an NPC is not “your character” in the way each player has a character. Though NPCs who travel with the party can be effective and fun when handled with caution, an NPC who effectively acts as the GM's character is often called a GMPC (Game Master Player Character) and can contribute to a feeling that the players are being coerced into making certain decisions.
Betrayal
Source GM Core pg. 14
NPCs, even allies, can shift allegiances. They might betray, fail, or sell out their companions, which can make for a meaningful story event. If an NPC is being set up to betray the party in some way, lay groundwork early on so the players don't feel ambushed by the twist. If the players can look back and see a clear path to this result, it's likely they'll feel the decision makes sense in the context of the story. Try to give the NPC a “tell” or a paper trail that can be found, especially one where the players have chances to pick up on that tell with smart use of their abilities and skills.
Respecting the Character
Source GM Core pg. 14
Sometimes when creating characters, a GM can unintentionally play into themes that can be harmful or hurtful. For example, an NPC with a background of abuse, a former or current slave, or a character with disabilities requires respectful handling. This is particularly true if you, as the GM, do not have the same life experience as the NPC in question. If you want to include these themes for an NPC, you should probably bring it up with your players beforehand and set expectations. You don't need to spoil the character, but sitting down and checking in with your players can help prevent unpleasant surprises and is better than assuming. To keep the representation respectful, avoid cliches and don't use the hook as a joke. Your group's guidelines for objectionable content can also help you portray NPCs respectfully
A Proper End
Source GM Core pg. 14
An NPC's story should have a satisfying ending. The NPC might leave your story when they achieve a major goal, go on to other adventures, give up their dream, or die. The death of a beloved NPC should have weight. Make it sympathetic and powerful, and ideally have it take place “on stage” with the PCs present. Be prepared that NPC deaths might stir up strong emotions within the group, and be prepared to cut the session short or to fade to black to mitigate the full brunt of the event if necessary. An NPC's death should matter beyond the PCs' emotions or search for revenge, too—maybe the NPC's sacrifice saved a village or inspired others. Let players see that legacy carried on.