Closed Oblomov closed 3 years ago
Right, I was trying to mimick the previous changelog entries 8-)
I'm actually having a bit of a second thought about this change. Since we're doing this “override productivity” for multiple things, I've been thinking that refactoring the code that I've now used for rails so that it can be used for all overrides would be nicer. I'll look into that.
OK, refactored the whole “override production” thing, and ported all overloads to the new mechanism.
@Oblomov Is this good to merge now? :slightly_smiling_face:
If you're happy with it, I'm happy with it. We can think about providing some kind of API at a later time, possibly with more stuff 8-)
This replaces the override for the obsolete rail recipe with an override for the new recipes for all rail types. Rather than hard-coding the recipes, we “reconstruct” the declared crafting recipes and simply pump up the amount produced by 50% (which was the increase achieved over the old recipe).
Fixes #162.