Potentially use forge configs with a workaround to load them early
https://github.com/TelepathicGrunt/Bumblezone/blob/6bbcb628672a77cfa7a2648be9b4d2428d1eeeb7/neoforge/src/main/java/com/telepathicgrunt/the_bumblezone/configs/neoforge/BzConfigHandler.java#L22

If not, probably use YACL
https://modrinth.com/mod/yacl

might be neat to ‘port’ config screen stuff to use the (NEO)forge config system, and use it for more than just pack config

will be for 2.1 on 1.20.4

bvbvbaefoijvboijdsfv this is not going to be fun

might be good to split configs up, with a couple of files each for server, common and client

Possibly something around these lines:

• config/aether_redux/common/datapacks.toml
• config/aether_redux/common/common_setup.toml
• config/aether_redux/server/worldgen.toml
• config/aether_redux/server/gameplay.toml
• config/aether_redux/server/server_setup.toml
• config/aether_redux/client/mob_models.toml
• config/aether_redux/client/resource_pack.toml
• config/aether_redux/client/rendering.toml (maybe this instead of mob models)
• config/aether_redux/client/client_setup.toml

Closing, as this is stuff that should go into an existing checklist (and I’m pretty sure it is one - so this is probably redundant too)