The Matrix Explained, ...sort of... Options Track this topic Email this topic Print this topic Download this topic Subscribe to this forum Display Modes Switch to: Outline Switch to: Standard Linear+

[noonesshowmonkey]

General consensus seems to be that the Wireless World section of the SR4 core book was inadequate in providing thurough and usable rules. This thread is intended to expand on the content provided in the core rule book, as a repository for user-created examples of matrix encounters, and function as an FAQ of sorts for the Matrix 2.0 in the 2070s.

Please limit posts to relevant information, questions and responses. I plan to link fruitful forum threads and sites on this thread as well as provide content.

[noonesshowmonkey]

In response to a question asked of my by one of my gamers, I will be expanding on the topic of Agents in this post.

Agents
Agents themselves, as the book states, are intelligent programs that can use other programs. Their effectiveness is limited by their overall intelligence and quality of design (roughly, their Pilot ratings). An agent's payload is its loaded programs. All programs loaded into an agent must be active (and thus count against the system limit for reducing response). Either the agent's Pilot or the node's System (whichever is lower) determines how many programs the agent can load before degradation of performance. Agents loaded onto a node run with the Response rating of the node they are on. Further, an Agent's pilot program cannot exceed the System rating of the node it is loaded on.

An agent functions as an independent connection and any node it is loaded into must use a subscription slot for this connection. This requirement somewhat limits the ability of a system to maintain multiple agents. If a System 3, Response 3, Firewall 3 node has two agents on it when a hacker loads an additional two more agents, its Response is lowered by one for having so many connections and running programs, reducing the Response that the Agent's function at by one which in turn lowers the System by one. As a result of the load placed on the system, all of the agents function with a lowered Pilot rating of 2. These penalties reduce the number of programs an agent can run before reducing response further and the lowered response reduces matrix initiative.

These reductions serve to make it difficult and disadvantageous for a hacker to bring a whole host of minions with him wherever he goes. A hacker can choose to do so, but will likely reduce the node's computing rate to molasses in the process.

So that is a loose summary of how Agents function. But what exactly are the agents, what do they do and how do they do it. For this, example agents are provided. These basic agents are designed for specific functions. An agent’s pilot program functions at its rating or the system rating of the node that it is currently loaded on. Their pilot ratings reflect the System rating of the network that they are run on (a more complex agent requires a higher system rating node to function at peak efficiency).

Agents by Knasser
Knasser's Sample Matrix Sites .pdf contained several useful examples of agents and their functions:

Receptionist Agent (Pilot: 2, Analyze 1): A user interface system operates on this node to deal with visitors, i.e. take messages for the company, direct people to the appropriate person for their enquiry, etc. In VR, it takes the image of a Japanese elf in a crisp, tight suit. The corporate logo glitters in gold on her lapel and her face is VR perfection. If in AR, then the secretary's face appears as a connection icon in the interface. It is capable of holding moderately sophisticated conversations in areas of its expertise. If unable to deal with a visitor, it will contact a (meta) human for assistance. The agent will approach any visitor to the node that it detects with a matrix perception test (Pilot Rating + Analyze vs. Hacking + Stealth). If "killed", the agent will be restarted later.

Low Level Security IC (Pilot 2, Analyze 2, Attack 2, Armor 2): The purpose of this IC is to investigate and deal with any unauthorized intruders on the network. It is normally inactive and will only be triggered if the node itself detects an intruder or if it is approached / attacked by an intruder. After doing so, it will remain on alert for up to an hour, investigating any other intruders. Note that when the IC activates, this reduces the node's response time to 2. The IC will not pursue users beyond the current node, but it will send an alert to its masters if left active after a confirmed encounter with an unauthorized user.

Attack Security IC (Pilot 5, Black Out 5, Attack 5, Armor 5): An extremely nasty piece of IC software originally boosted from a Renraku system and thoroughly sanitized, this IC will use Black Out whenever it can, or fall back on the Attack program only if it must.

***Other tasks and agents, with examples (by me)***:

Agents by NoOnesShowMonkey

