Options menu
[Previous] [Main] [Next]

This controls some obmm settings

Display warnings when running scripts:
If this option is checked, you will be warned about any script errors when activating mods. (Errors include invalid arguments, unknown functions and so on.)

Warn on script ini edit:
If this option is checked, you will be warned when a mod script attempts to modify oblivion.ini.

Show data files warnings:
If this option is checked, you will be warned about any actions which could cause loss of data. Such actions include deleting or cleaning mods, or deactivating mods.

Show esp deactivation warnings:
If this is checked, a warning will be displayed when trying to uncheck an esp which belongs to an omod.

Display omod info before installation:
Normally, when you double click an omod from outside of oblivion mod manager, obmm will install it automatically. If this option is checked, instead of installing it, it will offer to display the mod information, and then give you a change to cancel the installation. The information displayed is the same as if you rightclick an omod and click 'info'.

Lock FOV at 75
If this option is checked, obmm will automatically set the default fov line in oblivion back to 75 each time obmm is shut down. This is useful if you change oblivions fov in game using the setini command, as leaving the ini fov line at something other than 75 will misalign menus.

Compression boost
When using 7-zip style compression, this slightly increases compression ratio at the expense of slower compression speeds.

Track conflicts
If this is unchecked, all inactive omods will display green, and you will not get any advance warning of conflicts when activating an omod. Unchecking this can greatly speed up obmm. The 'view data conflicts' context menu item and the 'file xxx is already owned by omod yyy. overwrite?' dialogs will continue to work as normal.

Autoupdate conflicts
Checking this has an identical function to clicking 'batch actions|update conflicts' after activating/deactivating every omod.

Update unparented esp headers
If this is checked, obmm will rescan the header info (author and description) of every esp which is not part of an omod on each startup. If it is unchecked, the header info will be cached, and will not be updated correctly if you overwrite an esp outside of obmm. If you have many esps but don't use omods, checking this option may significantly increase obmm's starup time if you use many esps which are not part of omods.

Safe mode
Safe mode is obmm's default state, and is designed to allow you to use normal mods in conjunction with omods without obmm having a fit. In safe mode however, obmm can take a significant amount of time to start up, so the option exists to put obmm into its 'unsafe' mode. Never make changes to your data directory or obmm directory by hand while running in unsafe mode. This includes adding new files, removing files, modifing files, deleting omods from your omod folder or even something simple like changing the timestamps on esps. If you do, there exists the possibility of corrupting obmm's save data.

The extra checks which are performed while in safe mode are:
·Check for omods which have been manually removed from the omod directory and perform a forced deactivate to remove their associated files from your data folder  
·In unsafe mode, right click on the omod and click delete instead of deleting it from outside of obmm.  
·Load any omods which have been manually placed into your omod directory.  
·In unsafe mode use command line arguments or the load button to load new omods. Newly created omods will still be added automatically  
·Rescan unparented headers to make sure their description is up to date  
·In unsafe mode, click 'batch actions|rescan esp headers'  
·Scan for new esps which have been added to the data folder manually, or esps and other data files which have been removed manually  
·In unsafe mode, you must not manually install mods. Everything must be done through obmm  
·Check the plugins.txt file for any plugins whose activation has changed since the last time obmm was run  
·In unsafe mode, any changes to esp activation must be made through obmm  
·Check the timestamps of mods and update your load order accordingly  
·In unsafe mod, you must use obmm to adjust your load order. Any changes made by other applications will be lost the next time obmm is launched  
·Note that this effectively provides a copy of wyre bash's load order lock feature.  

Remember that if you make a change to your data directory while in unsafe mode, you can use the '-safe' command line parameter when running obmm to force it back into safe mode.

Use background process killer
If this is unchecked, clicking launch oblivion will immediatly launch oblivion/obse, or will execute your command line, if one is provided. If this is checked, obmm will first display the background process killer, which can be used to shutdown unwanted services and processes before launching oblivion.

Allow additional script types
If this is checked, omods will be allowed to use python, c# or vb for scripts, instead of obmm's usual scripting language. This is currently a beta feature, and there are probably security issues.

omod groups:
These options control the groups into which you can sort omods. The list box contains a list of all current groups. To create a new group, type into the box and click add group. To delete a group, select a group from the drop down list and click delete group. To rename a group select the group you want to rename, type in the new name and click rename. To change the font used by a group on the main panel, choose a group from the drop down menu and click 'set font'. You are limited to a maximum of 60 groups. Clicking clear will delete all group information.

Move omod folder
This option lets you move your omod directory to a location away from the default 'obmm\mods'. This is most useful for storing mods on a seperate drive if space on your main drive is limited.

Move temp folder
This option lets you move the temp directory used by obmm when you pack or unpack omods. For best performance, this should be on the same drive as your oblivion installation. Having it on the same drive as your omod directory should have little impact on performance.

Use default temp folder
This option will reset obmm's temp directory to the windows default. For windows xp, this is usually 'c:\documents and settings\local settings\temp'.

Oblivion command line
If this is left empty, clicking 'launch oblivion' on the main form will immediatly launch oblivion/obse. If there is text here, it will be executed as if you have typed it into the command line instead.

Resets all options back to their defaults. Be careful - this will wipe all omod group info, and all other settings, not just the ones displayed on the options menu. omod activation data will not be lost.