Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 5 months ago
All versions
4.0.16-beta
Beta
DeepNull Reforged (DankNull) [NeoForge/Fabric] 4.0.16-beta7 months ago 25
Compatibility
Minecraft: Java Edition
26.1
Platform
NeoForge
Supported environments
Client and server
Changes
DeepNull Reforged 4.0.16-beta
Follow-up beta release for Minecraft 26.1 on NeoForge 26.1.0.5-beta.
Ported 1.21.1 Hotfixes
- Ported the latest
1.21.1regression fixes forward into the26.1branch. - Brought the 26.1 line back in sync with the newer
4.0.16behavior on the main NeoForge branch where that logic still applies cleanly.
Gameplay and Behavior Fixes
- Added a new server config option,
voidFullItemsOnPickup, for DeepNull auto-pickup overflow handling. - Fixed auto-pickup so matching items can still be absorbed and voided when the matching DeepNull slot is already full, instead of being rejected.
- Restored stored single-item interaction proxying for non-block, non-bucket items so tools and similar stateful items behave more like the current
1.21.1branch again.
UI Fixes
- Fixed DeepNull info panels to show the actual tiered DeepNull item name instead of the generic mod item group title.
- Fixed DampNull info panels to show the actual tiered DampNull item name instead of the generic mod item group title.
Compatibility
- Added Inventory Sorter compatibility IMC so DeepNull storage/container slots are blacklisted correctly.
Docs
- Updated config documentation for the new
voidFullItemsOnPickupserver option in both the wiki docs and the in-game guide docs.
Beta Notes
- This remains a beta build targeted at NeoForge
26.1.0.5-beta. - Companion-mod compatibility still depends on matching 26.1-side releases being 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:sXZGtkwp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yYjkmjge:sXZGtkwp"
}![DeepNull Reforged (DankNull) [NeoForge/Fabric]](https://cdn.modrinth.com/data/yYjkmjge/31ec63f3fc0cc57184846c04facfd9ae8148dc9d_96.webp)

