Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 5 months ago
All versions
4.2.1-beta
Beta
DeepNull Reforged (DankNull) [NeoForge/Fabric] 4.2.15 months ago 706
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
DeepNull Reforged 4.2.1
Hotfix release for Minecraft 26.1 and 26.1.2 on NeoForge.
Fixes
- Fixed DeepNull stored stacks being exposed incorrectly to external item automation, which could cause some mods to collapse very large stored stacks down to a single normal stack during round-trip updates.
- Fixed tossed-item pickup delay so it only applies when a DeepNull could actually absorb that item, instead of affecting unrelated tossed items globally.
- Fixed Crafting Tweaks compatibility across the newer API variants so the DeepNull clear-grid integration no longer fails during initialization on affected setups.
- Fixed DeepNull Dock block capability handling for external automation so mods like Pipez can interact with the dock more reliably.
- Fixed docked generator-buffer extraction through the block capability path used by external automation.
- Fixed dock fluid and energy capability state to stay synchronized across side-based automation queries, addressing the stale-state path behind reported fluid duplication behavior with AE2-style setups.
Compatibility
- Kept support for both Minecraft
26.1and26.1.2. - Added stronger regression coverage for tossed-item pickup delay, visible DeepNull item capability behavior, dock capability state, and automation extraction paths.
Notes
- This release is focused on regression fixes and automation compatibility rather than feature changes.
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:TONzZghu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yYjkmjge:TONzZghu"
}![DeepNull Reforged (DankNull) [NeoForge/Fabric]](https://cdn.modrinth.com/data/yYjkmjge/31ec63f3fc0cc57184846c04facfd9ae8148dc9d_96.webp)

