Links
Tags
Creators
Details
Licensed MIT
Created 2 months ago
Updated 2 months ago
All versions
0.2.0
Beta
create_collision_fix 0.2.02 months ago 2,698
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Changelog
Version 0.2.0 - 2026-06-17
Fixed
- Core Fix: Resolved the critical
NullPointerExceptioncrash caused bymf.axisbeing null during specific collision events.- This was achieved by injecting a Mixin into the
ContinuousSeparationManifoldclass to handle the zero-distance separation edge case, ensuring theaxisandnormalAxisfields are correctly initialized.
- This was achieved by injecting a Mixin into the
Build & Configuration
- Mod Loading: Fixed an issue where the mod was not being loaded by NeoForge due to a missing Mixin configuration declaration in
neoforge.mods.toml. - Mixin Path: Corrected the package path in
mixins.createfix.jsonto match the actual Mixin class location, resolving aClassNotFoundExceptionon startup. - Project Structure: Added the necessary
META-INF/neoforge.mods.tomlandpack.mcmetafiles to ensure the project conforms to NeoForge mod loading standards. - Dependencies: Properly configured the
build.gradlefile with the required Create Mod Maven repositories and dependencies, resolving the initial dependency resolution failures.
Miscellaneous
- Version Bump: Increased the project version from 0.1.0 to 0.2.0.
- Code Cleanup: Removed an obsolete and invalid Mixin (
ContinuousOBBColliderMixin) that targeted an outdated Create API.
Version 0.1.0 - Initial Release
- Initial attempt to fix the Create Mod collision crash.
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:JAzhqJgX:rgsjLcdW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JAzhqJgX:rgsjLcdW"
}