Upgrade plugins safely
Keep matching artifacts, preserve server-owned configuration, and test your actual player workflows.Back up and stop
Record the installed JAR versions and stop the server cleanly. Back up complete plugin folders and each external database. Keep the old JARs outside the active plugins directory.
Replace the right artifacts
Install matching RCore and module artifacts. Replace old Free or Premium RCore, RDA, RDF and RDT JARs with their unified artifact. Keep exactly one RDQ, RDR or RDS edition installed. RModel is embedded in RCore; migrate its data to plugins/RCore/models/ and remove the old standalone JAR.
Merge configuration changes
Compare bundled defaults with existing files. Existing command YAMLs are server-owned and can retain retired roots or aliases. Preserve custom ranks, perks, quests, currencies, translations, stable server IDs and database credentials. RDF still accepts legacy premium settings; explicit limits values take precedence per field.
Check commands and permissions
Test /rc, /rc stats, /ra, /fish, /rq admin info, /rr, /rs and /rt for the plugins you run. Replace retired permission grants using the current plugin references. Grant ordinary player nodes deliberately; several generated player aggregates also include player-executable administration.
Verify before reopening
Check startup and database readiness, join as an ordinary player, and test menus, progression, storage, shops and travel that your server uses. Check optional economy and network flows separately. A successful JAR build or startup does not verify every gameplay feature.
Rollback
Stop the server before restoring a matching JAR, data-folder and database backup set. Do not combine an old JAR with a newer database blindly. Inspect unsettled economic operations before retrying them.