Tags
Creators
Details
1.9.1
Compatibility
Required content
Changes
🎯 Release v1.9.1 - Jetpacks & Drill Read Right Again
Highlights: Fixes the HUD showing jetpacks, exoskeletons and the portable drill as empty on current Create: Stuff 'N Additions builds.
🔧 Fixes
⛽ Jetpacks and the Hand Drill No Longer Show Empty
- On newer Create: Stuff 'N Additions (2.1.4+), the overlay drew every jetpack, exoskeleton and portable drill as empty, no matter how much fuel or water they actually held (#19).
- CS&A 2.1.4 stopped storing levels in item NBT (
tagFuel/tagWater) and moved them into a NeoForge fluid handler — fuel as lava, water as water. The overlay was still reading the old NBT, which no longer exists, so everything read as zero. - The overlay now reads the fluid handler directly and scales each bar to the tank's own reported capacity (so CS&A's configurable capacities are honoured). Pre-2.1.4 CS&A still works via the old NBT fallback.
🦴 Netherite Exoskeleton Now Shows Up
- The netherite exoskeleton holds both fuel and water, but it was missing from the overlay's recognised-item list, so it displayed nothing. It's now detected like the other exoskeletons.
🔄 Backward Compatibility
✅ Older CS&A still supported — pre-2.1.4 installs keep reading via the legacy NBT path. ✅ Existing configs keep working — your saved overlay position and settings are unchanged. ✅ Same Minecraft version — still Minecraft 1.21.1 / NeoForge.
📥 Installation
- Download the latest
.jarfile from this release - Place it in your
modsfolder - Launch Minecraft with NeoForge
Requirements: Minecraft 1.21.1 | NeoForge 21.1.233+ | Create 6.0.11+
Compatibility: Works with Create: Stuff & Additions (2.1.4+) and other Create-compatible tank items
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:csA0cpEX:uSPahtVl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:csA0cpEX:uSPahtVl"
}

