Glow My Teammates

Breaking Changes

• /teamglow on and /teamglow off are replaced by /teamglow toggle.
• Bare /teamglow config no longer prints the switch list — that output moved to /teamglow config list, and /teamglow config on its own now reports an incomplete command.
• Setting a switch gained an explicit verb: /teamglow config <switch> <value> is now /teamglow config set <switch> <value>.
• /teamglow status reports only the global on/off state; it no longer lists enabled teams or switch values.
• Permission nodes were consolidated: command.on / command.off → command.toggle, and command.team.add / .remove / .list → command.team. command.config is unchanged. Update any LuckPerms grants.
• /teamglow team list now requires OP 2; it used to be available to everyone.
• Minimum Fabric Loader is now 0.19.3 for 26.1, 26.2 and 26.3 (26.1 previously required 0.18.4). Minimum Fabric API is 0.155.3+26.1.2 (26.1), 0.157.0+26.2 (26.2) and 0.160.3+26.3 (26.3).

Added

• /teamglow config list — every switch with its current value.
• /teamglow config get <switch> — the current value of a single switch.
• /teamglow config reset <switch> — restore a switch to its default value.
• Support for Minecraft 26.3, built from the same codebase.

Changed

• Development builds now carry a -dev version suffix, so they cannot be mistaken for release jars.

Fixed

• /teamglow team add / /teamglow team remove suggestions now narrow as you type, matching vanilla's own team argument.
• Schema-1 config files with a null config object are repaired on load instead of being skipped.
• Hardened the locator-bar rebuild and non-player glow cleanup paths against stale levels and players disconnecting mid-cleanup.
• A config file that could not be read (temporarily locked, permission denied, unreadable disk) is no longer overwritten with defaults — the previous behavior destroyed a valid team list on a transient I/O error. The file is left untouched, defaults are used for the session, and every save is refused until a restart reads it successfully. The load path now distinguishes a read failure from a parse failure, so genuinely unparseable JSON, an empty file, or a literal null is still repaired on the spot as before.
• A config whose configVersion declares a newer major than this build understands now logs a warning at startup. Its fields are still parsed on a best-effort basis, but it is no longer silently rewritten as [1, 1] without a trace.
• A .tmp file orphaned by a save interrupted at the wrong moment (killed JVM, power loss) is removed once at startup instead of lingering in the world directory forever.
• The locator-bar rebuild drain is now bounded to a fixed number of rounds per tick, so a rebuild that keeps re-marking its dimension (another mod rewriting team membership from inside its own connection callbacks) can no longer spin the drain loop forever and wedge the tick. Reaching the cap defers the remainder to the next tick and logs it instead of dropping it.
• The LICENSE file is now actually bundled into the jar. Stonecutter builds each version as a subproject under versions/<mc>/, so the bare from("LICENSE") resolved to a nonexistent versions/<mc>/LICENSE and silently included nothing.

Performance

• Config-switch changes skip the locator-bar rebuild when the filter is inert.