For reasons yet unknown, kassandra had stopped responding - With this latest restart, I took the opportunity to roll in the latest batch of changes, namely:
. better handling of mixed case names
. now processes all recent @requests instead of just the most recent
. nag threshold correctly set to T-36H
. pay or trade orders accept both ‘@playername’ and ‘playername’
. shutdown notices properly trapped
. additional improvements to the kassandra personality module
All orders that have been submitted so far have been preserved. I’ll continue to keep an eye on things in the meantime.
"A rather large number of irregular withdrawals? Or perhaps an irregular number of large withdrawals? Or perhaps it was a just large withdrawal of irregular numbers? You know, the sort of thing that digital lifeforms do on the regular?
“Now if I were you, I’d be more concerned about the integrity of your exosuits than the integrity of your accounts. But what do I know? I’m just the gal that tries to keep this place running. Sheesh!”
“Hard to tell with Kassie sometimes. She’ll forget to hang up the intercom when she’s talking to herself or just get a little chatty. For the record: I maintain the accounts, she just writes the checks. No juice goes anywhere without my say so.”
Okay - it looks like the fix for the fix for the fix is working. I’ve added some extra debugging around the order parsing to make this easier to find if it happens in the future.
“Post-launch temporal shift, also known as ‘ship lag’. Don’t worry, it happens a lot to new crew members. The nagbot module was was installed for exactly this reason!”
I’ll try and run the numbers over lunch today and get round 2 up later this evening. The simulator isn’t nearly as finicky as the parser and I’ve been testing it in the background all week long to confirm accuracy.
