-
Notifications
You must be signed in to change notification settings - Fork 0
Journey Outcomes
When a journey ends, the cart is left exactly where it stopped. Nothing is lost and nothing is deleted. The reason is logged so an administrator can tell working as intended from an actual problem.
| Reason | Meaning |
|---|---|
ARRIVED |
Reached its destination normally |
SLACK_EXHAUSTED |
A loop was detected and stopped, working as intended |
BUDGET_EXHAUSTED |
Long legitimate route; consider raising the budget |
STALLED |
The cart got stuck, or rattled around inside one chunk |
DROPPED |
A cart travelling with others ended up far from them and was accounted for alone |
UNGENERATED_CHUNK |
The track heads into unexplored terrain |
LEFT_RAILS |
The cart derailed |
SLACK_EXHAUSTED is the loop detector doing its job. Seeing it on a loop is the correct outcome, and
it is what Verify It Yourself tells you to look for. Seeing it on track you
consider legitimate is what progress-slack-chunks is for.
BUDGET_EXHAUSTED means the route was genuinely long rather than circular, and
journey-budget-chunks is the setting to raise.
UNGENERATED_CHUNK is a track problem rather than a mod problem: the rails lead somewhere nobody has
been. Chunks are not generated to keep a cart moving.
ARRIVED, STALLED, DROPPED and LEFT_RAILS describe what the cart did and need no configuration
change.
Both settings mentioned above, and the clamping that applies to them in STRICT mode, are on
Configuration.