Minecraft 1.18.2 nickel and silver aren't spawning
RevoluPowered opened this issue ยท 9 comments
Important ores are missing from the game in singleplayer and multiplayer
So far I've found silver and nickel aren't spawning.
Versions & Modlist
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver was corrected from null to its default, SimpleCommentedConfig:{}.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver.distribution was corrected from null to its default, TRAPEZOID.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver.air_exposure was corrected from null to its default, 0.25.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver.vein_size was corrected from null to its default, 9.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver.min_y was corrected from null to its default, -48.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver.max_y was corrected from null to its default, 32.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver.attempts_per_chunk was corrected from null to its default, 6.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.silver.retrogen_enable was corrected from null to its default, false.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel was corrected from null to its default, SimpleCommentedConfig:{}.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel.distribution was corrected from null to its default, UNIFORM.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel.air_exposure was corrected from null to its default, 0.0.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel.vein_size was corrected from null to its default, 5.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel.min_y was corrected from null to its default, -64.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel.max_y was corrected from null to its default, 24.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel.attempts_per_chunk was corrected from null to its default, 7.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.nickel.retrogen_enable was corrected from null to its default, false.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel was corrected from null to its default, SimpleCommentedConfig:{}.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel.distribution was corrected from null to its default, TRAPEZOID.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel.air_exposure was corrected from null to its default, 0.0.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel.vein_size was corrected from null to its default, 6.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel.min_y was corrected from null to its default, -120.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel.max_y was corrected from null to its default, -8.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel.attempts_per_chunk was corrected from null to its default, 8.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.deep_nickel.retrogen_enable was corrected from null to its default, false.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.uranium was corrected from null to its default, SimpleCommentedConfig:{}.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.uranium.distribution was corrected from null to its default, TRAPEZOID.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.uranium.air_exposure was corrected from null to its default, 0.5.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.uranium.vein_size was corrected from null to its default, 4.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.uranium.min_y was corrected from null to its default, -64.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ores.uranium.max_y was corrected from null to its default, -16.
[19:10:59] [Server thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key ```
Seems forge modified some syntax in 1.18.2
just noticed botania is duplicated, I will try with botiana de-duplicated - nope same issue
Okay, what's your proof that it's a bug, lol?
They spawn fine for me. There is literally zero evidence here.
Okay, what's your proof that it's a bug, lol?
They spawn fine for me. There is literally zero evidence here.
So, we tested on our server for a couple of weeks and have not encountered it.
JEI + JER shows the ore, but the item won't open up the prompt like it normally does when you click it, the console server errors also seem to indicate something is broken with nickel.
Did some digging the bug with JER is just unable to show the ore gen. I think better to close, found nickel like at 10000, 25 10000 from spawn, I'll test again with all the mods enabled to confirm
For future reference: the ranges on which ores spawn is also detailed in the manual ;)
Did some digging the bug with JER is just unable to show the ore gen. I think better to close, found nickel like at 10000, 25 10000 from spawn, I'll test again with all the mods enabled to confirm
isn't JER doing a check on a limited range of chunks for ore presence to calculate the graphs? maybe it is not simulating but using exisiting data and you have no ore in those chunks since the time when loading regenerated the config?
You can run this to generate the ore distribution but some ores pre-supply the information somehow I think JER+JEI has an API to pre-register iron ore without the json file
