Currently the Fabric version of AppleSkin uses autoconfig + clothconfig for its config file and mod menu config screen integration. This works fine, but it means that AppleSkin includes a copy of Cloth as a jar-in-jar, which accounts for most of the size of the AppleSkin jar (1.1MiB jar with cloth, 76.7KiB without it).
Configured, instead, works more like ModMenu, where it automatically generates mod config screens for supported configs and is installed separately. For the NeoForge/Forge versions of AppleSkin, Configured works out-of-the-box.
However, to use Configured on Fabric, AFAICT AppleSkin would need to either:
Use a supported config system; it lists Framework or JEI
Not a fan of this option, as it'd mean taking on a (different) dependency that we'd likely have to include in the AppleSkin jar
Currently the Fabric version of AppleSkin uses autoconfig + clothconfig for its config file and mod menu config screen integration. This works fine, but it means that AppleSkin includes a copy of Cloth as a jar-in-jar, which accounts for most of the size of the AppleSkin jar (1.1MiB jar with cloth, 76.7KiB without it).
Configured, instead, works more like ModMenu, where it automatically generates mod config screens for supported configs and is installed separately. For the NeoForge/Forge versions of AppleSkin, Configured works out-of-the-box.
However, to use Configured on Fabric, AFAICT AppleSkin would need to either:
Just something to consider.
Other notes: