Quick answer
Repeated launch reviews report performance instability and UI friction. Isolated reports also describe multiplayer interaction trouble, obstructed quest access, unexpected item behavior, and control issues. These are player reports, not confirmed universal defects.
Current launch signals
This page is a dated report board, not a claim that every player will see every problem. At the August 26 source check, performance instability and interface friction were repeated themes across several launch reviews. Reports mention hitching, uneven frame delivery, heavy-foliage slowdowns, menu friction, and small or difficult text. That repetition makes the themes useful warning signals, but it does not establish affected hardware, frequency, or a universal defect rate.
One Steam review said the Steam Deck build on Low settings seemed usable while text remained small. That is a single device report, not a tested compatibility result. The current store page lists Windows requirements and Partial Controller Support; it does not list Steam Deck verification.
Issue ledger
| Signal | Evidence level | Current status | Safe action |
|---|---|---|---|
| Frame instability and hitching | Repeated player reports | Monitoring | Check current reviews and patch notes; lower expectations before changing hardware |
| UI and menu friction | Repeated player reports | Monitoring | Expect rough edges and verify readability during the refund window |
| Multiplayer item pickup or remapping failure | One launch report | Unconfirmed | Re-host, test a fresh session, and document steps; no reliable fix is published |
| Doorway blocked by a searchable bag in an early mission | One launch report | Unconfirmed | Avoid publishing a workaround until the current build is reproduced |
| Hatchet dropping unexpectedly | One launch report | Unconfirmed | Record input and inventory state if it recurs |
| Horse would not turn | One launch report | Unconfirmed | Reproduce across input devices before treating it as a broad control issue |
New reports under observation
These reports are research leads, not promoted standalone answers. A candidate stays in the observation queue until current demand is independently repeated and the intended mechanic, control, diagnosis, or workaround is useful enough to verify.
Placed objects and building interaction
Status: Reported / research queue. A current launch discussion asks how a placed hitching post can be removed. One community reply suggests a demolition hammer, but that answer is not marked, reproduced, or developer-confirmed. We have not yet established whether the question reflects an undocumented building action, a control-discovery problem, or build-specific behavior.
Open the dated Steam discussion.
Respawn body and missing loot
Status: Reported — not reproduced. One current Early Access report describes returning within a few minutes after death and finding neither the body nor its loot. A reply describes different inventory behavior, so the game's intended corpse persistence and recovery rules remain unverified. No save deletion, console command, file edit, or universal timer is recommended here.
Open the dated Steam discussion.
Horse movement after dismount
Status: Reported — single-source cluster. One current player posted both a movement lock after dismounting and a separate horse water-audio oddity. Those are two posts from the same author, not two independent reports, and they may describe different symptoms. Treat the cluster as a single-source signal until another player reproduces a specific behavior.
Open the movement thread or the separate audio-state thread.
The official Steam Community hub did not show a developer launch-day known-issues post or patch note during the check. That absence is why this page labels player evidence directly and avoids pretending an official acknowledgement exists.
Workaround policy
No workaround is promoted here unless it has repeatable steps, a current build context, and evidence that it addresses the reported symptom. Restarting, reloading a menu, lowering settings, or re-hosting may be reasonable diagnostic steps, but none is presented as a confirmed fix.
If you are deciding whether to keep the game, use Steam's current refund policy and your own play session as the controlling evidence. Save screenshots, note the time and hardware, and check the official Community hub before assuming an old reply applies to the launch build.
Update history
- August 26, 2026: Opened the tracker from the live Steam store, current review feed, and Community hub. Added repeated performance and UI signals plus isolated co-op, quest, inventory, and control reports.
- Next update trigger: An official patch note, developer acknowledgement, or a reproducible launch-build test that changes an issue's status.
The related co-op briefing explains the current multiplayer evidence boundary. The value briefing places these launch risks beside price, scope, and review context.
Sources & method
What this guide is based on
The factual core comes from the current official Steam listing, Nixalon Studios material, and dated secondary evidence, checked August 26, 2026. Early Access mechanics can change. Where the source does not publish a value or behavior, this guide says so instead of filling the gap with an estimate.
Open the primary source
