A Footnote Steed if I do understand it correctly
the way JSGME works is it looks at the file a mod
is replacing and makes a back up of it so that when
you deactivate the mod it can revert to original
however if my suspicion of your case is correct then
what happened is that a later mod created a seperate
back up imprinted with the uber settings
so the thing would follow this sequence
-Uber activation and left active but unplayed
-mystery mod activation
-uber deactivation whereby jsgme didnt detect potetntial conflict
(with longer wakes mod in after uber I get warnings from jsgme
to deactivate longer wakes first)
-mystery mod deactivation restoring by its back up the uber settings.
I dont know if its correct but its my only working hypothesis.
whether or not jsgme is required to warn or not in all circumstances
I do not know so I couldnt say if it is a failure of jsgme or for that
matter uber
to my mind sequencing is just a detail of modding often missed.
I dont think there is a better solution than when taking away a
mod from your game deactivate all the mods underneath it
and after the one your taking out is removed put back the
ones your keeping that came out
that should prevent any recurrence of this issue as long as your faithful
about it.
regards.
MM
|