POST-LAUNCH SUPPORT AUDIT · VERIFIED

Stardew Valley

ConcernedApe / Eric Barone (solo dev; self-published since Dec 2018; Chucklefish was original publisher) · 2016 · Farming Sim / RPG

Did the studio keep supporting this game after launch? This page is the evidence.
AFTERCARE SCORE 84 Tier A · Excellent Pattern: Steady
See it on SteamStore link opens Steam in a new tab.
LAUNCH CONDITIONGood
AFTERCARE PATTERNSteady
AUDIT STATUSVerified

A solo developer who treats a decade-old game like it launched yesterday — and apologizes out loud when it slips.

01Score breakdown

Patch Speed15 / 20
Maintenance Quality16 / 20
Communication17 / 20
Player Responsiveness17 / 20
Follow-Through19 / 20

Five categories, 20 points each, 100 total. Full method on the methodology page.

02The evidence

Eric Barone launched Stardew Valley to a warm reception in February 2016 and has supported it nearly solo ever since: multiplayer (2018), and the massive free 1.6 update in March 2024, nine years after launch. His response cadence is exemplary — 1.6.1 hotfix within 24 hours of 1.6, a Switch 2 co-op break acknowledged and patched within nine hours. The real blemish is the 1.6 console/mobile port, which took eight months instead of the promised one; he accepted full responsibility publicly. He even paused Haunted Chocolatier to finish the ports, and kept updating through 2025 (1.6.14, 1.6.15).

  • Crisis response is elite for a solo dev: patch 1.6.1 shipped within 24 hours of the 1.6 launch, and a Switch 2 online-co-op break was acknowledged and patched within nine hours of the report reaching him
  • Nearly a decade of major free content (multiplayer 2018; 1.6 in 2024), while pausing his next game — 'I have not touched Haunted Chocolatier in a long time' — to finish the 1.6 console/mobile ports
  • Unusually candid crisis communication: 'I never intended for the delay to be this long,' 'I accept the blame' for broken mods, and a public self-warning when a 2025 Switch patch introduced crashes
  • Console/mobile players bore the cost of the solo model: the 1.6 ports took ~8 months vs. a promised ~1 month, and late-cycle patches (1.6.15.1) briefly introduced Switch crashes before being fixed

03Sources

04Audit record

Launch date
2016-02-26
Evidence coverage through
Oct 4, 2026
Methodology
v1.0
Audit confidence
Medium
Why this confidence
Strong sourcing on 2024-2025 (1.6 era hotfix cadence, public statements), but the 2016-2023 record is summarized from secondary sources rather than a primary changelog audit, and the mobile port's history was complicated by the Chucklefish handover.
Score band
Excellent (Tier A)