All versions
๐ฅ ApoCinematicCore โ Changelog
1.0.1-beta
Beta
ApoCinematicCore 1.0.1-beta6 months ago 20
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.9
Platforms
Paper
Purpur
Changes
๐ฅ ApoCinematicCore โ Changelog v1.0.1-beta
Author: ApoloCR | Status: Feature Update | Date: April 2026
This update focuses on precision recording tools and sub-tick fluidity optimizations while maintaining the core timing stability.
๐ New Features
- Point-Based Recording System โ A new command structure for frame-perfect cinematic sequences.
/cinematic rec <name> <point_number> <time>โ Record specific coordinates and rotations as keyframes with custom timing./cinematic rec <name> <time>โ Standard continuous recording remains available.
โจ Smoothing & Stabilization
- Linear Frame Interpolation (
lerpFrame) โ The engine now calculates smooth intermediate positions (X, Y, Z, Yaw, Pitch) between recorded ticks, providing a high-fidelity visual experience without jitter. - Smart Angle Wrap-around โ Implemented rotation normalization to prevent the camera from spinning 360ยฐ when crossing the 350ยฐ to 10ยฐ threshold.
- Adaptive TPS Scaling โ The system monitors server health. If TPS drops below 18.0, sub-tick smoothing automatically scales down to 1 to preserve server resources, restoring full fluidity once stable.
- Anti-Bounce Stabilization โ Integrated gravity-dampening logic during playback to eliminate micro-vibrations caused by vanilla Minecraft physics.
โ ๏ธ Version Notes
- Timing Integrity โ Playback duration remains strictly 1:1 with the original recording, ensuring perfectly timed cinematics for synchronized events.
- Performance โ Minimal CPU overhead, designed for high-end networks requiring stable 20.0 TPS.
โ Version Status Summary
- Timing: Correct (Recording = Playback) ๐ข
- Recording: Point-based system fully active ๐ข
- Smoothness: Sub-tick linear interpolation enabled ๐ข
- Performance: Adaptive scaling & Anti-bounce active ๐ข
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:p52Pwx6B:UYnn994L"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:p52Pwx6B:UYnn994L"
}

