Badges update automatically and link to the mod page on MineUniverse.
Create, edit, remove, and manage recipes — directly inside Minecraft.
Acidglow's Ingame Recipe Editor is a server-authoritative recipe management tool for NeoForge that allows permitted players and server administrators to manage recipes without manually creating or editing datapacks.
Browse registered items, inspect existing recipes, create new ones, remove unwanted recipes, restore defaults, and hide items — all from an in-game interface.
Recipe changes are stored with the world and automatically reapplied whenever recipes reload.
Open the editor with:
/recipeeditorBy default, access is available to:
Editor access and the required operator level can be changed through the common configuration.
The built-in Item Book provides an overview of registered items and acts as the main entry point for recipe management.
From here you can browse items, inspect their recipes, and begin creating or modifying recipes without needing external tools or manually editing JSON files.
Items that have been hidden remain visible to administrators inside the Item Book with a (Hidden) marker.
The editor currently supports:
When an item has multiple recipes, you can navigate between them directly inside the editor.
Custom recipes can be created directly through the in-game interface.
Select the desired ingredients and output, configure the recipe, and save it without manually creating a datapack.
Existing recipes can also be used as a starting point.
When viewing an existing recipe, saving it only creates a new custom recipe after its editable contents have actually been changed.
Recipes are not limited to individual items.
Item tags can also be used as recipe ingredients, allowing a recipe to accept multiple interchangeable items.
To select a tag:
Hold Left Ctrl while hovering over an occupied ingredient slot, then select one of the available tags for that item.
This is especially useful when creating recipes intended for larger modpacks where multiple materials should be interchangeable.
Default recipes can be removed without permanently losing them.
Removed default recipes are placed in the Removed Recipes list and can later be restored through the editor.
Remove → Restore later
Remove → Permanently deleted
Custom recipes do not have the same restoration system as default recipes, so make sure you actually want to delete them before removing them.
Server administrators can remove all custom recipes and restore all previously removed default recipes with:
/recipeeditor restore_allThis provides an easy way to reset recipe modifications made through the editor.
Note: This command does not reveal items that have been hidden.
The Recipe Editor can also be used to hide unwanted items from a world.
When an item is hidden, its recipes are removed from the server recipe list and compatible recipe-viewer integrations.
The mod can also prevent the hidden item from continuing to exist or re-enter the world.
Depending on where the item exists, the system can:
Always make a world backup before using the Hide Item feature.
Hiding an item can permanently remove matching item stacks and placed blocks from the world.
Revealing the item later allows it to be used again, but:
Previously deleted items and blocks are NOT restored.
Use this feature as an administrative world-management tool, not as a temporary visibility toggle.
Acidglow's Ingame Recipe Editor is server-authoritative.
The server determines which recipes exist, which recipes have been removed, which items are hidden, and which players are allowed to modify them.
By default, Recipe Editor access is granted to:
These requirements can be adjusted in the common configuration.
Granting items directly through the Item Book is intentionally more restricted and requires either:
This keeps recipe editing useful for administrators while preventing normal players from using the editor as an unrestricted item source.
Changes made through the Recipe Editor are stored with the world.
This includes:
The changes are automatically reapplied when recipes reload, so you do not need to recreate your edits after restarting the game or server.
This makes the editor useful for both temporary testing worlds and long-term modpacks or multiplayer servers.
The common configuration file is:
acidglows_ingame_recipe_editor-common.tomlThe configuration allows server owners to control editor access and the required operator permission level.
NeoForge stores the configuration in the instance configuration directory and may also copy it into the world's serverconfig directory.
Install the matching NeoForge version of Acidglow's Ingame Recipe Editor in your mods folder.
For multiplayer use, the mod must be installed on:
Start the game or server once to generate the required configuration files.
Acidglow's Ingame Recipe Editor is designed to remove the repetitive work involved in managing recipes during development, testing, and gameplay.
Instead of stopping the server, editing JSON files, rebuilding datapacks, and reloading everything manually, common recipe-management tasks can be handled directly inside Minecraft.
Open it. Edit it. Save it. Keep playing.
Feel free to include Acidglow's Ingame Recipe Editor in both public and private modpacks.
No additional permission is required.
This mod is released under the MIT License.
You are free to use, modify, and redistribute the mod in accordance with the terms of the license.
