System requirements

ReplayCore supports the following Minecraft server platforms:

Paper, Purpur, Folia and Leaf (a Paper fork) on Minecraft 1.8.8 through 26.3, and Spigot on 1.8.8–1.12.2, 26.2 and 26.3 (native BuildTools). Folia is verified on 1.21.11 through 26.3 and Leaf on 1.21.11 and 26.3. Spigot 1.13 to 1.21.x is not verified: use Paper or a Paper fork there.

Replays are pixel-1:1 accurate on 1.8.8 and 1.21.0 to 1.21.5. Versions 1.13 to 1.20.6, 1.21.6 through 1.21.11, and 26.1 through 26.3 record and play.

On Folia, session rotation is disabled (one archive per server uptime) and extra-dimension terrain baselines are not captured; everything else records as normal.

On supported 1.13+ versions through 26.2, official PacketEvents 2.13.0+ must be in the server plugins folder. Servers on 26.3 need official PacketEvents 2.14.0+. Recording stays idle until the required version is present and ready. Download it from Modrinth (https://modrinth.com/plugin/packetevents) or GitHub releases (https://github.com/retrooper/packetevents/releases). Paper and Spigot 1.8.8–1.12.2 do not need PacketEvents.

Use the Java version your Minecraft version needs: Java 8 for 1.8.8 to 1.16.5, Java 17 for 1.17 to 1.20.4, Java 21 for 1.20.5 to 1.21.11, and Java 25 for 26.1 to 26.3.

Java 25 is required on 26.1 to 26.3 for every platform, including Folia and Leaf.

ReplayCore adds approximately 30-80 MB of RAM overhead per running server, depending on player count and upload queue settings.

CPU impact is minimal: the recording pipeline runs on a dedicated background thread, off the main server thread, so it does not compete with tick processing for CPU time.

Outbound HTTPS (port 443) to the ReplayCore cloud is required. Replay uploads are batched and compressed; typical bandwidth usage is 2-8 MB per player per hour of gameplay.

The plugin handles temporary network interruptions gracefully: replays are written to local .replaycore archives on disk and uploaded with automatic retries when connectivity is restored.