Closed ghost closed 6 years ago
Is there a sure way to reproduce this, or does it happen randomly? I haven't observed this behavior.
Steps to reproduce: 1.Create a new minecraft 1.12 instance (forge 2680 and 2705 are the versions I have used in my test packs, probably not significant however) 2.Install COG 1.8.0 3.Create new singleplayer world 4.leave the world via the escape menu (do not exit the minecraft application, this resets the issue) 5.create new world with at least this COG option set via the GUI: -Vanilla coal:none (others may cause this too, I know iron:none does this) There is no loading percentage, you return right to the title screen if you were to set coal:none on the first world you have no issues generating, but coal still generates
The bug actually happens if you change any cog setting. Edit: It doesn't happen with the first world you edit. Only after editing and creating the first world and editing the second one it kicks you out.
Version: CustomOreGen 1.12-1.8.0
After setting the config to handle vanilla gen and setting iron and coal to "none" in the custom ore gen gui during world creation followed by clicking create world I am returned to the title screen.
There is no hard crash and nothing gets added to the log or debug log as a result of attempting to generate in this way.
Edit: This may be an issue with the vanilla config imported via CustomOreGen_Config_Default.xml or with changes made in the gui when no CustomOreGen_Config.xml is copied/created from the default. More testing will be needed. Edit 2: This might also be due to creating a world, exiting the world, and creating another with different settings. This also causes all settings to reset to the CustomOreGen_Config.xml after clicking exit to desktop (maybe an intended behavior?) when attempting to reload the client after this bug.