All versions
1.0.0
Release
Frosty's Sorting Depot 1.0.0last month 0
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
1.0.0 โ 2026-06-23
First release: a complete, purely mechanical sorting network.
Added
- Depot Controller โ routes buffered items to registered destinations on a hopper-style cadence (~4ร a hopper) and pulls items from an inventory placed directly above it. Exposes its buffer as a comparator signal and as an item capability on its top face.
- Linker Node โ a placeable destination marker that holds a Filter Card and a priority and feeds the inventory it faces.
- Linker (tool) โ right-click a Linker Node, then a Controller, to register it into the network.
- Filter Cards โ three modes, all configurable in-world by right-clicking the card onto an item:
- Item โ match an exact item.
- Tag โ match a tag; click an item to cycle through its tags.
- Overflow โ accept anything.
- Priority Stamps โ set a destination's priority (1โ5); right-click a Linker Node to apply.
- Overflow Chest โ an entity-rendered chest (double-chest joining + lid animation) that catches any item no destination accepted.
- Depot Terminal โ a read-only dashboard listing each destination's target, filter, and fill level, plus overflow fill and buffer count; scrolls for large networks.
- Advancements โ a "Sorting Depot" progression tree.
- Recipes, loot tables (blocks drop their contents), and an in-game config screen.
Notes
- Items are never voided: anything with no available destination waits safely in the Controller's buffer.
- Works with any storage that exposes the standard NeoForge item capability โ vanilla and modded alike.
- Built on the 26.2 transfer API (
ResourceHandler<ItemResource>).
Known limitations
- A double Overflow Chest currently exposes one half to routing (single chests are unaffected).
- Tag filters bind one tag at a time.
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:fl70u3Ld:gwBU0LLm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fl70u3Ld:gwBU0LLm"
}

