Links
Tags
Creators
Details
All versions
0.0.5
Release
FPM X Compat 0.0.55 months ago 29
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Changes
0.0.5
- Intelligent Head Hiding: Added a context-aware visibility system that hides the local player's head and accessories in first-person (supporting custom EMF bone names) while keeping them fully visible for other players and in third-person view.
- Multiplayer Safety: Refactored all rendering offsets (Torso Z-axis, leg stabilization) to apply exclusively to the local player in first-person, preventing visual glitches on other players.
- Enhanced Logging System: Added a structured startup banner and unified diagnostic prefixes (
[Bridge],[Lifecycle]) for better troubleshooting. - Improved Initialization: Implemented explicit initialization for all compatibility bridges to provide immediate feedback on mod detection during startup.
0.0.4
- Integrated with Entity Model Features (EMF).
- Implemented a dynamic pause condition for EMF animations during combat actions (attack/roll).
- Broadened model part detection to handle both camelCase and snake_case naming conventions.
- Refactored Better Combat, Spell Engine, and Combat Roll bridges for universal player entity support.
- Optimized state detection logic to improve reliability across all rendered player models.
- Enhanced logging system with a structured startup banner and unified diagnostic prefixes (
[Bridge],[Lifecycle]). - Implemented explicit initialization for all compatibility bridges to provide immediate feedback on mod detection.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:FQu70XYH:run8Yt4S"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FQu70XYH:run8Yt4S"
}

