HomeGamesUpdatesPricingMethodology
Steam News15 February 20188y ago

Hotfix for Windows

Hey everyone, I just pushed out a quick hotfix for the Windows version of the game.

Full notes

Full Defender's Quest: Valley of the Forgotten (DX edition) update

Read the full published notes in a cleaner layout. The original post stays linked below.

Repeated intro

Hey everyone, I just pushed out a quick hotfix for the Windows version of the game. Apparently there was a regression which made it so that people who had unicode characters in their windows username directory (ie, lots of people from Russia, China, Japan, Korea, etc) were not able to save the game. You COULD recover from this if you went to the in game menu, selected miscellaneous, and then manually changed your save file location, but this is not ideal. So, today we've pushed out a fix that seems to work. There is one remaining known bug related to this issue: if you use the options menu to change your save file location, the directory picker will not recognize any path you select with unicode characters in it. "C:\this\is\a\path" is fine but "C:\カタカナ" is not. HOWEVER! The game will still recognize a custom path with unicode characters if you manually edit the paths.xml file. You can do this by clicking on the floppy disk folder button in the save slot screen, and opening paths.xml in a text editor of your choice, you would want to set it to something like this: <?xml version="1.0" encoding="utf-8" ?> Sorry for any inconvenience. Please report any further issues you have and we will try to fix them. NOTE: This only ever affected WINDOWS users, as far as we can tell.

What changed

1 fix0 additions0 changes0 removals
  • UI and audio
fixedHey everyone, I just pushed out a quick hotfix for the Windows version of the game. Apparently there was a regression which made it so that people who had unicode characters in their windows username directory (ie, lots of people from Russia, China, Japan, Korea, etc) were not able to save the game. You COULD recover from this if you went to the in game menu, selected miscellaneous, and then manually changed your save file location, but this is not ideal. So, today we've pushed out a fix that seems to work. There is one remaining known bug related to this issue: if you use the options menu to change your save file location, the directory picker will not recognize any path you select with unicode characters in it. "C:\this\is\a\path" is fine but "C:\カタカナ" is not. HOWEVER! The game will still recognize a custom path with unicode characters if you manually edit the paths.xml file. You can do this by clicking on the floppy disk folder button in the save slot screen, and opening paths.xml in a text editor of your choice, you would want to set it to something like this: <?xml version="1.0" encoding="utf-8" ?> Sorry for any inconvenience. Please report any further issues you have and we will try to fix them. NOTE: This only ever affected WINDOWS users, as far as we can tell.

Defender's Quest: Valley of the Forgotten (DX edition) changes

fixedHey everyone, I just pushed out a quick hotfix for the Windows version of the game. Apparently there was a regression which made it so that people who had unicode characters in their windows username directory (ie, lots of people from Russia, China, Japan, Korea, etc) were not able to save the game. You COULD recover from this if you went to the in game menu, selected miscellaneous, and then manually changed your save file location, but this is not ideal. So, today we've pushed out a fix that seems to work. There is one remaining known bug related to this issue: if you use the options menu to change your save file location, the directory picker will not recognize any path you select with unicode characters in it. "C:\this\is\a\path" is fine but "C:\カタカナ" is not. HOWEVER! The game will still recognize a custom path with unicode characters if you manually edit the paths.xml file. You can do this by clicking on the floppy disk folder button in the save slot screen, and opening paths.xml in a text editor of your choice, you would want to set it to something like this: <?xml version="1.0" encoding="utf-8" ?> Sorry for any inconvenience. Please report any further issues you have and we will try to fix them. NOTE: This only ever affected WINDOWS users, as far as we can tell.

Source

Steam News / 15 February 2018

Open original post

Changelog.gg summarizes and formats this update. How we read updates.