Tags
Creators
Details
All versions
1.3.1
Release
Magnetization 1.3.12 months ago 6
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
Fixed
- Fixed large pregenerated worlds freezing or triggering the server watchdog when optional magnetic integrations were enabled.
- External magnetic emitters now use chunk-local spatial indexing.
- Unloaded chunks are removed from the index immediately.
- Field evaluation no longer loads missing chunks.
- Disabled integrations are not indexed.
- Only emitters near active targets are processed, with a bounded per-tick budget.
- This resolves the large-world performance problem reported in GitHub issue #7.
Added
- Added the permission-free
/magnetization manualcommand for replacing a lost Patchouli Field Manual.- If the player's inventory is full, the replacement is safely dropped at their feet.
- Clear errors are shown when Patchouli is missing or its integration is disabled.
- Added independent configuration switches for the Field Manual recipes:
- Book + Raw Magnetite — enabled by default.
- Book + Lodestone — enabled by default.
- Book + Iron Ingot — disabled by default to avoid conflicts with other guide-book recipes.
- Added
compat.externalFieldApplicationBudget, defaulting to 256, for controlling the maximum number of optional-mod magnetic emitters applied per level tick.
Compatibility and upgrades
- Existing Magnetization 1.3.0 worlds and configurations remain supported.
- Missing new configuration values automatically use their defaults.
- Minecraft and required dependency versions are unchanged from 1.3.0.
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
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:anAikXvr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:j2z1RwvT:anAikXvr"
}

