Tags
Creators
Details
1.2.2
Compatibility
Required content
Changes
CurseForge import: magnetization-1.2.2.jar
1.2.2 — Finer power & ore-magnetism control
New config
New options in the in-game config screen (open it from the Mods list, or the main-menu Config button), listed by the section and option name you'll see there:
- Cross-Mod Compatibility → Require Redstone And Energy (default off): require both a redstone signal and buffered FE at once to run an emitter, instead of the default either-or. The internal FE buffer still fills from cables/generators at all times, but with this on the emitter stays dark — and burns no energy — until it also receives redstone; with both present it runs and drains FE normally. Lets you pre-charge a magnet and gate its activation with a redstone pulse for finer control. (Needs both Allow Redstone Power and Allow FE/RF Power on to have any effect.)
- Content Toggles → Ore-Break Field Affects Armor (default on): whether the brief residual magnetic field left when you break a ferromagnetic ore/block can pull the breaker through their worn metal armor. Turn off so mining no longer yanks you around — a narrow, ore-only version of Armor Reacts To Fields (which disables armor reaction to all fields). The residual still nudges loose item drops and magnetizable mobs.
- Content Toggles → Ore-Break Field Affects Items (default on): companion toggle — whether that same ore-break residual tugs loose ferromagnetic/diamagnetic item drops. Turn off so mining doesn't scatter or gather your loot. With both ore toggles off, a broken ore has no magnetic effect on armor or items, while emitters and other fields are unaffected.
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:j2z1RwvT:OugDyFLc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:j2z1RwvT:OugDyFLc"
}

