More Beacon Colors configuration

Four settings. showButton is read on the client, allowAnimated on the server.

The file

After the first launch with the mod installed, you will find config/morebeaconcolors.json next to your other configs (in .minecraft/config for the default launcher, in config on a server). It looks like this:

{
  "enabled": true,
  "showButton": true,
  "allowAnimated": true,
  "debug": false
}

The colors themselves are not in this file; see where colors are saved below.

Settings

Key	Default	What it does
`enabled`	`true`	Master switch. On a server, `false` refuses new colors (players get a message). Saved colors are kept.
`showButton`	`true`	Show the color button on the beacon screen. Client setting: turn it off if another mod puts something in the same corner.
`allowAnimated`	`true`	Allow Rainbow, Color cycle and Pulse beams. Server setting: with `false`, players can still pick solid colors and gradients.
`debug`	`false`	Write color changes, syncing and clean-ups to the game log (lines tagged `[debug]`). Handy when reporting a problem; leave it off otherwise.

Changing settings

You have four options, pick whichever is closest:

Edit the file with the game or server stopped, then start it. Simple and foolproof.
Edit the file and reload live with /mycel reload morebeaconcolors. No restart needed. See commands.
Change it live with a command, e.g. /mycel set morebeaconcolors allowAnimated false (needs operator permission; /mycel get morebeaconcolors shows every value).
Use the config screen from the mod list (Forge and NeoForge). Same four settings, with reset buttons.

Where colors are saved

<world>/data/morebeaconcolors.json on the server (or in your singleplayer save): one entry per colored beacon with its dimension, position, style, speed and colors as #RRGGBB. Plain JSON, so you can back it up or edit it by hand with the server stopped. Saves are atomic: a crash never leaves half a file.
config/morebeaconcolors-local.json on your client: colors you picked on servers without the mod, per server address.

Broken file?

If config/morebeaconcolors.json gets mangled, the mod logs a warning and falls back to defaults rather than crashing. If the world's morebeaconcolors.json no longer parses, it is kept next to the new one as morebeaconcolors.json.broken and the beacons start out vanilla, so you can fix the file and put it back.