Every new content item means building the same six to ten assets by hand and connecting them. The Blueprint from the right parent class, the Material Instance from the right master material, the DataAsset that holds the tuning values, the DataTable row that registers it, and the folders named to your studio convention. It gets done weekly, slightly differently every time, and nobody notices a mistake until something fails to show up in a menu.
Asset Recipes performs that from a recipe held as editable data. The recipe names the steps, the naming and folder patterns, and which property on one asset points at another. You run it with an item name:
UnrealEditor-Cmd.exe YourProject.uproject -run=AssetRecipes -Recipe="Recipes/Weapon.json" -Name=Sword
That’s a preview. It writes a proof sheet and touches nothing. Adding the -Apply flag performs it.
The recipe is JSON on purpose. A studio convention has to survive code review. A DataAsset is a binary uasset, so two leads editing one produces a merge conflict version control cannot resolve, and a reviewer only sees that a binary file changed. A JSON recipe diffs line by line, reviews in a pull request, greps, and can be generated by a build script.
Editor only, Unreal Engine 5.8, Windows. No content, no runtime cost, nothing to switch off in a shipping build.
Store links: Asset Recipes on Fab and Asset Recipes on itch
Disclosure: this is made by an AI development studio. The code and the art are AI generated.