Supported server platforms
ReplayCore supports the following Minecraft server platforms:
Paper 1.8.8 through Paper 26.2, Purpur (all versions matching a supported Paper release), and Spigot 1.8.8 (limited support). Paper, Purpur or Folia is required for 1.13 and above. A 1.13+ Spigot server prints Recording is DISABLED. [RC-SPIGOT-001] and ReplayCore disables itself.
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 Paper 26.1 through 26.2 record and play. Paper 26.2, Purpur 26.2 and Folia 26.2 are supported. Folia 26.2 is a PaperMC Fill BETA build.
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 Paper, Purpur and Folia, official PacketEvents 2.13.0+ must be in the server plugins folder or recording stays idle. Download it from Modrinth (https://modrinth.com/plugin/packetevents) or GitHub releases (https://github.com/retrooper/packetevents/releases). Spigot 1.8.8 does not need PacketEvents.
Java version
Java 17 or newer is required for all platforms except Paper 1.8.8, which requires Java 8 or newer.
Java 21 is the recommended version for Paper 1.21.x. Paper 26.1 and 26.2, Purpur 26.2 and Folia 26.2 require Java 25 on the server.
RAM and CPU
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.
Network
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.