Tags
Creators
Details
1.5.14
Compatibility
Changes
ADDED MINECRAFT 26.3 SUPPORT
- Paper: 1.8.8 → 26.3
- Purpur: 1.20.6 → 26.3
- Spigot: 1.8.8 → 26.3
- Folia: 1.21.11, 26.1.2 official and 26.2 experimental. Folia 26.3 is not verified.
Changes
- One unified ReplayCore JAR for supported server versions.
- PacketEvents is installed separately on modern servers. Use 2.14.0+ for Minecraft 26.3 and 2.13.0+ through 26.2. PacketEvents is not required on 1.8.8–1.12.2.
- Fixed replay version data for Minecraft 1.9.4, 1.11.2 and 1.12.2.
- Fixed false capture-loss warnings on Minecraft 1.13–1.15.
- Improved compatibility with older servers when newer event types are unavailable.
- Added capture for blocks changed by other plugins.
- Improved recording of player world changes on Folia and reconnect events on Velocity.
- Improved crash recovery, including recordings split across multiple files. Recovered replays show when final data or terrain is uncertain.
- Protected local recordings while cloud uploads are pending or incomplete.
- Reduced replay loading, upload and memory overhead.
- Improved held-item visuals, terrain loading, hurt effects and mobile playback.
- Improved kill/death-cam focus while keeping the replay viewer controls.
- Added Grim flag capture and staff review tools, including timeline flags, player history and evidence-pack drafts. Staff-only flags stay out of public shares.
- Added Evidence mode for supported v3 archives. Standard recording does not create v3 archives yet.
- Ready replays now open from the row and start playback. Processing replays stay unavailable until ready.
- Improved public replay links, moment framing, server lists and connection guidance.
- Updated first-run setup and Downloads instructions.
- Dashboard health displays now show unavailable values as unknown instead of misleading zeroes.
Download: https://replaycore.com/en/dashboard/downloads ^^^ We do not always post the latest update to Markets/Forums as we post minor updates / bug fixes most days, get the latest version in the dashboard or wait for each stable release on the marketplace.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ligHdY74:py9OVo0z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ligHdY74:py9OVo0z"
}

