Updating, backing up and rolling back

Updating to 1.1.0

Settings, per-server overrides and History are kept. Nothing needs reconfiguring.

From the admin area

1. Go to Admin → Extensions.
2. Choose Install, and upload krapple-player-manager-1.1.0.pteroext.
3. Confirm the replace. The extension stays enabled.

From the command line

php artisan p:extension:install krapple-player-manager-1.1.0.pteroext --enable --replace

--replace is required when a version is already installed.

Then

1. Hard-refresh the browser once (Ctrl+F5), so the new frontend loads.
2. Open any Minecraft server's Player Manager tab. The Connection tile should still say RCON.

On a panel with cron, the background pass picks up the new version within five minutes. To apply it immediately:

php artisan krapple-player-manager:setup-rcon -v

Checking an update went well

php artisan p:extension:list | grep krapple

The extension should show the new version and enabled. Then open the tab: if it lists your players and the Connection tile says RCON, the update is complete.

Backing up before an update

You do not need to back up for a normal update, but if you want to be careful:

What	How
Settings and history	Dump the panel database with your normal backup tool
Minecraft servers	Untouched by an update; your normal server backups cover them

The extension does not modify server.properties during an update. Only the automatic setup does that, and only when RCON is missing.

Rolling back

Keep the old .pteroext if you may need it. Install it the same way, with --replace.

History is kept across a rollback. The automatic RCON setup, the quiet console and the fix for list changes right after a server stops are gone after a rollback. Servers that 1.1.0 already set up keep RCON working, because the settings live in server.properties.

Uninstalling

Remove it from Admin → Extensions, or:

php artisan p:extension:remove krapple-player-manager

This removes the extension's files, assets, settings and its history.

Your Minecraft servers are not changed. RCON stays enabled in server.properties, the allocation stays with the server, and the whitelist, operators and bans stay in the server's own files.

To undo the RCON setup as well, for each server:

1. Set enable-rcon=false in server.properties, or remove the three RCON lines.
2. Remove the RCON allocation from the server's Network page if you do not need the port.
3. Restart the server.

To restore the console echo the extension silenced:

gamerule logAdminCommands true
gamerule sendCommandFeedback true

Moving to another panel

Install the package on the new panel. RCON settings live on the Minecraft server, not in the panel, so they keep working as long as the new panel can reach the same RCON port. If the node's address changes, RCON still works because the host is read from the allocation. If you had entered a host override, update it under Connection settings.