Tags
Creators
Details
All versions
1.4.5
Release
Magnetization 1.4.57 hours ago 20
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
Added
- Added optional Create: Ironworks 4.0.3 compatibility for metal armor and materials, with global and material-level opt-outs.
- Added optional Create: Coasters Simulated Additions 0.2.0 integration for Track Control Fins, including independent master and magnetization switches.
- Added the optional Jammarr 1.1.0
/magnetization howeaster egg. When Jammarr is installed and “Miracles” by Insane Clown Posse is in its available music library, the command starts playback through Jammarr. - Added isolated GameTest profiles for Ironworks and Coasters Simulated Additions, alongside Jammarr playback tests.
Verification
- CI passed for commit
bc28565and produced the attached release JAR. - Local unit/build/release-JAR checks and the Ironworks + Coasters Additions compatibility profiles passed.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:j2z1RwvT:RFBRHIId"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:j2z1RwvT:RFBRHIId"
}

