Have console save/load commands check save_dir

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Have console save/load commands check save_dir

Re: Have console save/load commands check save_dir

by Nokiaman » Thu Jan 01, 2015 1:01 pm

I'm sorry for bumping this, but I'm noticing same behavior and it's still not fixed in latest version. I use these 2 commands as a quicksave/quickload since it doesn't ask for confirmation every single time.
I use Steam versions of iD games and they are all in base folder. So instead of saving to base folder like autosave does. It puts it next to the base folder.
base
-----autosave.zds
-----zdoom.exe
quicksave.zds

Please fix this.

Have console save/load commands check save_dir

by bttrs » Tue Aug 27, 2013 4:26 pm

Good day. Something I noticed after I set a save_dir (to $PROGDIR\Save) in my ini file, as part of an effort to keep my zdoom $PROGDIR tidy, which is used just fine by autosaves and saving and loading via the menu. But I noticed that using the save and load console commands, such as

Code: Select all

save foo
, saves to $PROGDIR (or rather, as someone in the IRC channel said, it's actually the working directory from when ZDoom launched), resulting in $PROGDIR/foo.zds. To me, this seems like unexpected behavior. I don't see any reason why those commands shouldn't be checking the value of save_dir, and use that if set, so that

Code: Select all

save foo
results in $value_of_save_dir/foo.zds (that is, relative paths are relative to save_dir when it's set, and if it's not set, fallback to the CWD.

I would appreciate any possible feedback on this suggestion, as I feel it would be better if those commands were more consistent with their menu counter parts.

Thank you.

Top