My reading of the latest update is that the server stores pending orders, and commits them at the boot time in the event that the player has not already finalized and committed the orders.

While this may be beneficial in some circumstances, I think this could easily be abused by stallers... that want to drag the game out to the last second each turn by entering orders, and forcing the auto-commit to put the orders in at the last second. Is there anything that prevents this abuse?

As a side question - what happens if not all armies are deployed? Auto-deploy for the remaining armies? Cards to be deleted? Auto-delete cards?

Intentional stalling was possible before the update too, so it doesn't really change anything except make it slightly easier to do. Once the update is fully live I'll start reducing boot times and it won't be as bad. It's a temporary issue.

what happens if not all armies are deployed?

Then they miss out on un-deployed armies.

Cards to be deleted?

If they're forced to play cards then they'll be discarded at random.

Does this mean that you have to play every game until the enemy is eliminated? This can be very annoying especially in ladder games.

Or does it only affect realtime games ?

Edited 2/5/2019 17:41:18

good point Maik. Even if this affects realtime games only, it would be very annoying - imagine someone just rage quit and instead waiting one turn for boot time, you need to play multiple full-time turns to kill him.

what happens if i am matched with a player on the ladder and he doesn't pick in the distribution phase. is he booted or you randomly pick for him fizzer?

New achievement:
Win a ladder game (more than 5 turns) while don't taking any moves by yourself!

I think you guys are misunderstanding the mechanic. It stores orders that you have already put in. So for example if you put in no orders, you still get booted. However if you made 1 move or deploy, that will be used as your turn if you were supposed to be booted.

Ok, thanks for clearing this up. But then I don't see the motivation of this feature. Why should somebody who entered orders but did not commit them shouldnt be booted?

Or does it address a situation like this:

Mmh I would do my orders like this but I am not hundred percent sure. Therefore I enter them but don't commit. If I find time to think about them again, fine. Otherwise they will be automatically used once the boot timer triggers.

Edited 2/7/2019 16:26:31

Why should somebody who entered orders but did not commit them shouldnt be booted?

The best example is real-time games. Imagine you're entering your orders with very little time left. You've got almost all your attacks in but you aren't watching the timer and it hits 0. It's better to use your attacks you were able to enter than use none of them and kick you out of the game.

Possibly, this can be restricted to RT games. It looks in MD it creates more problems than it solves.

Its very good in team games. You can place orders, not commit and wait for your teammates 'ok'. Before it was like 'your orders are good, please uncommit to check mine'...

I'm loving it in multi-day team games so far!

True, the benefits for team games are indeed overwhelming.