Test quest changes¶

Result: New quest content works with a test player before players see it in production.

Test workflow¶

Copy the production setup to a private test server.
Back up the files and database you will use.
Change one quest idea at a time.
Run bdq reload.
Confirm that the command reports success, then read every warning for the changed group and quest.
Give the quest to a test player with bdq give.
If it uses need-starting: true, confirm progress is ignored before bdq start, then start it.
Test actions that should add progress.
Test actions that should not add progress.
Check task rewards, quest rewards, and cosmetics.
Restart the server and check saved progress and started state.
Test reset or reroll behavior when the quest uses it.

Content checklist¶

[ ] The Quest ID is unique and will stay stable.
[ ] The referenced group exists.
[ ] Every task ID is a unique number.
[ ] Task types and targets exist on supported server versions.
[ ] Conditions pass and fail in the correct situations.
[ ] Invalid condition values prevent the quest from loading.
[ ] Console commands are safe after placeholders are replaced.
[ ] Repeatability and assignment limits match the intended design.
[ ] Waiting assignments ignore progress until they are started.
[ ] Removing old content will not leave broken saved assignments.

Production rollout¶

Use a maintenance window. Keep a backup, reload once, and watch the full log. Test one real assignment before announcing the new content.

If the reload fails, the previous runtime remains active. Keep the first error, fix the files, and reload once more. Restore the matching files and database only when the underlying change also altered stored data.

Next step¶

Use the Quest recipe book or look up exact values in the Reference.