Current version: HOTFIX 0.05.006
The official Steam news feed places HOTFIX 0.05.006 above every other update for App 3312250. Its publication time is August 23 at 17:11 UTC. No later patch appeared in the first thirty official news records during the August 26 verification. That makes 0.05.006 the current reference point for this guide, while the live store continues to identify the game as Early Access and available for purchase.
A current version label is useful only when its source and check time travel with it. Every patch page here records both. If the developer posts a newer build, the patch registry must select the new record and keep 0.05.006 in chronological history. The site should never decide that an update is current from a filename, a calendar date, or an old screenshot.
What Hotfix 0.05.006 changes
The hotfix reverses an accidental spell-buying change and says purchasing spells is fixed. It also updates CHOPPER. The axe-wielding enemy no longer becomes stuck on dead players, its pathfinding is improved, and it shuts down for ten seconds after killing a player. Those statements replace the older 0.05.005 wording that treated CHOPPER behavior as a known concern at that time.
Two progression fixes sit beside the enemy change. A player leaving during the Day 3 B.O.S.S. fight should no longer break the following day. DOUBLE TAP should now be awarded to every player on the server after two bosses are defeated, instead of only the host. The developer also reports text fixes in several places but does not name every affected string.
Why Patch 0.05.005 still matters
Patch 0.05.005 is the main current source for version mismatch behavior, disconnect messages, Private and Solo lobby access, reassignable spell keys, weapon durability changes, FEARNAUGHT party scaling, Penetrator solo behavior, Ghoul decapitation, shop changes, and daily quest growth. A later hotfix does not erase those changes. It narrows or replaces only the subjects it addresses.
That distinction prevents a common patch-note error: treating every line in an older post as either fully current or fully obsolete. The Private and Solo outsider problem belongs in the fixed-in-0.05.005 bucket. The host-only DOUBLE TAP problem belongs in fixed-in-0.05.006. CHOPPER's old behavior note is superseded by 0.05.006. Missing strings and the listed animation issues remain tied to their 0.05.005 source until a later official notice changes their status.
Use patch history by topic
Players rarely need every line of a patch at once. A co-op connection problem should start with the version-mismatch and disconnect information. A spell purchase or failed-cast question belongs with the spell guide. CHOPPER, Ghoul, FEARNAUGHT, and solo Penetrator changes belong with their entity or play-mode pages. This hub links those subjects so a version number leads to a usable answer.
The same rule applies to equipment. The official 0.05.005 post names the pipe, rifle, Dogma's staff, cannon, rocket launcher, lock keys, syringe, and book, but that list is not the full ten-weapon catalog advertised on the store. The weapons guide keeps the complete official count separate from the subset named in patch notes. Patch evidence can explain a change without pretending to document everything in the game.
Read fixed, current, and reported issues separately
Official patch notes can establish that the developer fixed or acknowledged something in a named version. Steam discussion posts can show what players are asking about now, but a post does not prove a mechanic or create an official bug status. The known-issues page therefore separates current official notices, fixes in 0.05.006, fixes in 0.05.005, current community reports, and historical demo material.
That separation also controls which troubleshooting pages are published. The August 26 discussion sweep still showed questions about solo play and matchmaking, plus one Windows 11 startup-file report. It did not provide enough distinct current evidence for a dedicated multiplayer-not-working page. Those signals strengthen the co-op and known-issues answers without creating a thin URL that would overstate one report.
How this ledger stays current
The update check reads the Steam app-details response, the official Steam news feed, the current Community hub, the developer's official website field, achievements, and recent discussions. Store availability and patch order are checked again before a Production deployment. The public page keeps the last successful UTC timestamp so readers can judge whether a later in-game version may have overtaken the written guidance.
Summaries here are written from the official records rather than copied as full patch notes. That keeps the page focused and leaves the developer's post as the complete source. When wording conflicts across first-party pages, the registry keeps both claims with their scope. The launch announcement's 57-spell count and the store's more-than-30 wording are one example; neither source is silently rewritten to match the other.