Switch away from Cloth Config.

[melontini]

ATM Cloth Config support is incredibly hacky. I basically rewrote AutoConfig to support my custom wrappers and what-not.

While CC constantly updates, I find the API and screen gen design very convoluted. It has great ideas, but they are limited.

Many other projects also felt the same way, and now there's a plethora of Cloth alternatives. The upsides and downsides only apply to Andromeda, don't take them personally.

Fzzy Config

Seems like a good option for most configs, but I feel it does not fit Andromeda's needs.

Upsides:

• Automatic config GUIs.
• Config command.

Downsides:

• Doesn't support all MC versions Andromeda is on.
• "Automatic serialization to TOML"
• I couldn't understand the wiki.
• Doesn't seem to support complex objects.

YACL

Great, feature complete option.

Upsides:

• Good looking GUI.
• Easy API.

Downsides:

• No automatic config GUIs. (Has to implemented myself)
• Doesn't support complex objects.
• Major breaking changes between 1.19.2-1.20.1

Custom solution

I've been messing around with making my own config screen builder + generator. A combo of Cloth and YACL.

Upsides:

• As flexible as I wish it to be.
• Gson-like GUI providers (A GUI provider factory produces a GUI provider with type annotations passed as parameters)

Downsides:

• Pain in the ass to maintain.
• I'm not very smart.

Stay on Cloth

Upsides:

• 0 time spent on switching.

Downsides:

• Have to rely on terrible hacks.