QoMC

# Qconf Over Minecraft Commands (QoMC) <center> <img alt="preview" src="https://raw.githubusercontent.com/AmberIsFrozen/qomc/refs/heads/main/assets/thumb.png"/></br> <i>pull the lever, qomc!</i><br/> </center> --- **QoMC** automatically generates config commands for Minecraft mods utilizing <a href="https://github.com/sisby-folk/kaleido-config">Kaleido Config</a> (JiJ-safe implementation of Quilt Config) ### THE POISON CHOSEN ESPECIALLY FOR KALEIDO. KALEIDO'S POISON. A (https://modrinth.com/collection/zZVgWFum) utilize the config library **Kaleido Config**, which is convenient as it works on all loaders and minecraft versions. Kaleido-based configurations generates `.toml` files in the game's config directory, but these can't be changed while the game is running. (https://modrinth.com/mod/mcqoy) solves this by auto-generating client-side configuration GUIs which allow you to edit the configs in-game. This is good for singleplayer and client-side mods, but unhelpful for servers, or other situations where you need to see the before/after effect without going into the GUI. QoMC addresses this by generating config commands instead! ### ...RIGHT. After installation, QoMC will detect mods making use of Kaleido on startup, and auto generate a command for them. By default, the commands is generated as `/<Mod ID>_config`, e.g. `/qomc_config`. For client-side config, they are generated as `/<MOD ID>_config_client`. For mods with multiple config files, QoMC will split the commands by config, e.g. `/qomc_config demo` and `/qomc_config main`. ### IN MY DEFENSE, YOUR POISONS ALL LOOK ALIKE For devs, QoMC integration is implicit - just use (https://github.com/sisby-folk/kaleido-config) for configuration, and relevant commands will appear when QoMC is installed.<br/> QoMC is a purely optional runtime dependency, so don't depend on QoMC in your buildscripts or mod metadata - only on modrinth / curseforge. If you've implemented your own config commands, you can disable discovery of your configs using a metadata key: In **fabric.mod.json**: ```json "custom": { "qomc:hidden": true } ``` Or in **neoforge.mods.toml**: ```toml hidden=true ``` To make QoMC recognize a config as client-side, simply name your config as `client`. ### HOW ABOUT DESSERT? This project is licensed under the LGPL 3.0 QoMC takes direct inspiration from (https://github.com/sisby-folk/mcqoy), its client-side GUI counterpart!