Skip to content
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

Closed
RainbowSaber opened this issue Aug 24, 2017 · 6 comments
Closed

Config Custom Ore #27

RainbowSaber opened this issue Aug 24, 2017 · 6 comments

Comments

@RainbowSaber
Copy link

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.

@fnuecke
Copy link
Member

fnuecke commented Aug 24, 2017

Right, how about a list of block name + property values, e.g. ic2:ore[type=copper], that would work, yes?

@RainbowSaber
Copy link
Author

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.

@fnuecke
Copy link
Member

fnuecke commented Aug 24, 2017

Yeah, properties would be optional of course. Cool, I'll get to it then.

@RainbowSaber
Copy link
Author

Just a small note: MetaData could be important in some cases

@fnuecke
Copy link
Member

fnuecke commented Aug 24, 2017

That's what the properties are for. They're just metadata in readable form.

@RainbowSaber
Copy link
Author

Sure, makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants