Oredict meats for intermod compatibility #1
Description
Is your feature request related to a problem? Please describe.
I use Harvestcraft, which adds extensive food recipes. Many of these recipes call for animal meats but the slaughtercraft meats cannot be used.
Describe the solution you'd like
Harvestcraft uses the ore dictionary heavily in its recipes. Putting the Slaughtercraft meats in the correct ore dictionary entries will allow Harvestcraft to use the meats (along with other mods that use the same ore dictionary entries). The benefit of this solution is that this solution is not actually dependent on other mods, so no conditional object loading is required.
Describe alternatives you've considered
The only alternative I can think of is crafting recipes to turn your meats into vanilla meats. This is probably useful as well, for broader compatibility, but using the meats directly feels like it would be best for Harvestcraft.
Additional context
The ore dictionary entries are
- listAllmeatraw
- listAllbeefraw
- listAllporkraw
- listAllmuttonraw
- listAllchickenraw
- foodCalamariraw
and then of course the cooked meats
- listAllmeatcooked
- listAllbeefcooked
- listAllmuttoncooked
- listAllporkcooked
- listAllchickencooked
- foodCalamaricooked
Specific meats (the cow parts for example) should be double registered under the generic meat as well as the specific meat. For example the raw cow leg should be registered as ore:listAllmeatraw and also as ore:listAllbeefraw.
The meats that Harvestcraft does not have specific registries for should be registered under the generic (raw llama as ore:listAllmeatraw) and I recommend following the same naming convention and registering them under a specific name (eg ore:listAllllamaraw).
I would go with using plain animal names for the new lists (listAllllamaraw, listAllhorseraw, listAllmuleraw, listAlldonkeyraw) - English doesn't have separate names for the flesh of these animals vs the animal itself.