---

SS2Tool now installs BMM, see here.

---

---

DEPRECATED, use DMM.

---

• Requirements
• Installation
• How to use
• Source
• Download

Requirements
- Windows Vista SP2 or later (v1.16+), WinXP or later (until v1.15)
- System Shock 2 v2.4 or later.

Installation
SS2Tool automatically provides the most recent version.
For a manual installation, extract/place the program in a folder of your choosing, and it's ready to use.

How to use
Launch SS2 Blue Mod Manager, press Select game folder... and select your System Shock 2 main folder.



Press Install mod archives... and select the mod archives to install. You can select multiple files at once using Shift and Ctrl.



Activate mods and arrange priorities (mod that is higher on the list overrides every mod below it). That's all, now you can press Exit and start game. You can also just close the manager - mods will stay loaded and activated.



If you want further information about a mod, you can press Lookup (WWW) to see its thread here on Systemshock.org or open a ReadMe file if present. If you have no further use of a mod, you can Delete it.

Source
For compiling your own version of SS2BMM, see https://github.com/pshjt/ss2bmm.

Download

Argh, okay sorry.

Yes, mods must be extracted. For each mod you want to add: "DMM\AnyModName\{mod files here}"

Glad to hear it

If you would like to make a switch to MM it's recommended, but not necessary. However, it will be clearer having all mods managed by MM than split between DMM and DataPermMods folders.

DMM mods will also override DataPermMods, which might not be desirable, and it's difficult to keep track what is installed in DataPermMods. Having mods installed both ways would be messy.

If you are getting error messages about missing DLL files, you need to install Visual C++ Redistributable for Visual Studio 2012.

This is not 100% accurate - specifically, you need 32bit version (x86) even if you have 64-bit Windows. I installed 64-bit version (since this is usually the way to go - if I have 64bit system so I am downloading 64-bit version if they are available) - and the mod manager would not work.

Direct link (worked for me, but it may be temporary): http://download.microsoft.com/download/1/6/B/16B06F60-3B20-4FF2-B699-5E9B7962F9AE/VSU1/vcredist_x86.exe

Other than that, great work!

Yeah, me too. That is why I was absolutely stumped when it did not work. As a last ditch effort I decided to install 32bit version (I was absolutely certain that I will see message: "This software is not compatible with your version of Windows") - and it worked.

I have all my mods merged together inside DataPermMods - so what is my best course of action? Should I move/delete/rename "DataPermMods" folder and then unpack all original mods into separate directories inside "DMM" directory?

Ok, and what about conflicting files? They will be overwritten by the "last" mod in the 'queue'? (i.e. if there are conflcting files in mods number 1 and 2, then files from 2 will be used?

I know this is an early version but it would be great if some future version would have some kind of information/warning "mod [xxx] and mod [yyy] both contain files [zzzzzzz]".

May I suggest to call that mod type "gamesys" in keeping with what it's called and tagged as on this site?
"Gameplay" correctly describes what these mods do, but I think consistency would help users more in this case.

When I click the "Open mods folder", how do I select the mods from there?

Nevermind, I just found it basically imports them automatically.

Next version will not require application restart after changes in DMM folder.