RecipeAdvanced

Fixed

• Saving a recipe stalled the server. Pressing save in the editor rebuilt the whole vanilla registry: every recipe the plugin owns taken out of the server and put back, to publish a change to one of them. The server runs its own finalizeRecipeLoading inside every addRecipe, rebuilding ingredient tables and reloading advancement data for every player online, so the real cost was one full reload per recipe on the list — a server with sixty of them dropped to 17 TPS on every save. Only the saved recipe is re-registered now, so a save costs the same whether the server has five recipes or five hundred. Deleting one takes it back out of the server too, which it never did: a deleted recipe used to stay craftable until a restart.
• The recipe tree scattered a set of armour. Entries were ordered by the name on the item, which groups another plugin's sets but not your own: you name a recipe hunter_helmet, the tile says «Diamond Helmet» or puts the set word last, and the set ends up spread the length of the page. This plugin's own recipes are ordered by their id now, which is where you put the grouping; everyone else's still by the name on the item, which is where theirs is.
• A recipe switched off by an admin came back on every restart. The removals were made while plugins were enabling and did not last: another plugin finishes its own startup a few seconds later, rebuilds the recipe registry from the data packs, and takes every disabled recipe back out of the bin with it. Measured on a server with CraftEngine — gone at enable, still gone when the server announced it was ready, back half a minute after that — and only /ra reload, run late enough, made it stick. The removals are re-asserted now if anything undoes them, so no reload is needed.