Scope cut to state only — soul pool vs capacity vs threshold, fury, and the two
reaction procs. Rotation knowledge (dump before meta, star-hold, dot upkeep) and anything the CDM
already shows (cooldowns, buff icons) are deliberately absent. Same hard moment everywhere:
Soulburst just procced · VM 28/35 · 9 souls, capacity 10 (MoC) → 37 crosses the 35 threshold ·
RT would overcap (9 > 8) · fury 96/140. Correct read: SPEND, then REAP ▸ META, don't press RT.
EXACT — plain data, 12.1-safeDISPLAY — C++ renders, we positionWHITELIST — soul-count element, pending the SF flag
01
One object
everything fuses into the existing bar — the reaction is its left cap, fury its under-rail
SPENDSoulburst
28+9 ▸ META
one anchor point, one glance line — the ember slice past the RT notch IS the "don't press RT"VM fill · ticks · furySPEND cap = AuraButton childsoul segment
02
Split gauges
the pool gets its own fixed 10-cell scale — nothing moves its origin, every boundary is a landmark
SPEND
Soulburst · then reap ▸ meta
SOULS 9reap 4RT ≤8cap 10
28+9 ▸ 35
cells read at a count-glance; the 9th cell going ember = RT bait caughtprogress · fury · boundarieschipcell fill
03
Radial minimal
arcs at the character, zero eye travel — pool left, progress right, fury topping the ring
SPEND
9/10 ▸ meta
peripheral by design — arcs read without focusing; needs the 12.1 radial API (secrets OK)progress + fury arcshalo + wordpool arc + count
04
Typographic
no gauges at all — the state as one legible sentence, sized by urgency
SPEND
9/10 · 28+9 → 37 ▸ META · RT FULL
96
for number-readers — everything is text, so the 12.1 fallback (Blizzard-rendered count) drops in seamlesslyprogress math · furywordthe 9 and the sentence logic