Tags
Creators
Details
1.4.3
Compatibility
Required content
Changes
Magnetization 1.4.3
Magnetization 1.4.3 is a compatibility and mounted-Railgun hotfix for Minecraft 1.21.1. It keeps every integration tied to the individual addon, never a modpack.
Fixed
- Mounted Railguns now explicitly cover both reported failure modes: they fire external staged payloads while installed on Sable ships, and they ignore ferromagnetic blocks belonging to their own host craft instead of launching themselves.
- Optional dependency metadata now accepts the behaviorally verified releases used by supported packs: AeroPortals 1.1.2, Create: Coasters Simulated 0.1, and JEI 19.27.0.336.
- AeroPortals 1.1.2 retains safe magnetic-state cache invalidation and ship reconstruction without resolving APIs that only exist in newer releases. Railgun Remote and Simulated swivel remapping remain enabled automatically on AeroPortals versions that expose the required plot geometry.
Compatibility verification
- Added isolated behavioral profiles for both the pack-pinned and current AeroPortals and Coasters Simulated releases.
- Expanded real-addon coverage for Coasters: Magnetized, Coasters: Engineered, Create: Coasters Extras, and CBC Aeronautics Missiles.
- Added isolated private-X-server client boots for Engineered with Jade, Extras, the complete missile stack, and JEI/JER. The JER gate requires all 28 synchronized resource charts to register exactly once.
- Added exact recommended-pack launch and configuration-migration fixtures while enforcing that pack names, slugs, and project IDs cannot enter the shipped runtime JAR.
Configuration
All 1.4.2 compatibility switches and defaults are unchanged. Existing configurations migrate by preserving every prior key and adding only missing defaults.
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:H0KIVLSK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:j2z1RwvT:H0KIVLSK"
}

