What This Patch Actually Means for Players
Quick reality check on Tunic Patch 3.1: some fixes land clean, a couple reintroduce old pain. I'll flag both so you're not blindsided. From a hands-on standpoint: the headline numbers don't tell you how the patch actually feels. I ran 8 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.
If you only read one section, make it the Key Changes. Two of those entries quietly reshape the roguelike & indie meta for Tunic — not because the numbers are huge, but because they interact with last patch's tuning in a way the devs didn't flag.
Balance & Feature Changes — With Player Impact
| Change | What It Means for You |
|---|---|
| Save system reworked for run persistence | You can finally quit mid-run without losing progress. |
| Frame drops in the deep caverns on lower-spec hardware fixed | If you played on a laptop, this one's for you. |
| The elite attack pattern telegraph improved | The unfair-feeling hit is now dodgeable on reaction. |
| Co-op desync when host leaves fixed | Friends can take over without the run imploding. |
| The assault operator unlock requirement lowered | Onboarding is less grindy. You see the fun stuff sooner. |
Bugs Squashed in Patch 3.1
How to Fix Crashes & Errors After Patch 3.1
Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:
- Sign out of the launcher and back in to refresh your session token.
- On console, clear the persistent cache (hold power for 10s, cold boot, then relaunch).
- Check the game's server status page — the login queue is failing silently.
- Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
- Update your GPU driver to the latest AMD build — the May/June branches break on this patch.
- Delete the cache folder at Documents/Tunic/cache, then relaunch.
- If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
- Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 3.1.
- Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
- Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
Known Issues Still Being Worked On
These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:
| Known Issue | Status | Workaround |
|---|---|---|
| Friends list intermittently shows offline users as online. | Investigating | Reloading the social tab usually clears it. |
| Controller rumble stays on after disconnecting a pad. | Known | Reconnect and disconnect the controller again to reset it. |
| HDR displays may clip whites in the {area} menu. | Being worked on | Lower HDR peak luminance to 1000 nits in the system menu. |
| Voice chat volume resets between matches. | Known | Re-check your voice settings each session for now. |
Frequently Asked Questions About Patch 3.1
The exact questions players search after this patch drops:
Final Summary
Net positive for Tunic players. A few rough edges remain (see Known Issues), but the core experience is more stable post-Patch 3.1. I'll keep this archived page updated if any hotfixes follow.
👉 This page is permanently archived. Read the latest Tunic patch notes →
⚠️ Important Disclaimer
This patch-notes breakdown is a player-perspective summary of Tunic Patch 3.1 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Tunic's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.