Skip to main content

Which Rust plugin settings should survive an update?

Read three copies of the settings before accepting changed defaults. Your current file includes intentional choices and old defaults. A fresh configuration from the new build shows which options the author added, removed or renamed.

Get each copy from a known version

Save the current working configuration before testing any update. Use a fresh private copy of the old build to see its defaults, and a separate copy of the new build to generate new defaults as its author describes. Read the release notes before starting the new version with existing data. Keep the working files untouched during the comparison.

Read by setting rather than by line number

JSON objects can list the same settings in different orders. Compare named settings and values, including their types.

Read by setting rather than by line number
What you findWhat to take forward
Your old setting differs from the old default and the same option still existsCheck that the difference is intentional. Carry it forward using the new version's expected type and meaning.
Your setting matched the old default and the new default differsDecide whether the author’s new behavior suits your world. Avoid silently preserving the old outcome without an owner decision.
An option disappeared, was renamed or changed typeUse the author's migration instructions. Ask the maintainer if the replacement is unclear.
An option exists only in the new defaultsRead what it does and check the result that players would see before enabling it.

Check a changed rule before copying another

Start the candidate on the private world and check it loads. For an example notice setting, join with the matching test account and check the exact text. Read the file back after restart to confirm the intended setting persisted. Stop if the version has rewritten a setting you still need. Keep the saved configuration and the smallest failing comparison ready for the author.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details