Running servers

Every server has a page with sections for each part of its life. What you may do depends on your role.

Desired and observed

Shardkeep keeps two things apart: what you asked for (desired: running or stopped, which software, how much memory) and what the Node reports (observed). The Overview shows both. When they differ for a reason that needs you, the server shows a condition explaining why; see Conditions.

Start, Stop and Restart change what you asked for; the Node does the rest. Stops are graceful: the server saves its world first.

If a server crashes, the Node restarts it, up to a limit. After too many crashes in a row it stays stopped with a CRASH_LOOP condition.

Console

Console shows the server’s live output (up to the last 1,000 lines, then new ones) and sends commands, as if you typed them at the server. Shardkeep never stores console output: it carries player names and IP addresses.

Files

Files browses the server’s data: download, upload (up to 64 MiB), create folders, move and delete. The Node confines every operation to the server’s own data. Installed software and Shardkeep’s managed plugins (in .shardkeep/) cannot be changed here.

Settings

Settings edits server.properties, keeping its comments and order. Common gameplay settings have proper controls; everything else is under All settings. Changes apply when the server next starts.

Settings Shardkeep manages (the port, RCON, query, and online-mode for servers in the network) are shown but cannot be changed.

Resources

Change resources on the Overview adjusts the reserved memory and CPU, if the Node has room. A running server restarts gracefully to apply it, since Java sizes its memory at start.

Software versions

Software moves the server to a newer Minecraft version, or a newer build of the same one. Shardkeep downloads and verifies it, and the server uses it at its next start. Going back to an older Minecraft version is refused: worlds cannot be downgraded. Back up first.

Schedules

Schedules run on the server’s Node at times you set (cron expressions in your time zone):

• Back up to a destination, keeping the last N backups.
• Restart gracefully.
• Command: send one console line, such as a broadcast.

They run even while the Controller is down. A run missed while the Node itself was down is skipped.

Activity

Activity lists what happened to the server and when: who changed what, and what its Node did.

Deleting

Delete server in the actions menu stops the server gracefully and removes its container and data. Backups are kept until you delete them.