CHROME Rulebook /// control

Scenes and Encounters

Scenes

Those who have experience playing TTRPGs know that sometimes game sessions can run longer than expected. CHROME is played in a Scene-based structure to help facilitate a more efficient and engaging experience. This allows players and Control to get to the action of the story quickly. If your group has no time restrictions or enjoys a more open sandbox-type play-style: it’s your game, ignore everything we say and play however you choose!

While on Mission, the Operators receive an assignment and then progress through a series of scenes to accomplish that assignment. Some Missions may have a single Scene, and others may have several.

All Scenes Have

A Purpose: Something of relevance to the Operators’ Mission.

Examples

  • Information to be learned
  • Combat
  • Items to be located
  • A person to be met

A Location: A place where the action occurs.

Examples

  • Abandoned research station
  • Seedy bar in Ward 14

Some Scenes have

Non-Player Characters

  • Allies (friendly)
  • Bystanders (neutral)
  • Enemies (hostile)

Loot

  • Gear and equipment
  • Experimental tech
  • Credits

Encounters

When Operators roll , and the action becomes turn-based, it is considered an Encounter. Most commonly in CHROME, an Encounter means physical combat. But many other situations that require player and adversary turns are considered Encounters as well.

Encounters

Scenes are the places where Encounters happen. Encounters are dice-resolved conflicts. Most often, they are combat Encounters, but not always. Any time the players attempt actions contested by the environment, enemies, or NPCs that require dice rolls and game rules is an Encounter.

Operators may be attempting to hack a system via a series of or doing battle with a cybernetic abomination via Combat. Both are Encounters.