- Docs
- Getting started
- Reading order feedback
Reading order feedback
What an accepted order means, and why its result can still be a rejection.
An accepted order still needs a result#
An accepted order has entered the match's command stream. The game checks whether it can execute when its turn arrives. Acceptance alone does not mean that a villager has moved or reached the destination.
Figure: order feedback in the experimental kernel-w1 build. This explanatory diagram is not a gameplay screenshot.
Read the outcome#
| Feedback | Meaning |
|---|---|
| Accepted | The order was admitted for a turn. |
| Executed | The game applied the order on that turn. Travel can continue afterwards. |
| Rejected | The game did not apply the order. Read its reason before trying again. |
For example, an order to move another player's villager is rejected. A valid move order for your own villager can execute and then take several turns to reach its destination.
Before trying again#
Check which unit the order refers to and read the rejection reason. Compare the result with the feedback meanings above.
This article intentionally contains no cost or timer table. Those values belong to the applicable game's rules and will require a generated reference when they are documented.