Mistfall Hunter Bugs, Known Issues and Fixes

Players see team and friend features locked or failing silently. Three separate causes circulate: the social menu not unlocking until the tutorial and first expedition are done (community-reported), mismatched client versions, and the region wall — accounts in different store regions cannot party at all, which a developer reply confirms is by design rather than a bug.

Several players say party members received credit on Hallowgrove while their own account remained blocked, including after solo attempts and landing the final hit.

Reports describe Q/E, mouse attacks, jumping and interaction failing while basic movement and spotting still work. Reddit and Steam players now independently report the same pattern, including lost gear after force-quitting.

Bellring says the in-stage causes are complex and still being worked case by case. The 7 August notice does not promise a one-shot fix, only that lag issues should taper off with successive updates, and every post since has repeated that shape. Three separate causes were named in August — cloud server CPU hyper-threading on 15 August, and chime and treasure chest refreshes triggering excessive computation on the 19th. The 27 August update shipped two named server-side rubberbanding reductions without touching the chime and treasure-chest refreshes it had named; the 3 September companion post still lists performance optimization among the team’s highest priorities rather than calling latency closed. The 15 September update is the first to claim a resolution with a cause attached — non-CN servers moved from AWS EFS to EBS storage, fixing rare hitches of over five seconds caused by a log I/O disk-write bottleneck — but it is scoped to one symptom, one server group and one cause, and says nothing about the rest.

Launch-day reports describe completing or entering the tutorial and then being unable to reach normal play.

More than one Game Pass player reports never reaching the game after launch.

Recent Reddit and Steam reports describe Fatal Error crashes after basic repair steps. One Steam player says forcing DX11 reduced crashes but caused long freezes, so this remains a watch item rather than a safe workaround.

A player reports that the Brandrgarde objective names Oath Bridge but neither the place name nor a tracked quest icon appears.

A reader reports being dead and returning to their own corpse when another character died on top of it. The interaction on offer became looting that character rather than recovering their own body, and the recovery was unavailable while the two overlapped. This is the weakest-sourced item on the page: one private email, no public thread, not reproduced here. It is listed because the failure is specific and it lands on the one mechanic the death guide tells players to rely on.

Distinct from the raid input soft-lock: the character is otherwise responsive and only the single dodge-attack input is dropped, with the shot animation playing and no projectile leaving. The creator cannot identify what triggers it and suspects input timing. Recorded because Bellring said on 5 August it is actively investigating reported stuttering and latency, and a swallowed input is what that class of problem looks like from the player’s seat.

Two complaints from the same solo session, pulling in opposite directions. Several fights start as a plain one-versus-one with nobody else on the map, and then a spawn arrives already contested by four players moving as a group. The player explicitly declines to call it cheating. Bellring’s 3 August Fair Play post defines Illegal Teaming as exactly this — several players deliberately entering the same match to gain an advantage — and publishes matchmaking suspensions for it, so the official channel already treats the pattern as real.