Search-Bot (pilot 3, browse 3, analyze 3, optional Decrypt or Scan 3): This search-bot is loaded onto a node with a set of instructions and search arguments and left to run. Its primary purpose is datamining. When loaded into an icon, it functions as a sort of sensor suite if Scan is loaded. When outfitted with the Decrypt program, the search-bot is capable of digging around in even a secure data haven.

Example: In earlier examples LoCoPyRo was searching around a Renraku financial system and found a datacache but did not have time to look through it and accomplish his mission. Instead, PyRo left behind a search-bot to sift through the data and locate paydata. Left with instructions to find sensitive materials (finance or defaulted corporate knowledge, 2 test) or anything with the target’s name, the agent begins to dig through the data on the node, decrypting as necessary.

Smoke and Mirrors (Pilot 4, Spoof 4, Analyze 4): This agent is designed to give a hacker increased exposure time in a secure system by constantly spoofing his data trail. Should the agent become aware (through analyze or the hacker issuing a command) of an active attempt to trace the agent or hacker, the agent begins a redirect action.

Example: Ch0pp3r is doing what he does best: breaking into a secure system and mining it for information. Rather than having to go through the headache of worrying about security, he has loaded a spoofing agent into his persona to do it for him. The slight load on his commlink is worth the security. While he is accessing an employee database looking for work and pay schedules he finds out that some IC is trailing him and trying to determine his location. The agent switches over to redirect automatically and buys Ch0pp3r some precious seconds (via a redirect using hacking + spoof) to find the data he is looking for and get outta dodge.

Ares U-Boat (Pilot 4, Stealth 4, Analyze 3, Black Out 3, optional Sniffer 3): The Ares U-Boat series of IC is popular for its sudden brutality. The IC lurks in a system, checking users one by one and if it detects any nefarious activity it strikes without warning. Most users are not even aware that it is tracking them until they are fried. These IC are often deployed in groups of two or three, a "wolfpack" in hackerspeak.

Example: PyRo is logged onto the Internal Accounting node of the Renraku financial subsidiary that his team is attacking. He has just found his paydata but it would seem as though the system has also found him. Confident that he has slipped in and out like the wind, gotten the paydata without getting a scratch, PyRo does not notice the U-Boat (failing his computer + analyze vs. the agent’s firewall + stealth) until it is too late. Before PyRo can even load up his defensive programs he is slammed by a hard hit from the Black Hammer. Looks like this hacking job won’t be as easy as he thought…

NeoNet Beagle Probe (Pilot 4, Stealth 4, Analyze 3, Track 4, Sniffer 4): The Beagle Probe is technically IC, though it does not directly attack a user. Instead the IC patrols a node, searching for unusual activity and checking every user that comes along. When it detects an unauthorized user (by computer + analyze or electronic warfare + sniffer) it can notify the system, set an alert and begin tracking the intruder. Should the agent be attacked, it will flee or shutdown, freeing up system for a combat agent.

Example: Skulking about the Internal Accounting node on the Renraku system is a Beagle Probe agent. PyRo seems intent on finding his paydata and does not realize that something may be amiss until there is a slight lag in performance as a combat agent loads up. Doing a quick scan of the network yields no information (computer + analyze), so PyRo sets about his work once again. Little does he know, a Beagle Probe has detected his illegal activity and has dispatched a U-Boat agent to knock him off the network.

Operator (Pilot 3, Sniffer 3, Browse 3, Decrypt 3): a common telecom program reborn into a surveillance application, Operator’s primary purpose is the automated detection, observation and interception of commcall activity. Operator logs all communications it detects and once it has begun surveillance of commcall activity moves on to another open connection. The agent may be told to focus on any particular bit of telecom activity or to remain in scanning mode until it finds a particular kind of telecom activity.

Example: LoCoPyRo is running surveillance for his team in at a public park, disguised as a bum. Figuring that two sets of “eyes� are better than one, he loads his Operator agent to help him scan the area for activity. Deciding that discretion is the better part of valor, PyRo has the stealth program loaded into the agent, trusting that a slow response time is better than being detected. The agent first detects and monitor’s the Johnson’s telecom activity and, at the behest of PyRo, looks for any activity connected to the Johnson’s commlink. Finding several different connections, the Operator determines that two of them are telecom and attempts to monitor them.

