Documentation Index
Fetch the complete documentation index at: https://mintlify.com/bruhnn/BD2ModManager/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The profile system allows you to create multiple mod configurations and switch between them instantly. Each profile saves which mods are enabled or disabled, making it easy to maintain different setups for various purposes.How profiles work
Profiles are independent configurations that track:- Mod enabled/disabled states - Each profile remembers which mods are active
- Profile metadata - Name, description, creation date, and last modified date
- Active profile - One profile is always active at a time
profiles/ directory, with each profile having a unique ID (see src/models/profile_manager_model.py:518-539).
Profile data structure
Each profile contains:Default profile
BD2 Mod Manager creates a Default profile automatically on first launch. This profile:- Cannot be deleted
- Serves as the standard profile for managing mods
- Is automatically created if corrupted or missing
src/models/profile_manager_model.py:396-414:
Creating profiles
Name your profile
Enter a unique name for your profile (e.g., “PvP Setup”, “Story Mode”, “Favorite Characters”).
Profile names must be unique. The manager prevents duplicate names.
src/models/profile_manager_model.py:442-454:
Switching profiles
Switch between profiles to instantly change your mod configuration:Automatic state update
The mod manager immediately updates to show which mods are enabled in the selected profile.
src/models/profile_manager_model.py:501-516):
- The previous active profile is deactivated and saved
- The new profile is marked as active and saved
- A signal is emitted to refresh the mod view
- All mod enabled states are updated from the new profile
src/models/mod_manager_model.py:138-152:
Editing profiles
Modify profile details at any time:- Rename profile: Change the profile name (except for Default)
- Update description: Modify or add a description
- Modify mod states: Enable or disable mods in the profile
updated_at field tracks when the profile was last modified (see src/models/profile_manager_model.py:117-120).
Deleting profiles
Remove profiles you no longer need: When you delete a profile:- The profile JSON file is removed from disk
- The profile is removed from the manager’s cache
- The profile list updates automatically
src/models/profile_manager_model.py:456-476:
Profile metadata
Each profile tracks useful metadata:Timestamps
- created_at: When the profile was created
- updated_at: Last modification time (automatically updated)
Mod counts
- Total mods: Number of mods tracked in the profile
- Enabled mods: Number of currently enabled mods
src/models/profile_manager_model.py:108-115):
Use cases
Profiles are perfect for different scenarios:Character-focused profiles
Create profiles for your favorite characters:- “Angelica Mods” - Only Angelica character mods
- “Swimsuit Characters” - Seasonal costume mods
- “Main Team” - Mods for your primary team
Content-specific profiles
- “Story Mode” - Cutscene and dating scene mods for story enjoyment
- “PvP Clean” - Minimal mods for competitive play
- “Screenshot Mode” - Idle animations and special illustrations
Testing profiles
- “Testing New Mods” - Isolated profile for trying new mods before adding to main setup
- “Mod Development” - Profile for testing your own mod creations
Automatic profile updates
Profiles automatically stay in sync with mod operations:- Mod renamed: All profiles update their references to the new name
- Mod deleted: All profiles remove the mod from their configuration
- Mod added: New mods start as disabled in all profiles
src/models/mod_manager_model.py:389-392 for rename handling).
Profile storage
Profiles are stored as individual JSON files in theprofiles/ directory: