Provide some way to select which recipes should be overloaded

[Oblomov]

With the changes introduced by #169 we have a very powerful mechanism to manipulate existing recipes. One could argue that this is a bit too powerful, since the mechanism currently is applied to all recipes that provide a specific items. This can be somewhat game-breaking for items that can be converted back into their raw material, as exemplified by the case (that was also causing a crash) presented in #170: there's a recipe to produce ehlphabet:block 8 from 8 default:paper, and a recipe to convert back each ehlphabet:block into a default:paper: with moreblocks redefinitions, the “back to the raw material” craft is pumped up, meaning you can go through ehlphabet:block to produce extra paper.

Considering that we may want to expose the “production increasing” function as an API, we should consider a way to make it possible to be more restrictive on when the amount change should be put in effect. The specific example can be avoided by skipping shapeless recipes (since the recipes we intend to override are shaped anyway), but a more general (and robust) mechanism should be devised for API purposes.

[BuckarooBanzay]

One could argue that this is a bit too powerful, since the mechanism currently is applied to all recipes that provide a specific items.

This messes with a lot of mods, just fyi, here farming for example:

yield was 4 before, 12 afterwards

Instead of a blacklist, can't you just do a inclusion/whitelist to include only those that need to be redefined?

[Oblomov]

Well, the whole point of the change that introduced this issue was to not having to keep the recipes up-to-date whenever they changed in MTG. Whitelisting kind of defeats that. Ideally we'd want some way to know where a recipe comes from, so that e.g. we only override the ones defined in default, but that's not easy. I'm open to suggestions on the best way to balance the things.

(As an aside, I'm not sure I would consider the pumping-up of the farming recipe a bug, since it is in the same spirit as the override of the papyrus recipe from MTG, but of course that's subjective.)

[Calinou]

We can probably remove the crafting recipe overrides we currently have in More Blocks. Now that Minetest Game balancing is more fair, it doesn't make as much sense to have built-in recipe overrides.

[Oblomov]

Hm I can see the point for the signs (the 4 was probably inherited from a time where the default recipe was for a single sign) and for the rails, but the paper from papyrus one is still 4 vs 1. And it's also the one creating problems with the other mods.

[fluxionary]

191 entirely removes the recipe overrides. such a feature is not within the bailiwick of this mod(pack).