Updates

Fiveops updates itself. You don’t download or reinstall anything, and the server doesn’t restart: only the Fiveops resource restarts for a few seconds. Players stay connected; the Fiveops menu closes and reopens during that time.

One-time setup

The resource needs permission to restart itself. Add this line to server.cfg before ensure fiveops, then restart the server once:

server.cfg

add_ace resource.fiveops command allow

Without it, updates are downloaded but not applied, and the console and Configuration → Updates say so.

Choose when updates are applied

Under Configuration → Updates → When to apply:

Option	When the update is applied
Right away (recommended)	As soon as it’s downloaded and verified.
At set hours	Every day within your time range, by the server’s clock.
When the server is empty	When no players are online (right after a daily restart counts).

Automatic updates can’t be turned off. If your condition doesn’t happen within 24 hours, the update is applied anyway.

What happens during an update

1. The server downloads the package and checks its signature. A package with a bad signature is never installed.

2. At your chosen time, Fiveops backs up the files it replaces and writes the new version.

3. Fiveops restarts itself. If the new version doesn’t connect within 2 minutes, the previous version is restored automatically.

Kept on every update: license.txt, the .json files (identities, bans, whitelist, settings, playtime, stashes) and the files you changed in editable/. Editable files you didn’t change get the new defaults. If you changed one whose default changed too, yours is kept and the panel tells you which.

Configuration → Updates shows the running version, the last update and any update in progress.

Manual install

Only for the first install, or if you need to reinstall the resource:

1. Download the new version of the fiveops resource from Download resource in the Fiveops panel sidebar.

2. Stop the server.

3. Replace the files in resources/fiveops, but keep license.txt, editable/ and the .json files.

4. Start the server.