Again, I hope this is helpfu.

- der Menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemingway

[Rotbart van Dain...]

[Blade]

About agents, you might like to add that there are two different interpretations and, as far as I know, there hasn't been any official answer about it.

1) An agent can be loaded on a node and act on another
Agent is loaded on rating 6 node A and its "persona" goes in rating 3 node B. It will still have it rating 6 because he's still running on node A

2) An agent has to load itself on a node to act on it.
Agent is loaded on rating 6 node A and it wants to go on rating 3 node B. It will unload itself from rating 6 node A and load on rating 3 node B, downgrading his attributes to 3.

If you don't have any official answer, please don't start an argument about it. It has been discussed numerous times and nobody has found any proof that clearly shows the canon answer. Both interpretation have their own advantages and disadvantages and, despite what some people like to say, their own consistency.

[NightmareX]

I find that the majority of the connection limits vs fluff issue simply goes away if one remembers (or if I may daresay reintroduces) the concept of the RTG/LTG.

This presumes one is counting a connection to the RTG/LTG as a single connection subscribed to your system, allowing connection to virtually any amount of nodes IF they are accessed via the RTG/LTG (in a similar way to open tabs on Firefox or IE).

Of course, this is simply my opinion/suggestion - I'm by no stretch of the imagination a Matrix specialist ;)

[Blade]

Obviously, the only raison d'être of the subscription list is to prevent a rigger from controlling too much drones at the same time, to prevent a hacker from having too much agents on the run or and to simply prevent some exploits that could maybe happen if there was no such limitation.

Allowing to use only one subscription for the connection to the RTG/LTG would be ok for drones, but wouldn't for agents (in most cases).

[NightmareX]

[Blade]

The mesh network just costs more money which limits the size of the army. But in the Matrix there's virtually no limit on how many public nodes you can find to load agents on.

[NightmareX]

[noonesshowmonkey]

In response to how an Agent functions and interacts with Nodes and Personas:

Agents Continued...

Agent Response on Nodes and Personas
An agent can function as an independent program, relying on its Pilot program for intelligence (and in fact can be quite intelligent, at times nearing human levels of intellect depending on the subject and the kind of Agent). Agents may also be loaded onto a hacker's commlink and the hacker's "Persona", essentially adding the Agent's functionality to the hacker's icon like a piece of equipment or a spell.

Agents in a Persona
When loaded onto a commlink and a Persona, the Agent counts against subscriptions for that device and is a running program. Both of these conditions serve to eventually lower the Response and System rating of the Persona's commlink should there be too many programs running at once (the aforementioned "mob of agents or drones" effect).

Once loaded, however, the Agent can perform various passive functions on its own. If the agent is running an Analyze program coupled with Sniffer, it may manifest on the Persona's Icon by way of a pair of goggles or high tech sunglasses or some other appropriate metaphor. Such an agent would make Matrix Perception tests on its own every round to see what it could see and report back to the user.

Agents loaded into a persona can only affect that persona, granting extra abilities that its programs have, or affecting the icon it is loaded into. Common uses are for Armor or Medic programs, functioning as an automated combat medic.

An agent loaded into a commlink may engage an agent or IC or hacker that is attempting to hack that commlink. By the intruder attempting to open a connection on the node, there is sort of local instantiation of the intruder that can be attacked by the agent. In this way, an agent can be loaded onto a tech-luddite's equipment and will vigilantly guard that runner's system.

Example: Proto’s commlink runs a nasty chunk of software he has named “Butch�. “Butch� is an IC program given to him by his buddy LoCoPyRo. PyRo claims that he was getting tired of Proto’s complaining and getting hacked during runs, so PyRo setup some IC. In their next run a security hacker tries to hack into Proto’s commlink to mess with the linked cyber. When the hacker is almost in, “Butch� has at him. The poor hacker didn’t see the Black Hammer 3 coming… Looks like if this hacker really wants to screw with Proto’s gear, he is going to get a headache at the very least.

