Tags
Creators
Details
2.4.0
Compatibility
Required content
Changes
Ji-AFK Cinematic v2.4.0 — Fabric
A major update focused on cinematic quality, stability, and customization. This release introduces a redesigned camera system, improved controls, expanded music management, and integrated bug reporting.
Added
-
In-game Support Center — Report bugs and submit suggestions directly from the mod, with optional diagnostics.
-
Expanded music management — Improved local
.oggmusic support, custom folder management, and resource-pack export.
Improved
-
Cinematic cameras — More natural movements, improved framing, and smarter shot selection based on the surrounding environment.
-
Camera collision handling — Safer camera paths that adapt to nearby obstacles and available space.
-
Shot variety — Reduced repetitive compositions and improved transitions between shots.
-
Music playback — Better track distribution, persistent playback history, and fewer repeated songs.
-
Controls — Reworked shortcut handling, improved conflict detection, and more reliable custom keybindings.
-
Configuration interface — Better organized settings with dedicated sections for cameras, music, controls, and support.
-
Overall stability — Improved cinematic activation, interruption handling, and camera state restoration.
Fixed
-
Fixed stationary sprint-key presses unintentionally cancelling cinematics.
-
Fixed several issues involving overlapping shortcuts and repeated key presses.
-
Improved recovery from camera conflicts and unexpected cinematic interruptions.
Notes
-
Supports Minecraft **1.21.x and 26.x.
-
Default quick-toggle shortcut changed to F7 + U.
Thank you for your continued support and feedback!
Optional dependencies
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:NYveE6yC:PsoCikjB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NYveE6yC:PsoCikjB"
}

