Dimraeth bugs and fixes
Most common Dimraeth problems have a fix or a workaround. Maintaining the Defenses stuck on Rahaner: update the game, the first public hotfix fixes it. Trapped in a small invisible box at your camp: teleport to a waypoint. Thrown back to the main menu while loading or saving: check whether Windows Defender or antivirus is blocking the game from writing to disk.
Find your problem
| What happens | Try this |
|---|---|
| Rahaner has no dialogue for Maintaining the Defenses | Update the game: the first public hotfix fixes the turn-in |
| You can only walk a step in any direction at your camp | Teleport to a waypoint |
| Kicked to the title screen during the first cutscene, or Failed to save progress | Check Windows Security, Protection History, for blocked writes |
| Screen goes black and zooms in after Vanishing Strike | Exit and reload the game |
| Another player emptied your chests, even ones set to Private | Update the game, then turn on LockBuildtoOwner and rebuild the chest |
| Returning friends cannot join a New Characters Only world | Turn the setting off in Settings, Multiplayer |
| XP spent at a campfire but no level-up | Confirm one attribute order at a time; if XP truly vanished, send your character and world files |
| Constant stutter every few seconds, or a crash | Keep player.log before restarting and hand it to the developers |
Some of these may already be fixed, so check the Dimraeth patch notes and the Dimraeth roadmap and update history before assuming a bug is still live. The developers answer bug reports fastest on the official Discord; links to it and the other channels are on the Dimraeth Discord, subreddit and forum page.
Maintaining the Defenses will not finish
The quest tells you to talk to Rahaner, and Rahaner offers nothing but Leave. Update the game: the fix was tested on the playtesters branch and then shipped to everyone in the first public hotfix.
“Fixes Maintaining the Defenses quest not able to turn in”
Mudtek
Players who cancelled the quest before that hotfix could not accept it again. The same hotfix made side quests impossible to abandon, so the cancel button is gone. The early quest chain around this quest is laid out in the Dimraeth beginner guide.
Stuck in an invisible box at your camp
You load in at your camp in the Sanctum and cannot get more than a step away in any direction, even by dashing. The developers tie it to the tent and campfire combination.
- Open the map.
- Teleport to any waypoint you have already unlocked. Teleporting is free, so there is nothing to lose.
- Walk or teleport back to the Sanctum and carry on.
The teleport only works once you have finished the tutorial and have a waypoint to go to. Removing buildings is a coin toss: one player found removing the campfire was enough, another removed the tent and campfire and verified files with no change. A hotfix for it went to the playtesters branch before the main branch. The tent, the campfire and the rest of the Sanctum are covered on the Dimraeth Sanctum and building guide.
Trying a hotfix early: the playtesters beta branch
To try a hotfix before it reaches everyone:
Find Dimraeth in the list.
The properties window opens on the game.
The choices are Default Public Version and playtesters.
Then load your save and see whether the problem is gone. To go back, select the default public version again.
Kicked to the title screen, or Failed to save progress
Two versions of one problem. Some players are dropped back to the title screen during the first cutscene or the load after it; others play for a while, see a save failure, and are sent to the main menu. The first thing to check is Windows stopping the game from writing to disk; when that happens the game quits to the menu on purpose, so you do not play for hours without saving.
- Open Windows Security.
- Go to Protection History and look for entries about blocked writes at the time you were kicked.
- If your Steam library folder is marked as protected, that is likely the cause.
- If Protection History is clean, check whether other antivirus software is blocking the game.
“so windows defender protected any writes, so basically during loading it cannot write to the disk and just kicks you back to the main menu.”
“You can check this by going to Windows Security -> Protection History and see if you see logs of writes blocked.”
“If it's not that it could also be anti-virus software blocking the write attempts or something along similar lines.”
On a handheld launched in Xbox mode through Winhanced, one player with a clean Protection History got past the first cutscene by switching to desktop mode and starting the game straight from Steam. There is no manual save: the game uses auto saves.
Vanishing Strike soft-lock
After Vanishing Strike, your character disappears, most of the screen goes black and zooms in, and nothing responds; waypoints still teleport you but the screen stays black. Exit and reload the game to clear it. It has happened against the treant in The Corrupted Beast quest and against the goblin king, and a developer is looking into it.
The second hotfix lists “Partially fixes vanishing strike making player teleport to the ether”; if you still get the black screen, the reload still works. If your build leans on it, the other ways to spend those points are on the Dimraeth skill tree page, and the fights where it has happened are on Dimraeth bosses.
Chests emptied by another player
Players in different worlds found every chest empty, including ones they had locked. Players report that the Private switch only stopped crafting benches from using a chest, and that the real lock was a world setting. Update first: the second hotfix lists “Fixes chests set to be private for local interaction as well as workbench pooled inventory”, and two later hotfixes tightened private chests on the server and fixed chests not showing for joining players.
The world setting, and how to check that a chest holds, are on the Dimraeth co-op page. Every line of all four hotfixes is on Dimraeth patch notes.
New Characters Only locks out returning players
On a world with New Characters Only, friends who had already played there can be refused after a server restart, even though they are returning players. Turn the setting off:
“Looking into it - fortunately if you just want to play now you can turn off the new character only setting in the Settings -> Multiplayer menu.”
Be sure before you do: the game warns that you cannot turn it back on. The other world settings and how hosting works are on Dimraeth co-op and multiplayer.
XP spent at the campfire but no level-up
Leveling in Dimraeth means spending XP on attributes, and the XP you spend fills the level bar. If you confirm a level-up and stay the same level with the XP gone, the likely cause is a preview bug: when you add and remove attribute points back and forth, the order changes the cost of later upgrades, and the preview bar stops matching what you will actually get. A patch for it is planned.
Pick your attributes in one pass instead of adding and removing points in the preview, and trust the level you end on rather than the bar. If the XP really vanished, send your character and world files to the developers on Discord or by email. How attribute costs rise is explained on Dimraeth leveling and respec.
Spending more skill points than you have
Clicking more nodes than you have points for can crash the game, and one player’s character then crashed on every load while a new character was fine. The developers say this happens when you put in more points than the game should allow. The player suspected it happened because a co-op friend disconnected at that moment, so avoid spending points while a friend is dropping.
Crashes, constant stutter and player.log
Stutter at a few fixed spots, such as the Earlwood bridge into the Farmlands, is scene loading on lower-end hardware and is covered on Dimraeth system requirements. Stutter every few seconds everywhere is different: your player.log file may be spamming errors and overloading the disk write. Where that file lives, and the other stutter fixes, are on Dimraeth stutter and lag fixes.
After a crash, send the developers player.log before you restart the game: a restart clears the log. If one character crashes every time it loads while your others work, they want that character file instead; bring it to the Discord.
Other reported problems
Quest-specific problems, such as a counter that resets or an item you cannot find, are collected by quest name on Dimraeth stuck quests.