Example 2: See earlier example for "Smoke and Mirrors" the spoof program.

Agents on Nodes
If a user wishes to have an agent perform functions beyond the local or passive levels or wishes the agent to run autonomously while he runs off to do something else, the hacker must load the agent onto a node. An agent loaded onto a node uses that node's Response for its own and cannot run a Pilot program higher than that node's System.

An agent so loaded can autonomously run its program payload and go about its business. If its controller’s access permissions include mobility through other nodes (or if those nodes are public), the Agent can move from node to node if it is equipped to figure out how to do that (has an Analyze program for perception). An agent of sufficient quality may even hack its way into various systems if it is loaded with the necessary program suite. Such independence comes at a cost, however. The agent must report back for new instructions as it reaches various goals and this can create a datatrail back to its controlling hacker.

For an agent to engage in cyber combat on behalf of an Icon, it must be loaded into the Node so that its programs can actively and directly interact with (ie fight) the programs loaded into that node.

Note that all Agent programs are considered active and its rating is considered its System for determining program overload. A low System rating on a node can lower the Response of the Node and the Agent, further taxing the agent when its programs are too numerous for it to run effectively. The latest whiz tech can only run as fast as the subsystem (node) it is loaded onto and there is no Matrix constitution that states that All Nodes Were Created Equal. A company does not need a high speed, massive connection hosting server to manage information that only gets accessed infrequently and by a few users. Such a system would not need to accommodate the system load of several agents on top of a couple of hackers smashing the system apart with high tech programs.

It is useful to remember that the "reality" of the VR matrix is directly generated by whatever Nodes a user is in contact with. If the integrity of those nodes is challenged by way of overloading them, the literal world will begin to glitch, a "Bullet Time" effect may occur unintentionally as everything hiccoughs for a moment as the system tries to keep up. As a general rule, a Node has a System and Response rating equivalent to its use, sensitivity of information and intended program loads. A high security node needs a high System and Response so that several users can be going about their business while a security hacker patrols along side of multiple agents. This also means, however, that high security Nodes, by their nature, provide intense, high speed VR combat zones because the system itself is capable of rendering in high detail all of the chaos.

Example: Ch0pp3r is chopping his way into a particular slice of data heaven: a NeoNet telecom server. He makes his way onto the server and has a look around, deciding to snoop around in the Client Accounts node (System 2, Response 2, Firewall 2). The Client Accounts node is a large data storage node that is used in conjunction with several other nodes. Currently loaded is a Switchboard agent (pilot 2, Browse 2, Analyze 1) that scurries about and finds users data. Ch0pp3r gets unlucky and the Switchboard agent somehow scans him and finds his illegal programs and sets an alert. Ch0pp3r drops a Search-Bot to find him some paydata and gets ready for IC to show up. When the IC finally comes around, the node itself is at a snail’s pace. Switchboard, Search-Bot, Attack IC and Ch0pp3r are all active in the node, reducing system and response to one. Luckily, the IC itself will have a hard time doing anything (its Response is probably in the toilet, and so is its Matrix initiative) but that does not change the fact that Ch0pp3r must spend even more time finding his paydata… more time while the system is aware that something is wrong.

Example Agents that run on a commlink and Persona

Saw Bones (pilot 3, medic 3, armor 3): Saw Bones is an automated medic program that can be loaded into an Icon or Node. The Agent functions akin to a combat medic, identifying damage and doing its best to repair the wounded program or icon.

Example: MCCCXXXVII is hacking his way into an Ares Macrotechnology security server. Not the brightest idea, smashing through the front gates, but that’s what the circumstances allowed. He is immediately greeted by a pair of IC and things get rough. The first round of combat results in seven boxes of wound damage to his Icon. The next phase comes up and MC3’s Saw Bones agent kicks in and makes its Pilot + Medic check and fixes three boxes of damage. By the end of the round the two IC are toast and MC3’s Icon is nearly fried, but the Saw Bones is slaving away to fix him.

