KubeJS and Draconic Evolution: Why Fusion Crafting Needs Clear Rules
If you run a modded Minecraft server with Draconic Evolution and want recipes you can tweak without digging through JARs, KubeJS is often the first stop. It lets you script recipes in JavaScript-style files, reload when your pack allows it, and keep everything versioned alongside your other tweaks. Fusion crafting is one of the mod’s signature mechanics: big energy costs, tiered catalysts, and multi-item inputs that feel closer to a ritual than a single crafting table click.
That power comes with a detail that trips people up the first time they script fusion in KubeJS: some ingredients are meant to be consumed, and others are meant to stay in the recipe grid as permanent “fixtures.” Getting that wrong changes balance overnight, so it pays to understand how the script expresses it.
What “consumes” really means in fusion recipes
In Draconic Evolution’s fusion system, many recipes assume ingredients are used up when the craft completes. That is the usual behavior players expect for expensive materials. Sometimes, though, you want an item to participate without vanishing—think of a reusable catalyst, a stabilizer block, or a special orb that should remain after the craft. KubeJS exposes that choice with a simple true or false flag paired with the ingredient.
By default, parsing tends to treat ingredients as consumed, which matches how most fusion crafts are designed. You only need to specify false when you deliberately want the item to persist through the recipe. If you forget and everything disappears, check whether you accidentally left the default behavior in place for something you meant to reuse.
Reading a minimal KubeJS fusion example
A typical ServerEvents block listens for recipe registration, then calls into Draconic Evolution’s fusion crafting builder. You name the central input item, list the supporting ingredients (with optional consumption flags), define the output, pick a fusion tier, and set the energy requirement. Tiers map to the progression names players already associate with the mod—draconium, wyvern, draconic, chaotic—so the recipe feels at home in the tech tree.
Energy values are not cosmetic: they gate how soon a base can realistically run the craft and how much infrastructure you expect players to build. If a fusion line feels too easy, raising energy or tightening inputs often fixes the pacing without touching world generation.
Arrays, booleans, and keeping recipes readable
When you list ingredients, plain entries behave like normal consumed stacks. When you need an exception, you pair the item with false so the recipe knows not to eat it. Mixing both styles in one list is normal: one row might be ["minecraft:obsidian", false] while another stays a simple consumed stack. Keeping comments beside each line helps future you remember which parts are reusable, especially when you maintain dozens of fusion lines across updates.
Organizing files by tier or by machine stage also keeps servers sane. Players rarely complain about “too much documentation” inside your script folder, but they will notice when a chaotic-tier recipe accidentally uses wyvern energy because a line was copied and not updated.
Testing on servers and in single player
After you add or change fusion recipes, validate them in a test world before pushing to a live server. Confirm consumed items disappear, reusable pieces remain, outputs match expectations, and energy draw aligns with your generators. If something misfires, the culprit is often a boolean flipped the wrong way or a tier string that does not match what Draconic Evolution expects for that fusion table level.
Pack makers who juggle many mods sometimes centralize downloads and updates so testers stay on the same build. If you are curating a custom lineup, you might appreciate that this mod can be easily installed via the foxygame.net launcher—a flexible, modern Minecraft launcher where you can grab mods straight from the menu without hunting through scattered pages. It does not replace careful recipe testing, but it trims friction when everyone needs the identical stack for fusion tweaks.
Balance tips that survive version bumps
- Match tier names to the progression you advertise in quests or tooltips so players are not surprised by gating.
- Document energy numbers beside major crafts so you can rebalance when power generation mods change.
- Use non-consuming inputs sparingly; each reusable piece multiplies how often a farm can run the same craft.
- Reload or restart according to your KubeJS setup—some changes need a full reboot to avoid stale recipe caches.
Closing thoughts
KubeJS gives you a precise vocabulary for Draconic Evolution fusion: central item, ingredient list with consumption flags, tier, and energy. Treat the true or false switch as part of your balance toolkit, not an afterthought. Test deliberately, comment generously, and your fusion lines will feel intentional—challenging, fair, and unmistakably Draconic Evolution—whether players craft in single player or on a busy modded server.