Upgrading to 1.0.7

What you must do after installing the 1.0.7 jar. Jar updates do not overwrite live YAML.

Do this

1. Full server restart with the new jar (and matching SoapsCommon).
2. Run /st reload once and read the self-test output.
3. Spot-check a linked pair and, if you use them, one RTP portal and one paid gate.
4. If you customized messages.yml or gui.yml, compare keys to Config Reference.

What changed

Change	What it means
Packaging / build	Same owner workflow; restart with the new jar
Behavior polish from 1.0.6	Floor-pad portals, routing, economy timing, custom shapes, GUI fixes — see Changelog
New permission nodes	st.command.removecondition, st.protection.bypass, st.portal.limit.bypass if your LuckPerms sets are minimal

Soft new-install defaults are not forced onto existing configs. Portal data in portals.yml is preserved across jar swaps.

Older upgrades

Coming from 1.0.5 or earlier: review 1.0.6 reliability notes in the Changelog (payment timing, limits, one-way behavior, floor pads).

Verify

Use the checklist on Getting Started.

See also: Troubleshooting · Config Reference