Actually Additions · Addon guide · Advanced
KubeJS Actually Additions Guide: Custom Reconstructor & Empowerer Recipes
In this advanced guide, you will learn how to create and modify custom recipes for Actually Additions machines like the Atomic Reconstructor, Empowerer, and Crusher using KubeJS. Mastering this allows modpack developers and power users to deeply integrate Actually Additions crystals and machines with other tech mods for a unified progression system.
What you need
- Minecraft with Actually Additions and KubeJS installed
- JEI (Just Enough Items) or EMI for verifying recipes and item IDs
- A code or text editor (such as VS Code) to edit scripts
- In-game access to the /reload and /kubejs commands (cheats enabled)
Step by step
1Set Up Your KubeJS Server Script
Navigate to your Minecraft instance folder and open the 'kubejs/server_scripts' directory. Create a new file named 'actually_additions_recipes.js' and open it in your text editor. Start your file by declaring the recipe event listener: ServerEvents.recipes(event => { // recipes go here });. All custom machine recipes must live inside this block because the server handles recipe registration during world load and datapack reloads.
Tip: Keep your Actually Additions tweaks in a dedicated script file so you can easily troubleshoot syntax errors without disabling your entire modpack's recipes.
2Export Existing Recipe Schemas
Before writing custom JSON recipes, it is best practice to inspect how your specific version of Actually Additions formats its data. Load into a test world, place an Atomic Reconstructor or Empowerer, and run the command '/kubejs dump_innards' or export the datapack structure using KubeJS utilities, or simply extract the mod's JAR file to inspect the 'data/actuallyadditions/recipes' folder. This shows you the exact JSON keys the mod expects for energy, time, and item inputs.
Tip: Use the in-game command '/kubejs hand' while holding an item like a Restonia Crystal to copy its exact item ID and NBT data to your clipboard.
3Create a Custom Atomic Reconstructor Recipe
Inside your ServerEvents.recipes block, use the 'event.custom()' method to register a laser transformation recipe. Define a JSON object with 'type': 'actuallyadditions:laser', an 'ingredient' object specifying the input item (such as 'item': 'minecraft:amethyst_shard'), a 'result' object with the output item ID (such as 'actuallyadditions:diamatine_crystal'), and an 'energy' integer representing the Crystal Flux (CF) cost. When you drop the input item in front of an active Atomic Reconstructor in-game, the laser beam will now consume that exact amount of CF to convert it.
Tip: Check JEI for standard crystal conversion costs to balance your custom energy values against default progression.
4Add a Multi-Input Empowerer Recipe
The Empowerer requires a central item on the Empowerer block and four modifier items on the surrounding Display Stands. To script this, add another 'event.custom()' call with 'type': 'actuallyadditions:empowering'. Your JSON object must include a 'base' ingredient for the center item, a 'modifiers' array containing exactly four ingredient objects for the Display Stands, a 'result' object for the final output (like an Empowered Enori Crystal), plus 'energy' (total CF required), 'time' (duration in ticks), and 'color' (an integer or hex value that tints the laser beams).
Tip: The order of the four items inside the 'modifiers' array does not require a specific compass arrangement on the in-game Display Stands.
5Script Dual-Output Crusher Recipes
Actually Additions Crushers and Double Crushers support a primary output and a chance-based secondary output. Call 'event.custom()' with 'type': 'actuallyadditions:crushing', specifying the 'ingredient' object for the input ore or item. Next, define a 'result' array containing one or two output objects; each output object includes the 'result' item ID and count, along with a 'chance' float value (where 1.0 is 100% for the primary output, and a lower decimal like 0.2 represents a 20% bonus output).
Tip: Use Forge or NeoForge item tags (such as 'tag': 'forge:ores/copper') in the ingredient field instead of specific item IDs to ensure compatibility across multiple mods.
6Remove or Modify Default Recipes
If you are replacing a default recipe, such as changing how Void Crystals or Black Quartz are processed, you must first remove the original recipe to prevent conflicts. At the top of your 'ServerEvents.recipes' block, use 'event.remove({ id: "actuallyadditions:laser/crystal_red" })' or filter by output and recipe type. You can find the exact recipe ID in-game by enabling advanced tooltips (F3 + H) and hovering over the output in JEI while holding Shift.
7Test and Reload In-Game
Save your JavaScript file and return to your running Minecraft test world. Type '/reload' in the chat to force KubeJS and the server to re-parse all recipe scripts. Open JEI and search for your new output items to confirm the Atomic Reconstructor, Empowerer, and Crusher tabs display your custom recipes, then build the physical machine setup with Display Stands and a CF generator to verify the energy consumption and laser animations.
Tip: If your recipe does not appear in JEI after reloading, run '/kubejs errors' in chat to see the exact line number where a missing comma or invalid item ID occurred.
How it works
Modern versions of Actually Additions are completely data-driven, meaning the mod registers custom recipe serializers (like 'actuallyadditions:laser', 'actuallyadditions:empowering', and 'actuallyadditions:crushing') with the vanilla Minecraft recipe manager. Instead of hardcoding crystal transformations in Java, the machines query the server's active datapack library whenever an item enters a Crusher slot, sits on a Display Stand, or lies in the path of an Atomic Reconstructor beam.
KubeJS acts as a bridge by generating a virtual datapack in memory before the world finishes loading or during a '/reload' command. When you call 'event.custom()', KubeJS translates your JavaScript object directly into a standard JSON file and injects it into the recipe manager. Because this happens at the server datapack level, JEI automatically detects the new recipes and displays the updated Crystal Flux costs, secondary output chances, and Display Stand requirements to the player.
Common mistakes
- Placing machine recipe scripts in 'client_scripts' or 'startup_scripts' instead of 'server_scripts', which causes the recipes to never register.
- Providing fewer or more than four modifier ingredients in an Empowerer recipe JSON, which can cause recipe serialization errors or prevent the Display Stands from activating.
- Forgetting to remove the original Atomic Reconstructor recipe when creating an override for a vanilla item (like Redstone or Iron), leading to the laser choosing the first registered recipe instead of your custom one.
- Setting the Empowerer energy cost higher than the internal CF buffer of the Display Stands without adjusting machine configurations, making the recipe impossible to complete in-game.
FAQ
Why do I need to use event.custom() instead of a built-in KubeJS shortcut?
Unless you have a dedicated KubeJS addon for Actually Additions installed, KubeJS does not know the mod's proprietary recipe syntax by default. Using event.custom() works directly with the mod's native JSON datapack format without requiring extra bridge mods.
Can I use lenses like the Lens of Color in custom Atomic Reconstructor recipes?
Standard laser transformations use the 'actuallyadditions:laser' recipe type, while lens-specific behaviors or color cycling may use distinct recipe types or tags depending on your mod version. Always check the mod's internal 'data/actuallyadditions/recipes' directory via JEI recipe IDs to see the exact serializer used.
How do I change the laser beam color on a custom Empowerer recipe?
The 'actuallyadditions:empowering' JSON accepts a 'color' parameter, which takes a decimal integer representation of a hex RGB color code. You can convert any standard 6-digit hex color to a decimal number to match the visual theme of your custom item.
Do custom Crusher recipes automatically work in the Double Crusher?
Yes. The Double Crusher pulls from the exact same 'actuallyadditions:crushing' recipe registry as the single Crusher, simply processing two slots simultaneously.
By leveraging KubeJS's custom JSON recipe event with Actually Additions' native recipe serializers, you can seamlessly customize Atomic Reconstructor, Empowerer, and Crusher recipes to fit any modpack progression.