Replay does not appear
Replays upload after an archive is sealed, not when the last player leaves or a short match ends. Duration is captured ticks, not wall-clock, so an empty server freezes seal progress. On Paper, Purpur and Spigot 1.8.8 the default is a 30-minute recorded-play window, or a server restart. Folia seals on restart only. /replaycore forcestop only pauses capture; it does not seal or upload. If a replay is missing, confirm Recording is ENABLED rather than ReplayCore is dependency-blocked, that a player was online long enough for a seal, that outbound HTTPS on port 443 is allowed, and that a still-uploading archive is given time to finish. A dependency-blocked Paper, Purpur or Folia server records nothing until PacketEvents is present, recent enough and ready. If the plugin is enabled and the Replays list is empty, read the console for [RC-CLAIM-GATE] or the legacy alias [RC-CONFIG-CLAIM]: an unclaimed connection needs the owner to open the printed Downloads URL (https://replaycore.com/en/dashboard/downloads, or /en/dashboard/downloads on a configured self-hosted origin), match the short code, and approve the server before those recordings appear.
Missing entities or desync in playback
Playback reconstructs the match from captured events. Gaps usually trace back to dropped events during capture, which happen only when an integration's event queue was momentarily full under extreme load. Reducing load, or recording at standard quality rather than hd, lowers the chance of drops. If a specific match consistently shows gaps, note its replay id when contacting support.
Cross-version playback
ReplayCore lets you record on one Minecraft version and watch on another, handling the version gap automatically. You do not need to match your client version to the recording. If a replay renders incorrectly, confirm you are using the in-browser cloud viewer rather than an external tool, since the cloud viewer is the supported playback path.
Getting help
If playback problems persist, contact admin@forgevector.co.uk with the affected replay id, the recording server's Minecraft version and platform, and a description of what is wrong. The replay id lets the team inspect the exact archive.