Here's how it works, for each phase:

1. Consider all players with unprocessed orders. Is the top order for everyone an Order Delay card? If so, process one OD card from everyone.
2. Process the top order from each player whose top order is not an order delay card.
3. Reverse the move order.
4. If there are still unprocessed orders, go to 1.

https://www.warlight.net/MultiPlayer?GameID=11157247 Turn 7.

The attack phase begins to process. Sultan has first move, Njord has second. First, we check if all player's first order is an Order Delay card. They aren't.

Now we process one order for each player. Sultan's first order is an Order Delay card, so he's skipped. Njord's first order is the attack from Kenya's so it's processed and removed from his pending orders list.

Move order reverses. Now Njord is first, Sultan second.

Both players top order is an OD card, so we process both of them.

Now we process one attack from everyone. Njord is first in the move order, so his transfer to Hong Kong goes first.

Thanks for the explanation Fizzer. Farah had it right ;)

Thanks Fizzer. Sounds legit

That makes sense, but doesn't seem like it should be that way. I always thought if both used the same card (in the same position), they would just cancel.

Good to know.

I thought it worked that way too.

Thanks for the explanation. I had misunderstood aspects of this card and apparently wasn't alone!

Here are proposed changes to the turn history messages to clarify the order delay card behavior.

change 1: When a player is 'skipped' due to an order delay card on top of their orders, add a history entry like "playerX delayed".

change 2: Reword the message "playerX plays an order delay card" to something like "order delay card for playerX expired".

So the history for turn 7 https://www.warlight.net/MultiPlayer?GameID=11157247 would start like:

Sułtan delayed
16 armies... (Njord)
order delay card for Sułtan expired
order delay card for Njord expired
1 army... (Njord)
17 armies... (Sułtan)
...

Would these changes be useful?