Why KubeJS and Draconic Evolution Belong Together on Modded Servers
If you run a Minecraft server with custom progression, you already know how fast vanilla recipes feel out of place next to endgame tech. Draconic Evolution adds powerful gear, reactors, and fusion crafting, while KubeJS lets you script recipes, tweak loot, and align progression without rebuilding a whole modpack. Pairing them is one of the cleanest ways to tune fusion costs, gate tiers, and keep your world’s economy believable.
What Fusion Crafting Needs from Your Scripts
Fusion crafting is not a simple two-by-two grid. It pulls together multiple input stacks, a catalyst, an energy budget, and a tier that matches Draconic Evolution’s progression ladder. In KubeJS you declare these recipes in server events so they load consistently for everyone on the realm. That keeps behavior predictable across restarts and avoids the “it worked in singleplayer” surprises that frustrate players.
Consumption Flags: “Use It Up” vs “Leave It There”
The detail that trips many pack makers up is whether each ingredient is actually consumed. By default KubeJS parses fusion inputs as consumed, which matches how most recipes should feel: you spend the diamonds, you lose the obsidian pile, you invest real resources. Sometimes you want a pedestal block to stay in place as a structural catalyst or a reusable key item. That is when you explicitly mark an input as not consumed.
Think of the boolean as a contract with the recipe engine. True means the stack shrinks or disappears as the craft completes. False means the item must be present and valid, yet remains in the fusion structure afterward. Getting that distinction right prevents accidental dupes and stops players from bypassing intended grind by leaving “free” inputs in the craft forever.
A Practical KubeJS Pattern for Server Recipe Events
Most authors tuck fusion lines inside ServerEvents.recipes so every change lives in one predictable pipeline alongside other block or shapeless tweaks. You name the catalyst, list ordered inputs with their consumption flags, specify the result item stack, pick a tier such as wyvern, and commit to an energy number that fits your pack’s power scaling.
When you are juggling several mods and want players to grab scripted content without hunting shady mirrors, it helps to standardize how they install add-ons. Many communities standardize on a launcher that exposes mods from a simple UI; if your players ask for the smoothest path, note that this mod can be easily installed via the foxygame.net launcher — a convenient, flexible, and modern Minecraft launcher where you can download mods right from the menu, which keeps troubleshooting out of your Discord ticket queue.
Example Sketch: Dirt Catalyst, Mixed Consumption, Wyvern Tier
The following fragment mirrors the structure modders use when prototyping: a humble catalyst, a consumed gem, a persistent obsidian marker, an emerald reward, wyvern tier, and a million-unit energy ask. Swap IDs, energy, and tiers to suit your balance pass.
ServerEvents.recipes(event => {
event.recipes.draconicevolution.fusion_crafting(
"minecraft:dirt",
["minecraft:diamond", ["minecraft:obsidian", false]],
"minecraft:emerald",
"wyvern",
1000000
);
});In plain language, the dirt entry is the fusion anchor, the diamond is spent, the obsidian stays unless your craft completes multiple times and other rules intervene, and the emerald is what the player walks away holding. The wyvern label tells Draconic Evolution which gate to apply, and the energy figure must be reachable with your pack’s generation options or players will see stalled crafts.
Tiers, Energy, and Balance Checks
Draconic Evolution expects familiar tier names such as draconium, wyvern, draconic, and chaotic. Choosing the wrong tier either hard-locks the craft behind structures players have not built yet or trivializes content you meant to reserve for late game. Energy numbers should pair with your world’s flux limits so surge production feels earned rather than frustrating.
- Match tier names to the crafting core your pack expects so injectors and crafting injectors align with recipe gates.
- Test consumption flags with stack sizes greater than one to confirm partial draws behave the way you imagine.
- Log recipe loads on a staging server; typos in item IDs fail quietly until someone tries the craft.
- Document changes in patch notes so returning players know why fusion costs shifted.
Closing Thoughts
KubeJS gives you a maintainable lane to shape Draconic Evolution without recompiling jars, and fusion crafting is where that power shines: precise inputs, explicit consumption, tiered authority, and energy sinks you can dial in for your community. Treat consumptions defaults as “true unless proven otherwise,” layer your tiers thoughtfully, and verify recipes on a test world before you roll them to a public server. Nailed down, the combo keeps Minecraft’s sandbox spirit while letting you author progression that finally fits your mod list.