BG3: Dismiss Multiplayer Custom Characters

Balancing party composition in Baldur’s Gate 3 multiplayer sessions often requires flexibility, especially when handling custom characters created by friends who have left the game. Patch 2 introduced a straightforward official method via Withers, but advanced users have console commands and mods for more control. This guide explores all options to keep your adventure on track.

Understanding Custom Characters in BG3 Co-op

In Baldur’s Gate 3, multiplayer allows drop-in co-op where friends join your campaign and craft unique characters scaled to your progress level. These custom avatars persist in the party even after the creator disconnects, turning into NPC-controlled allies under the host’s command. While convenient for solo continuation, this can clutter your roster, displace favored Origin companions like Astarion or Shadowheart, and limit new joiners if slots are full.

Pre-Patch 2, the sole remedy was reloading an earlier save before multiplayer activation, which was devastating for long campaigns started in co-op. Larian Studios addressed this in Patch 2, enabling hosts to dismiss these ‘wayward friends’ without restarting.

Official Method: Withers’ Wardrobe Feature

Patch 2’s standout addition is the Wardrobe of Wayward Friends, a camp-based tool for managing dismissed custom characters. Here’s the step-by-step process:

• Ensure the original creator is not currently in the session; Withers’ dialogue won’t trigger otherwise.
• Travel to your camp and locate Withers, the enigmatic undead merchant.
• Initiate conversation and select the option to discuss absent friends or party adjustments.
• A lore-appropriate dialogue appears, letting you politely send the target custom character to camp limbo.

To reinstate a dismissed character, return to camp and interact directly with the Wardrobe—a physical cupboard stocked with portraits of exiled allies. Click a portrait and hit ‘Drop’ to restore them to active duty. This wardrobe auto-handles act transitions, ensuring accessibility throughout the game.

Key Limitation: This sends characters to storage but doesn’t delete them permanently. Full party custom rosters remain capped at four, blocking Origin swaps unless space frees up. Available on PC and PS5 at Patch 2 launch.

Advanced Removal: Console Commands for Save Editing

For permanent deletion—crucial if you want to erase a custom character entirely—leverage the BG3 Script Extender (BG3SE) with console commands. This mod-heavy approach modifies save files directly but risks corruption if mishandled.

1. Setup: Download BG3SE Updater from GitHub (choose console variant). Extract and run as administrator.
2. Load Save Solo: Boot your game alone, load the target save, and highlight the custom character’s portrait (white outline confirms).
3. Access Console: Alt-Tab to the console window. Enter these sequentially:
   • osi (enables scripting)
   • MakeNPC("UUID-HERE") – Replace with UUID from prior output
   • SetHasDialog("UUID-HERE", 0)
   • SetOnStage("UUID-HERE", 0)
   • Osi.DB_Players:Delete("UUID-HERE")
   • Osi.DB_Avatars:Delete("UUID-HERE")
   • Osi.DB_PartOfTheTeam:Delete("UUID-HERE")
4. Verify & Cleanup: Return in-game; the character vanishes. Manual save as ‘Post-Delete’. Delete temp files from BG3SE folder to fix launcher errors.

This frees slots for companions or new customs, but backup saves first—botched UUIDs can brick files.

Mod Solutions for Effortless Party Control

Mods elevate management beyond vanilla tools. The ‘Recruit Any NPC’ mod via Nexus Mods uses BG3SE to grant a spell that toggles any character (including customs) in/out of party.

• Install via BG3 Mod Manager for safety.
• Cast on party member to dismiss (teleports to camp); recast to recruit.
• Works on multiplayer customs, ignores party limits, and handles act changes.

Community forums note persistent gaps: no vanilla permanent delete, though respec/magic mirror allows tweaks to lingering customs. Steam guides suggest dual-instance tricks for mid-campaign swaps.

Party Management Comparison Table

Best Practices for Multiplayer Campaigns

To preempt issues:

• Discuss party plans pre-session; designate ‘temporary’ customs.
• Host maintains backups at multiplayer milestones.
• For four-custom parties, prioritize deletions before new joins.
• Test mods/commands on duplicates to avoid main save mishaps.

Larian forums echo player frustrations from launch, fixed partially by Patch 2 but craving full delete UI. Future patches may expand this.

Frequently Asked Questions (FAQs)

Can I remove a custom character if their owner is online?

No, Withers’ option requires their absence.

Does dismissing affect achievements or story progress?

No impact; characters are treated as camp NPCs.

What if my party is full of customs and I want Origins back?

Use console delete or mods to purge slots.

Is PS5 wardrobe identical to PC?

Yes, Patch 2 parity confirmed.

Can I change a dismissed custom’s race/class later?

Via magic mirror respec, but body/race locked.

Troubleshooting Common Issues

• Wardrobe Missing: Ensure Patch 2+; rebuild camp.
• Console UUID Fails: Recopy precisely; restart extender.
• Mod Conflicts: Run BG3 Mod Manager’s conflict checker.
• Launcher Data Mismatch: Clear temp files post-edit.

These tools empower hosts to curate ideal parties, enhancing co-op replayability. Experiment safely to tailor your Forgotten Realms saga.