[Calahan]

I either currently am admining, or have admined, several games over the past few months, and can also confirm the recent llamaserver disobedience.

My experience to date is that the game obeys the hosting time stated on the game's status page, but any deadline or hosting time you see referenced anywhere else is not to be trusted.

As a prime example, anyone who has ever used the "Postpone Hosting" function can't fail to have noticed the message that comes up afterwards which says....


"Hosting postponed for (Name of Game) by X hours. The game will now host at Time : Day : Date.

Please note that this information will not be updated on the game status page for a few minutes."


The time stated in this message is not to be relied upon at all. Since as a matter of rule, whenever I postpone a game, I always make sure that the llamaserver has updated itself (usually every 5 minutes unless it is currently processing a game turn, when it updates after it), so that I can confidently say that the postponement I requested has actually taken affect. I'd say currently roughly 5% of all the admin jobs I do, and llamaserver functions I use, have to be re-done due to the first attempt not having been carried out by the llamaserver.

To date, everything has gone through on the second attempt, and I have never seen a game host before the deadline (without negative delays featuring in some way).

But I would advise that all admins make sure to check the status pages to ensure postponements are taking affect. And don't rely on either the admin logs or the post postponement message as any sort of guarantee that a postponement requested has actually happened. Since the only hosting time statad anywhere that means anything is the one on the game's status page, so an admin should always check the time on that page until he/she can see the postponement has been registered. Or re-do the postponement if it hasn't registered. Although always make sure the llamaserver has definitely updated itself since the request was made.

Edit: All the above is just in my experince of course, and not how the llamaserver is designed to work (as it usually works very reliably indeed)