Links
Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 2 days ago
All versions
1.4.10+26.3
Beta
1.4.10+26.32 days ago 4
Compatibility
Minecraft: Java Edition
26.3-snapshot-7
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Catalog completeness release. Every cell rebuilt: the vault catalog is shared across all cells, so the classification work below applies product-wide, not just to 26.3.
Added
- The 48 items Minecraft 26.3-snapshot-7 introduced are now classified, not dumped in
Uncategorized. 32 concrete slabs + stairs (all 16 dye colours) -> Colored Blocks, ranked
directly beside the concrete they are cut from. 16 new per-target map items --
ancient_city_map,buried_treasure_map, the six*_village_maps, the explorer maps and the rest, which Mojang split out offilled_map-> Materials & Utility, ranked besidefilled_map. - The pre-existing classification backlog is closed too. 16 cushions and
straw_bed-> Fabric & Color; the 7 infested blocks -> Stone & Masonry, each beside its base block;player_head-> Magic & Treasure with the other mob heads. 73 items classified in total, with keyword-search entries for the 48 new ids. - The remaining 21 net-new registry ids are creative/technical only (command blocks, jigsaw,
structure/test blocks, spawners, bedrock,
budding_amethyst,suspicious_sand, spawn eggs, ...) and are deliberately excluded from the vault, consistent with howbarrierand the spawn eggs have always been treated. They are now recorded as such in the taxonomy, so the "needs classification" list is empty and stays empty instead of re-surfacing every version.
Fixed
- A new Minecraft version used to add its items to the vault as storable-but-Uncategorized. Nothing
reported this: the load-time log prints the catalog's own item count, which does not change when
the registry grows, so the gap read as healthy. Catalog completeness is now an explicit release
gate --
tooling/bv_new_items.pymust return zero before a version ships.
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:GfbuXagl:veg4CTWh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GfbuXagl:veg4CTWh"
}

