Creating an NPC repository

One of the things I would like to do is a PDF with a recollection of NPC for quick characters in a game or during it's preparation.

The idea comes from the Eclipse Phase NPC supplement which has saved me from more of one headache.

For Cyberpunk I could rely on the quick NPC generation from the core rulebook but it make random characters without any logic. And it doesn't even use any of the info on the splatbooks.

My template would be this:

And an example of a quick NPC would be like this:

Ideally I should make various levels of characters ... low level mobs, average opponents/allies, expert ones, etc. ... it's a lot of work, but well. It ain't gonna make itself, right?

Let's see if I have time to do it.

Edit: One year later ... no, I did not have the time :D that's life for you :P


Anatomy of a Datafortress

You're connected to a datafortress, searching for the financial archives of a small corporation hoping to find something to extort them for. But there's nothing here, only terminal, door and camera links. "Whats wrong?" you ask yourself as you patrol the virtual space within the fortress.

A new data wall rises in front of you, it's security clearance higher than before. As you crack it, the virtual sound of an alarm resounds in your ears. "My program didn't trigger it, I'm sure" you wonder as you hurry to pass the wall an reach the other side.

"One LDL?" is the only think you're have time to think while you jump into it, you don't have time to wonder while the bloodhounds run toward you.

The basics

The typical thing a netrunner do is stealing data from a datafortress, but which kind of data and how do they find it?

Information is stored on databases, folders and files in the system. Those are typically represented as memory blocks which represent local data. But some data is saved on the "cloud", basically an external system usually maintained by another corp.

To access external data you have to enter a protected LDL icon (with a standard Code Gate opener), which will send you to another datafortress with new security measures. Take into account that cloud services boast about their security measures, so expect extreme brute force if they detect your illicit access to their system.

What's in a typical Cloud Memory Unit (CMU)? Boring stuff mainly. Work databases, operations documentation, personal info, provider/client databases, personnel calendars, etc.

What's in a local memory Unit (MU)? The same stuff as a CMU (if the datafortress doesn't use cloud services) and meaningless stuff like power point presentations, internal messages, local info or images ... and the good stuff, the one that's so black that you wouldn't entrust external corporations to manage it.

Bigger is better

The previous schematic is for a single shard server. The one you would find on small enterprises, lone buildings or similar.

Single shard? You must be asking yourself. Well ... when things grow up, a single server isn't enough to control everything. Nor is it even desirable. If your factory machines aren't working as expected, you don't want to reboot security cameras, doors or international operations.

So you connect multiple servers (called shards) and divide the workload between them. Now, if your factory is having problems with the machinery, you don't need to unplug the security systems.

And now every shard has it's own defenses.

Yes, that's more work for you. Aren't you happy?

What does this mean? It basically means that now you have to defeat various data walls to reach the destination you want. You first break into the login/net server which only contains minimal operational MUs and then search for a shard index and try to breach it's security.

You want access to cameras and doors? That's a shard.
You want access to machinery? That's another shard.
You want access to terminals and accounting MUs? Guess it. Yes, another shard.

Every one of them has it's own data walls, code gates and probably, a sysop.

Additionally, some shard are only accessible once you have connected to a specific shard. For example, if you want access to the black ops file, you will need to hack into the initial login shard, then the management shard and then to the internal security shard.

Who runs it?

A lot of datafortress have enough CPU to be managed by AI.

But you won't find a lot of them managing sites anyway. Why? Because AI are predictable, reprogrammable and exploitable. They do not learn or react as a humans (you don't really want an AGI wandering freely) and they do not spawn spontaneously ... which mean you must pay someone to create them.

And when someone find a way to exploit one, the news spread fast between the netrunners hubs.

It's easier, cheaper and more reliable to use human sysops to monitor the system. True, those can be bargained, extorted or even bribed ... but don't expect it. And if the sysop is fried, you don't have to pay his salary.

