@ PsiSoldier/All
Phonics/Atlantis didn't stale the original turn 84, although I confess to being surprised it's taking so long to submit an altered turn.
The hosting is set to Friday because the game automatically uses the current schedule for working out when the deadline should be during a rollback. Since we are currently on a 72 hour schedule, it correctly (from a working llamaserver PoV) set the deadline to Friday as the rollback occurred on Tuesday.
I could have entered a negative number into the postponement function to bring the hosting deadline forward. But my number one rule of admining is never ever reduce the hosting deadline for any reason what-so-ever. It only causes problems. Also, when the hosting deadline was reduced recently in the 'Forge of Godhood' game, the game decided to host straight away for some reason (the altered deadline was still several hours away at the time). Only bad things happen when deadlines are reduced, while only patience is required on the flip-side of it.
While it would be nice and convenient to just say "Sod it, we'll take the mass stale and move on", I only want to do this as a last resort. Since it could have serious ramifications for the game, and I for one have not spent 6 months and 200+ hours on this game to see it either ruined, or turned into a joke at this late stage. Since there's no telling if this error will even go away if we take the mass stale.
We have only attempted one or two minor things to achieve an error free hosting so far (re-hosting and myself submitting a blank turn), so I would like to at least try a few more things to get the turn to host properly before turning to the last resort. We are making another attempt now, and if that fails, then I will probably be contacting Pelthin/Niefelheim, to see about submitting some 'test' turns where there are no Skratti's with potentially dubious stealth/shape changing orders, to see if the error can be isolated and solved (as per my suspicions stated previously regarding the cause of the hosting error).
This error was completely out of my hands, but I guess I can apologies for it on behalf of the game/llamaserver. But I do want to try and get an error free hosting, and I would very much appreciate a little patience on behalf of the players while attempting to solve it
We all want the same thing after all, which is for the game to get going again, but I'm not yet willing to possibly sacrifice the credibility of the game to do so. Especially not without trying a few reasonable steps to solve it first.
My main problem at the moment is a lack of time to devote to getting this problem solved. As RL work is going to be causing me a lot of very busy days from now until the end of the month, culminating in a four day trip. But I will try my best to find some time this evening to address this issue, and if Phonics hasn't submitted his turn by then, then I'll just force hosting and hope for the best.
But if anyone is frustrated by this error, then just think of the extra RL time it's causing as a chance to enjoy the last few days of summer
(depending where you are in the world). And be thankful you are not the admin trying to solve it by messing around with the llamaserver, seeking help from those in the know, and having to send out/post messages and instructions for everyone during each rollback and error solving attempt.
Patience and understanding is the key to getting this error solved I feel