PlanetsCentral

Stefan, I'm not sure the game is completely reset to the previous state.

Please take a look at the game info page: http://planetscentral.com/host/game.cgi/11-Pleiades-3

and then at the scores at turn 35

• 6 The Cyborg 536892
• 1 The Feds 492607
• 4 The Klingons 462246
• 2 The Lizards 356000
• 10 The Rebels 337955
• 5 The Privateers 335429
• 11 The Colonies 334132
• 8 The Samurais 302752
• 7 The Tholians 298381
• 9 The Robots 238787
• 3 The Bird Men 156659

and turn 36

• 6 The Cyborg 548090
• 4 The Klingons 493459
• 1 The Feds 476835
• 2 The Lizards 398788
• 10 The Rebels 353497
• 11 The Colonies 349177
• 5 The Privateers 335696
• 7 The Tholians 317567
• 8 The Samurais 301600
• 9 The Robots 247181
• 3 The Bird Men 174814

Several players' scores don't match neither of those scores.

In case you verify everything is correct, do we have to submit turn36 again?

Thanks.

EDIT:

Mmm, could it be that the host run again and some players changed their turns? That would explain why some scores change and others don't.

ComCitCat in Re: kinda holiday:

That was truly unexpected... I can't remember the scheduler acting that way from Just a Second. Anyway, granted that no one objects I'll end my t35 now and send it via mail?

The problem with computers is that they do what you tell them, not what you mean. Thinking a little more, what the scheduler did was totally expected: host runs Sundays and Thursdays 16:00 GMT, and since there was no Sunday turn, it'll happily run a host in the 16:00 -- 22:00 time window allocated for the host run. It was a busy week, so I probably would have overlooked that anyway. Sort of like an easter-egg, maybe.

I have now reset the game to the previous state and hope I didn't break anything (there isn't a function to do that yet in the software, so it's manual work in the file system and database).

Please submit your turn file for turn 35. Since everyone has seen the "preview" of turn 36, I cannot forbid you to use that knowledge and update your turn.

I will monitor the game and re-enable the scheduler when everything works fine again. Sorry for the inconvenience.

--Stefan