"Polish" usually means visual work — particle effects, screen shake, the satisfying crunch of a good hit. That's not what this sprint is about. This sprint is behavioral polish: fixing the places where the elemental interaction system works mathematically but doesn't feel like it works.
The clearest example: when a Catalyst player triggers Fracture Burst before the Anchor has fully built the resonance bar, the burst fires at partial power. That's intentional — partial bar, partial burst. The problem is there's no feedback to either player that it fired early. The numbers are smaller, the visual is identical, and nobody knows why the combo didn't hit as hard. That's not a math problem. It's a feel problem. And feel problems are what this sprint exists to fix.
Three Fixes in Progress
Resonance bar feedback. We're adding a visual "lock" indicator that appears at 80% fill — a distinct glow state on the bar itself, plus a brief screen-edge pulse that both the Anchor and Catalyst can see. There'll also be an audio cue at the lock threshold, different from the ambient sound the bar makes while filling. The goal: Fracture Burst should feel like a decision. Right now it feels like a discovery — you fire it and find out after whether the timing was right. That's backwards. The lock indicator puts the information in front of the Catalyst before they commit, so triggering the burst at the right moment is intentional, not accidental.
Combo chaining — role clarity. Weaver's Threadmark debuff wasn't stacking correctly when a Striker followed up within the same elemental window. The debuff was being applied — we could see the buff icon — but the elemental window timer was resetting instead of extending. Which meant a Striker following up quickly would actually shrink the window for the third chain rather than sustain it. The timer logic is fixed. Threadmark now stacks up to 3× within a 4-second window before decaying, and each Striker follow-up within that window extends the timer rather than restarting it. The Weaver/Striker chain now rewards quick succession the way it was designed to.
Elemental persistence on terrain. Catalyst's Verdant Attunement ability leaves elemental zones on terrain surfaces. Those zones are supposed to decay — but they were lingering past 12 seconds in practice, which was causing unexpected resonance triggers for an Anchor entering the zone after the Catalyst had already moved on. The Anchor would step into what looked like cleared terrain and get pulled into a resonance build they didn't initiate. We've added a hard decay cap at 8 seconds. More importantly, the zone visually fades from 6–8 seconds so players can see it expiring rather than just having it disappear. That fade window gives both players the information they need to decide whether the zone is still useful.
What's Not Fixed Yet
Honesty check: the Striker/Weaver combo chain still has an edge case. If a third chained ability fires in under 2 seconds from the second, it occasionally triggers the burst suppression flag incorrectly — the system reads it as a burst attempt rather than a chain continuation and suppresses what should be a valid third hit. It's rare. It's reproducible. We've seen it happen maybe a dozen times across hours of test sessions.
We're not shipping a workaround. Increasing the suppression window would paper over the symptom while leaving the root cause intact, and it would penalize fast Striker play in the process. We're fixing the flag logic directly in the next sprint. It goes on the board as a known issue in the meantime.
Why Polish Before Alpha
Alpha testers form their first impression of the combat system inside the first ten minutes. If Fracture Burst fires at the wrong moment with no feedback, that impression is "the combat is inconsistent" — and that's hard to undo. Fixing the feel layer now means Alpha feedback will be about the design, not the implementation. We want testers asking "should the resonance window be longer?" not "why did that burst feel weak?" The former is useful design feedback. The latter is a bug report that tells us something we already know.
What's Next
Next devlog: the first zone enemies. The Ashveil Watchers — their patrol AI, how they respond to elemental anomalies in the fog, and why we designed them as a teaching enemy rather than a tutorial popup enemy. There's a philosophy behind that distinction that shapes how every enemy in the game is going to work. Next post is where we get into it.
If you want in for Alpha access, the Founder's Pack is still open.