One hotfix, two bugs, both inherited from v0.38.0. The serious one hit the raid: the three wardstones in the Nythraxis arena were invisible to just about everyone — and they are the only thing that stops Deathless Rage. The second turned the whole screen black on high graphics settings on some machines. No combat value, no item, no data changes.
Released August 16, 2026Since v0.38.12 fixes
💡 Click a card for details.
01Nythraxis: your wardstones are back
If your raid stopped seeing the arena stones after v0.38.0 and took Deathless Rage to the face with nothing to do about it: that was not new difficulty, it was a bug. It is fixed.
What was happening Fixed
The three arena stones share their item with an old zone 2 quest, The Sunken Bastion. Since v0.38.0 the game hides quest collectables from anyone not currently on the quest — so from everyone who finished it or never took it. No stone, no minimap mark, nothing to interact with.
See the details
Why it mattered Raid
In phase two (below 70% health), Nythraxis casts Deathless Rage every 45 sec, on a 10-second cast.
The only counter is the three stones: three different players, 5 seconds of channelling each, before the cast finishes.
Done in time, the cast is cut and the boss is stunned for 5 sec. Missed, it hits everyone in the room for 82% of max health — and 115% on heroic, which is a wipe.
See the details
What does not change Scope
The Bastion Ward Stone you pick up outside for the quest stays hidden until you are on the quest: that is v0.38.0's intended behaviour, and it is kept.
The attunement crypt's quest relics stay hidden off-quest too.
Only objects a dungeon explicitly declares "interacted with, never picked up" escape the hiding — today, the three arena stones.
02The black screen on high graphics
On Linux with an NVIDIA card and Chrome, the game could render a fully black frame on High or Ultra since v0.38.0. Low and Medium were never involved.
Where it came from Fixed
On grass tufts and building edges seen at a grazing angle, a lighting computation produced an invalid value. The bloom blur then smeared it across the entire frame, and the whole picture went black.
See the details
Who was affected Reach
Only High and above: they are the only tiers that run the final image pass which adds the bloom.
On Low and Medium the frame goes straight to the screen in a format that clamps invalid values away — hence no symptom at all.
The flaw only showed on one graphics driver path, observed on Linux + NVIDIA + Chrome. Nothing to do with your game settings.
So it cannot come back Guard
The fix is visually neutral: it only triggers on the invalid value, never on a normal surface.
Two tests pin the result: one checks the guard inside the 3D engine itself, the other the scrub right before display.
If a future 3D engine update drops either one, the test fails before release.
03And nothing else
This is a hotfix in the strict sense. Everything v0.38.0 brought the day before stays exactly as it was.
Nothing moves in the game Scope
No combat value: no spell, no talent, no mastery, no set.
No item, no creature, no quest, no zone.
No data migration: nothing to redo on your character.
Not one string modified, in any locale.
The scenery did not change Behind the scenes
27 Eastbrook and Fenbridge 3D models were re-stamped as part of the fix.
Only their internal fingerprint changes: geometry and textures identical, same file size, no visible difference.
v0.38.0 still stands Reminder
The four-tank rebalance, Baleful Roar and Savage Mending on the bear: all in place.
Chronomancy's level-20 ranks, the Thuggery cut, Honor for arena losses: same.