Ex deorum appears to be incompatible with skyblock builder. If you have both installed with a void world enabled in the config then you overwrite and set the world to void world when we would want it to be a Skyblockbuilder world. Disabling the void world setting forces the world type to default to a regular world setup and both settings override the forge-common.toml settings.

You appear to be correct. Thank you for testing.

I believe you are incorrect. While the file isn't created by default it certainly functions exactly as the documentation outline. Furthermore if you do a quick github search for forge-common.toml you will find that every skyblock uses that file to set their defaults. Thank you for amending the config.

It doesn't actually function, I just tried it without Ex Deorum. I also double-checked in Fantasy Skies, which uses Skyblock Builder, and they don't have the forge-common.toml file either.

Skyblock Builder's documentation is incorrect. There is no such thing as forge-common.toml—go into a fresh instance of Forge, you'll see. I can add an option to Ex Deorum to specify what the default world type should be, instead of just a true/false.

I think I'm just going to make Ex Deorum override the world type to use Skyblock Builder whenever that mod is installed, since that's the whole reason people install it anyway.