Tags
Creators
Details
4.0.16-beta-fabric
Compatibility
Changes
DeepNull Reforged 4.0.16-beta-fabric
Fabric beta for Minecraft 1.21.1.
This is a beta build of the Fabric port. It is playable, but it is not final yet. Expect bugs, edge cases, and a few remaining parity gaps while the port continues to be stabilized.
Highlights
- DeepNull Reforged is available on Fabric 1.21.1
- Fabric config files now load through a real Fabric-compatible config backend
- DeepNull and DampNull custom item rendering is restored
Shift + Scrollslot selection works again- Stored right click item-use behavior works again for supported singleton items inside the DeepNull
- GUI stack counts are formatted correctly again, including values like
1K - Creative DeepNull energy display is fixed
- DampNull fluid placement is fixed
- Creative DampNull keeps matching source fluids in the selected tank and voids overflow instead of moving it into another tank
- DeepNull and DampNull GUI titles are restored
- DeepNull auto-pickup now absorbs and voids matching item overflow by default when the matching stored slot is already full
- Added the
voidFullItemsOnPickupserver config option for the new overflow behavior - Chemical Upgrade now only loads and appears when Mekanism is installed and chemical storage is enabled
Notes
- Middle click is blocked only inside the DeepNull GUI where custom extraction uses it
- Fabric now generates real
client,common, andserverconfig files for DeepNull Reforged - This build should be considered test-ready, not final
- Back up worlds before updating
Bug Reports
If you hit a problem, please report it with:
- The exact item, block, or screen involved
- What you expected to happen
- What actually happened
- Crash log or latest log if available
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:yYjkmjge:std62AJ3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yYjkmjge:std62AJ3"
}![DeepNull Reforged (DankNull) [NeoForge/Fabric]](https://cdn.modrinth.com/data/yYjkmjge/31ec63f3fc0cc57184846c04facfd9ae8148dc9d_96.webp)

