<Cybercore>

Mission Tier

Missions and Ops (Operations) in Cybercore are categorized by a Mission Tier, guiding GMs to appropriate challenges for each Tier. Players must know the Mission Tier in advance, as specific abilities hinge on this designation.

GMs; for mission design, pacing, encounter building, and the three-Op arc, see the GM Guide: Missions.

Abilities labeled "per Mission Tier" grant usage based on the Mission's Tier; once for Tier 1 missions, twice for Tier 2, and thrice for Tier 3, aligning closely with the player's current Tier. The same applies to "per Op Tier" abilities.

Example: Tier 1 Mission; "Cargo Recovery on Kepler Station"

Your squad of Rank 2 operatives is tasked with recovering a stolen data core from a derelict cargo hub. The GM sets this as a Tier 1 mission, TL 40.

The mission has three Ops:

  • Op 1 (Infiltrate): Dock at the station, bypass the airlock security, and scout the interior. The Sec-Ops hacks the docking clamps; rolls d100 + Electronics vs TL 40.
  • Op 2 (Execute): Locate the data core in the server room. A scavenger crew is already there. Combat breaks out; enemies have TL 40. Your AF roll of d100 + 15 needs to beat 40 to avoid taking full Hits.
  • Op 3 (Extract): Grab the core and get out before the station's automated defences come online. The Rigger jury-rigs the cargo lift; Engineering vs TL 40.

Your Medic has an ability marked "Once per Mission Tier." On a Tier 1 mission, that is one use for the entire mission; choose wisely whether to spend it in Op 1, 2, or 3.

If this same squad later runs a Tier 2 mission at TL 65, that same ability gets two uses, every skill check is now vs TL 65, and the enemies hit a lot harder. Same structure, higher stakes.


Mission Threat Level (TL)

Every mission has a Threat Level (TL); a single number that represents the overall danger level. The GM sets the Mission TL at the mission briefing. Individual Ops may have a different TL (higher or lower) to reflect localised difficulty spikes.

Mission TL Table

Mission TierRanksSuggested TL Range
Tier 10–340–50
Tier 24–655–75
Tier 37–1080–100+

All skill checks, saving throws, and contested rolls on a mission use the Mission TL as the target number. Roll d100 + modifiers vs TL. That's it.

TL 40 is the floor of organised play. The combat outcome bands (TL−30 / TL / TL+30 / TL+60) are tuned so that a Rank 0 squad at TL 40 trades constant chip damage with rare spikes; risky but fair. Below TL 40 the bands collapse into safety: a starting squad Deflects most incoming and Solid-Hits half its attacks. Save TL 20–35 for juvenile creatures, mooks, and hazards that are meant to be swept aside; never for a mission's baseline.

Individual Ops and Creatures often override the Mission TL with their own TL when the local situation is significantly harder or easier than the mission baseline.

Mission Threat Bands

For operations involving electronic systems, security infrastructure, and networked environments, the Mission TL is divided into three Threat Bands; a Low, Standard, and High threshold representing the range of difficulty across systems on any given mission.

Low Threshold = Mission TL × 0.75 (round down) Standard = Mission TL High Threshold = Mission TL × 1.25 (round up)

Mission TierTLLowStandardHigh
Tier 1 Low40304050
Tier 1 High50375063
Tier 2 Low55415569
Tier 2 Mid65486582
Tier 2 High75567594
Tier 3 Low806080100
Tier 3 High10075100125

The GM uses Threat Bands to set difficulty for networked systems and electronic infrastructure:

System TypeExamplesTarget
AccessDoors, elevators, airlocks, basic locksLow Threshold
SensorCameras, motion sensors, scannersMission TL
ControlLife support, gravity, lighting, commsMission TL
WeaponTurrets, defense grids, automated dronesHigh Threshold
ServerData cores, AI systems, command networksHigh Threshold

GMs can assign any individual system a different difficulty if the narrative demands it. Threat Bands are guidelines; a back-alley terminal might sit at Low even if the mission is Tier 3, while a prototype server on a Tier 1 mission might be set at High.


Introducing Deep Ops

Deep Ops serve as specialized, optional Ops within a Misson, adding a layer of challenge and extending the standard three Op/Mission format. Engaging in a Deep Op will stretch the squad's resources even though it provides an opportunity to recharge or gain extra uses of abilities according to the Deep Op's Tier.

For example, consider an ability designated as "per Mission Tier" already used in the Tier 1 mission. This ability would be refreshed should the player embark on a Tier 2 Deep Op, granting one additional use. Similarly, "per Op Tier" abilities would receive an extra two uses. This recharge mechanism offers players enhanced flexibility and a strategic edge as they strive to achieve the added objectives of the Deep Op. Nevertheless, pursuing these optional Side Ops presents a significant gamble of risk versus reward. Successfully navigating a Deep Op without tapping into the extra ability allows its conservation for subsequent Ops within the ongoing Mission. Conversely, failing the Deep Op leads to the loss of any unused abilities and further depletes resources due to operational strain.

Opting into a Deep Op comes with inherent risks, potentially affecting the outcome of the primary Mission. Players should know the Deep Op's Tier beforehand, employing strategic foresight or abilities like Rodi Premonitions to make informed decisions. Even environmental cues, like a sign warning of a "Level 2 Secured Area," can serve as subtle hints towards the challenge level ahead.

It's important to note that the difficulty of Deep Ops is scaled according to the parent mission's Tier, ensuring challenges remain balanced. A Tier 3 Deep Op on a Tier 1 mission is not the equivalent of a genuine Tier 3 Op. If it wasn't scaled, it would lead to a less enjoyable experience for the players and potentially give manic GMs a case of the giggles (You know who you are).

Deep Ops: The only thing harder than the mission is explaining to HQ why you painted a smiley face on the ships hull.

-- Jock Stargazer.