An easy to use config api. Just some straight forward file io, probably an json5 format or so. An Gui for setting would be nice, but not necessary. A optional way to sync the config from server to client would be an neat addition for some mods too.

Retracted my previous comment since my stance on this has changed a bit since then. First off, 1.16 is not really viable for major features such as this before, and in addition to that, we have since had quite a few discussions about how we could possibly go about adding a config library into Architectury without making it too much of a bloated mess (or a nightmare to maintain like Cloth has become), and the truth of the matter is — it's just not that easy to find something that works well for everybody and has all the features someone could wish for, and creating it from scratch at this point also just seems like too much of a time sink to really be worth the trouble for the time being :P

I won't be closing this issue since I still want to express some form of interest into at least creating some cross-platform config library, whether in Architectury, as an external dep or as some kind of "Architectury Extras" project like the one we'd discussed on Discord a couple of months ago, but I'll still at least "symbolically" lower its priority to indicate there are no active plans to work on this in the near future ourselves.

So some quick notes on this, mostly originally taken from Discord:

Originally, Cloth was supposed to be the de-facto cross-platform config mod, but seeing as

• it's an external dependency
• it's far from finished
• it handles things like server configs, config sync, etc. rather pooly
• dan hasn't had the time to patch it up for a while now

we probably want to go for our own solution.
Since @LatvianModder needs a Config API for the FTB Suite anyways, I wanted to involve him in this perhaps unless he tries to implement weird formats like SNBT again (stop)

Either way, bumped the priority of this to medium since we know of mods where this would be immediately useful to have now.

We should probably have a short discussion about which version to target with potential pull requests down the line, personally, I'm aiming for 1.16 as it seems to be easier to port features forward rather than back