Issue Description:

There is a rather strange incompatibility with Aether II on the most recent versions as of 12/12/2018
Most recent versions of all things involved used

When you attempt to create a new world with the Biomes O' Plenty world type, the game will, instead of getting the world, get stuck on a screen that looks like this: http://prntscr.com/ltx2rn

The only way out is to close it out manually using the X, because it doesn't count as not responding. Usually the launcher would say the game crashed, however what happens in this case is much more strange: Every program will act as if Minecraft is still open, even though its been closed. The launcher will say the games already running, modifying files in the directory will say its being used in Java TM Platform binary, even though the game is closed. I checked the task manager and it doesn't show up there either. The only way to fix it is to restart your computer!
Because of the lack of a crash report, I cant send any technical information other than the screenshot. I also double checked, and it wasn't Orbis API either, (A mod that is required for Aether II to work)

Steps to reproduce:

1. Install Orbis API (Dependancy of Aether II), Biomes O Plenty, and Aether II.
2. Run minecraft
3. Attempt to create a Biomes O Plenty type world.

Additional Information:

• fml-client-latest.log or fml-server-latest.log:
  debug.log
  latest.log

• Screenshots: http://prntscr.com/ltx2rn

Affected Versions (Exact numbers, do NOT use "latest"):

• Biomes O' Plenty: 1.12.2-7.0.1.2419-universal
• Minecraft: 1.12.2
• Forge: 1.12.2-forge1.12.2-14.23.5.2768
• Orbis API: orbis_api-1.12.2-1.1.12a
• Aether II: aether_ii-1.12.2-1.1.12

EDIT: It wasn't showing on task manager because i had it set to fewer details. Setting it to more details had Minecraft (Java TM Platform Binary) show up. Ending the task results in everything updating that minecraft is not open, however no crash report is made. This is also when i recovered Latest and Debug .log files.

There's nothing in the stacktrace that suggest this has anything to do with BOP. I don't even think they'd have compatibility for anything with us, but maybe we changed something and it's breaking some sort of integration they have for BOP? Either way, you're going to need to send this to them, because BOP doesn't appear in the stacktrace at all, so it's out of our hands.