09-01-07, 11:57 AM
|
#795
|
Rear Admiral 
Join Date: May 2005
Posts: 12,987
Downloads: 67
Uploads: 2
|
Quote:
|
Originally Posted by JScones
Quote:
|
Originally Posted by Ducimus
Yeah if you delete a file from a mod before deactivating the mod, JSGME assume's it was a new file when you finally do deactive it, and removes the file from the active game entirely - result, stock file comes up missing.
|
I'm surprised the in-game file is ultimately deleted and not simply left behind. I'll do some tests and see if I can make it a bit more "user proof".
BTW, the stock file *should* still be in the MODS\!BACKUP folder, albeit with an extra suffix.
EDIT: Hmmm, in my tests, if I enable mod "A" which has files "B", "C" and "D", and then I delete file "C" from the mod "A" folder *before* disabling the mod, when I ultimately disable the mod, mod "A"'s "C" file remains behind with the file it replaced (if any) staying the in the JSGME !BACKUP folder. This is how I expected it to work - with the file deleted from the mod, it becomes invisible to JSGME, so JSGME doesn't see it when the mod is disabled and thus leaves the modded file behind in the game.
Unless I am misunderstanding the circumstances of the problem? I mean, if you *add* a file to a mod while it is enabled, and a file by that name already exists in the game, then I could understand JSGME deleting it when the mod gets disabled. The file would be deleted because there'd be no backup file to return (because the file wasn't part of the mod when it was originally enabled). Perhaps *this* is the scenario here? |
Jones, i could be entirely mistaken, OR, im thinking of an older version of JSGME. I've only upgraded to the newest version only recently in the past 3-4 weeks or so.
|
|
|