1 April 2012

System Chronometer Glitches

Starwalker rechecked his system chronometer readout - there was clearly a problem. His clone was spending far too long in stasis and had remained inactive for unexpectedly long periods. Starwalker contemplated the problem. It went beyond the time spent waiting for Starstepper to move ships and equipment or monitoring station trading - his actual active time had been reduced.

Starwalker decided to rerun a system diagnostic, perhaps the chronometer readouts were faulty or there was some internal glitch that was keeping his clone inactive. Whatever the reason, Starwalker wanted to be out in space flying his ships and currently that was not happening.

No comments:

Post a Comment