Open TheCodedOne opened 4 years ago
These should be aimed at bulk creation rather than fine customization via code then.
There's different options possible :
What options would be acceptable ?
One data generator that could be useful would be for translating vanilla recipes in our own to use the more advanced resource features.
my thought is that they always generate to a “generated” directory & used a gradle plugin, so they couldn’t be used at runtime.
We also shouldn't need to overwrite vanilla recipes in this circumstance as the way the resource system works is it only allows 1 to be registered, vanilla would always be there & as such modded iron ingot couldn't exist, so no need to translate.
We also shouldn't need to overwrite vanilla recipes in this circumstance as the way the resource system works is it only allows 1 to be registered, vanilla would always be there & as such modded iron ingot couldn't exist, so no need to translate.
I was thinking more for the work of porting mods. You don't want to rewrite your 23654 json recipes from using mc tags to the resources system. Is there some doc on the resource system ? Could help to know how all of this should be done
The resource system is still in dev, no docs have been made.
The resource system is still in dev, no docs have been made.
Btw, a design proposal can serve as base for writing docs :wesmart:
With a lot of resources being JSON data, it would be helpful to allow modders to provide most of the data in-code which automatically generates the respective JSON for them.
The API should contain: