Scavenge-Baubles: Bridging Scavenge and Baubles in Minecraft
Minecraft modding thrives on interconnected systems, where one creator’s framework becomes the foundation for another’s brilliant expansion. The Scavenge mod introduces a powerful, scriptable condition system for customizing gameplay progression, while Baubles adds extra equipment slots for rings, amulets, belts, and more. Scavenge-Baubles is the lightweight addon that fuses these two worlds, letting modpack makers and server operators check what a player is wearing in those additional slots directly through Scavenge’s condition engine.
Understanding the Core Concept
At its heart, Scavenge allows you to define custom “stages” or unlock requirements using JSON-based conditions. Originally, these conditions could inspect a player’s inventory, held item, or even their location. With Scavenge-Baubles, the scope expands dramatically—you can now query the Baubles accessory slots. This means a modpack can gate access to dimensions, crafting recipes, or special abilities based on whether a player is wearing a specific ring, amulet, or any other Bauble type.
The addon introduces a single, versatile condition type called has_bauble. Once installed alongside both Scavenge and Baubles, this condition becomes available in your Scavenge scripts, ready to be woven into complex progression trees. It works seamlessly with other conditions, so you might require a player to have both a certain item in their hand and a specific charm equipped to proceed.
The has_bauble Condition: Parameters and Flexibility
The real magic lies in the condition’s parameters. Each one fine-tunes exactly what the game checks, giving you granular control without needing to write Java code. Here’s a breakdown of every parameter you can use:
- disableJEI (Boolean, default false) – Determines whether the condition and its requirements appear in JEI (Just Enough Items) integration. Set to true if you want to hide the unlock logic from players.
- name (String) – The type of Bauble slot to check. Accepted values are: Amulet, Ring, Belt, Trinket, Head, Body, Charm. You can target one specific slot per condition entry.
- stack (Object) – Defines the item stack that must be present in the chosen slot. This object contains three sub-parameters:
- name (String) – The registry name of the item (e.g., “minecraft:diamond”).
- amount (Int, default 1) – The required stack size. Usually 1 for Baubles, but you can specify higher if a mod adds stackable accessories.
- meta (Int, default 32767) – The metadata value to compare. The default 32767 acts as a wildcard, ignoring metadata entirely. Use a specific number to require a certain variant or damage value.
- nbt (String, default IgnoreNBT) – A reference to an NBT file or raw NBT string. If provided, the condition checks that the Bauble’s NBT data matches. Leave blank to skip NBT checks.
All these parameters are case-sensitive and must be written exactly as shown. The condition type itself is simply “has_bauble”, and it has no incompatible condition types—it can coexist with any other Scavenge condition you dream up.
Practical Use Cases in Modpacks
Imagine a magic-themed pack where players must attune themselves to an ancient power. You could create a Scavenge stage that only unlocks when a player wears a specific Amulet of Attunement in the Baubles amulet slot. The script snippet would look something like this:
"conditions": [
{
"type": "has_bauble",
"name": "Amulet",
"stack": {
"name": "mysticalmod:attunement_amulet",
"amount": 1,
"meta": 0
}
}
]
Another scenario involves gating a boss fight. Require the player to have both a Ring of Protection and a Charm of Warding equipped simultaneously. Since each condition instance checks only one slot, you would simply list two has_bauble conditions in the same array—one for the Ring slot and one for the Charm slot. The Scavenge engine evaluates them together, so both must be true for the stage to unlock.
For server administrators, this opens up creative possibilities like daily quests that demand a specific Trinket be worn, or event-based progression where players earn temporary Baubles that grant access to limited-time areas. The addon’s tight integration with Scavenge means you can combine has_bauble with location checks, time-of-day conditions, or even player scoreboard values.
Installing Scavenge-Baubles and Getting Started
Since this mod is an addon, it requires both Scavenge and Baubles to be present in your mods folder. You can obtain the main Scavenge mod from its CurseForge page (search for “Scavenge” on CurseForge) and Baubles from its own CurseForge project. Once those are in place, drop the Scavenge-Baubles jar into the same folder, and you’re ready to script. If you prefer a more streamlined approach to mod management, the foxygame.net launcher offers a modern, flexible way to browse and install all three mods directly from its built-in mod menu, automatically handling dependencies and keeping your instance tidy without manual file juggling.
After installation, verify that the condition is registered by attempting to use it in a test Scavenge script. Any syntax errors in your JSON will be logged, so keep an eye on the console. The JEI integration parameter is especially handy during development—leave it visible while you test, then hide it once the pack is finalized to avoid spoiling the discovery for players.
Conclusion
Scavenge-Baubles might be a small addon, but it fills a crucial gap for modpack creators who want to leverage Baubles’ accessory system within Scavenge’s robust condition framework. By exposing a clean, parameter-rich has_bauble condition, it empowers you to build intricate progression gates, class systems, and quest logic that respond to what a player is literally wearing. The combination of Scavenge’s scripting power and Baubles’ equipment slots opens a new dimension of player-driven storytelling in Minecraft. Whether you’re crafting a hardcore survival challenge or a narrative adventure, this addon deserves a spot in your modding toolkit.