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

Question regarding Custom Ore Generation #32

Open
Dulciphi opened this issue Jul 15, 2018 · 1 comment
Open

Question regarding Custom Ore Generation #32

Dulciphi opened this issue Jul 15, 2018 · 1 comment

Comments

@Dulciphi
Copy link

Hi. I tried running COG and UBC and found that none of the generated ores were UBified. UBify ores was definitely checked in the config. It seemed as though COG was loading later than UBC in the different stages of chunk generation.

Is this a known issue or something that is capable of being addressed?

I seem to remember there being a config option in previous versions of UBC that would force it to run as late as possible. Is it possible to get an option like that back?

2018-07-15_02 10 20

@LemADEC
Copy link

LemADEC commented Aug 12, 2018

CoG used to explicity call UB redoOres() after its generation on 1.7.10. As such, even if you regenerated the ores, it would still be ubified. There's probably an API incompatibility here.

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