Tags
Creators
Details
0.3.8.alpha
Compatibility
Changes
Add some more options for the Adv Item Filter Var
[Added]
-
Advanced Item Filter cards can now match items by Mod ID (matching all items belonging to a specific mod) or by Item Tag (such as
#minecraft:planks). -
Scrollable tag selector within the filter card settings panel to choose matching tags dynamically.
-
Cycling item preview animations on cards configured for tags, cycling once per second through all items associated with the selected tag.
-
Visual "MID" text overlay on filter card slots when they are configured to match by Mod ID.
-
Custom tooltip lines on filter cards to describe whether they are matching by a specific item, mod namespace, or tag.
-
Introduced a slot configuration developer API (
ISlotConfigurable) that allows third-party add-on creators to reuse the compact block slot selector menu on their own custom nodes. -
Added a dynamic error-handling API (
INodeClientProperties#getErrorTooltip) that enables custom flowchart blocks to display custom validation errors and warning card tooltips in the interface.
[Changed]
-
Aligned quantity configuration fields to the right of the item slot in the variable card overlay, making room for color and tag controls.
-
Refactored network code into a separate processing module to clean up the mod's initial boot sequence.
-
Re-organized how client-side settings, screens, and keybinds register themselves during game startup.
-
Refactored slot selector menus to support configurations on any compatible custom inventory node rather than restricting them exclusively to the default item input and output blocks.
-
Moved visual node error message logic out of main system rendering loops and into modular client registries.
[Fixed]
- Isolated client-only code paths to prevent crash loop errors when hosting or running dedicated multiplayer servers.
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:LTva5BWN:IoDwVe1T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LTva5BWN:IoDwVe1T"
}