If a sysop is working locally, they will use the mainframe as their terminal to administrate the datafortress. Which means multiple actions and amazingly fast programs. Also, it means you know exactly where they are on the building and someone can "unplug" them in the real world.

If not, they will use their own cyberdecks and work as a netrunner would.

And that's all.

Try not to die the next time you assault a multiple shard datafortress with multiple cloud services and a mix of black ice ;)


Netrunning small revision

While my initial intention was to use the rules as they come in the basic manual for my latest forum games. I've finally decided to make some small adjustments and clarifications for my players to better suit my preferences.

Step 1: Preparing for the run

The first thing you need is a cyberterminal and some programs. If you miss one or both, you will not reach very far.

When you turn on the terminal and prepare to surf the net, the first thing you'll find is a virtual room off your own terminal. Here you can run your programs locally and specify the name/appearance you'll have once you're inside the net.

Step 2: Traveling on the global network

If you are already connected directly to the target network, you can skip this step.

To travel around the world you have to go through a number of main nodes/proxies. Those are usually in major cities and are often in freely available public lists. However, each node keeps track of your path through the network to inform any tracking program where you come from.

If you want to avoid leaving a trace around the net (that correspond with your real world position, remember I-G algorithms) you have to bypass their security protocols. It's not a very difficult thing to do, but as you reroute signals and stack fake IDs, it slows down your connection.

Each node has a value of "trace" and one of "security" (as always). The former adds to the difficulty of tracking you, the sum of the second divided by two is a penalty of your initiative rolls.

Ex .: If you pass by Night City, Los Angeles, Mexico City, Panama City and City of Bogotá, you'll have a trace value of 13 and a -4 penalty to initiative (7 divided by 2).

Step 3: Infiltration

Once you've reached your goal, you must get into the data fortress and execute your malware ... of which there are plenty.

While you're out of it inoffensively, the system will ignore you. But the moment you start an attack, the system will defend against you (or will send the sysop a notice of your presence). It will be time to throw initiatives and move by turns ... you'll better have Stealth programs to hide or you will understand why runners fear black ice.

Typical checks on the net are:

Initiative: REF + speed + 1d10 terminal.
Stealth and evasion: 1d10 + prog. STR  Difficulty: 6 + Detection prog. STR.
Anti-system attacks: 1d10 + prog. STR  Difficulty: 6 + Data Wall or Code Gate STR.
Anti-personnel attacks: 1d10 + prog. STR + INT + Interface.  Difficulty: 6 + prog. STR + INT + Interface.
Anti-software attacks: 1d10 + prog. STR + INT + Interface.  Difficulty: 6 + prog. STR + INT + Interface.
Drivers and utilities: 1d10 + prog. STR  Difficulty: 6 + Data Wall STR.

The STR refers to the strength of the attacking or defending program. If for example you want to hide, you'll need to use programs to mask your signal or hide your ID and beat the system detection programs (like the Dog series).

If the opponent (either an AI or sysop) is aware of your presence, it can attack you freely. If not it will have to locate you first even if your are running mayhem in their system ... or in a desperate act, they can cut external communications or reboot the system.

To be able to FIND, READ, EDIT, COPY and DELETE data from a data fortress, you first have to overcome their defenses (Data Walls or Code Gates) with appropriate anti-system programs (such as Drill). If you leave the fort and the administrator becomes aware of the security breach, they will be restored.

Step 4: Exit

Once you've finished with your work, you just have to leave to other areas of the net or disconnect (with a roll of 8 or more with a d10).


If you have broken through a data fortress Data Walls or Code Gates, you do not need a test to control remote computer (but you still need the program!).

Without programs you cannot manipulate the net, but you can still browse it, manually interact with Code Gates and access unprotected memory blocks. If you know someone you my try to acquire programs from them or reach Netrunner hubs in the search of a kind soul.

Also, keep in mind that most of Datafortress have public zones where it is not necessary to make a raid to access it. In them you can typically find all kinds of contact information, products or organize meetings.