Describe the Bug:
Versions 2.3.0 and 2.3.1 do not generate or pay attention to any config files, and trying to modify configs via the menu causes a crash.
(Presence of 2.2.0 config files leads to the same exact results, so it doesn't matter if there are config files present, it's just flat out ignoring them)

Note: The spawnrates config stuff still generates and works, but seeing as that's an entirely different format I'm assuming those systems aren't even connected with the same system, so I'm just saying there's no config files to keep things simple based off of what I've observed

How to Reproduce:

1. Make a completely empty new minecraft instance running forge for 1.16.5 with this mod installed, the bug happens regardless of forge version or what other mods are installed.
2. Launch the game
3. Go to the config folder and observe the lack of any infernal expansion config files
4. Attempt to use the mod's custom config menu and watch your game crash the moment it tries to save anything

Expected Behavior:
Config files being created and/or used

Version Information:

• Operating System: Windows 10
• Mod Version: 2.3.1 (also 2.3.0)
• Minecraft Version: 1.16.5
• Forge Version: 36.2.4
• Other mods that were running when the crash happened: Nothing, just forge and infernal expansion.

Additional Context:
Here's a debug log where I launch forge 36.2.4 for 1.16.5 with only infernal expansion 2.3.1 and nothing else installed, open the mod's config menu, and then attempt to close the menu, leading to a crash: debug.log
(This is the only crash I found that results from this bug)