OBMM and new mod versions

[Mumin]

The Oblivion mod manager has an incredibly annoying feature: Whenever I overwrite a mod with a new version, OBMM puts the mod last in the load order though I obviously want it to remain where it was before the update. Does anyone know if OBMM can be made to keep the old load order?

[gregathit]

I think there is a setting that you can lock your load order.  However, you will need to remember to unlock it each and everytime you need to move anything around.

 

Wrye Bash offers more controls in this regard, as you can set time and dates for files and various other things.

[Mumin]

I find options to deselect "New esps always load last" or select "Never modify load order". Saving a mod still places it last though. Can Wrye Bash lock it, you say?

[movomo]

Saving a mod in CS, not overwriting with some other version? That's supposed to happen I guess. All you need to do is exporting/importing an olod file. ( or just memorize where it was before you edit the plugin, anyway)

If my memory serves tes4edit does not change the load order after saving.

[JSmith20142]

I check where it used to be immediately before saving the modified plugin (just open 'data' again and look).

[Mumin]

Well, moving it back to where it was before is what I do now but why...on..earth would anyone want the load order to change when saving in the CS? That's just bizarre.

 

Exporting/importing the load order sounds more convenient though. I was unaware of that feature. Thanks for the tip movomo!

[mem4ob4]

but why...on..earth would anyone want the load order to change when saving in the CS? That's just bizarre.

 

 

The load order is 'ordered' by the date stamp on the file.

OBMM and probably Wrye changes this date to insure you get the order you want.

The CS saves any changes you make to a mod with the current date stamp (common practice).

It (the CS) did not mean to give you a hard time. It's just doing its thing.

 

Mem

[Mumin]

 

but why...on..earth would anyone want the load order to change when saving in the CS? That's just bizarre.

 

 

The load order is 'ordered' by the date stamp on the file.

OBMM and probably Wrye changes this date to insure you get the order you want.

The CS saves any changes you make to a mod with the current date stamp (common practice).

It (the CS) did not mean to give you a hard time. It's just doing its thing.

 

Mem

 

Oh, so it is Bethesda's lack of proper ordering that is shining though here. Suppose it had been nice with automatic importing/exporting of the load order when starting/exiting OBMM then. (Actually, that was how I believed it worked. That was apparently wrong!)