NEWS

[SR4] Nexi and processor, persona and subscription limits

  • 6 Replies
  • 4931 Views

sniperfox47

  • *
  • Newb
  • *
  • Posts: 13
« on: <10-23-14/0533:51> »
Hello, I'm looking to get a rule clarification on two issues, sorry if this has been asked before.

1) first processor and persona limit:
The SR4a on page 223 states "Nexi have larger processor limits (System x3)." and unwired on page 50 states "Nexi are designed to run multiple personas; their persona limit equals System x 3."

However, unwired also states "Nexi have a minimum processor limit of 10 and a maximum of 50.", provides prices/availabilities based on processor limit and persona limit, and doesn't have a single sample nexi that follows the first two rules.

What is the proper way to do processor and persona limits? Is it systemx3 for both, or do you pick and choose manually at the time you make the system?

2) Second is with regards to subscription limits on nexi:

The SR4a on Page 224 states that "Each persona is limited to a number of subscriptions equal to twice its System (e.g., a persona on a System 3 commlink could have up to six active subscriptions at a time)."

If I have 3 personas on a system rating 3 nexi, does this mean they can have six subscriptions each or that they have to split the six subscriptions between them? What if I have 9 personas being run on that nexi? If each of them get six subscriptions, how is the system suddenly able to make more connections at a time than with 3? If they have to split the six subscriptions, how could there be 9 connected at once? Unless are 3 of them were stuck in the home node?

I understand that these may not be easy questions to answer and would like to thank you in advance for any clarifications you can provide.


Michael Chandra

  • *
  • Catalyst Demo Team
  • Prime Runner
  • ***
  • Posts: 9941
  • Question-slicing ninja
« Reply #1 on: <10-23-14/0707:00> »
Processor Limit isn't based on the stats, but something you pick when designing the Nexus. The price then depends on how much extra space you want.

For example, if you want a filing system supporting only half a dozen people and 1 program each, you'd go low in the Processor Limit, sticking to 12. If you want to support a dozen people+ics using on average near-3 programs, you'd want to go for the maximum of 50.

You say the Persona Limit of the example nodes does not follow the first two rules. The first list of examples, however, does follow the Persona Limit: Each sample Nexus on p50 has Persona Limit as Systemx3. The Processor Limit, however, depends on the Nexus's owner's choice. Only the prepackaged Nexi aren't exactly equal, which may be a miscommunication or simply representing how corps can get things done differently.

So the small matrix cafe doesn't care about programs, whereas the online shop wants people to run Browse and thus has a higher Processor Limit. The Large Matrix Cafe knows some people will use programs, while the Public Library knows people will be employing programs to help them find and do things.

Each individual persona is limited to their own Systemx2, not the Nexus itself. The subscriptions of the persona aren't relevant, only their subscription to the Nexus matters and that's the Persona Limit.


Let's say I want a Nexus. I want it on System 4, which means the Persona Limit is 12. I want a Firewall of 6 and a Response of 5, and a Processor Limit of 20.

The Response has an availability of Response Rating x 4, so 20. It costs Rating = 5 x Processor Limit = 20 x 100 nuyen, so 10.000 nuyen.

The System has availability Persona Limit / 2 = 6, and costs Rating = 4 x Persona Limit = 4x3 x 50, so costs me 2.400 nuyen.

And the Firewall of 6 has Availability Processor Limit/5 = an easy 4, while it costs Rating = 6 x Processor Limit = 20 x 50, so costs 6.000 nuyen. So this Nexus costs me 18.400 nuyen  for System 4, Firewall 6, Response 3.

If I wanted a 50-PL R3S3F3 system, it'd cost me 11.925 versus the 10k of the Evo Mobile Terminus which has a better Persona Limit because Evo cheats. The MCT Sentinel is overpriced on the other hand.
How am I not part of the forum?? O_O I am both active and angry!

sniperfox47

  • *
  • Newb
  • *
  • Posts: 13
« Reply #2 on: <10-29-14/1804:24> »
Thank you for your reply, I'm sorry for being so slow getting back.


With regards to processor and persona limits:

Since you didn't quote any additional sources can I assume that your reasoning is based solely on the rules I mentioned? If so then that system while being a valid reading, sadly is not the only one that could be made of these ambiguous rules.

