Very simply, ArchiveMover will not allow users to overwrite games with the same name, even if the file creation date > than the old one, and the number in Version > old one.
Is this how we want things to behave? I was under the impression that with the move to the new Modinfo format, burying all of this within the files, that it wasn't going to be necessary to constantly change the actual filename of the SDZ. Keeping the SDZ the same would ease maintenance, especially for point releases.
ArchiveMover and the new Spring Modinfo.
Moderator: Moderators
Re: ArchiveMover and the new Spring Modinfo.
+1 please fix.
-
BrainDamage
- Lobby Developer
- Posts: 1164
- Joined: 25 Sep 2006, 13:56
Re: ArchiveMover and the new Spring Modinfo.
by any chance, did you have a lobby/singleplayer program open?Argh wrote:Is this how we want things to behave? I was under the impression that with the move to the new Modinfo format, burying all of this within the files, that it wasn't going to be necessary to constantly change the actual filename of the SDZ. Keeping the SDZ the same would ease maintenance, especially for point releases.
iirc windows doesn't have non-locking file access mode (read: when a program reads/writes a file, it puts a lock on it so no other progs can edit it) so perhaps it was blocking the file overwriting (i didn't check archive mover source if it supports overwriting)
Re: ArchiveMover and the new Spring Modinfo.
No, I didn't have a lobby open. I just double-clicked on the file. It just refuses to replace the file by default, it appears.