How do you make hacking useful without excluding other players?

Question

My Shadowrun group has a reasonably typical composition: "face", technomancer, rigger, mage, adept, and street samurai. The problem I have is making sure that the technomancer can use her skills without spending a long time on matrix-only stuff and potentially putting a roadblock in front of important parts of the adventure.

For example, perhaps the party have to infiltrate an office building. It would obviously be very useful to have the technomancer hack into it and take control of some or all of the systems. However, what our technomancer ends up doing is putting the adventure on hold while she hacks into the building's systems, usually involving an extended test over several hours. I don't blame her for this -- this is how the rules work, as I understand them, and it's a totally sensible thing to do. But it's still problematic.

How do I make such an endeavor interesting? I don't want to spend 30 minutes playing out an encounter between the technomancer and the security systems, but neither do I want to give the technomancer access to everything without a challenge.

Basically, I want a middle ground between "just fake a couple of rolls and give the technomancer security access" and "spend 30 minutes on technomancer stuff that nobody else is interested in". How can I run this so everyone feels included and challenged?

Answer 1

Caveat: I bever played Shadowrun - I have passing knowledge of the world etc. but I have no specific experience with the mechanics (or the different editions).

Therefore what I will suggest may very well be impractical (or maybe someone has already provided household rules and then you are lucky ;) ).

If you want to make hacking a meaningful part of the gaming experience, you have to involve the other players. This means (assuming that this makes sense in terms of how cyberspace is depicted) that you must make hacking a mini-game in itself, and provide something to do for each player.

My suggestion: model various "programs" (defensive, offensive, utilities) as seperate entities, and give one to each player - the tactical decisions must be done by the hacker, but each player will have a sort of mini-character sheet and some meaningful mechanic to apply.

Also, have them roll at least part of the skill contests (ex.: attacking program vs. defense sentry) using the program "version" or "quality" as base, and the Hacker's skill as a modifier.

If Shadowrun has already something similar in place, just convert it so that the other players have "something to do", otherwise invent or adapt an unrelated game, maybe even a boardgame - just convert the relevat programs stats and hacker's skill level to the new framework.

I suggest not to make the players part of the defenses, though. This could be fun, but I am not sure that their desire to have the hacker succeed would make this work.

Answer 2

You are not alone with that problem. Perhaps these links can help you:

• Shadowrun 4 - Simplified Hacking
• "Hacking, too easy, too time consuming?" on rpg.net

Answer 3

N.B. I'm not particularly familiar with the hacking rules of Shadowrun. However, this is a general response on how you might structure your game for a more cinematic experience.

Try designing your missions so that the hacking and the rest of the job run in parallel. For example, the ultimate goal is to gain steal a piece of prototype hardware from deep inside a heavily secured compound. As the runners are breaking in, have the hacker attempt to disable certain security systems, open doors, misdirect guards, etc. The runners can get pinned down at a troublesome door, and while they're in a caught in a firefight the hacker can attempt to open the door, providing an escape route; the success or failure the hacker's rolls should determine how long it takes for the door to be opened.

Make sure that as you're letting the active team progress through the mission, you're also cutting back to the hacker to give him something to do. While the runners are dealing with problems in realspace, the hacker should be dealing with problems in cyberspace, and the two spaces should be able to affect each other. Just as the hacker can open the security door, the runners can set-up physical patch lines allowing the hacker to move from system to system. This is the sort of thing you see in movies and television all the time.

Of course, all this might require lightening up on the hacking rules. Make the assumption that the hacker is able to gain initial access to the compound's systems, and any checks he makes are to actually make things happen. Forgo the tedious setup bits, and just focus on the in-the-moment actions that can keep the story flowing.

Answer 4

This is a similar problem to that of having the party split up, especially on a larger scale (think Lord of The Rings, when the Fellowship starts going separate their ways). There are basically two ways to solve this:

1. Have your technomancer show up early and pre-play that part of the session with you. Then when the rest arrive, the building's security has already been hacked into.
2. Use a co-GM. This might be one of the players who has GM'ing experience and can run the technomancer's adventure thread while you run the rest of the party (or vise versa).

As a GM, I've used both of these approaches. The latter worked well, but I felt like I missed out on what happened to the characters while run by my co-GM.

Answer 5

Leverage deals with this rather well, as it's something of a low tech Shadowrun type setting it's a good example. Each of the 5 character types gets a spotlight scene, of which the Hacker is one. So rather than having the party always work together, with the Hacker being separate, you have various scenarios where only one or two characters gets to do anything, and everyone else has some down time. Since everyone has spotlight time and downtime, it ends up being fair, and ends up mitigating the Hacker alone getting spotlight time issue.

Answer 6

There are a couple of approaches that you can take to solve this problem. I'd suggest combining a little of each.

You can try to speed up hacking. A couple of ways to do this:

• Expect the player to know their abilities. If you're running a one-shot game with unfamiliar characters, do the math for them in advance, and write or print it on the sheet. You can give out a copy of pavao's cheat sheet for hacking, too. (http://pavao.org/shadowrun/cheatsheets/)
• Not every node requires multiple hacking tests, and cybercombat. If the player wants to break into a trash can's RFID, and track its coordinates, just let them roll Hacking+Exploit, and tell them if they've succeeded. Save the full-blown intrusion rules for checks that are difficult and important to the adventure.
• Warn them about going off on data-stealing tangents. The longer they're in a system, and the more snooping around they do, the more likely they are to get tracked, crashed, or fried by security. Encourage them to limit time spent in the system, to minimize risk.
• Simplify the math for matrix mooks. As a rule of thumb, I pick a rating for the opponent, and double the rating to determine the IC or spider's dice pool. (Ex: rating 5 > 10 dice on tests)

You can try to run hacking and other activities in parallel:

• Use a co-GM (as Y0mbo mentioned) to run hacking events separately
• Impose a time limit. "Probe" type hacking takes hours. Put them in situations where they only have minutes.
• Prevent them from doing too much work in advance. Use a Faraday cage, or ECM, to block the signal. Run external connections through a 'gateway' node which audits connections every 5 minutes (forcing a reroll against Stealth). Put them in a place with no network, and let them hack only nodes that their commlink can actually reach. Limit the Signal rating of devices of interest, so the hacker has to be in close proximity (recall that hacking is two-way. When communicating between two devices, the lower of the two Signal ratings is used).
• Run hacking in sync with other combat. When the party gets into a firefight with the guards, and the PCs are distracted, that's the most opportune moment for a security hacker to strike in cybercombat. Reveal the presence of new nodes on the network, when the drek hits the fan.

The most important thing overall is to make sure all of the players get GM attention. (It's hard to do!) Put the hacker on hold at a dramatically appropriate moment, and switch to something else. Let the other players scope out the site, do legwork, or fight bad guys, while the hacker is at work. It's OK to leave the hacking player in suspense!

Answer 7

I play a Hacker in a campaign my friends and I came up with one day and one thing that I noticed our group has a lot of issues with is the extra initiative passes me and our adept have. The solution our GM used was to let us use one or two initiative passes when the turn cycle came around to us then let everyone else go and let us take our remaining initiative passes at the end of the initiative order. I feel this works very well since it allows everyone to feel like they are a part of the group and no one person is taking a lot of time on their turn. Also, if they are taking a lot of time trying to think of what to do (believe me I know what it's like as a hacker :~ ) just ask them to delay their action until they can think of what to do, that way they can simply come back at anytime in the initiative order and be ready to go.