Live Settings
Every important setting in AtomCombat can be changed without touching a YAML file or restarting the server — from an in-game menu or from a single command. Both paths write straight into the module's existing file, in place, so comments and formatting are never lost, and both trigger the same reload as /atomcombat reload.
The Settings GUI
Open with /atomcombat settings, or the Live settings button inside the Admin GUI. Permission: atomcombat.admin.
The main menu lists one item per module. Clicking one opens that module's settings page, where each row is a live value:
- Numbers — left click to increase, right click to decrease, by the step shown in the item's lore. Hold shift for a x10 step.
- Toggles — click to flip on/off.
- Cycles (like the active knockback profile) — left click for the next option, right click for the previous one.
Curated pages exist for Combat Core (knockback profile and the custom profile's values, shield blocking, sweep attack, attack timing), Combat Rules (combat tag duration, grace periods, PvP default, keep-inventory/experience), Bounties & Headhunter (amount limits, killstreak broadcast, every Headhunter Contract setting), Rank Abilities (each ability's cooldown, swap-hand trigger) and Effects (every particle/sound/firework toggle).
/atomcombat set and /atomcombat get
The GUI covers the settings admins tune most often. Everything else — any key in any module file, or in the root config.yml — is reachable with two commands:
/atomcombat set <module|config> <dotted.path> <value>
/atomcombat get <module|config> <dotted.path>Examples:
/atomcombat set combat-core knockback.profile custom
/atomcombat set combat-core knockback.profiles.custom.horizontal 0.45
/atomcombat set combat-rules combat-tag.duration-seconds 20
/atomcombat set bounties headhunter.interval-minutes 15
/atomcombat get bounties headhunter.minimum-streak<module> is one of combat-core, combat-rules, bounties, stats, rank-abilities, effects, announcements, or config for the root config.yml. <dotted.path> matches the YAML structure exactly as it appears in the file. set runs a full reload immediately after writing the value, the same as /atomcombat reload.
Tab-completion suggests module ids for the second argument, and — for modules with a curated Settings page — the known setting paths for the third.