Updating Your Build

Your EUR 15.00 purchase includes updates for the current major version — no subscriptions, no per-feature fees. Because System is delivered as a personal 1:1 build, updates are not fetched from a public download page: they reach you through the official Nerotek channels, via the license-gated update channel and the same DM conversation where your original build was delivered. You always know where your build came from, and there is exactly one place to get the next one.

#The version line, precisely

System is a 4.x product. The current stable release is 4.4, and the repository's tag history runs through 27 published versions on the way there — the 3.7x and 3.8x lines, then the 4.x line with 4.3 and 4.4 landing back-to-back, followed by stability and tooling work. Each release is documented: release notes listing new config keys and defaults ship with the version, so an update never changes behavior silently. If you are ever unsure whether a build you were offered is an update or a new major version, ask in the DM before applying it.

#How an update happens

1. Watch the official Nerotek channels or simply ask in your DM conversation — the developer announces current stable releases there, with notes on what changed.
2. Request the updated personal build for your license.
3. Receive the new build in your DM conversation, delivered personally like the original.
4. Stop the server cleanly — this also lets the restart scheduler's backup path do its job if a scheduled run is close.
5. Replace the old jar with the updated one in plugins/.
6. Start the server and confirm with /system status.

#What to preserve

An update replaces the jar — nothing else. Your configuration, your data and your backups all live outside it, and they are the things to protect:

• Your `config.yml` and addon configs — every toggle and value you tuned. Keep a copy before version jumps; new keys arrive with documented defaults and are merged without destroying your values.
• Your MongoDB and Redis data — the economy persistence, cache and leaderboard live in your databases, not in the plugin.
• Your backup archives — the tar+gzip files produced by the backup manager, including the retention history you care about.
• Your license and loader files — they are bound to your purchase; never delete or edit them while updating.

#Infrastructure changes

Because the license is bound per server with IP and hardware limits, infrastructure changes are the one case where you should talk to the developer before touching anything. Migrating to a new host, changing server IPs or upgrading hardware can all invalidate a binding — a license reset resolves it in minutes. Message the developer in your original DM conversation, where your purchase is on record; the platform documentation describes the process in Requesting a License Reset.