Most quark systems are dependent on the singular config file, which deletes all formatting and is really hard to read. In addition, if any string is mistyped, quark will crash on startup.

For example:

I suggest this current instance be moved to a tag. This will also enable adds modders to add support on their end without using mixins.

Some other things that it would be cool to make data drive include:

• Valid ancient tome enchantments (since there are enchantment tags now)
• Matrix enchanting candle influences
• Begoned enchantments
• Baked enchantments (a new data driven system would be nice with 1 json for each tool, that would be really cute and significantly easier to debug)
• Piston moving blacklists
• "Important enchantments" in automatic tool restock

This could make make modpack organization a lot more modular, and so that modpack devs don't have to maintain a 100KB toml file.

ive been wanting to do this..
as of now the phylosophy has been to make all user facing stuff config and modder facing ones tag.
I thing this has worked in the past and remains true now too but a lot less so since the tag datapack system is used widely in mods and users are a lot more used to it

Chain moving being based on tags would be awesome, many modded chains don't work pistons and it's annoying

Instead of making these options entirely tag-driven I think it would be best to allow mixing tag IDs and block IDs in them. That way if you want to make a tag for your modpack, you can do that and put your tag in the config file, and users won't lose the ability to conveniently add things through the config GUI / configure clientside-only options

minor thing but it would be nice to have a built-in tag in the list so people don't have to choice paralysis about what to call the tag :))