Licence errors

On Paper, Purpur, Folia and Spigot 1.8.8 the recorder prints a short RC-* code in the console, for example [RC-KEY-000]. That is the line to search for. The Minecraft server itself keeps running; only ReplayCore recording stays off until the code is cleared.

For a new install, open Downloads, enter a friendly server name, copy the two-line config, paste it into plugins/ReplayCore/config.yml and restart.

No recording key is configured. Recording stays disabled. Open Downloads, enter a friendly server name, and copy the two-line config. Paste both lines into plugins/ReplayCore/config.yml (or set REPLAYCORE_LICENSE_KEY and REPLAYCORE_SERVER_NAME), then restart.

The configured key is malformed, incomplete or corrupt. A missing rck_v1_ prefix, a line break, or a partly copied value is rejected before the cloud is contacted. Re-copy the whole license-key onto one line. No public server ID is required for a normal installation.

ReplayCore could not load or safely persist this install's private identity. Confirm that plugins/ReplayCore/ is writable. On an upgraded install only, also check that a retained explicit legacy identity contains no invalid whitespace.

The cloud rejected or revoked the key. Check Billing for subscription status, then open Downloads, enter a friendly server name, and copy the two-line config. If the key has leaked, rotate it, update every server, and restart those servers. Rotation invalidates the old key immediately. If you purchased recently, allow a few minutes for activation. If it still fails, contact admin@forgevector.co.uk.

One key covers your whole network, and your plan caps how many distinct servers can record to the cloud at once (Free 1, Starter 5, Pro 15, Enterprise unlimited). A new server over the limit logs one clear warning and fails closed without recording; the console line is [RC-LIMIT]. It never claims an upload or retries registration in a loop. Existing authentic archives and private plugin state remain on disk.

Free a slot by removing a retired server on the Servers page, or upgrade your plan, then restart the affected server.

The cloud could not be reached and no usable authenticated grace state remains. Verify the server allows outbound HTTPS to api.replaycore.com on port 443 and that no proxy or firewall is intercepting the connection. Check the status page for any ongoing incident before raising a ticket.

ReplayCore tolerates a brief loss of connectivity when matching authenticated grace and last-known-good state remain usable. A brand-new server with no eligible cached state fails closed and records nothing while the Minecraft server keeps running. Restoring outbound connectivity and restarting re-validates the licence.