While a step of the day waits for the route worker, the player can act. Three steps then resumed on what they had
noted before:
- a sales trial overtaken by an action ran again with the happy customers as indices into S.biz: a customer dropped
meanwhile made one point past the end and the day stopped on an exception. dayAgain() makes the trial's checks,
the customer and who is happy again on the game as it is; an offer signed or declined by hand meanwhile is not
the desk's;
- the intern's PNI round placed the batch's quotes as they were: a PNI ordered by hand while it waited was ordered
a second time. pniRequote() quotes each order again just before it is placed;
- a failure and the monkey's snip took the last incident after their routing: repaired meanwhile, it was gone or
another one. They keep their own incident before the routing, and offer a repair only while it stands.
The day split of #312 on its own, from 3.0.0, without its routing core, save or map changes. On a big network at
x8 the game stopped whenever a day rerouted: after a failure, an event, the NOC intern's shift or the sales desk's
signing, dayPost() routed on the page.
* The day is a generator (dayRun(), dayPreRun(), dayPost()): each yield is a compute() it needs. dayTick() answers
them on the spot (tests, fallback); in play rwGo() posts each one to the route worker. A failure (failureRun()), a
DDoS and Auto-RTBH (ddosNewsRun()), the chaos monkey's snip (mkSnipRun()), an event's cut (eventRun()), the
intern's shift (opsRun()) and the sales desk (slAutoRun(), its trials answered by the worker with offerTrial())
are steps of the day. fireFailure(), opsDay() and slAutoDay() still play them in one go.
* yield DAY_REST lets a long day draw a frame between two steps (half a frame, 3 to 8 ms, RW.budget). One day in
flight at a time, resting or routing: the clock waits for the day, and a half day is never saved.
* UI.tick is set around every step (dayStep()), so quiet notifications hold in play, not only in dayTick().
* The daily mood check works out the land islands once per pass over the customers (TERR), instead of walking
every land link for each customer afraid of sharks. This fix is thesysadmindev's, from #310; here the islands are
worked out again if something routed meanwhile (RW.gen), since the mood loop can now rest between customers.
Same game either way: tests/day-steps.test.js plays a second page as the worker and compares each day with
dayTick(), the intern on every order, failures, events, DDoS and the monkey forced.
Thanks to thesysadmindev for the profiling in #310 that pointed at the reroutes, and for the sharks fix.