Flags¶
For: advanced users sharing state between lines.
Flags are variables command lines share: match-wide, per-player, per-role, or run-only. The one-line forms live in the cheatsheet.
Flags are variables commands can share. Omit the value to read, pass
one to write; writes return nothing, and reads of unset flags yield
null, which pairs with <default> for fallbacks.
<default:<pflag:cooldown>,0> reads 0 until the flag is set; any
blank or case-blind null value falls back, anything else passes
through. Names match exactly and may hold spaces inside quotes.
| Tag | Scope | Lifetime |
|---|---|---|
<gflag:name,value> |
Whole match | Dies with the match. |
<pflag:name,value> |
Executing player (-CONSOLE for console lists) |
Flushed when the player leaves, is eliminated, or disconnects for good; dies with the match. |
<rflag:role,name,value> |
Named role (hunter, speedrunner, or ALL) |
Dies with the match; player removal leaves role flags alone. |
<lflag:name,value> |
This run only | Set in an early line, read in a later line, discarded after. |
<default:value,fallback> |
One expression | Instant: falls back on blank or null. |
<lf>, <pf>, and <gf> are short aliases for <lflag>,
<pflag>, and <gflag>; they behave identically everywhere,
including flag references and the tag cheatsheet.
<pflag:"cooldown",<gstat:"duration">> stamps a cooldown;
<pflag:"cooldown"> reads it back. <rflag> names its role up
front: <rflag:hunter,boost> and <rflag:speedrunner,boost> keep
independent values under the same name. The role is hunter,
speedrunner, or ALL (any case). ALL fans a set out to both
roles and reads back the shared value, or null when the two sides
disagree. Anything else warns, reads null, and skips writes. Role
flags need no executor, so console lists can use them too.
Flags are modifier-agnostic on purpose: any modifier can read what
another wrote. For a strictly private flag, namespace the name with
<id>: lastuse-<id> can only collide with itself. Flags live in
memory: a reload or restart wipes them.