Mitsuhama X-Scan Pro (pilot 4, Scan 4, Sniffer 4): Mitsuhama’s offering for the surveillance market landed with a splash. The X-Scan Pro is a highly intelligent program designed to ferret out hidden mode commlinks, hidden nodes and generally find anyone who does not want to be found.

Example: Grot Harvey, hacker extraordinaire, is in the midst of a run at a Yakuza gambling establishment. His goal is a secure file server somewhere on the premises. He loads the X-Scan Pro with an additional Stealth program and lets it run while he plays some AR games. Within a few minutes the Agent has located four hidden mode commlinks and encrypted wifi traffic between three separate nodes. Logging all the information, Grot makes a show of “losing� some nuyen and leaves the gambling den in disgust. Hopefully he can crack the crypto, analyze the data he has and figure out if the server is out there.

Example Agents that run on a Node

Havok-Bot77 (Pilot 4, Attack 4, Exploit 4, Stealth 4, Analyze 4): When a hacker needs a distraction, he calls on the Havok-Bot77. The prime directive of this disruptive little chunk of software is to run amok in a system, crashing all mundane programs it comes across. When it detects IC or a security hacker, the Havok-Bot77 lets out a cackle, leans on the stealth program and flees looking for another unsuspecting and unarmed victim.

Example: When it comes time for Grot to smash his way into the Yak’s secure server at the gambling den and get the payadata he has no idea how he is going to do this and not get fried… He decides to try out the Havok-Bot77. Hacking his way into a secure account, he loads the Agent on to the network real quietlike and lets it rip. Within moments several programs that monitor cameras are crashed and the system alert status skyrockets. IC come flying out of nowhere to engage the nasty little imp. In all the confusion, Grot loads up his Exploit program, cracks his digital knuckles and starts to hack the server with all the subtlety of a thousand pounds of TNT. If he is lucky he will get in and out before the system can realize what he is doing and re-task IC to come and get him.

Search Bot: See earlier notation and examples of the Search Bot.

Useful information on this post has been cross-referenced and added to the main Agent's post as necessary.

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemingway

[noonesshowmonkey]

System's Guide to Paranoia v1.3 by Serbitar

An utterly amazing resource for understanding the ways of the wireless matrix in the 2070s from the shadowrunner's perspective.

Includes descriptions of how necessary and actively used a Commlink is, how vunlerable the wifi connection it actually is and how much any given ID hack can get you. Well written with some very classy quotes.

This should be standard reading for any tech-savy party member of a Shadowrun game. Completely indespensible.

Some golden quotes:

[Dashifen]

[Sterling]

[Fortune]

This is very helpful. Thanks 'monkey. :)

Can an Agent that is active in a person's Commlink call up another stored but not currently active Agent? For example, Muffintop has an Agent (Analyze, Sniffer, Spoof, Stealth) loaded into her Commlink. If it detects a hacking attempt, could it call up it's big brother (not active at the moment) to attack the intruder?

[noonesshowmonkey]

In response to questions about Agents being able to call in other Agents:

As intelligent programs that can use other programs, I am inclined to believe that they can start other agents. The tricky issue is whether or not the action of loading the agent requires a complex action by the hacker who is controlling the commlink either through system load or by active work to load the agent. I am inclined, for the sake of balance and sanity, to say that loading an agent takes a node a complex action (regardless of the hacker being active or not).

This is a very dangerous issue, however, as finding conditions that result in the spawning of agents can easily be exploited and bring a system to its knees. In fact, one of the matrix examples I am working on right now reviews this very phenomenon...

Anyhow, I will be offering an in depth example of a system that is setup for complete automation at a later date. In the mean time, I hope that this quick response is plenty.

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemmingway

[Fortune]

Thanks.

Ok, same scenario as above. Would the Big Brother Agent that is called up need to include Analyze in its loadout in order to attack the intruder?

[noonesshowmonkey]

In response to the necessity of an Analyze program on a combat Agent:

