AltTab

Mistfall Hunter patch notes since launch, all 19 dated

Mistfall Hunter Guide 13 min read

Mistfall Hunter’s patch notes since launch, in order: Bellring Games / Skystone Games has posted 19 official communications to the Steam news feed between 29 July 2026 (launch day) and 9 September 2026, an average of one every 2.2 days. The 19 come from a pull of 69 news items on 13 September 2026, filtered down by dropping third-party syndicated posts — SteamDB sales charts, a PS5 review, outlet previews — that carry no development signal. This page is checked through the 9 September 2026 “Weekend Rewards Are Now Live” post; the table below is dated, and it is the whole run, not a highlight reel.

Mistfall Hunter launched on 29 July 2026. Between then and 9 September — 42 days — the developer posted 19 times. Posting slowed from the near-daily burst of the first three weeks (13 posts in 23 days, one every 1.8 days) to a steadier one-every-2.2-days pace across the full six weeks, but it never went quiet: there was no calendar week in this stretch without at least one official communication.

The 19 posts, in order

Date (2026)TitleTypeNotable content
Jul 30Launch Rewards & July 30 UpdatePatch notesWithered Knight balance pass, 13 bug fixes, store-review-approved build
Jul 30Known IssuesKnown issues notice12 issues disclosed same-day as launch, before hotfix approval
Aug 1The Second Wave of Launch RewardsMilestone reward500,000 players milestone; reward mail
Aug 3Fair Play Penalty AnnouncementFair play penaltyTranslation correction on “Illegal Teaming” definition; first partial ban/penalty lists
Aug 5Roadmap and Launch Rewards: Wave 3Roadmap + milestone1,000,000 players milestone; Brandrgarde Solo Mode promised for “mid-Season 1 in September”
Aug 6August 6 Live UpdatePatch notes41 “Fixed an issue” lines, Dried Flower Knot drop enabled
Aug 7August 7 Server Online Update NoticeServer status updateServer-side hotfix; ~30 ad accounts banned in chat; forecasts next week’s Soul Harvest update
Aug 12August 12 Live UpdatePatch notesSoul Harvest mechanic launch, 35 “Fixed an issue” lines, Blocklist feature added
Aug 12Fair Play Penalty AnnouncementFair play penalty438 cheating bans, 232 teaming penalties, feedback-email feature announced
Aug 15Server Stutter Optimization Update & Soul Harvest Launch RewardsServer optimization + rewardCloud CPU hyper-threading fix applied Aug 13–14; reward mail for launch patience
Aug 19August 19 Live UpdatePatch notes34 “Fixed an issue” lines, controller vibration on fall damage, dedicated server frame-rate monitoring disclosed
Aug 20DevNote #8Developer note1.5M players milestone; class balance philosophy; Season Task count (152) explained; Javelin weapon teased
Aug 21Fair Play Penalty AnnouncementFair play penaltyNew “Frequent Temporary Teaming” category from an 80%-approval community poll; 630 cheating bans, 76 + 396 teaming-related penalties
Aug 27August 28 Server Maintenance UpdatePatch notes + task rebalanceSeason Task and Contract Task difficulty reduced (“kill count requirements” and “equipment value restrictions” both eased), new Oceania server added, 21 bulleted fix lines
Aug 28Fair Play Penalty AnnouncementFair play penaltyFirst appearance of a third category, “Intentional Illegal Teaming,” alongside the existing cheating and temporary-teaming lists; both larger lists display 500 names, a figure that looks like a post display cap rather than a stated total
Sep 3September 3 Live UpdatePatch notesBrandrgarde Solo Mode (Normal and Cataclysm) added; 22 bulleted fix lines plus class-balance changes under five class headings (Mercenary, Withered Knight, Shadowstrix, Sorcerer, Blackarrow; no Seer section)
Sep 3Brandrgarde Solo Mode Now Available & Limited-Time Special RewardsStatus update + rewardOne-month-launch milestone; frames the same day’s Solo Mode addition as delivery on the Aug 5 roadmap promise; three-day login reward chain through Sep 5
Sep 8Fair Play Penalty AnnouncementFair play penaltyThird category repeats; lists again cap out (52 / 353 / 389 names shown, the two larger ones below the prior post’s 500-name ceiling)
Sep 9Weekend Rewards Are Now LiveReward + matchmaking testRecurring Friday/Saturday/Sunday login rewards through end of Season 1; same-day server update adds a “dynamic player cap” letting matches start with fewer players, described as an experiment the studio is soliciting feedback on

What the raw feed doesn’t tell you: the cadence

The first 13 posts landed across 23 days — one every 1.8 days on average. Widen the window to all 19 posts across the full 42 days from launch to 9 September and the average pace settles to one every 2.2 days. Steam’s news feed presents these as isolated items with no sense of tempo; laid end to end, the tempo is the story, and the story here is a fast initial burst that cooled into a steadier, still frequent, cycle rather than trailing off to silence.

What the raw feed doesn’t tell you: where the time went

Sorting all 19 posts into a single primary type each, rather than reading them as a flat list, shows a lopsided allocation:

