Upgrading

Before you upgrade

Read the changelog entry for every version between yours and the target, not just the newest one. Breaking changes and migrations are listed per release, and skipping a version does not skip its migration.

Back up the database. Your tuned definitions and player progression both live there, and neither can be regenerated.

The upgrade

1. Stop the resource.
2. Replace the resource folder. Keep your own config.lua if you have edited it — but read the changelog first, because a release may have added settings that the old file does not have.
3. Run refresh, then start the resource.

The refresh matters when the file list has changed. The server caches which files a resource contains at start, so a plain restart will not pick up a file that did not exist before. The symptom is a new feature reporting an unknown action even though the code is present.

What happens to your configuration

Definitions already in the database are not overwritten by a new version's seed values. Your tuning survives an upgrade.

Settings added by a new release are filled in at their documented defaults when the resource loads, so a new option becomes visible in the administration console without your existing values being disturbed.

After upgrading

Check the console line reporting framework and inventory, then run one action of each kind — harvest, craft, sell — and confirm each leaves a transaction row. That takes two minutes and catches almost everything an upgrade can break.

Alpha versions

TrapNexus is alpha software. Configuration and data formats may change between versions. Migrations are provided where they are needed, and anything that will stop working on an existing server is recorded under breaking changes in the changelog for that release.