Tes4Mod:BOSS Masterlist Manager

:Note: This utility has been succeeded by BOSS Userlist Manager.

:Note: As of BOSS 1.7, this utility is almost obsolete due to the userlist.txt feature in BOSS. In the  , follow the "BOSS User Rules ReadMe" shortcut to see usage instructions. Users transitioning from an existing BOSS setup can generate a userlist.txt file. For further instructions see #Transitioning to BOSS 1.7+.

BOSS Masterlist Manager (BOMM), created by Suruzal, is a wonderful companion to BOMM. It facilitates the addition of custom definitions to your local BOSS masterlist, and when run, it updates the masterlist by downloading the latest update from the web and reapplies your overrides to the latest version, as well. No longer will you have to grieve over needing to re-tweak your masterlist after an update. BOMM takes care of all of that for you. Suruzal also added options that extract various features from the masterlist (i.e, Bash tag suggestions pertaining to your mod list) to be viewed separately.

Installation

# Download BOSS Masterlist Manager.
# Create a folder for BOMM (or Word DOC Macros) in your documents folders, and drop the BOMM archive in it.
# Extract the BOMM archive there.
# Open 'BOMM Installer.doc'.
# Read the instructions, in their entirety, in order to install BOMM.
# Stop here, if you do not want to make a shortcut to launch BOMM.
# Right-click on BOMM.doc and choose copy
# Right-click on the desktop or quick launch bar and choose "paste shortcut"
# Before completing the configuration, copy the path to your BOMM file (not including the file name itself, just to the folder)
# Scroll down to the "Installation" section in order to configure Microsoft Word for your BOMM configuration.

Running BOMM

# Find and launch the shortcut for the BOSS Masterlist Manager (BOMM) you made ages ago.
# Once it loads, click "Run BOMM."
# When it finishes, you will see it populated the section under the third green header with your unrecognized mods.
# To define these in your master list:
## In the second (unrecognized definitions) section, copy and paste each unrecognized mod in a row.
## Now you have to decide which mods to load each plugin after. The best way to do this is to open up the BOSS Masterlist.txt file (in the Data folder) and look through it to find similar mods.
## Choose a plugin to load it after, copy the name, and paste it in the right column next to the relevant plugin.  
##:Note: a plugin can be designated to load after another unknown, just make sure its definition is declared after the one it needs to load after
# After defining all of your unknowns, choose "Run BOMM" again. It should prompt you with each plugins name if they were defined properly. 
#:Note: scroll down to the last couple of pages for more instructions about definitions
# You can also define overrides in the first section to override definitions in the original masterlist. For example:  \BeginGroup\: Supreme Magicka \BeginGroup\: L.A.M.E.\\ --moves the SM group after LAME
# After adding all of you definitions, choose "Run BOSS." (scroll to the bottom and see the empty unrecognized list)
# Click "Run BOMM" again after BOSS finishes runing. Now, looking at the third section, BOMM has removed all of the newly defined plugins.  
#:Note: If the BOSS Log or original masterlist is not updated the unrecognized plugins will not be removed from the bottom list, so you should re-run BOSS after adding definitions. Then run BOMM again with the updated log file.
# Close BOMM.

Transitioning to BOSS 1.7+

Since v1.7, BOSS has made its integrated masterlist management features robust enough to replace BOMM; however, due to the structural changes, users who have been using BOMM v5.4.6 and have lots of changes may want to preserve those changes during the transition to BOSS-only management. The instructions below walk through that process:

Stepping through the last run with BOMM

# Run the BOSS v1.7 installer and check the option to have it cleanup the old files
# Run BOMM
## If BOMM does its update thing at the start, just cancel once given the option.
# In the doc, click   from the toolbar.
## Point the 'OSS folder setting to the new  .
##* If Oblivion is installed to  , the full path is  
## Check 'Allow editing of BOMM System Settings'
## Change 'Boss Command' to point to  
##* If Oblivion is installed to  , the full path is  
## Click 'OK'.
# In the doc, click  
#* This creates a userlist.txt file with your rules in it to the BOSS folder.
# Close BOMM, saving your changes.

Finish the transition with BOSS

# Navigate to the new BOSS folder ( ).
# Open the BOSS User Rules ReadMe via the shortcut to it.
#* This file provides instructions for using Userlist.txt
# Run BOSS.
#* Users of Bash can launch BOSS through Wrye Bash so as to not conflict with Bash's   setting, but if you don't want BOSS to actually modify your load order this time, don't bother.
# If there is red at the top about bad rules in the Userlist.txt file, see the User Rules ReadMe for instructions, and some notes to bring users up to speed follow:
#* Group overrides in Userlist.txt only require the group name, not the exact test of the begin group line.
#** Example: Have Supreme Magicka load after L.A.M.E. in Userlist.txt  OVERRIDE: Supreme Magicka 
#**   If a plugin is set to load relative ( , ,etc.) a plugin that is not installed, the rule is invalid. This is a constraint BOMM did not have, so be wary of this change.
# Save the Userlist.txt file.


Now you can use BOSS as you normally would, and BOMM can be retired in favor of BOSS's integrated Userlist feature.''

See Also
BOSS

External Links
BOSS@TESNexus