Do Mods Disable Achievements in Baldur's Gate 3?

If you've spent any time browsing the Baldur's Gate 3 community, you've probably seen this question come up — and for good reason. The answer isn't a simple yes or no. It depends on which mods you're using, how you're installing them, and when in your playthrough you add them.

Here's a clear breakdown of how the achievement system interacts with mods in BG3.

How BG3 Achievements Work by Default

Baldur's Gate 3 tracks achievements through standard platform systems — Steam, GOG, or PlayStation Network depending on where you're playing. These achievements fire based on in-game triggers: completing certain quests, making specific choices, defeating bosses, or reaching story milestones.

Under normal circumstances, the game communicates with the platform's achievement API in the background. As long as nothing disrupts that communication or alters the core game state in ways the system flags, achievements unlock as expected.

The Core Rule: Official Mod Support vs. Third-Party Mods 🎮

This is where the distinction matters most.

Larian Studios added official mod support to BG3 in 2024, built around a curated mod manager integrated directly into the game. Mods approved through this system — sometimes called "supported mods" — are generally designed not to disable achievements. Larian specifically structured this so players could use cosmetic mods, quality-of-life tweaks, and certain gameplay additions without losing their achievement progress.

Third-party mods, particularly those installed through external tools like BG3 Mod Manager or manually dropped into game directories, operate differently. These mods bypass Larian's official pipeline and can modify files, scripts, or game states in ways the achievement system wasn't designed to accommodate.

What Actually Triggers Achievement Disabling?

Not all third-party mods are treated equally by the game engine. A few factors determine whether a mod is likely to break achievement tracking:

Script Extender (BG3SE) The Baldur's Gate 3 Script Extender is a foundational tool required by many popular mods. Using it — even with otherwise benign mods — has historically flagged save files in ways that can interfere with achievements on certain platforms. Its presence alone has been enough to suppress achievement unlocks for some players.

Save File Modification Mods that directly alter your save file — adding items, adjusting stats, modifying character flags — are the highest-risk category. The game's internal consistency checks can recognize these alterations, and achievement triggers tied to "legitimate" progression may simply not fire.

Gameplay Overhauls Large-scale mods that change class mechanics, combat rules, or progression systems can inadvertently skip or corrupt the conditions required for certain achievements to trigger. This isn't necessarily intentional — it's a side effect of deep system interaction.

Cosmetic and UI Mods Texture swaps, UI reskins, and minor visual mods generally carry the lowest risk. These typically don't touch the game's logic layer, so achievement tracking proceeds normally. That said, even here there are edge cases depending on how the mod is packaged.

Does It Differ Between Platforms?

Yes — and this matters depending on where you're playing.

PC players on Steam and GOG have the widest exposure to third-party mods and therefore the widest range of outcomes. Console players are largely limited to what Larian's official mod pipeline allows, which makes achievement disruption less common but also limits mod variety.

The "Modded Save" Problem

One thing that catches players off guard: once a save file is flagged as modded, it often stays flagged — even if you later remove the mods. This means loading an old modded save to try for achievements after uninstalling mods usually won't restore achievement eligibility. The flag is written into the save data itself.

Starting a fresh playthrough without mods is typically the only reliable way to ensure clean achievement tracking if your current save has been touched by incompatible mods.

Which Mod Categories Are Generally Safe?

While no guarantee applies universally, the community has developed a rough working understanding of mod safety tiers:

• ✅ Generally safe: Official Larian-curated mods, cosmetic texture packs, audio replacements, minor UI tweaks
• ⚠️ Situational: Quality-of-life mods, companion dialogue expansions, camp decoration mods
• ❌ High risk: Script Extender-dependent mods, stat editors, full gameplay overhauls, cheat-adjacent tools

What Changes Based on Your Setup

The real-world outcome for any individual player depends on several converging factors:

• Which specific mods are installed (even within the same category, two mods can behave differently)
• Whether Script Extender is present in the game directory
• The platform you're playing on and how its achievement API handles flagged saves
• When the mods were added — before starting a run, mid-playthrough, or after a checkpoint
• Whether official or third-party installation tools were used
• How recently the mods were updated relative to Larian's own patches, since game updates can change how mods interact with core systems

A player running three cosmetic mods through the official in-game mod manager on a fresh save is in a very different position than someone six hours into a run using a Script Extender-dependent overhaul installed manually. Both are "using mods" — but the achievement implications are entirely different.

Your specific combination of mods, platform, and save state is ultimately what determines where you land on that spectrum.