If the intruder has been found by the system, it has been found. Unless the intruder makes an active and very serious attempt to hide, he is in the spot light and can be thoroughly (excuse the pun) lit up. Think of a discovered character who was at one time stealthed. They are considered in plain site (man I am punny today).

Personally, I ain't a bettin' man, but most hackers are not so slick as to duck and run immediately and play it slow. But then again, there are some pretty smart chummers out there and a few of 'em are stupid enough to plug a perfectly good brain into some computers.

A great way to keep a player on their toes would be to attack with programs that use Stealth regularly. Most attack IC that players (and NPCs) use will be combat heavy, leveling an Attack program next to Armor and skimping on Analyze. In general, however, Analyze is used for Matrix Perception. Without the program the agent would have to default to its Pilot rating. This may be enough to track an intruder and engage it, but I wouldn't count on it.

In general, however, any Combat IC Agent that is worth its 1's and Zeros will include a decent Analyze program.

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemmingway

[Fortune]

That's helpful, thanks.

So, is there any limit on the number of non-active Agents that can be stored on a Commlink?

[noonesshowmonkey]

In response to the amount of inagents capable of being loaded into a commlink:

In SR4 with the advances in computing tech and memory, there is no particular reason to track storage space. Thankfully we do not need to tabulate our current memory on a graphing calculator as in SR3.

So no, there is no limit (other than nuyen) to the amount of programs or agents loaded onto a commlink.

I can remember, just a scant few years ago, operating on a 512 mb hard drive... And only a few years before that, such a drive was massive. Now I run on a pair of 150 gig SATA drives and they are a little "small" compared to a lot of things currently available... Oh SR4, the future I can't wait to have sometimes!

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemingway

[Fortune]

Ok, that's what I thought, but I wanted to be sure. Thanks again.

More on Agents ...

Could a hacker send out a pair of Agents to work together (independent of the hacker), one a search-type and the other to protect the first and cover tracks?

[noonesshowmonkey]

In response to the tasking of multiple agents to a complex task:

Presumably, yes. Agents can work together quite well. The question at hand will be program load and inter-communication. I would guess that if a Pilot program is a barometer of general intelligence, that the Pilot program would be a good place to start in determining if Agents are capable of automatically performing any given task as a team without further input from the host. There is nothing in the rules that would suggest a hard limit, but I would suggest a soft limit of Pilot/2 rounded down. This would derive a number of Agents that can work together without causing problems of whole armies of agents marching off to hack the planet.

Without some manner of limit, a hacker is motivated to load a zillion mini-agents to do a task. Logically speaking, a low Pilot program is not expected to be able to figure out complex tasks (a dog brain, afterall), much less coordination amongst other agents working on that shared complex task. The limits built into Nodes for program load and subscriptions ought to do a decent job of handling over-taxing a system.

Good agent teams would resemble the stealthy pair of the NeoNet Beagle Probe and the Ares U-Boat, for example. Remaining entirely clandestine, the pair would stalk about a node, looking for trouble. Once found, the U-Boat can either engage or follow an intruder until other IC comes to assist.

The following is a rough guide to how intelligent a Pilot program is regarding the use of its programs, its ability to understand complex tasks and coordinate its effort, and to execute its tasks efficiently. The most important aspect is, however, the human touch: discretion.

*** content generated by me and in no way backed up by any rulebook ***

Pilot rating 1 - Dog Brain: A rating 1 pilot program is capable of understanding basic instructions in terms of geometry or timing. Examples would be to "go there, do this and then that". General intelligence would be limited to pre-programmed responses based on a specific topic.

Pilot rating 2 - Semi-Intelligent: At rating 2, a Pilot program can engage in more complex tasks, even compound tasks, limited reasoning, and is far more dynamic. Intelligence still is limited to an area of expertise, but the program is capable of realizing its own limitations.

Pilot rating 3 - Intelligent: By rating 3, a pilot program is capable of reasoning within its area of expertise with little instruction. A rating 3 pilot program can autonomously engage in basic level problem solving and regularly produce positive results. As a program, it is self-aware enough to know its own limitations and understand its role in the system to where it can take appropriate action and is capable of a surprising amount of animal cunning.

