I have seen many mods want to make YACL an optional dependency so if the user decides they want to configure with a GUI, they can, if not, they will configure with the config file. This prevents the mod author from utilising YACL's config API, because it is in the same jar.
How it would work.
YACL would be split into two modules: gui and config. GUI would depend on the config module and the mod jar would publish with both modules.
Client-sided mods would depend on YACL like before, with both modules.
Server-sided mods would depend and include on YACL's config API, and depend on YACL's gui.
Other benefits.
This will also allow for #41 because split sourcesets will no longer be needed.
Why?
I have seen many mods want to make YACL an optional dependency so if the user decides they want to configure with a GUI, they can, if not, they will configure with the config file. This prevents the mod author from utilising YACL's config API, because it is in the same jar.
How it would work.
YACL would be split into two modules:
gui and config. GUI would depend on the config module and the mod jar would publish with both modules.Other benefits.
This will also allow for #41 because split sourcesets will no longer be needed.