Compare BetonQuest configuration errors with player-state errors

Applies to: BetonQuest; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A quest that fails for one player may have valid configuration but different stored state. Compare accounts before changing a working quest path or clearing progress.

Check the installed content

BetonQuest expresses a quest through objectives, conditions, events and conversation links. Keep the package and player state together during testing. The linked reference describes the 2.2 documentation branch; select the corresponding documentation if your server runs another major version.

Work through the change

1. Record the quest package, failing interaction and first relevant log message. Preserve the package files and player storage checkpoint before making a staging reproduction.
2. Load the same package on staging and inspect unresolved definitions or syntax errors. Fix a genuine load failure before interpreting differences between player accounts.
3. Use one disposable account in the expected starting state and another reproducing the affected state. Compare active objectives, relevant tags and eligibility conditions through supported inspection tools.
4. Run the same interaction on both accounts and trace the first differing decision. Keep a written record of state changes rather than clearing everything until the quest happens to work.

Verify the result

The comparison should identify whether the failure is shared configuration or a specific state transition. A proposed fix should pass both the originally working route and the reproduced failing route.

If the result differs

If both accounts fail identically, return to the shared definitions and event chain. If only one fails, inspect its precise condition or objective state before changing global rewards or dialogue.

Keep a recovery path

Restore the previous staging package and checkpoints if the trial introduces another fault. Any live state repair should be a separate narrow operation with a completed backup, not an undocumented full reset of the player quest history.

References and related help

Check the maintainer reference: BetonQuest documentation, BetonQuest documentation, BetonQuest documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.