Pilot rating 4 - Very Intelligent: As a highly developed piece of software, a rating 4 pilot program has complex AI behaviors that can extend well beyond its basic functionality. Even complex tasks such as loading and unloading software dynamically or intelligently traveling nodes, can be attempted with a reasonable rate of autonomous completion. Interactivity is on par with a human for areas of expertise.

Pilot rating 5 - Extremely Intelligent: Programmed by truly talented hackers and software engineers, a Pilot program at rating 5 is almost a true AI. Self aware, intelligent, capable of learning and processing data at rates that are beyond that of humans, a rating 5 Pilot program can engage in extremely complex tasks and be relied upon to reach success. Self-awareness extends to being aware of other programs as complete entities with limitations, not simply as tools. A rating 5 Pilot program can, with sufficient input, function indefinitely.

Pilot rating 6 - Supra-intelligent: Representing the pinnacle of AI programming, a rating 6 Pilot program makes a mockery of most humans with its massive apprehension rate and uncanny capabilities. Completely self aware to a point even of human cunning, a rating 6 pilot program goes beyond a simulacra of human intellect to some strange in-between. Nearly any task can be reasoned through as any highly intelligent human with massive memory banks would be capable of doing. Perhaps its largest drawback would be the rank efficiency and the coldness of its operation.

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemingway

[noonesshowmonkey]

Gah... it looks like I will be needing to consolidate all the recent banter about Agents into yet another Agents Continued (part 2) post.

Expect some cleaning soon.

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemmingway

[Fortune]

You've been extremely helpful. Sorry for semi-derailing the thread.

[Aku]

im sorry, i disagree with your assumption that the pilot limitd the things a program or drone can do. Anything can attempt something, but the pilot limits how WELL that can be done. Just like any other test. Just because Joe Blow made a Cha 1 face, are you only going to let him try to talk a little kid out of their lunch money?

[noonesshowmonkey]

If you read closely the Pilot program explanations they explain that the Pilot program gives a guide for how complex of a task can be expected to be performed with success.


Purely extrapolating "rules" based on the guidelines given above:

If you were to give a drone a simple task, such as "go there, do this", it is not hard to do. However, asking an agent to carefully hack its way into a secure node, load up some new programs, learn the node and its functions, choose which area of the node is most likely to result in a mission complete and then hack its way around other nodes looking for information or whatever its goal is... Then I think it is reasonable to assume that would take a Pilot (task difficulty) check. In the extremely complex task the threshold would be around a 3. A pilot 6 program can succeed that kind of task most of the time. Preperation on the part of the hacker to extend the "basic functionality" of the agent towards the task at hand would help a great deal.

When I have some more time I will post further explanation including a chart of what would produce modifiers, what a good threshhold is.

Note that this information is in no way required and in fact I would personally not even use it. This information is to be used as a reference for understanding what a player can expect from a drone. You can ask a Pilot 1 drone to do a complex series of tasks... and you can also expect it to fail regularly. If a GM has a good understanding of what a pilot program means, how they interact with Agents, and what an Agent can ge expected to do then he can completely forgo the rules. This is the best of all worlds. No rolls, no time spent, totally streamlined... But the book itself provides very little in the way of explanation or example regarding the intelligence of a pilot program or what a pilot program for an Agent is like.

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemingway

[noonesshowmonkey]

Hacking, a “How To�
a primer for hacking in SR4

Though the SR4 core book provides all of the tools necessary to go about a hacking scene, construct a network and navigate the complexities of hacking, the book itself provides little in the way of guidance or explanation. As a result, players, in my experience, are not sure how to go about hacking, what to do, where to do it and in what order. The purpose of this section will be to explain exactly these things and to use the tools in the book to create a scene, show how to do this and then how to run that scene.

Terms to know:

Hacking can be a rather complex process and it is good to understand a few complex terms before setting about the task at hand. When hacking a system, several key features come to the fore.

