Board Game Arena

I consider it a bug that self::eliminatePlayer() occurs immediately, whereas notifications via self::notifyAllPlayers() are batched and occur at the end of the request. This makes the game log very confusing because it's out of order. See attached. The state sequence is: 3 (activeplayer) -> 10 (multipleactiveplayer) -> 60 (game) -> 15 (activeplayer) -> 60 (game) -> 91 (game) -> 98 (game). I am doing the elimination in state 91. The message appears in the log far earlier than it should for some reason.

I want the elimination message in the game log to appear in the correct order with other notifications, or at least I want the ability to suppress anything from printing in the game log (and I will handle this myself). How can this be fixed?

Only admins can actually fix that, but I found that multiple game states does not work well together.
I got multiple weird issues, mixed notifications, unroll affecting all game states (i.e. if something bad happens in last state
it unrolls all game states), so end up re-working state machine not to use chained game states unless absolutely necessary

I don t know if it could help, but if you suit several autostep states , you need to send a 'notify' (without anything, if you don t need to do something to the client) on each to synchronise server and client, if not synchro refresh is not done

This incorrect logging order has been fixed in the framework.