Update SkinsRestorer

SkinsRestorer checks for updates at startup and periodically afterward. The repeating interval is randomized between 60 and 240 minutes.

Update checks and automatic downloads are different actions. Download behavior depends on the platform.

Manual update

1. Read the target release notes and platform requirements.
2. Back up the active storage.
3. Stop the affected instances.
4. Replace the old JAR with the matching release artifact.
5. Remove duplicate SkinsRestorer JARs.
6. Start the instances.
7. Read the startup logs.
8. Complete the first skin check.

On a network, update the proxy and backends together. A Fabric or NeoForge update also needs a matching Minecraft and loader version.

Disable automatic downloads

Create an empty noautoupdate.txt file in the SkinsRestorer data directory. The older noupdate.txt filename is also recognized by this release.

Restart after changing the file. This controls the updater's download behavior. Plan manual updates instead of relying on a disabled downloader.

advanced.noConnections also stops update connections, but it disables skin lookups and URL generation too. Do not use it only to manage updates.

If the update fails

Restore the backup and compatible previous artifact. Keep the failed startup log for diagnosis. Do not delete storage to make an incompatible release start.

Read support diagnostics if you need help with an update error.