Topic: SAP timers gone mad

Like this

Have a productive day, runner!
R.I.P. Chenoa, you'll never be forgotten.
DEV Zoom: Line, sorry, I was away for christmas.
http://perp-kill.net/?m=view&id=252086

Re: SAP timers gone mad

New Crimea happened twice, 11:27 and the second SAP right at 12:27, raising it from 80 to 100 within an hour (we killed the first SAP, didn't do specimen.
Am I wrong or should SAPs only happen after 8 hours? Or is this a new feature?

Re: SAP timers gone mad

It seems this is only a one-time glitch (or three-time to be precise) due to the restarts yesterday, not a permanent bug. We're still investigating.

Re: SAP timers gone mad

3 intrusions/outposts were affected:
South Iseitsu
Fort Douglas
New Crimea

The first two had no stability change, they remained at 100 so we didn't have to interfere.
New Crimea went from 80 to 100 due to the issue, so we reverted that back to 80.

Also deleted the 3 faulty intrusion log entries.

Re: SAP timers gone mad

how about uria?..

The theory of mutual interests
Why the crybabies wins?
Где Ханя - там победа (с)
DEV Zoom: No need to speculate...

Re: SAP timers gone mad

Offer for the next patches: one day before install of patch, set the time of next patch as 2 days + standard random time.  I mean just freeze for a time maintenance work.

Re: SAP timers gone mad

I would cancel any events for the few days after each patch (such like intrusions).

The theory of mutual interests
Why the crybabies wins?
Где Ханя - там победа (с)
DEV Zoom: No need to speculate...

Re: SAP timers gone mad

Yeah we missed Uria, deleted that entry too. (no stability change there either)

Btw we used to turn off intrusions for patches but we forgot it now...