Quote
Originally posted by suydam:
**Yes but, in my case, the game then creates two users. One, is the name of the new copy and the other is the name of my original character. That's why I always quit immediately and discard the copy. Each to his own.
**
Hmm. As long as the file is renamed back to the original name (xxx.usr where xxx is the character name) I've never had the game make another copy.
(I just checked, and if I call the file something else, then it =does make a copy, renaming it to the charactger, just as you said).
Assuming a hacker name of xxx .... During the game I periodically:
(list=a)
() Duplicate the usr file. (original file "xxx.usr", new file "xxx.usr copy.usr"
() Move the duplicate to the backup directory.
(*) Rename the duplicate sequentially (xxx-1.usr, xxx-2.usr, etc)
(/list=a)
This leaves me with xxx.usr in the usr directory, and a series of backups in the backup directory. If I get disavowed or something and want to switch to a backup I:
(list=a)
() Move the current (bogus) xxx.usr file to the backup directory
() Rename the current usr file to something like xxx-9.bogus
() Move or copy a good backup file to the usr directory (it might be xxx-8.usr)
() Rename the backup back to the original name (xxx.usr)
(*) Play the game.
(/list=a)
Doing it this way, the game accepts the xxx.usr file, and doesn't try to duplicate or reform it.
I just checked and confirm that if you name it something else, like bubba.usr, as soon as you play the game makes a new file with the original name. I agree with you that if your backuping system causes the game to make a duple, it's best to immediately exit and then use the correctly named copy. But I think it's easier to just name it correctly myself before entering the game.
Naming the backups the way I do makes it easy to restore the name properly.
My other system is to try to play very very carefully, so I don't need to restore a backup. Easier said than done <g>.
------------------
r