What KubeJS Botania adds to your modded Minecraft world
If you love Botania’s mana systems, flowers, and ritual-style crafting—but you also want total control over recipes and custom brews—KubeJS Botania is the bridge you have been looking for. This addon extends KubeJS so you can script Botania content the same way you already tweak vanilla-style recipes: with clear events, readable builders, and repeatable results across worlds and servers.
Why pack makers and server admins reach for it
Botania is deep: petals, runes, altars, and world-changing automation all depend on consistent recipe balance. When you are tuning progression for a modpack or a private server, hard-coded defaults rarely match your vision. KubeJS Botania lets you align Botania’s mechanics with your pack’s pacing—without rebuilding the mod from scratch.
- Register custom brews with mana costs, effect timing, and restrictions.
- Remove or replace Botania outputs when something clashes with your economy.
- Script classic Botania recipe types so they match your item IDs and gating.
- Work on both Forge and Fabric, so your scripts can follow the loader your pack uses.
Loaders, files, and version sanity
KubeJS Botania supports Forge and Fabric, but the exact file you need can depend on your Minecraft version and loader. When you browse the project files, treat the Files tab as the source of truth: Recent Files often highlights only the newest upload, which might not be the build that matches your modpack stack. Double-check that your KubeJS major version lines up too; KubeJS 6 (KJS6) changes conventions, so examples written for earlier styles may need a careful rewrite to match KJS6’s patterns.
Custom brews: flasks, incense, and the Tainted Blood Pendant
One of the standout features is brew registration through Botania’s brew registry event in your startup scripts. You define a brew ID, set the mana cost, and attach effects using the same conceptual parameters you would expect from the /effect command—just remember durations are in ticks, not seconds. From there you can shape how the brew behaves when converted into Botania’s consumable formats: think flasks for drinking, incense for area-style use, and infusions for items like the Tainted Blood Pendant.
Mana cost is not just a number on paper; it affects how expensive it feels in real play. For pendant-style applications, the documentation-style notes you will see in examples matter: pendant ticking can scale with cost, duration, and effect level in ways that can quietly drain mana pools if you are not careful. That is exactly the kind of detail KubeJS helps you iterate: tweak, reload, test, repeat.
You can also opt out of specific delivery methods when a brew should not be “free real estate” for every Botania item type. Flags like denying incense or denying pendant infusing are practical guardrails when you want a strong effect to remain flask-only, or when incense would trivialize a dungeon biome encounter.
Botania recipe types you can script in server scripts
On the server side, KubeJS Botania exposes Botania recipe mechanics as first-class recipe helpers. That means you are not limited to “vanilla crafting table” thinking—you can work with the systems players already associate with Botania progression.
- Mana infusion conversions, including catalyst-style inputs when the recipe expects them.
- Elven trade, including multi-input and multi-output trades for cleaner loot-like exchanges.
- Pure Daisy transformations, including variants where you specify additional parameters.
- Petal Apothecary mixing, Runic Altar crafting with mana costs, and Terra Plate assembly for high-tier crafting pressure.
- Worldgen-adjacent flower behaviors such as Orechid and Orechid Ignem, plus Marimorphosis with biome lists and weighting-style numbers.
A typical workflow looks like this: remove a default recipe that breaks your pack’s early game, then reintroduce a replacement that uses blocks and biomes you want players to explore. After that, wire your custom brew into Botania’s brew recipe helper so the new effect is obtainable through Botania’s intended crafting loop—not a random shapeless shortcut.
When you are juggling many mods, installing the right combination of KubeJS, Botania, and bridge mods should feel straightforward. If you like a launcher that keeps mod workflows tidy, 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—so you spend less time hunting files and more time testing mana numbers.
KJS6 migration: expect to adapt examples
If you are coming from older snippets, do not copy-paste blindly. KJS6’s event style and API surface can differ enough that a working server script from a previous era needs translation, not just a filename change. Treat community examples as a blueprint: keep the Botania intent (inputs, outputs, mana, timings), then refactor the surrounding KubeJS syntax to match your installed major version.
Conclusion
KubeJS Botania is less about “adding random items” and more about making Botania’s crafting, brewing, and world mechanics obey your pack design. Whether you are tightening elven trades, rebalancing ore generation flowers, or inventing a bespoke brew with strict usage rules, the combo of KubeJS scripting plus Botania systems gives you a maintainable path to deep customization—especially when you verify loader builds, respect tick-based durations, and plan pendant costs before players speedrun your mana network.