The Dark Mod Quick Save Bug Destroyer . . .

[dominoid]

The last line of the save "command" sets the load variable to the last quicksand.

[LEGION]

Though I don´t know "quicksand" I seem to understand, I´ll add that to Doom3 too, it´s always better to have more than one quicksave as you already pointed out, mistakes happen.

[dominoid]

Sometimes I hate the iPhone auto correct. Lol.

[gnartsch]

I think I will edit my program to create/append the AutoExec.CFG file automatically instead of what I am doing now.

 

Great idea !

 

Works for me (the pure script version with AutoExec.cfg) !

 

The only thing to keep in mind:

The first Quicksave you do since you (re)started TDM will always overwrite Quicksave1.

No matter where you left off the mission the day before.

But that should not be a problem.

 

Thanks !

Edited August 26, 2010 by gnartsch

[dominoid]

Already thought of that. I will programtically create the lines in the AutoExec.cfg file at run time to correctly start at the proper quick save based upon the save file dates.

Edited August 26, 2010 by dominoid

[Tels]

Looks like it's time to come up with a script for Linux to achieve the same thing. Does anyone know of a program to monitor changes to a directory? That would be the main factor and the rest can be easily scripted.

 

Oh, sure:

 

$ watch /home/te/.doom/darkmod/somefmhere/savegames

 

There are others (based on the monitoring of files), too, but they escape my mind atm.

 

You could do also:

 

#!/usr/bin/perl -w

# read the directory to watch
while (3 < 5)
 {
 # watch the directory for changes
 if (directory changed) { do something }
 }

 

Same would work with shell code, but I am not that fluent in it. It is a rather trivial in linux.

 

However, I am confident it would be MUCH better to fix the darkmod bug than to have another wrapper around TDM..