The next day's hotfix, settling three problems born in v0.41.1. The most annoying one hit us directly: with two officers in the guild bank, one of them got kicked out with an alarming error message. Then the Crucible Quartermaster becomes reachable at last — the day before, he had been moved to the far side of a wall. And phones finally apply the updates they were downloading.
Released September 2, 2026Since v0.41.14 pull requests0 combat values changed
💡 Click a card for details.
01The guild bank stops kicking you out
This is the bug that hurt active guilds most: two officers tidying the bank at the same time, and one of them thrown out of the game with an alarming message that had nothing to do with it.
What was happening Fix
Two officers swapping materials caused a save conflict. The game treated it as a character takeover and showed "your character was taken over by another session" — a message that suggests a compromised account, when it was only two colleagues tidying the bank.
See the rule that replaces it
A polite refusal instead New
When the bank is mid-save, the operation is simply refused, with: "The guild bank is still saving a recent change. Try again in a moment."
You stay logged in, your character does not move, and you retry two seconds later.
A second message covers the case where you are the busy one: "You are busy. Try again in a moment."
And refusals stay rare Detail
The gate checks your edit rights first: no point refusing someone for a save when they had no right to touch the bank at all.
It reads a per-guild index instead of scanning the whole realm — so no slowdown.
And the save is dampened so it does not retrigger in a loop, which would keep the refusal window permanently open.
02The Crucible Quartermaster is reachable
v0.41.1 moved him out of the raid to save you entering an instance just to spend sigils. Right idea, wrong spot: he ended up on the far side of the wall.
He was behind the wall Verified
The old spot landed on the raw terrain shelf outside the west wall, thirteen yards below the raid door, with the wall in between. Reaching him meant leaving the fortress, swimming round the isle and walking up to the foot of the rampart.
See the exact correction
Where he stands now Fixed
On the landing court, one flight of stairs below the keep door.
Six yards from the door, on the west edge so the flight stays clear.
And outside the door's walk-in trigger, so you do not get pulled into the raid while talking to him.
Reachable from the door and from the court below: both paths are walkable.
A terrain fix too Behind the scenes
The real culprit: the game computed his position on raw ground, ignoring the floor plates laid over it inside the fortress.
A body seated that way ends up sunk into the plate — and the collider check then reads it as trapped in a prop.
It can now seat feet on the top of the plate. That will serve every future character placed inside a building.
03Phones finally apply their updates
A particularly tiresome mobile bug: the app downloaded the new version correctly, but never launched it — and then refused to connect.
The symptom Fix
On Android and iOS you hit "game and server versions are incompatible" with nothing you could do about it.
The update had been downloaded and staged: it was simply never switched on.
The bundle is now applied at the moment it is staged, and the app also picks up one staged before it booted.
What has not changed Scope
No game data moves: spells, talents, sets, items, mobs and zones are identical to v0.41.1.