Links
Tags
Creators
Details
1.1.0-26.1.x
Compatibility
Changes
VaultCrates 1.1.0 — Minecraft 26.1.x
For Paper 26.1 – 26.1.x · Java 25 required
Running 26.2 or 26.3? Use 1.1.1-26.2 or 1.1.2-26.3 instead. On 1.21.x, stay on 1.0.1.
⚠️ Before you update
- Java 25 is now required (Paper 26.x needs it too).
- This jar only loads on Minecraft 26.1 or newer.
- Your configs are kept — missing keys are filled in automatically.
✨ New
- Support for Minecraft 26.1.x (built against Paper API 26.1.2)
- ItemsAdder 4.x furniture: Display/Interaction entities and multi-part furniture (display + hitbox) are detected — clicking any part of a furniture crate opens it
- FancyNpcs 2.x and ZNPCsPlus 2.x NPCs can be linked:
/vc linknpc <crate> fancynpcs <name>/znpcsplus <id> - Citizens NPCs are linked by their NPC id, so the link survives respawns
- VaultUnlocked is supported for the key shop and economy crates
- Enchantments in rewards accept namespaced ids from enchant plugins, e.g.
"myplugin:soulbound": 1 - The update checker only offers builds for your server's Minecraft version
🐛 Fixes
- NPC crates opened without a key — every NPC link now runs the same key, permission and economy checks as the crate itself
/vc linknpclinks did nothing when clicked; Citizens NPCs could not be linked at all- Furniture crates broke when clicked (ItemsAdder picked them up); IA can no longer break or interact with a placed crate
- Shift + left-click on a furniture crate no longer deletes it silently — it shows the ID; remove with
/vc remove <id> Glow: trueadded a hidden Infinity enchant —/enchantand anvils failed with "cannot support that enchant". Glow is now a pure visual glintGlow: falsenow also hides the glint ItemsAdder items carry by default- ItemsAdder
:icon:font images were not replaced on ItemsAdder 4.x - MMOItems and ExecutableItems rewards did not load on current versions of those plugins
- The key shop stayed disabled when the economy plugin started after VaultCrates
- Startup error (
NullPointerException) when ItemsAdder rewards were loaded - Purple/italic lore in the selectable-rewards GUI, shop GUI and reward footer
- "Another crate is too close" with no crate nearby (stale placements are ignored)
/vc reloadwith a YAML error inconfig.ymlreset the config to defaults — it now keeps the last valid config and prints the error
🔧 Checked against plugin APIs
ItemsAdder 4.0.18 · Nexo 1.29 · Oraxen 1.220 · MMOItems 6.10 · ExecutableItems (SCore 5.25) · Citizens 2.0.44 · FancyNpcs 2.11 · ZNPCsPlus 2.0 · PlaceholderAPI 2.12.3 · VaultUnlocked 2.20
Optional dependencies
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:yjvMVJWc:gmeuKRVn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yjvMVJWc:gmeuKRVn"
}

