-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config Custom Ore #27
Comments
Right, how about a list of block name + property values, e.g. |
As long as the property value is optional that would be perfect (some of the Geolosys ores can drop several kinds of Ore (ex: Lead/Silver) so they couldnt be "assigned" to an existing oreDict ore. |
Yeah, properties would be optional of course. Cool, I'll get to it then. |
Just a small note: MetaData could be important in some cases |
That's what the properties are for. They're just metadata in readable form. |
Sure, makes sense |
Custom Ores cant be added to the Ore filters
Geolosys adds Ores, that cant be added to the oreDict, a config option, that allows to add non oredict Ores to your filters would alleviate that problem.
The text was updated successfully, but these errors were encountered: