The default VTMB script for Mod Organizer 2 cannot access folders such as Bin and Unofficial_Patch, and struggles with mods that span multiple folders. This updated plugin fixes both of these issues. MO2 now reads data from the game root, instead of the Vampire folder, granting the installer access to the entire game directory. Additionally, all Unofficial Patch folders (including the SDK and documentation folders) are recognised and writable.

This plugin should account for any non-overhaul mod. If the MO2 installer pops up with a folder structure error, simply restructure the folder until it matches the folder layout determined by your game root. If you don't know what this means, please refer to this video: https://youtu.be/0kxp4oTsD6Q?si=CvRUz13wAsvyqoTD
While this tutorial is designed for STALKER Anomaly, the interface is identical.

My hope is that MO2 with this plugin is now viable for Bloodlines. It is best suited for small/medium sized mods, like skin replacements, tweaks, maps, etc. The ability to enable and disable individual mods in a seperate instance is especially fantastic for troubleshooting. It's also very encouraging to be able to auto-download a bunch of mods straight from the Nexus and install them with a couple of clicks, with no need for manual installation.
For overhauls, however, please stick to manual installation and the UP mod loader. I have no idea how overhauls with dedicated folders will be read from the game root, the save directory is instanced (which might lead to auto-save corruption) and MO2 is unlikely to recognise the mod data structure.
If you're in the doubt, the rule is this:
Mods that are pasted straight into an existing vanilla or UP folder (which is the vast majority of them) will work.
Mods that instantiate a new folder in the game root will likely NOT work, use the UP loader for these.

Installation

1. Create a new instance in Mod Organizer 2, choose "Create a global instance", and choose VTMB from the game-list (it should appear automatically, alongside your other MO2 compatible games). If your installation is in a non-standard location, you will need to browse to it manually.
2. Name the instance, and choose the following when prompted: Disable profile-specific .inis AND profile specific save games, keep automatic archive invalidation enabled (not used for this game, but I keep it enabled for safety). Save the instance path wherever you want, although I'd recommend creating a dedicated MO2 instance folder with a VTMB instance subfolder. Don't change the downloads, mods, profiles, or overwrite paths if prompted. Link to your Nexus account if you haven't already. Finish and launch the instance.
3. Once you launch the instance, skip and close the tutorial if prompted, then click on the dropdown to the left of the Run button at the top left. Select <Edit...>, and add -game Unofficial_Patch to Arguments under the Vampire - The Masquerade: Bloodlines tab. Click Apply, then OK. Now close MO2.
4. Navigate to your MO2 application installation (not your instance folder!) and follow this path: plugins\basic_games\games
5. In this folder, paste the updated game_vampirebloodlines.py and overwrite when prompted.
6. Reopen MO2, the Data pane on the right should now show the Bin, Unofficial_Patch, and Vampire folders, as well as Vampire.exe. If so, you're ready to install mods and play!