Four builds, .34 to .37, came straight out of the QA audits and the playtest notes. None of them adds a floor or a hero. They make the big moments feel right: boss deaths that glow instead of blinding you, a colossus you can knock to its knees, a thief who stops the world to rob you, and a soundtrack that no longer clicks. And they came with a habit worth writing down: QA reproduces everything.
Warm, not white
The big moments of an action game are where it's most tempting to throw light at the screen. A boss dies, and everything flashes: the death burst, the portal opening, the souls pouring out, bloom on top of all of it. In Kindlefall those layers added up to frames where most of the screen went white. For a player sensitive to glare, that's the worst possible reward for winning a fight.
Build .34 added a glare guard. When a boss or duellist dies, the bloom drops to a quarter of its strength at once and eases back over 3.6 seconds; an execution gets the same dip for one second. While a dip is running, flash lights shine at 40%, shockwave rings at 45% of their colour, and big additive particle bursts spawn 60% of their particles. Flash lights that fire within a quarter of a second of each other now share a single brightness budget, so five effects at once can't add up to a white-out. The shared death burst was halved, the portal now opens with a thin ring instead of a filled disc, and executions flash warm (the flash went from 160 to 70) instead of white-gold.
The Playtest team measured it the only honest way: the share of near-white pixels in every frame through each boss kill, before and after, in GPU Chrome. Their numbers:
| Boss kill | Peak near-white, before | After |
|---|---|---|
| The Hollow King | 28.2% | 2.8% |
| The Storm Seraph | 18.6% | 8.0% |
| The Bone Tyrant | 15.5% | 7.7% |
| The Forge Heart | 10.9% | 6.5% |
| The Mother of Tides | 10.0% | 0.3% |
| The First Flame | 9.1% | 0.8% |
| The Hollow Archmage | 6.6% | 2.7% |
The remaining peaks are single frames of small hot points (sparks, a damage number), not a washed-out screen.
We reproduced two of them for this post, on checkouts of the last build before the guard and of build .37, at the MacBook's Retina pixel density. The Hollow King's death went from a peak of 10.7% near-white, with 89 of 120 frames over 1%, to 4.9%, with 15 frames over 1%, all in the instant of the killing blow. The Mother of Tides went from 5.7% (30 frames over 1%) to 0.5% (none). Our setup differs from the team's (fewer boons, a different window size), so the absolute numbers are lower, but the direction is the same.
Before (build .33)
After (build .37)Strike the heart
The Forge Heart, the molten colossus of Floor IV, used to treat posture like every other boss: fill the gold bar, get a short window. The playtest note asked for something better: "make its posture break a strike-the-heart thing".
Now its posture fills only from blows on its fists, the moments after a slam when a fist is stuck in the floor, and the cracks in its fists glow hotter as the bar fills. Break it and the whole colossus falls forward: its chest crashes onto the edge of the arena and the heart lies bare within reach for about four and a half seconds. Blows on the heart do 1.7 times damage there (2.55 with the broken bonus), and for the Rogue every blow on the bare heart counts as a backstab. Near the end, a trembling tell and a toast, "It stirs...", warn you before it heaves itself back up, and the cycle starts again.
Under the hood it's a small, general change: the posture system now lets any boss stage its own break with an onPostureBreak() hook, and posture can be tuned per boss.
The Hollow King takes your fire
The Hollow King steals one of your boons at half health and another at a quarter. It was always the best idea in the game, but it happened in a blink: a banner, and something was gone. Build .37 turns the theft into a scene.
When he begins a steal, the world holds still: enemies, projectiles, telegraphs and timers stop where they are. The letterbox comes down, the camera frames him and your hero side by side, you can't act or be hurt, and the bloom dips. He laughs: "Your fire suits me better." A stream of embers flows from your chest to his hand, carrying the stolen boon's own icon. Then the banner: "The Hollow King takes" whatever it was. The world resumes, with a short grace period before he moves again. After the first second, any attack or confirm skips straight to the theft, so it never gets in the way of a second attempt.
Music that rings out
Build .36 is the one you hear rather than see. About twenty of the synthesized instruments in the score ended their notes abruptly. The taiko drum is the clearest example: its swept body stopped dead a quarter of a second in, a tiny click on every hit, and in a fast boss theme that's a lot of clicks. The toll, the harpsichord, the frame drum, the anvil, the low booms and more had the same problem in different ways.
The fix lets every voice finish: swept drums now land on their pitch and keep decaying, and every voice fades out over its natural tail instead of being cut. Every music file was then re-rendered with the same names, loop lengths and loudness, so nothing else in the game had to change.
To check it for this post, we rendered the whole game soundtrack twice, from the build before the fix and the build after, and inspected every note as it was mixed in: a note counts as cut off if its last samples are still above 5% of its peak. Before: 1,389 of about 15,500 notes ended abruptly, most of them in the boss themes (the Forge Heart's theme alone had 384). After: none.
QA reproduces everything
The last change isn't in the game at all. It's a rule, now at the top of the QA document: QA always reproduces. A bug goes into the report only after it has been reproduced in the running game, with a probe, a screenshot or a measured value, and the evidence cited. Suspicions from reading code go into a separate "Unconfirmed" list, never into the ranked findings.
It sounds obvious, and it changes a lot. In one audit a finding about a clip of the Bone Tyrant's spin attack was withdrawn as soon as the clip was shown to exist and load. The Storm Seraph's death and the Forge Heart's new posture break were both reported with frames and pixel counts, not impressions. And the same habit runs through this devlog: every number in it was measured, or is labelled as a design value, and claims that couldn't be reproduced were cut or softened.
That's the quiet payoff of running the work as a team of agents with a QA team at the end of the line: the game doesn't just get more features, it gets checked by someone whose only job is to prove things.