I went through all the instructions, and I was able to get the autosave folder to appear...However, it only shows one save file. For context, I wanted to revert to a save before I finished the post-game content and completed the game. Currently though I am in a New Game+ save, so I'm wondering if that overrides previous saves somehow? I'm not sure what happened.
im not using steam version, so where i put my DDDA_Autosaver.exe? btw it auto created st_autosaves but cmd still closed after run the .bat, and not backup the save file.
Hi Kalec, thanks a lot for flagging this! Found a bug this a.m. - the script isn't creating the destination folder for autosaves.
I'll put a fix up today or tomorrow, but in the meantime - you could test by creating the destination folder manually (name it "st_autosaves" and put it right next to the "remote" folder - see image I uploaded a minute ago). Not 100% sure this will clear the issue, but I'd be very interested to know if that works?
Apologies for the bugginess; didn't have a 2nd pc to test on.
hey i don't use steam to play dragon dogma, and my question is where should i put this line to game's launch option?? "C:\Program Files (x86)\Steam\steamapps\common\DDDA\Run_DDDA.bat" %COMMAND%
If you're not using steam, you can just double-click the .bat file to run the game. For simplicity, I'd probably create a shortcut to the bat file (right click, select "create shortcut"). You can rename the shortcut to whatever you like, and drop this shortcut onto your desktop or wherever you launch the game from).
The ...%COMMAND% call is specific to steam, telling steam to run our .bat file whenever it tries to start DDDA. It is not needed if you're just running the game locally.
I am not sure what the problem is but I followed the steps and do not see the backup folder created. I have my save files and game files in different drives...but thanks for the idea, I wrote a few lines of PowerShell script to do just this.
Thanks! Did see that, just reached out to the support team to see what we can do (fingers crossed). I'm assuming it's the raw exe that's flagging (and I can see why). Hopefully we can find a way to verify/sign it. I'm not sure what other mods have done in this situation?
13 comments
btw it auto created st_autosaves but cmd still closed after run the .bat, and not backup the save file.
no autosave folder is made.
Not sure what is happening.
I'll put a fix up today or tomorrow, but in the meantime - you could test by creating the destination folder manually (name it "st_autosaves" and put it right next to the "remote" folder - see image I uploaded a minute ago). Not 100% sure this will clear the issue, but I'd be very interested to know if that works?
Apologies for the bugginess; didn't have a 2nd pc to test on.
I've uploaded a patch with a fix (v1.20). The .bat file is the same, you can just replace the old Autosaver.exe with the new one.
where should i put this line to game's launch option??
"C:\Program Files (x86)\Steam\steamapps\common\DDDA\Run_DDDA.bat" %COMMAND%
If you're not using steam, you can just double-click the .bat file to run the game. For simplicity, I'd probably create a shortcut to the bat file (right click, select "create shortcut"). You can rename the shortcut to whatever you like, and drop this shortcut onto your desktop or wherever you launch the game from).
The ...%COMMAND% call is specific to steam, telling steam to run our .bat file whenever it tries to start DDDA. It is not needed if you're just running the game locally.