We just had our first game session today, and after having a discussion with the player who is playing our hacker, we decided to houserule it a bi based off of how Chummer handles Nexi. Part of the reason for this is if persona limit is systemx3 then why did they write availability and cost as "persona limit ÷ 5" and "Rating x persona limit x 25¥" rather than "Rating/2" and "Rating2*75¥"? These houserules also account for the wonky persona limits on prefab nexi.

Quote from: HOUSERULES
What we did was set a base of systemx3 processor  and persona limits respectively, with a minimum of 10 for processor limits. These are the values that a prefab nexi bought from the stores has. If you get a nexi built for you, or build it yourself then you have your choice of processor limits between 10 and 50, and persona limits between systemx3 and 50. Changing processor limits requires replacing both the response and firewall modules with new modules of matching limit. Changing the persona limit requires replacing the system module.

With regards to the subscription limits:

That's kinda what I figured, but it just seems so artificial to me. I always have problems accepting rules when they restrict things in ways hardware would never be restricted in real life... I need to keep in mind that rules don't need to make sense since they're there for balance rather than RP >.>

Thanks again for the info. I appreciate the heads up, even though we chose to home rule it in this case.
« Last Edit: <10-29-14/1812:25> by sniperfox47 »

Michael Chandra

  • *
  • Catalyst Demo Team
  • Prime Runner
  • ***
  • Posts: 9941
  • Question-slicing ninja
« Reply #3 on: <10-30-14/0236:16> »
As long as you realise Chummer is unreliable and you are using a houserule, it's fine. I consider it silly to use a problematic table over a decent table and explicit rules though.
How am I not part of the forum?? O_O I am both active and angry!

sniperfox47

  • *
  • Newb
  • *
  • Posts: 13
« Reply #4 on: <10-30-14/0312:13> »
Chummer is unreliable at best, I agree, case and point is the aspected magician properties which are all coded wrong. That being said it offers a basepoint.

However if you're using only the sources I mentioned and have no other readings to draw from then while your reading is certainly valid it certainly doesn't follow the "explicit rules". The explicit rules are contradictory since it explicitly states processor limit is both systemx3 (in the sr4 and sr4a) and between 10 and 50 (in uw). In fact your reading isn't even the *implicit* rules since those two rules would imply system is limited to being between 4 and 6 since that's the only point those two rules are both valid.

Your reading is certainly plausible, and probably rules as intended, but its certainly not " explicit rules"... I'm sorry to be argumentative but it drives me insane when people mark their interpretation of a passage as "Rules as Written" as opposed to a home rule. If you had said "at my table we read it to mean this" I wouldn't have thrown a fit like this :P

Michael Chandra

  • *
  • Catalyst Demo Team
  • Prime Runner
  • ***
  • Posts: 9941
  • Question-slicing ninja
« Reply #5 on: <10-30-14/0626:55> »
My guess, by the way, is what we have here is a version change. I don't know much about the FanPro->CGL transition, but I've seen in SR5 what happens if rules are changed while there's already an existing document. Tables and examples are often missed. So my best bet is that CGL had this document, decided to do some balancing and such, and forgot to update the problematic table. The table on the page with the rules, though, matches the new rules perfectly.

For a houserule, by the way, I'd say it's a good idea to use Systemx3 as minimum, to prevent someone from cheaping their way into a Nexus.
How am I not part of the forum?? O_O I am both active and angry!

sniperfox47

  • *
  • Newb
  • *
  • Posts: 13
« Reply #6 on: <10-31-14/0157:11> »
For a houserule, by the way, I'd say it's a good idea to use Systemx3 as minimum, to prevent someone from cheaping their way into a Nexus.

I thought I did state it in our block about what our table did for the houserule, but maybe I didn't. We did set systemx3 as a minimum for persona limit for custom builds but left processor limit with a flat minimum of 10 (as per the standard rules). Since the whole purpose of a nexi (at least in my eyes, correct me if I'm wrong) is their higher process limits. Cheaping out on them makes them pointless if it means taking a low process limit anyways.

One other question did pop up though, is there anything explicitly preventing a single person from running more than one persona for themselves? I'm thinking specifically in terms of an AI character, although an answer for meatbags would be appreciated as well. Either on one nexi, or multiple comlinks via multiple datajacks or trodes?

 

SMF spam blocked by CleanTalk