For context: I am programing a die roller which is part of a much larger project.

Thread for the roller

And the question came up:

Can you stack Edge to reduce interval in half, rush the job to cut the interval in half AND program in a nexus programming environment to half the interval effectively making your interval / 8 on a programming extended test?

I would really like to know what everyone thinks as I want the die roller to be as accurate to the rules as I can get it.

Thanks!

yes you can, while remembering that using edge to half your interval is a houserule and not in the list "spending edge" in the core book.

Some people think so. *Shrug*. I don't think you'll get a better argument.

Wow, thats surprising as you take say the 3 month interval (assume 30*3 days / 8 ) 11 days 6 hours per roll (if my mathing is correct).

It is indeed. I'd never allow it.

if you have a sleep regulator you should be able to reduce the effective time even more. although that's not in the rules some will agree with me.
an interval of 3 months is probably intended to equal 3 x 4 x (5 or 6 ) workdays. with one workday being like 10 hours or something. But that's when the developer fell asleep and forgot to mention it.

It would have been nice if they had listed them as man hours or man minutes, or something like that. (or women hours, or person hours if you prefer) Just saying it takes a month or a week doesn't work well.
Unless you take it to mean 7 days of constant none stop work, ie 7 days x 24 hours of total work to be done. After all that's what an extended test that's got an interval of 1 complex turn, or 1 minute would be. There would be no breaks, it's constant work.

Using a month as a measure of time is a bad thing to do in any case. Since not all months are equal. Best I think to use 4 weeks. I think that works better.

The Edge being spent that way is under optional rules, The Rush the Job and Nexus Programming environments are not. Although in all honesty, all rules are optional, and each group has to individually decide what rules to use and what rules not to use.

Not house rule directly, as that would not be in the book at all. It is listed as a optional rule for edge use. As such it sits on the middle ground between a house rule and a official rule.

yes. my bad. false assumption an posting to fast

Ok I need clarification since I have now confused myself wile programing this in...

If one were to use edge to 1/2 the interval (Glitches on 1s only)
If one were to rush the job to 1/2 the interval (Glitches on 1s And 2s)
if one were to program in nexus env. to 1/2 the interval (Glitches on 1s only)

So if all were combined it would be interval / 8 but 1s AND 2s would be applied toward glitches correct?

yes, correct.
no matter WHAT ELSE you do, you are STILL RUSHING it.

can you still use Edge on glitches (which have a good chance to occur now)? afaik you may use edge only once at any given test.

Ok the "I want a Rating 12 Program in 3 days stacking rule set" is in there.

Will someone please check the accuracy of it? --> The Roller


I'm fairly sure its working correctly but its always better to get fresh eyes on it.

When you use SR rules to optimize the Five Year Plan it does start to creak a little bit.

Common Use software has a threshold of Rating, and Hacking software has Ratingx2 so, 12 would not take all that long to create at a base of 1 month for the interval. Even without doing anything special.
Hacking would be not really be all that different. A threshold of 24 with a 1 month interval is not all that bad. Now having that 1 month dropped down to 3 and 3 quarters days makes you write it in a couple of weeks...

After getting all the rules in its not that bad a thing to allow stacking... If you rush a job your chances to glitch out are pretty high. So players would end up wasting more time than they saved by going for it.

Yes, lots more bugs in the software becomes likely with doing a rush job on programming.

But you can still reduce time by factor of 4, not rush the job, and get your 12 Week interval down to 3 weeks... Not bad at all... And, as some have indicated, with a Sleep Regulator, you may even benefit with a time reduction of 8, without rushing, so that 12 week interval is now 1.5 Weeks/Roll...

I imagine a programmer would use the time gained from a nexus programming environment and a sleep regulator for watching porn and playing games. Then 1 month before the deadline he recognizes he's behind schedule and rushes the job and invests all his mental resources.
all in all he finishes in the originally estimated time.

I definitely would.

I agree that it's a pretty big stretch to assume that your programmer spends his every implant-augmented waking hour doing nothing but making programming progress. The simplest answer is 'the RAW doesn't say anything about more waking hours speeding up Extended tests'; I think that's pretty unsatisfying, but better than your players walking on you.

SR3 had a rule for working/training that said that any character could work for 8+Willpower/2 hours a day and could roll a Willpower test to squeeze some more hours. I liked it. I guess you could use it for SR4.

So that is how the Corps do it...