QUOTE (Yerameyahu @ Mar 11 2011, 04:27 PM)
On a side note, I think it'd be more interesting if the System were limited by the *current* Response rating. As it stands, Response degradation does nothing except make you marginally slower in Cybercombat, so feel free to run as many programs and subscriptions as you want.
Judging by the SR4 book (not SR4a), that was how it worked when they first wrote it:
QUOTE
Edited: I apparently botched the formatting of the quotes here and lost the info I typed in twice, so I'm not looking it back up. Suffice to say, on page 213 of the SR4 book, it says flatly that System is capped by Response rating, with no mention of it only being capped by the base response rating.
What it looked like in SR4 (again, not SR4a) was that if your Response dipped too low from running programs (or any other reason), your System would drop and higher rated programs would likewise drop.
This actually made a lot of sense. If you jammed up a node with programs the Response rating would drop, and the System rating would be affected. If you piled on so many programs that the Response dropped to 0, the System would go to 0 and the whole thing would come down. This served as a limitation on players for how many programs they run, but it also served as a cap on the number of IC that a company could conceivably keep on a node for defense. Too many IC would lower the Response and System of the node, and reduce the overall effectiveness of system security.
This was never updated by errata, but it was changed in SR4A (and the FAQ has an explanation) so that the only the
base Response rating matters for capping System.
This swings the pendulum completely in the opposite direction, since Response only matters in Cybercombat.
Thinking back to earlier editions, where transfer rates and file sizes mattered, I might propose some house rule to make Response a little more meaningful:
Current Response rating caps the number of hits achievable on each Data Search, Transfer File, Encrypt, Decrypt, or Edit roll made as part of an extended test. It's not crippling, but if you jam up your commlink with all your pet programs at once, you'll take a really long time to perform extended actions because your commlink is struggling to handle the data load.
Just a thought.