Home / Guides / Troubleshooting
Fixing launch, display and save problems
A blank window and a broken save are different problems. Start with the reversible checks, use the browser build to separate game data from desktop packaging, and never clear site data as a first experiment. The platform notes below keep developer fixes separate from community reports.
Checked against v3.0.0
Do not delete browser storage or overwrite a working install
Browser saves live with that browser profile and site storage. Clearing cookies/site data, switching profiles, or testing in a private window can make a save appear missing. Keep the original profile untouched while you test another browser or the downloadable build.
Recent builds give you the tools to do this safely. Use the backup button in the top bar first: it writes a ledger file you can read back later with Load a Ledger. Lock the ledger on the title screen, so it cannot be erased, abandoned or restored over while you experiment, and the game still saves into it. Hand over its ledger writes the same guild to a file or as text, which is also the easiest way to give the developer a save.
Find the first branch that matches
1. Browser works: the desktop package is the suspect
Keep playing in the browser while you test the platform-specific launch flags below. The game itself and the current web bundle are loading.
2. Both builds fail: check network, browser and version
Reload the itch page, disable only extensions that alter scripts or storage, and note the version before reporting it: clicking the version badge copies it.
3. New profile is empty: that does not prove save loss
Return to the original browser and profile. Storage is isolated between browsers, profiles and private sessions.
4. Only one save fails: preserve it for a report
Do not repeatedly overwrite it. Record the last action, game day and screen, then report the smallest repeatable sequence.
Arch Linux AppImage: white window after launch
The developer's first recommendation is to disable the WebKit DMABUF renderer for that launch. Run the command from the directory containing the AppImage, adjusting the filename if yours differs.
WEBKIT_DISABLE_DMABUF_RENDERER=1 ./DungeonsAndDynasties.AppImageIf the first launch still shows white, the developer suggested also disabling compositing:
WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 ./DungeonsAndDynasties.AppImageThe developer said the first flag resolves most reported Arch white screens, but the original reporter still had trouble. Treat these as known workarounds, not proof that every white window has the same cause. If both fail, use the browser build and include your desktop environment and terminal output in the report.
Windows 7: use the browser as a community fallback
The downloadable build may not start on Windows 7. One community member reported that the browser game ran in Firefox 115 ESR. That is useful field evidence, not an official promise of continuing Windows 7 support. If you try it, keep the wording and expectation exactly that cautious.
Fullscreen, pointer and installers
Windows and Linux downloads have shipped since 2.01, and since 2.09 the installers name their author and describe the game, so placeholder text means an old download. In the desktop builds F11 and Alt+Enter toggle fullscreen, fullscreen is remembered between sessions, and 2.17 fixed a pointer that could vanish in fullscreen on Windows 10. If either still happens, note the exact version in the report.
Slow AppImage: compare against the browser build
A player reported severe AppImage slowdown on Arch while the browser build remained smooth. That single report cannot establish a general performance bug, but the comparison is a good isolation test: if the same save and machine behave normally in-browser, include that difference in the report.
Save appears missing? Check identity before recovery
- BrowserAre you in the same browser that created the save?
- ProfileIs it the same browser profile, not Guest or Private mode?
- OriginDid you launch from the same itch.io game page rather than a copied iframe or another host?
- CleanupDid the browser, privacy tool or extension recently clear site storage?
- BackupDo you have a ledger file from the backup button? A refused backup now says why, instead of always blaming a different version.
What to put in a bug report
- Game version from the version badge (click it to copy), currently expected to be v3.0.0; the game prints it as 3.00.
- Browser and version, or operating system, desktop environment and download type.
- The exact last action that worked and the first action that failed.
- Whether the same save works in the browser build and downloadable build.
- A screenshot and terminal output when the desktop build fails to launch.
- For a broken save, a ledger file written with Hand over its ledger or the backup button.
Official game page: Dungeons & Dynasties on itch.io