Keep a BetonQuest journal entry separate from objective progress

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

A journal can describe progress without starting or completing the underlying objective. Check the event paths independently when the book and quest behaviour disagree.

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 journal entry ID, objective ID and the point at which each should change. Save the package and a disposable test-player checkpoint before editing the flow.
2. Inspect the events that add or remove the journal entry and those that start or finish the objective. Check their references against the documentation matching your installed branch.
3. On staging, enter the quest normally and inspect both the journal and active objective state. Perform partial progress and completion while recording the resulting book text.
4. Test relogging and a normal restart, then compare a second account outside the quest. Confirm that narrative text and progression are updated for the intended player only.

Verify the result

The journal should accurately describe the active or completed state, while objective tracking should work independently of whether the player has opened the book.

If the result differs

If text changes but progress does not, inspect the objective event chain. If progress works but the journal is stale, inspect entry references and update events rather than resetting the quest.

Keep a recovery path

Restore the saved journal and event definitions together if the trial becomes misleading. Keep production player progress intact and correct the presentation path separately from any genuine missing objective state.

References and related help

Check the maintainer reference: BetonQuest documentation, BetonQuest documentation.

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