I’d pick Cities Without Number for short hacking turns, Cyberpunk RED for on-site netrunning, and Shadowrun Fifth Edition for deeper Matrix play. In all three, I’d give the hacker a clear job - open the door, stop the camera, or control the turret - and keep everyone on the same combat clock.
The difference? How many steps come before the crew can act on the hack. I compare actions, resolution time, connection range, and teamwork, while keeping printed rules separate from house rules.
Quick Comparison
| Game | Actions and resolution | Connection range | Crew’s role |
|---|---|---|---|
| Cities Without Number | Move action to Jack In; Main action per program, with Access and CPU limits | Cable access, or wireless within about 98 feet with line of sight | Secure the connection and act on program results |
| Cyberpunk RED | 2–5 NET Actions instead of a Meat Action; passwords and Black ICE can add turns | Usually within 20 feet of an access point | Protect the runner and use opened routes |
| Shadowrun Fifth Edition | Marks, tests, and device commands add steps; VR uses Matrix initiative | Wireless at range; direct connections reward reaching hardware | Help secure access and protect the decker |
My rule of thumb: shared turns aren’t enough. A hack should change what teammates can do next - without giving the hacker extra turns or skipping required tests.
Cyberpunk TTRPG Hacking: CWN vs. RED vs. Shadowrun
1. Cyberpunk RED
Action Economy
Cyberpunk RED puts hacking on the same combat clock as everything else. Each turn, a Netrunner chooses one Meat Action or a batch of NET Actions: 2 at Interface Ranks 1–3, 3 at 4–6, 4 at 7–9, and 5 at 10. You still get your Move Action, so you can reposition or stay near the access point. The trade-off? You give up your attack that turn.
Resolution Time
Moving between NET Architecture floors is usually free. Jacking In or Out, activating programs, and interacting with files, passwords, control nodes, or Black ICE cost NET Actions.
Count NET Actions, not floor changes, to judge how long a hack takes. A shallow system might take one combat turn; passwords and Black ICE can stretch the job across several. Black ICE can force you to protect yourself, deal damage, or threaten your programs. Meanwhile, the rest of the crew stays on the same combat timeline.
Physical Proximity
The normal connection range is 20 feet (6 meters) from an access point, and a wall in the way can block access. That short range puts the runner near the building’s physical infrastructure - and gives the crew a position to protect.
Crew Coordination
The runner needs access-point range. Everyone else needs to secure the room around them.
Side-entrance example: A Rank 4 runner moves into access-point range while two teammates cover the corridor. Jacking In costs one NET Action, and Backdooring the password costs another. Each camera or door control node still takes its own NET Action. On the next turn, the runner can stay in range, keep working the Architecture, and open the door while the crew advances.
If Black ICE or a password stalls the runner, shift attention back to the physical fight. Hacking doesn’t need to become a separate mini-game.
| Feature | RED’s practical trade-off |
|---|---|
| Connection requirement | Usually within 20 feet (6 meters) of an access point; walls can block the signal. |
| Turn choice | Either one Meat Action or 2–5 NET Actions based on Interface Rank, plus movement. |
| Common hack cost | Jacking In/Out, activating programs, and many Interface abilities take 1 NET Action; floor changes are usually free. |
| Crew benefit | Disabled cameras, opened or locked doors, and other device controls immediately change the fight. |
| Isolation risk | Moderate: Black ICE or deeper Architectures can slow the runner, but the shared combat timeline keeps the scene connected. |
2. Shadowrun Fifth Edition
Action Economy
Shadowrun keeps the decker in the crew’s round structure, but working through access layers can stretch their time in the spotlight. Compared with RED, marks and host rules add depth - and more moving parts.
AR keeps the decker on physical initiative. Cold-sim and hot-sim use Matrix initiative; hot-sim is faster but riskier. Hosts and IC also act on Matrix initiative, so the GM should track Matrix and physical turns together. VR leaves the decker’s body more exposed and adds biofeedback risk.
Resolution Time
Access and control are separate steps. Hack on the Fly gains a mark quietly; Brute Force gains one loudly through Cybercombat. After securing access, Control Device uses the action appropriate to the operation - it isn’t necessarily a Free Action.
The decker can affect a fight soon, but must clear the access chain first.
Physical Proximity
Wireless hacking works at range, though hidden or protected icons may require Matrix Perception. Distance and interference add Noise, which penalizes Matrix actions after noise reduction. A direct connection removes distance Noise and can bypass some host defenses, giving the crew a reason to reach the hardware.
A host is a Matrix environment, not simply a stronger device. Entering generally requires a mark on the host. Once inside, devices slaved to it count as directly connected, but that connection doesn’t grant the marks needed to operate them.
Crew Coordination
Sharing the spotlight works best when the decker’s access plan changes the physical scene rather than turning into a side quest.
Checkpoint spotlight check: Identify whether the camera is standalone or host-slaved. For a standalone camera, get the required marks and use Control Device while teammates approach the gate. Host protection can lengthen the access chain; cut back to the rest of the crew after each major action.
During combat: Spoof Command needs a mark on the drone’s owner, not the drone itself, followed by its own test. Direct control needs the appropriate marks on the device. Establishing access before the firefight lets the decker attempt a useful command sooner while teammates maneuver or attack.
| Dimension | Shadowrun Fifth Edition | Spotlight effect |
|---|---|---|
| Access prerequisites | Marks come before control; some targets also require Matrix Perception. | Preparation reduces midfight delays. |
| Physical presence | Wireless access works at a distance; direct connections reward reaching hardware. | Infiltration gives teammates a supporting role. |
| Complexity | Host defenses, IC, alerts, and failed tests can turn a simple objective into a longer task. | Narrow objectives help limit spotlight time. |
Hacking in Cyberpunk Red is dope #short #cyberpunk #cyberpunkred
3. Cities Without Number
Cities Without Number keeps hacking close to the main fight, but it still demands actions and careful positioning.
Action Economy
Jack In costs a Move action, and running a program costs a Main action. Hacking shares the same round as movement and attacks. Each program pairs a Verb with a Subject, such as Blind + Camera.
Resolution Time
First, confirm the connection and a free CPU slot. Then choose a Verb and Subject, pay any Access cost, and roll Intelligence/Program vs. Security, applying any Verb modifiers.
On success, the program takes effect. On failure, the action and any spent Access are lost, and the network may alert security. Each program affects one target, so every additional device takes another action.
Physical Proximity
The connection method makes positioning a team concern. Cable access means reaching the hardware or an accessible maintenance point. Wireless access offers convenience but requires range and line of sight.
The rest of the crew has a clear job: hold space, maintain sightlines, and protect the hacker.
| Requirement | Cable | Wireless | Crew impact |
|---|---|---|---|
| Position | Reach the device or an accessible maintenance point | Within roughly 98 feet (30 meters), with unobstructed line of sight. | Secure the panel or preserve the sightline. |
| Cyberspace checks | No wireless penalty | −2 penalty. | Reaching hardware improves reliability. |
| Active program limits | Active programs occupy CPU | Active programs occupy CPU; the avatar cannot leave the connected node. | Protect the hacker and prioritize effects. |
Crew Coordination
In round one, the hacker moves to the maintenance panel while another teammate watches the hallway. In round two, the hacker spends a Move action to Jack In through a cable and uses the Main action for Analyze + Camera, learning which camera covers the team’s intended path. In round three, the hacker spends the required Access and uses Blind + Camera or Deactivate + Camera. On a success, the team advances; on a failure, the Access is lost and the GM can raise the alert risk rather than starting a separate cyberspace encounter.
Track Access and CPU separately. Access pays for operations; CPU limits how many programs can run at once. A CPU 4 deck can maintain up to four active programs.
In combat, check that the Verb works with the Subject before allowing a pairing like Hijack + Turret. Giving a controlled device a new command can take another Main action. Resolve the check, describe the result, and move initiative forward.
Shared Spotlight vs. Hacking Depth
Shared initiative doesn’t guarantee shared attention. The test is how much extra game state the GM must track before hacking affects the rest of the table.
| System | Action economy | Resolution model | Proximity | Teamwork hooks | Isolation risk | Main trade-off |
|---|---|---|---|---|---|---|
| Cyberpunk RED | Closest to shared combat flow. | Sequential Architecture checks can slow the scene. | Local access keeps the Netrunner near the crew. | Protect the runner; use opened routes and disabled defenses. | Lower than Shadowrun’s, though Black ICE can take up GM attention. | Strong combat integration, but Architecture tracking remains. |
| Shadowrun Fifth Edition | VR adds a parallel initiative track. | Mark-based Matrix actions require extra tracking. | Remote access allows separation; direct connections encourage infiltration. | Secure connections, protect the decker, and use tactical information. | Highest risk of splitting the scene. | Most procedural depth - and the most bookkeeping. |
| Cities Without Number | Hacking uses ordinary combat actions. | Brief resolution, with access and CPU limiting options. | Connection requirements tie hacking to positioning. | Secure access and act on program results. | Less procedural separation than Shadowrun, but isolated connection points can split the crew. | Fast resolution, but less room for repeated actions. |
RED keeps the Netrunner beside the crew and on the same combat clock. Still, running an Architecture can pull the GM’s attention away from everyone else, especially when Black ICE enters play.
Shadowrun rewards precision. Its access chain, mark-based actions, and detection rules give hacking more procedural depth, but they also demand the most bookkeeping.
Cities Without Number keeps hacking brief, while access and CPU limits shape the party’s choices. Keep both resources visible to the whole table so the crew can plan around them.
The next section turns these differences into table habits that keep the rest of the crew involved.
How to Keep the Whole Crew Involved
Use the comparison above to keep the whole crew in the same scene: define the objective, connection, test, payoff, and consequence, then cut only at results or escalation. Build only the network functions the mission needs, and stop when the objective is complete. Make each success immediately useful to teammates, with its duration and restrictions clear. Each system needs a slightly different approach.
For Cyberpunk RED, establish usable cover near the access point. Limit the Architecture to the mission’s immediate control points and defenses so the physical fight stays active. If that position becomes unsafe, make relocation a crew problem. Hacking shouldn’t put physical danger on hold.
For Cities Without Number, track the live connection, what could sever it, and the objective it serves. Keep hacking resources visible. That lets teammates decide whether to protect the connection, secure another route, or drop a secondary objective. When the connection’s risks are clear, the crew has work to do while the hacker acts.
For Shadowrun Fifth Edition, write the shortest rules-legal sequence for the objective. Keep all required marks, actions, opposed tests, and consequences. Use automatic spotting when the rules allow it; save Matrix Perception for hidden targets. Bring attention back to the team after each major step, cutting after each meaningful result without changing initiative timing.
Use this quick reference when spotlight problems arise:
| Pacing issue | Procedure | System(s) | Rules status |
|---|---|---|---|
| One player receives an extended solo scene | Outside combat, alternate short exchanges. In combat, preserve action order and elapsed time. | All three | GM presentation; granting extra turns is a house rule. |
| Hacking succeeds, but the table stalls | Ask which teammate acts on the result next. Follow initiative in combat. | All three | GM presentation; benefits follow the rules. |
| Pressure becomes a random penalty | Advance guards on normal turns. Apply rule-based alarm, connection, and resource consequences - not extra hacker turns. | All three | Rules application and scenario framing. |
Which Hacking Rules Fit Your Crew?
Choose based on how much separate digital action your crew is willing to sit through - not raw hacking power. Compare each game’s action economy, resolution speed, range, and teamwork.
| If your crew wants… | Best fit | Trade-off |
|---|---|---|
| On-site hacking and brief program checks | Cities Without Number | Access and CPU limit the hacker; key systems usually require physical access. |
| Dedicated netrunning on shared turns | Cyberpunk RED | Exploring an Architecture adds depth, but the GM must deliberately shift the spotlight between players. |
| Deep Matrix tactics and escalation | Shadowrun Fifth Edition | Marks, defenses, and Matrix actions require more preparation and pacing work. |
CWN keeps the shared scene tightest. RED takes the middle ground: the runner stays within 20 feet (6 meters) of an access point while acting on the same combat clock. Shadowrun offers the deepest Matrix play, with the most work to keep it moving.
FAQs
How can I keep failed hacks fun for the whole crew?
Treat failure as a plot complication, not a dead end. Keep the game moving with immediate, high-stakes consequences: hazards in the surroundings, arriving reinforcements, or a changed objective. Make the netrunner and crew work together to respond.
Show everyone at the table what changed and why it matters. The setback should move the story forward, not leave one player dealing with it alone.
How much hacking should I prepare before a session?
Don’t spend too much prep time on stand-alone hacking scenarios. Use ready-to-run hooks and job ideas to cut prep work. Build encounters around three-round combat goals or specific tactical objectives instead of complex, separate sub-games.
Keep hacking part of the main action. During combat, netrunners can disable enemy equipment or redirect smart weapons. This keeps the netrunner on-site with the crew and avoids long solo scenes that leave everyone else waiting.
How can I simplify hacking without weakening the hacker?
Keep hacking in the main crew scene, not a separate mini-game, so the netrunner stays involved with teammates. Start with simple attempts, then add complexity as the group gets comfortable.
Use action-economy rules to keep solo turns short. When a hack fails, let it create complications instead of stopping the scene. That keeps the pressure on and the action moving.
