A recipe offers "1 of 99" when it should allow fewer

99 is the cap for recipes whose costs never run out (only tools, or free). Stack limits should stop it sooner. Check that the item has a limit in VORP's items table, or set limit on the recipe. With Config.Debug = true, the server console shows how many stack limits were loaded on start.

Item [nil] does not exist in DB

A recipe with no output (an action) is fine. If you see this, check your recipes for ingredients or outputs written in the old VORP format, { name = "...", count = 1 }, instead of { item = "..." }. If it only appears when a particular item arrives in an inventory, another script is reacting to that item.

A weapon shows a plain name, or no image

Weapon names come from VORP's weapons config. On other frameworks, set label and image on the recipe.

Recipes added by another script disappear

They're lost when tr-crafting restarts. Register them on start: see For developers.