Plan a Quests storage change without starting with empty progress

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

Changing storage settings alone is not a safe progress migration. Prepare a supported conversion and comparison before pointing a live quest server at a different database.

Check the installed content

PikaMug Quests has its own quest editor and player progress storage. Confirm that you use this plugin rather than another project named Quests. Current maintainer documentation targets version 5 and newer; use the legacy reference when your installed release needs it.

Work through the change

1. Record the current storage backend and installed Quests version. Take a completed backup of quest definitions and all current player progress while the staging copy is stopped.
2. Read the storage documentation and its supported conversion tooling. Keep the target database separate and empty for the trial rather than mixing copied records with an existing live dataset.
3. Run the documented conversion procedure on staging with the matching tool versions. Keep credentials private and avoid editing tables or assuming that switching the backend setting moves the data.
4. Start the staging server on the converted backend and compare several known accounts: active objectives, completed quests and cooldown state. Check that new progress persists through a normal restart.

Verify the result

The converted backend should preserve representative progress and store subsequent changes correctly. Record the source checkpoint and comparison results before planning a production maintenance window.

If the result differs

If accounts appear new, stop the trial and inspect the selected backend, database and conversion output. Do not let players continue on two diverging stores while deciding which contains the authoritative progress.

Keep a recovery path

Return staging to the original configuration and backed-up source data if validation fails. Keep both trial outputs for diagnosis, and prepare an explicit production cutover and rollback plan before any live storage change.

References and related help

Check the maintainer reference: PikaMug Quests documentation.

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