Accessibility: Where the network that you are hacking is located is a measure of accessibility. Whether a target is a commlink that requires the hacker to be within the signal range of the device or a closed network on a corporate campus, a hacker needs to know where to find that target network and the conditions of the hack.

Exposure: Once the network is found, even if only abstractly, a hacker needs a way in. The weakest link of a security system is generally the guard (he can be bribed, he falls asleep or becomes disinterested, he can be shot or strangled or knocked out) and often it as at the points of intersection between men and machine that a hacker finds the greatest exposure. Networks also require connectivity to function and this leads to exposure. Wireless connections to drones, cameras or any device that is logged onto the network can provide a hacker with the toe-hold needed to scale the security ladder.

Security: While a corporate campus can at times seem impenetrable, its network’s defenses of inordinate complexity and redundancy, every network must share information to function. Security sees to it that only those that who are allowed to access information can get to it. From IC to corp-spiders, difficult and confusing network design, cameras and motion detectors and even mundane or dual natured animals, it is amazing the diversity and complexity of security systems.

Sensitivity: To a skilled hacker, few things are impossible. In fact, most things can be done, given enough time or recklessness. Any system can be hacked. Some systems and their administrators, however, make it their business to make hacking their networks highly unprofitable. When a hacker is engaged in clandestine and hostile computer work he should never forget the scope of the job at hand. Should he bite off more than he can chew, he may get away with it but not live long enough to use the data. Sensitivity is a measurement of how meaningful data is on a network and of how far that data’s owner is willing to go to protect its integrity.

By reviewing these abstract terms, a hacker (or a GM) can quickly assess the steps necessary to hack a target. By reviewing this list, a hacker can quickly assess whether or not the job can be done and perhaps find new methods for completing the mission.

Example: Grot Harvey is trying to hack his way into a Saeder-Krupp employee database to find information for an extraction. Thinking of accessibility he comes up with several options. He can check the matrix for published public data, though this is unlikely to yield information about sensitive targets. Without having a reliable and direct source for information he settles on hacking the S&K subsidiary that his team has been casing.

Doing some legwork comes up with info on the system design: the employee records are held in an on site, closed and wired network that is routed through other Saeder-Krupp facilities in the region. His info also comes back with a word on Security: Saeder-Krupp maintains some very nasty IC and several security hackers that are on call. Its all BlackHammer out there, chummer.

Through various bits of leg work and minor hacks to gain information, Grot determines that there are several routes into the network. His team can kidnap a middle manager and make him “call in sick� to “telecommute�, piggybacking his connection. An alternative is to hack into the security devices on the exterior by staging a “maintenance call� on one of the cameras that must be in communication with the rest of the system in some fashion. Once in, Grot could hack his way back through the Security node and perhaps into the Employee System. A third option would be to infiltrate the Saeder-Krupp facility and setup shop right near the server’s location, drill through the walls and try to hack directly in.

Some more legwork reveals that security on site is tight with several patrols of armed guards making regular rounds. The guards make general use of dual natured dogs and the whole of the campus is wired for motion detectors and cameras. Presumably a High Threat Response team is on call. Saeder-Krupp is well known for handling problems “in house�, so LoneStar will not even be notified.

Grot decides on the following: Access demands that they get into the main Saeder-Krupp network without going through the main matrix nodes – too many hacking jobs, too much time in the system and too much security. For exposure he chooses the weak link of the networked camera as his way in. Security will be tight, with meat bodies and IC all over. Sensitivity is nearly high enough to have him call it off, Saeder-Krupp is known as an organization that you don’t fragoff and live to tell about it. Hopefully, if he is quick and thorough, no one will be the wiser!


***Later hacking templates will include:***

Can You Hear Me Now? - How to Hack a Commlink in all of its glory.
This is not the Cyberware You are Looking for – Hacking security devices on the fly.
More to come…

- der menkey

"Certainly there is no hunting like the hunting of man and those who have hunted armed men long enough and liked it, never really care for anything else thereafter."
~ Ernest Hemingway