Yeah in the latest release it works like this:
- First 3 commands received by the engine are processed like usual
- The last command received is ignored (for the current tick), and queued only to be processed on the next tick.
When I initially raised the issue the command queue was cleared on each tick, so 1 bot’s command was essentially discarded every tick (and not re-queued). This has since been fixed.