Multi-Commlink Hacking Rules, Curbing the Hacker-muncher insanity. Options

[mdynna]

First, some concepts need to be firmly established that are implied but not explicitly stated in the SR4 core rulebook.

1. Every Commlink has only one Persona and that Persona is permanently connected to that Commlink (it is “burned” into the MPCP chips - to use the old terminology)
2. A user (Hacker) can only focus his “consciousness” on 1 location of 1 Persona at a time. Any other “instances” of any other Personas the user is controlling are sitting idle.
3. Agents and “Utilities” are the only programs that can “piggy back” into a system with a Persona. Other Persona programs can not.
4. (This one I created) Shifting your “mental perception” between active Commlinks is a Complex Action. Eg. “Moving” from your cyberware Commlink to your external Commlink connected through Datajack or Trodes. Working a second Commlink in AR mode while another is in VR mode incurs the normal penalty for taking “meat” actions while in VR.

The results of these rules are as follows. If a Hacker wishes to bring multiple Commlink Personas into a host, each Persona/Commlink must hack into the system independently. That means if you hack into a system with Commlink A, then want to bring in the Persona from Commlink B, the Hacker will need break through the Firewall all over again using the attributes and programs present on Commlink B. Meanwhile Persona A, present in the system, would be sitting idle and vulnerable to attack. Subject to your GM’s approval, the Hacker could break in using Persona A and validate a user account that Persona B could use to log on.

Secondly, Matrix damage done to Persona A does not carry over to Persona B, their CM’s are tracked separately. However, any “Black” attacks made to any Persona connected to a Hacker through DNI will damage the Hacker’s “person” regardless of whether they are “controlling” that Persona at the time.

Thirdly, given the permanent link between a Persona and its originating Commlink there is no way to avoid being traced. Given enough time and enough hits, any trace will eventually find its way back to your Commlink. That means that, unless you have a really long datajack cable or a big stick to hit the buttons on your Commlink with, your physical location can be determined. Using Commlink A to log into Commlink B and then hack a system does nothing. Either Persona A will leave a copy of itself in Commlink B, or Persona A will leave Commlink B. You can use a standard Redirect action to “route” Commlink A’s “call” through Commlink B but this should be handled exactly like any other Redirect action. The final point is: there is no way to make a “call” coming from a Commlink untraceable.

Does anyone have anything else to add?