Baldur's Gate 3's PS5 Shotgun Mod Fiasco: Why It's Still a Critical Warning for Console Modders in 2026

I've been playing Baldur's Gate 3 since its explosive launch back in August 2023, and as a professional gamer who's seen it all, I can tell you that not every community creation is a blessing. Even now, in 2026, the memory of the notorious Evelyn's Sweetheart shotgun mod still sends shivers down my spine. It wasn't just a mod that broke the game; it nearly broke entire campaigns on PlayStation 5, leaving players completely locked out. Let me take you back to that moment and explain why this cautionary tale still matters today if you're modding on consoles.

Back in late 2024, the Baldur's Gate 3 community was buzzing with excitement over mod.io integration bringing a flood of new mods to PlayStation 5 and Xbox. For many console players, this was a dream come true. Then, on October 19th, 2024, a mod known as Evelyn's Sweetheart shotgun went live. It promised the absurd joy of gunning down mind flayers with a trusty boomstick, and over 14,000 players eagerly downloaded it. But instead of a hilarious twist on Faerûn's tactical combat, they got a one-way ticket to a broken loading screen.

Within hours, social media lit up with desperate warnings. Redditor BladeC96 sounded the alarm on the Baldur's Gate 3 subreddit, urging PS5 users to steer clear. I read through thread after thread of frustrated players who could no longer launch the game – not just the modded save, but the entire title. Many were completely barred from reinstalling Baldur's Gate 3 on their console. Imagine losing access to a Game of the Year winner because of a single unsupported mod file. That's exactly what happened. One player, SpiritsJustAHybird, cracked a dark but perfect joke: "Baldur's gate knows you disrupted the timeline and the DM won't allow the guns lol." It was funny, but the reality was far worse for those staring at a black screen.

Why did a simple mod cause such a catastrophe? The answer lies in how console platforms handle shaders and custom files. The shotgun mod included shader additions that were never meant to run outside of a PC environment. Larian Studios' community moderator, SaloAtLarian, addressed the disaster with a statement that many of us still quote: "The team has re-checked this mod and unfortunately it does not pass our curation testing due to adding shaders, and should not have gone live. We removed the mod from console and Mac earlier today, as the files are not supported on the platforms. Apologies for the inconvenience and confusion!"

The apology was genuine, but the damage was done. PS5 players were hit the hardest, suffering complete game lockouts that required deep system intervention. On Xbox, the situation was slightly less dire. As BladeC96 noted, Xbox players could still access other campaigns as long as the offending mod remained inactive. However, crashes and critical errors still plagued those who had downloaded it. This platform disparity raised a critical question: If a mod can pass through Larian's curation process and still cause such destruction, how safe is console modding really?

I've been around long enough to know that mods are the lifeblood of PC gaming, but they've always been a double-edged sword on consoles. In 2024, Star Wars: Outlaws had a patch that PS5 users were advised to avoid, so the problem wasn't unique to Larian. Yet, Baldur's Gate 3 was different. This was a studio that had built an unprecedented reputation for player trust. They had a curation testing pipeline precisely to prevent such disasters. That the shotgun mod slipped through shattered the illusion of invulnerability.

Looking back from 2026, what can we learn? For starters, console modding has matured immensely. The tragedy spurred Larian to overhaul its shader validation for community creations, and other developers followed suit. Still, the core risk remains. Here's a quick breakdown of the key facts from that dark week:

• 🛡️ Mod Name: Evelyn's Sweetheart shotgun

• 📅 Release Date on Mod.io: October 19, 2024

• 🎮 Affected Platforms: Primarily PS5 (game unplayable), Xbox (crashes but recoverable)

• ⛔ Root Cause: Unsupported shader files bypassed curation

• 🔧 Larian's Action: Immediate removal from console and Mac; direct support for affected players

Even today, I tell every console player: stick to mods that explicitly state console compatibility and have a proven track record. Larian's mod.io integration is now far more robust, but the ecosystem is still community-driven. I often wonder, did that mod's creator realize the chaos a few lines of code could unleash? Probably not. Enthusiasm for adding wild content can blind modders to the technical jungle of cross-platform support.

This incident also underscores a timeless truth in gaming: no review system is perfect. Larian's curation failed once, but their swift response saved them. For us players, the lesson is to never blindly download a mod on day one. Wait for community feedback, backup your saves, and if you're on PS5, maybe think twice before introducing firearms to a world of swords and sorcery. The "shotgun fiasco" remains a cornerstone of Baldur's Gate 3 lore – not for its gameplay, but for its sobering reminder that even the best games can be broken by a single unchecked addition. So, as you scroll through the mod manager in 2026, please: let that shader-safe serenity guide your download finger. Trust me, your campaign will thank you.

SaloAtLarian's full statement

"The team has re-checked this mod and unfortunately it does not pass our curation testing due to adding shaders, and should not have gone live. We removed the mod from console and Mac earlier today, as the files are not supported on the platforms. Apologies for the inconvenience and confusion!"

In the end, Baldur's Gate 3 survived, and its community is stronger for it. But every time I hear someone mention "Evelyn's Sweetheart," I don't think of a romantic gift – I think of the day a shotgun nearly killed a masterpiece. ⚠️