What ReplayCore does

You put a single file, ReplayCoreLoader.jar, in your plugins folder and start the server. The Loader downloads the recorder that matches your server and, on 1.13 and newer, installs PacketEvents for you. It is linked to your account, so there is nothing to configure and the same file works on every server you run.

Automatic updates are on by default. A new recorder version is installed the next time the server restarts, and a download that fails its signature check is never started. If you would rather choose when to update, set auto-update to false and run /replaycore update yourself.

ReplayCore records Minecraft Java Edition 1.8.8 through 26.3 on Paper, Purpur, Folia and Leaf. Folia is verified on 1.21.11 through 26.3 and Leaf, a Paper fork, on 1.21.11 and 26.3. Spigot is verified on 1.8.8–1.12.2, 26.2 and 26.3; on Spigot 1.13 to 1.21.x use Paper.

There is one download for all of them. The recorder works out which server and version it is running on when it starts.

Replays play in a web browser, on a computer or a phone, so staff do not need Minecraft open to check a report or an appeal. You can fly a free camera or watch through any player's eyes, and click a player to see their health, inventory, armour and effects at that moment.

When a player goes through a portal, the replay follows them into the Nether or the End.

The combat panel lists every melee hit in a replay: the tick, who hit whom and the estimated reach. Click a hit to jump to that moment with the reach drawn between the two players, or watch it again from the attacker's or the victim's view. You can filter the list down to hits worth a closer look and have playback pause on each one.

Reach figures are estimates to help staff review a fight. They do not prove that anyone is cheating. If you run Grim, its flags are written onto the replay as well.

On paid plans you can set your own logo and colours. They show in the dashboard, the replay viewer and public watch pages. You can also connect a domain you own, such as replay.yourserver.com: add the CNAME record shown in the dashboard and ReplayCore sets up the route and its certificate.

Free workspaces keep ReplayCore branding.

Invite your team and give each person a role: owner, admin, staff or member. For each viewer feature you decide which roles can use it, so combat analysis can be open to admins and closed to everyone else. People who watch through a public link have their own setting.

Paid plans include staff seats and you can add more at any time.

The REST API covers replays, servers, webhooks and more, using API keys you create in the dashboard. The open-source Java SDK wraps it for Java 8 and newer, with no dependencies beyond the JDK.

On the server itself, your own plugins can use the plugin API to add timeline bookmarks and mark where each match starts and ends.

Replays are written to disk on your server, compressed and uploaded to the ReplayCore cloud in the background. If the connection drops, uploads wait and resume when it comes back. Storage and playback are then handled away from your game server.

Free includes 1 GB of storage and keeps replays for 14 days. Starter has 50 GB and 30 days, Pro has 150 GB and 60 days, and Enterprise is agreed with you. You can delete a replay at any time and the space is freed straight away.

We ran ReplayCore 1.5.41 on a PaperSpigot 1.8.8 server with 100 bot players for ten minutes at a time. The bots moved, fought, built and changed worlds throughout. Two runs with ReplayCore recording averaged 19.77 and 19.78 TPS. The same test with no plugin installed averaged 19.77 TPS.

That is one test on one machine. Your own figures will depend on your hardware, your other plugins and how many people are online.