Update typeCountShare of 19 posts
Patch notes (Live Update / maintenance)631.6%
Fair play penalty announcement526.3%
Milestone / reward315.8%
Server status / optimization210.5%
Roadmap15.3%
Known issues disclosure15.3%
Developer note15.3%

Fair play penalty announcements alone make up more than a quarter of everything Bellring Games has published since launch — still ahead of roadmap posts, developer notes, and known-issues disclosures combined. For a PvPvE extraction game, where a single cheater or an illegitimate three-squad alliance directly steals another player’s loot run, that ratio is a direct signal of where player-facing trust problems concentrated, and it has not eased off six weeks in: the fifth announcement (Sep 8) added a third penalty category rather than winding the first two down.

What the raw feed doesn’t tell you: the fix count

Six of the patch-note posts carry a running tally of individually itemized bulleted fix lines (phrased as “Fixed an issue,” “Fixed a visual issue,” or similar). Counting them by hand across all six gives a number no single post states:

PatchDateBulleted fix linesPatch length (characters)
Launch Rewards & July 30 UpdateJul 30133,424
August 6 Live UpdateAug 6416,061
August 12 Live UpdateAug 123510,338
August 19 Live UpdateAug 19347,881
August 28 Server Maintenance UpdateAug 27218,835
September 3 Live UpdateSep 3225,953

That is 166 individually itemized fixes across six patches in 35 days (Jul 30–Sep 3), an average of roughly 28 per patch, none of it counting the class balance changes, which are listed separately and are not phrased as fixes. The August 12 patch is both the longest and the one that shipped the season’s flagship mechanic (Soul Harvest) on the same day, which is why its bug-fix count sits alongside a mechanic launch rather than being a pure hotfix; the two most recent patches (Aug 27, Sep 3) run shorter fix counts but each pairs with a larger structural change — Season/Contract Task difficulty cuts and Brandrgarde Solo Mode, respectively.

Bulleted fix lines per patch, July to September Hand-counted across six patch-note posts, 30 Jul-3 Sep 2026 Jul 30 13 lines Aug 6 41 lines Aug 12 35 lines Aug 19 34 lines Aug 27 21 lines Sep 3 22 lines 166 fixes total across 6 patches; class balance changes are listed separately and not counted here.

Reading the pattern

Three structural notes fall out of the ordering that a flat news list obscures. First, server performance is a throughline, not a one-off: it is explicitly addressed on Aug 7 (server-side hotfix), Aug 15 (cloud CPU hyper-threading fix), Aug 19 (dedicated frame-rate monitoring disclosed), and again inside DevNote #8 on Aug 20 — four separate touches on the same underlying stutter/lag complaint in three weeks, which argues against treating any single “we fixed it” line as the end of the story. Second, the Fair Play Penalty Announcement format kept evolving past that point: the Aug 3 post had to walk back a mistranslation of its own rule definition, the Aug 21 post added the “Frequent Temporary Teaming” category from a player poll, and by Aug 28 a third category, “Intentional Illegal Teaming,” had appeared alongside it — three format changes to the same recurring post type inside five weeks. Third, the promised delivery arrived roughly on schedule: the Aug 5 roadmap named “the middle of Season 1, in September” for Brandrgarde Solo Mode, and the Sep 3 Live Update shipped it, framed the next day as a one-month-launch milestone rather than a bare patch note.

For the specifics of what those Fair Play announcements actually penalized and how the policy language changed post to post, see the fair play penalty tracker. For how the promises made in the Roadmap and DevNote posts above measured up against what actually shipped, see the roadmap-vs-delivered tracker.

What the 69-item pull doesn’t cover

  • The full Roadmap graphic from the Aug 5 post is an image, not text, and its contents are not reproduced in the Steam news API payload we pulled. We can confirm the one item spelled out in the post body (Brandrgarde Solo Mode, delivered Sep 3) but not the rest of the roadmap’s contents.
  • Whether “kernel-level anti-cheat” is the specific technology behind the Fair Play penalties. None of the news items we reviewed name a specific anti-cheat product or describe driver-level detection; they describe penalty outcomes (bans, matchmaking suspensions) and poll- or algorithm-driven rule changes, not the underlying detection method. We do not assert a specific anti-cheat architecture in this dataset.
  • Exact ban and penalty totals for the Aug 28 and Sep 8 announcements. The Aug 21 post’s numbers (630 cheating bans, 76 + 396 teaming penalties) read as genuine totals. The Aug 28 post’s two larger lists both display exactly 500 names, which looks like a post display cap rather than a stated count; we report the displayed list lengths (74 / 500 / 500) and the Sep 8 lengths (52 / 353 / 389) as list lengths, not as confirmed totals.
  • Total player count beyond the four milestones stated. The posts confirm 100,000 (8 hours post-launch, Jul 30), 500,000 (Aug 1), 1,000,000 (Aug 5), and 1.5 million (Aug 20, per DevNote #8) — no milestone post after Aug 20 restates a player count through Sep 9, so we report only these four figures.

Sources

Related posts