Links
Tags
Creators
Details
V1.0.0-NeoForge
Compatibility
Changes
Port of Immersive Weathering by Ordana, MehVahdJukaar, and Keybounce, brought up to Minecraft 1.21.1 / NeoForge. Upstream baseline: 1.20.1-2.0.5 (LGPL-3.0).
Verified in play
- Iron rusting on land and in water
- Moss spread on stone, cobblestone, brick, and stone-brick families
- Sapling, flower, and bush placement on Rooted Grass, Earthen Clay, Sandy Dirt, Silt, Permafrost, and the grassy variants
- Weeds (crop) growth ticks (NeoForge CropBlock.getGrowthSpeed signature divergence from vanilla handled — would have crashed on first chunk tick)
Known divergences from upstream (1.20.1)
These are intentional regressions taken to keep the port shippable; each is a candidate for a follow-up patch release:
- Custom particle network packets are no-op. Leaf-decay and similar client-side particle effects are not pushed from server to client. Block state changes, sounds, and gameplay-affecting behavior are unaffected.
- Per-item fuel times are no longer registered in code. They now live in
data/<modid>/neoforge/fuels.json. Existing burnable items fall back to default behavior unless redeclared via datapack. IcicleItem/IceSickleItemare no longer edible andIceSickleItemno longer applies custom sword damage values. Both are wired through 1.21 data components and need to be re-enabled at registration.- Trident channeling check simplified in
FulguriteBlock: lightning triggers on any trident hit during a thunderstorm rather than specifically channeling-enchanted hits. - Data-driven block-growth / fluid-generator / position-rule-test systems are inert. The
Codec.dispatchchains were stubbed during the port pending aMapCodecmigration. Existing JSONs in those directories are parsed but not applied. - Charred projectile interaction is a no-op.
See META-INF/PORT_NOTES.md inside the jar (or the GitHub repo) for full technical detail.
Required dependencies
- Moonlight Lib 1.21-2.29.33+
- Architectury API 13.0.8+
License & credit
LGPL-3.0-or-later, same as upstream. Original authors: Ordana, MehVahdJukaar, Keybounce. Port: QanoriaPorts.
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:AtjxBimt:CA9VgDj5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AtjxBimt:CA9VgDj5"
}

