-
Notifications
You must be signed in to change notification settings - Fork 2
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
JER doesn't show custom ores in JEI #16
Comments
You seem to be using an extended world height - some entries like minecraft:mossy_stone_brick_slab go up to index 380 (which is something like a height of 324). JER doesn't support this, and will raise an error like this one:
This isn't really something I can fix, as it's fundamentally a limitation of JER's format. I could in theory generate world-gen.json files for such worlds that would be valid, but that'd mean discarding all the data above y=256. Interestingly enough, if I replicate your setup (including EMI), I don't get the error in question (I only do when I disable EMI). Probably EMI breaks JER's intergration and so it never ends up even trying to load the file. |
This is very similar to issue #11, except there the issue was that some worlds can go below -64, and here the issue is that some worlds can go above 256. Guess I can handle it the same way - discard all the data that JER can't show and print a warning about it. |
Should be fixed in 0.3.6, in the sense that the generated world-gen.json will omit heights above 255 and thereby be compatible with JER. |
This seems like a different issue - please elaborate if you're still experiencing it. I don't spot anything missing on a cursory glance. |
Modded ores that got scanned don't show up in "world gen" in JEI in game.
It also misses some modded ores like Immersive engineering ores in the worldgen file.
Versions:
World Gen .json File (put in /config folder of modpack)
world-gen.json
The text was updated successfully, but these errors were encountered: