YARG2 , 24 players EA RAND game [7/24 players left]

[Squirrelloid]

Wait, you got a turn 35? Not only did I not get that, Llamaserver said the game was on turn 33! (Its now back on 34, and I am still confused!)

[Squirrelloid]

oh wow, this is made of fail.

The server is sending a different turn number than it thinks its on. Llamaserver thinks its on turn 34, it just sent me an email saying it was turn 34, but when i dled the turn it thinks its turn 35. Of course, this means any attempt to submit a turn will fail, because it'll read the incoming turn as 35, which is not 34, and tell you that you submitted the wrong turn!

Strangely enough, my turn e-mail this morning claimed it was for turn 34 (while the server displayed 33 and the game displayed 34), but the new email also claimed 34 (server displays 34, game displays 35).

Horribly horribly broken!

[rdonj]

I guess the only sensible answer is to send out the llamasignal. Let's do that and see what happens!

[Calahan]

So the llamaserver tricked us into thinking it did a rollback, when it actually just changed the turn number on it's emails and status page to make it appear the game had rolled-back. That's certainly a good one : and confirms the llamaserver is definitly developing a personality all to itself.


Options now are either to wait until llamabeast wades in to bust some heads open. Or roll the game back, make sure everyone knows to use the most recent turn file, and then wait to see (and hear) if it will accept turn files. Or not, because the servers current turn number for the game is out-of-synch with the game's actual current turn number. (as it might be the game that checks if the turn files are correct rather than the llamaserver. If it's the game that checks them, things should be ok. Apart from the out-of-synch status page and emails that is)

[Psycho]

The turn number in the email is different from the actual turn number, that is the only problem. Wait for llamabeast to do his magic and then roll back to turn 34, nobody submit anything in the meantime. Then use the received turn 34 to continue.

[rdonj]

Originally Posted by Calahan

So the llamaserver tricked us into thinking it did a rollback, when it actually just changed the turn number on it's emails and status page to make it appear the game had rolled-back. That's certainly a good one : and confirms the llamaserver is definitly developing a personality all to itself.


Options now are either to wait until llamabeast wades in to bust some heads open. Or roll the game back, make sure everyone knows to use the most recent turn file, and then wait to see (and hear) if it will accept turn files. Or not, because the servers current turn number for the game is out-of-synch with the game's actual current turn number. (as it might be the game that checks if the turn files are correct rather than the llamaserver. If it's the game that checks them, things should be ok. Apart from the out-of-synch status page and emails that is)

Yeah, the llamaserver has learned how to play pranks on us

[llamabeast]

Ok, I haven't looked into the details here, but the server's turn number is now correct. If you guys did a force host, maybe you'll want to do a rollback. Or perhaps you should just continue from where you are.

Sorry about the problems. Turns out it all arises from a typo on Tuesday. Butterflies and all that.

[rdonj]

Thank you llamabeast. I'm rolling back the turn now... pray all goes well, everyone.

[Stagger Lee]

I'm sure you know this rdonj, but the game's gone. Llamasignal?

[Squirrelloid]

This game comes with a terrible curse!

...but it also comes with a free frogurt!