
ThinAir: ReLived
A NeoForge 1.21.1 port of Thin Air by fuzs and a foundation for more. The air isn't always breathable. Go too deep, too high, or into the wrong dimension and you'll need to come prepared. Respirators, air bladders, and soulfire can keep you alive.
Creators
Details
1.0.0
Compatibility
Required content
Changes
Thin Air — NeoForge 1.21.1 Port | v1.0.0
- First public release of the NeoForge 1.21.1 port.
Requirements
- NeoForge for Minecraft 1.21.1
- Optional: Curios 9.5.1+1.21.1 — respirator head slot, belt - --- - lantern slot, and Curios rendering
- Recommended: Cloth Config — in-game config from the Mods menu (otherwise edit serverconfig/thinair-server.toml)
What's Included
- Full air quality system (green, yellow, red, blue) by dimension and height
- Safety Lantern, Signal Torch, Wall Signal Torch, Respirator, Air - Bladder, Reinforced Air Bladder, Bottle of Soulfire
- Safety Lantern belt slot via Curios; lantern colors update in hand, belt, and world
- Reinforced Air Bladder crafting copies durability from the ingredient bladder
- Advancements, recipes, loot injections, and drowned air-drain behavior (configurable)
- Chunk air-quality sync for multiplayer and air-provider bubbles
- In-game config screen for server settings
- English, Russian, and Chinese localization
- Server config via thinair-server.toml
Fixes & Polish in This Build
- Air bladder hold-to-refill works correctly in thin air
- Safety Lantern mines and drops properly with a pickaxe
- Curios GUI works when Thin Air is the only mod registering slots
- Respirator and Safety Lantern advancements trigger correctly
- Placed lanterns update when nearby air sources change
- Signal torch wall placement and block rendering match vanilla behavior
- Tag parity with upstream (NPC air sensitivity, air-provider tags, respirator protection rules)
Known Limitations
- Loot table injections in structures not yet fully verified in generated worlds
- Some multiplayer edge cases not exhaustively tested
- Report bugs in this repository's issue tracker
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:OPyUN2Vn:Y4PcH1YU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OPyUN2Vn:Y4PcH1YU"
}
