Skip to content

Server management and instance limits

How servers appear in the panel, plan instance limits, renaming, and removal.

5 min read

How servers appear

Each Minecraft server registers itself with your account on first start and appears on the Servers page. Its stable identity is generated and stored privately in the ReplayCore plugin data folder, so it survives restarts and also survives redeployments or host migrations when that persistent data is retained. A listed server can still be unclaimed. Current plugins print [RC-CLAIM-GATE]; already-shipped boxes print the legacy alias [RC-CONFIG-CLAIM]. Both mean read the short code from that server's console or /replaycore status, then open the printed Downloads URL (https://replaycore.com/en/dashboard/downloads, or /en/dashboard/downloads on a configured self-hosted origin) and approve the server.

Give every server a distinct name with server-name in config.yml (or the REPLAYCORE_SERVER_NAME environment variable per container). The name is how replays are labelled and filtered in the panel.

Instance limits

Your plan caps how many distinct server instances can record to the cloud at once: Free covers 1, Starter covers 5, Pro covers 15, and Enterprise is unlimited. An instance is one Minecraft server (Hub, Bedwars, Practice, and so on) running the plugin under your licence.

Starting a new server beyond the limit fails closed: that server logs one clear warning and records nothing, while the Minecraft server and every other connected server remain available. Existing authentic archives and private plugin state stay untouched. Upgrade your plan, or remove a retired server to free the slot, then restart the affected server.

Renaming and removing

From the Servers page you can rename a server (changing only its panel label) and remove a server you have decommissioned. Removing a server frees its instance slot; its existing replays remain available until their retention window lapses or you delete them.

Networks and containers

On a multi-server network, every server may use the same licence key and has a distinct server name plus its own private identity. On Pterodactyl or Docker, set REPLAYCORE_LICENSE_KEY and REPLAYCORE_SERVER_NAME, and keep each server's plugin data folder on a separate persistent volume. Copying plugins/ReplayCore/ onto a second live server prints Recording is DISABLED. [RC-ID-409] and that copy records nothing.