If you have a token on the turn-order, then delete it (say it was slain). The turn order for the client will update but the API server will not receive the turn-order changed event. When you advance the turn-order, you get two events back-to-back as the API server plays catch-up. This isn't really an issue except if you have a script that's watching the top of the tracker. If you delete the token currently at the head of the tracker manually, as no turn-order event is fired, nothing updates to account for the current 'turn' which is the new head of the turn-order. Does this happen to anyone else? I do admit it's a niche case for scripts tracking initiative. I could circumvent it, but then I'd have to account that on the next turn advancement the event is old and should be ignored before coming back in sync on the second event (of the double change events). EDIT: I also believe that Campaign.get("turnorder") still returns the old turnorder with the deleted item's id still within, prior to the deletion pending on however it's internally tracked.
