A well-run scene typically follows a clear sequence:
GM Describes the Scene
Begin by painting a picture of the environment, key details, and immediate points of interest.
Example: "The neon-lit docking bay hums with the magnetic clamps of arriving ships. A flickering holo-sign warns 'Restricted Access' in three languages, while a pair of armoured security drones patrol near a battered cargo hauler. The scent of ozone and stale synth-coffee hangs in the recycled air."
Players Seek Clarification
Players will naturally ask for more details to inform their decisions. Encourage this—it means they’re invested!
Example Questions:
"Are the security drones armed, or just surveillance models?"
"Does the cargo hauler look recently damaged, or is it just old and poorly maintained?"
"Is there anyone else in the room who stands out?"
Players Take Action
Now, players will respond based on the information given. This could involve roleplaying dialogue, making strategic choices, or attempting skill checks.
Example Actions:
"I’ll try to hack into the docking bay’s security terminal to disable the drones—rolling interfacing."
"I motion for the team to act natural and pull out my scanner for a closer read—rolling detect."
"I approach the cargo hauler’s crew, flashing my forged ID badge—rolling Deception to bluff my way onboard."
Resolve The Action
The action works as intended, but the world reacts.
Example Success:
"You hack through the security grid—the doors hiss open. no one seems to notice…"
The action fails, but the story moves forward.
Example Failure:
"The door doesn't respond, the system logs your intrusion; you’ve got 90 seconds before lockdown."
Example Complication:
"I think accidentally trigger a subroutine. The AI mistakes me for an admin and starts uploading its entire database to my wrist computer, which makes it frozen until I get it fixed.
With the action resolved whether through success, failure, or a thrilling complication the cycle begins anew. The GM describes the evolving situation, players ask questions and plan their next moves, and the dice decide their fate once more.
With scene progression understood its is still important to consider a few a other factors
1. What’s the point of the scene
During a scene you should be mindful of what it’s for. Does it advance the story or character development. Is it about exploring the setting, characters or NPCs. Is it about having fun or an opportunity for banter, is it just a break between scenes or encounters. You might have what you want the scene to be in mind but should reflect, is that what others want. You should be flexible and willing to cut or expand upon scenes given player interest. Maybe an opportunity to advance the plot comes from a silly or fun scene, if a scene appears not to interest the players skip over and incorporate any important elements into the next scene. All stories benefit from editing and keep in mind that lengthy scenes with loving amounts of detail may actually be constraining the story.
An alternative to assigning objectives to scenes is having a bullet point list of things that you aim to communicate in the session. If this list is close by you can slide these points into the emergent narrative rather than constructing rigid purpose built scenes to communicate these plot points.
2. What’s the tone of the scene
Tone sets the emotional backdrop of the scene, influencing how players engage with it. Whether it's tense, mysterious, humorous, or dramatic, tone affects player immersion and decision-making. Understanding what your table prefers in this regard is helpful. If your players prefer a lighter whimsical tone then lean into it while taking brief dives back into the darker side. Invariably a mixture is likely the best solution too serious or too silly can pull people out of the characters and the world. If it’s too bleak then player character motivations might be hard source aside from survive. Similarly if the story has no consequences it may tend to have shallow characters doing things to see what happens with little consistency or opportunity for development. For a tense encounter with a rogue AI, use dark, ominous descriptions and a foreboding atmosphere. For a humorous subplot, incorporate witty dialogue and light-hearted scenarios.
3. Link in the lore
A shortcut to build stakes and sourcing character motivations is to use Armournaut’s world building as a scaffold. This will save time but allow characters to make more in character decisions. For instance a GELF character can use this element to inform their feelings on the factions and characters in the story. A Venti merchant prince may dislike aligning with characters that are ideologically opposed to them or run counter to the interests of the republic. Armournauts bicker amongst themselves about whether ASC or MOA are more honourable weapons of war. In any case the wider lore of Armournaut is rife with tension and conflict and drawing on these wider conflicts can inject a greater sense of urgency and stakes into your sessions. Now remember you mustn't adhere rigidly to the lore. Members of factions are first people and they themselves are flawed and inconsistent. Don’t be constrained by elements of the lore that might stifle your collaborative storytelling in a scene. The lore can provide motivation for your NPCs but be open the emergent narrative of your sessions. Motivations change and the cluster is a weird place with shifting alliances and complex competing interests.