All versions
1.3.0-26.2
Release
Frosty's Sorting Depot 1.3.0 [26.2]last month 0
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
1.3.0 โ 2026-06-29
Added
- Filter Card NOT / exclude mode. A new toggle button at the top-right of the Filter Card
screen flips the card's decision: a card configured
NOT [cobblestone]accepts everything except cobblestone. Works in every mode (Item, Mod, Tag) and pairs naturally with a higher-priority specific filter for the items you want elsewhere. Hover the button for an in-game explanation. The card tooltip and the Depot Terminal both prefixNOTon negated rows. - Two-hand Filter Card copy. Hold a Filter Card in each hand and shift-right-click to copy the main-hand card's configuration onto the off-hand card. Cuts the time to set up a network of similar Linker Nodes way down. Over-hotbar confirmation, no chat spam.
- Depot Terminal: search box. A 150-px text field at the top of the dashboard filters rows by target block name OR filter text (case-insensitive substring). Typing "e" no longer closes the GUI when the search box has focus.
- Depot Terminal: click-to-highlight. Click a row to outline the corresponding Linker Node in-world for 5 seconds, drawn through walls so you can spot it from anywhere โ no more hunting "which chest is this one again?" in a 200-node base. Uses the existing beam-render path so the colour follows your Linker Beam config.
- Linker Node: Unlink button. Open the node GUI; if it's registered to a Controller a red Unlink button appears next to the status label. Clicking removes the node from the network without breaking the block (so you keep the card inside).
Fixed
- Terminal click-to-highlight now x-rays on every branch. Previously documented as a
per-version caveat on 1.21.x โ the highlight was hidden by intervening blocks. Resolved on
1.21.5 / 1.21.8 via a NeoForge
PipelineModifierthat disables depth testing for the highlight pass, and on 1.21.1 via a custom no-depthRenderType. Behaviour now matches 26.2 (which usesGizmos.setAlwaysOnTop).
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:zTHEJDXB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fl70u3Ld:zTHEJDXB"
}

