Bagnon Not Working | Fixes That Get Your Bags Back

Bag chaos isn’t fun when you just want to play. This guide gives you clear, field-tested fixes that work on Retail, The War Within, Classic Era, Season of Discovery, and Cataclysm Classic. You’ll see why the issue happens, how to repair it fast, and what to try next if the first fix doesn’t stick. Steps are grouped from fastest to deeper repairs so you can stop as soon as bags behave.

Quick Wins Before You Dig In

Quick check: Start with three actions that solve most cases in under five minutes. They fix bad files, missing dependencies, and clashing modules without touching your other settings.

• Update From CurseForge — Install the current Bagnon release for your exact game flavor (Retail, Classic Era, Season of Discovery, or Cataclysm Classic). Patch days change bag events; a new zip often restores normal behavior.
• Install And Enable BagBrother — Keep the companion module BagBrother on. Bagnon relies on it for item caching and character tracking; without it, windows can fail to build.
• Disable Other Bag Controllers — Turn off anything that replaces or skins bags: ElvUI bags, AdiBags, ArkInventory, Sorted, or any “one-bag” module. Only one bag controller should run at a time.
• Reload The UI — Type /reload and test again. A reload re-hooks bag events after changes and clears hiccups from updates.

If bags open after these steps, you’re done. If not, move to the next section and work through the fixes in order.

Bagnon Not Working Fixes For Retail, Classic, And TWW

Deeper fix: Follow this sequence. Each step targets a common failure point—wrong flavor, missing files, layout corruption, or addon clashes. Stop as soon as your bags open and respond to clicks normally.

1. Match The Addon To Your Game Flavor — Open your addon manager and confirm the installed build matches Retail, Classic Era, Season of Discovery, or Cataclysm Classic. Retail zips won’t load on Classic branches, and Classic zips won’t load on Retail.
2. Confirm Dependencies On The AddOns Screen — At character select, click AddOns. Tick “Load out of date” if you’re testing a fresh patch. Ensure Bagnon, Bagnon_Config, and BagBrother are enabled for the character.
3. Turn Off Duplicate Controllers — If you use ElvUI, open ElvUI settings and disable both the bag and bank modules. Avoid running two bag systems; they compete for the same events and frames.
4. Reset SavedVariables — Exit the game fully. Go to World of Warcraft/_retail_/WTF/Account/<ACCOUNT>/SavedVariables/ (use the matching folder for Classic flavors). Delete Bagnon.lua and Bagnon.lua.bak. This clears corrupt layouts, off-screen positions, and old per-character toggles. Launch the game and test.
5. Clean Reinstall The Addon — With the game closed, remove Interface/AddOns/Bagnon and Interface/AddOns/BagBrother. Reinstall both from the official project page. Mixed files from earlier zips cause frame errors and silent failures.
6. Minimal Test Session — Disable every other addon. Log in with only Bagnon and BagBrother enabled. If bags open, the base is working. Re-enable the rest in small batches to find the clash.
7. Short-Term Fallback — If you need to raid or farm right now, switch to Blizzard’s combined bags in Settings → Controls. It’s not as flexible as Bagnon, but it keeps you playing while you sort the root cause.

Why Bagnon Breaks After A Patch

Bag addons hook inventory events, tooltips, and frame names to draw one clean window for all containers. Expansion launches and point releases adjust those events and the security around them. When names or flows change, a bag addon can’t listen correctly, so your bag key does nothing, the frame flashes and disappears, or the bank opens while inventory stays silent.

Clear sign: the AddOns list shows Bagnon enabled, yet pressing the bag key opens nothing, or you see a flicker and the UI stops responding until a reload. That points to a broken hook or a module clash rather than a profile issue.

• Missing BagBrother — Bagnon expects BagBrother for cached data and cross-character counts. If it’s missing or disabled, features break and the window can fail to build at all.
• ElvUI Bag Module — ElvUI can take over bags on its own. If both run, one usually blocks the other. Pick one bag solution to avoid event tug-of-war.
• Out-Of-Date Or Mixed Files — Old libraries left in the addon folder produce odd runtime errors. A clean reinstall removes stray files and restores a consistent code path.
• Damaged Layout Data — Corrupt SavedVariables can pin the frame off-screen, lock it to zero size, or crash right after opening. Resetting the Lua file fixes that without touching your other addons.

When bagnon not working reports spike right after a patch, it usually traces back to one of these buckets. Updating the zip, clearing the layout file, and turning off a competing controller fix the bulk of cases.

Clean Reset: Layouts And Clicks

Goal: wipe only Bagnon’s settings and layout while leaving the rest of your UI intact. This step is safe and reversible if you make a quick backup first.

1. Close The Game — Fully exit to desktop. The game writes SavedVariables only on logout or /reload.
2. Open The SavedVariables Folder — For Retail use World of Warcraft/_retail_/WTF/Account/<ACCOUNT>/SavedVariables/. For Classic branches, open the matching flavor path.
3. Back Up The Files — Copy Bagnon.lua and Bagnon.lua.bak somewhere safe. If you dislike the reset, you can restore them later.
4. Delete Those Two Files — This clears positions, column counts, filters, and per-character overrides that can break after a big update.
5. Launch And Test — Log in and press your bag key. If the window opens and clicks respond, the old layout was the culprit.

Still stuck? A clean reinstall removes lingering libraries and mixed files. Delete the Bagnon and BagBrother folders inside Interface/AddOns/, then reinstall fresh. This step removes half-updated code that survives normal updates.

Conflicts To Rule Out

Some clashes show up again and again. Testing them first saves time.

• ElvUI — Open ElvUI settings, turn off both bag and bank modules, and disable any ElvUI skin that also touches bags. If bags now open, keep Bagnon as the sole controller. If you prefer ElvUI bags, leave Bagnon off to avoid duplicate hooks.
• ConsolePort — Gamepad mapping can collide with bag keybind handling. Test with ConsolePort disabled. If the freeze vanishes, remap the target-frame binding or exclude the bag key from ConsolePort’s profile.
• Tooltip Mods — UI addons that rewrite tooltips (Pawn, TipTac, and similar) sometimes trip during rapid bag updates. Test with those off. If behavior improves, add them back one by one and watch for the return of the glitch.
• Skin Packs And Suite Compilations — Large skin suites move frames and change scale. While you troubleshoot, run only one skin to keep the bag frame where Bagnon expects it.

When you find a clash, pick the controller you want to keep and disable the other. Two bag systems at once always invite trouble.

Recent Patch Issues And Reliable Workarounds

Big updates across Retail’s The War Within and the Classic branches shook up inventory events and frame behavior. That led to common reports: the bag key does nothing, the window opens for a moment and vanishes, the bank works while inventory stays locked, or the addon disappears from the list for a specific flavor. The fixes below match those symptoms.

Symptom	Likely Cause Or Fix
Bag key does nothing	Update Bagnon and BagBrother, enable the dependency, then test without ElvUI bags. If still broken, reset SavedVariables and try again.
AddOn list shows Bagnon, but it won’t load	Wrong flavor selected in your manager. Install the build that matches Retail or the correct Classic branch.
Cataclysm Classic build disappears after updating	Grab the corrected release. A specific May build drew reports until a replacement landed.
Bags open, then the UI freezes on input	Known conflicts with ConsolePort or aggressive bag skins. Test with those off and re-enable slowly.
Bank opens, inventory stays closed	Mixed files or a broken layout. Do a clean reinstall and delete the layout files.

When a hotfix lands and the addon lags behind, use the built-in “Combine Bags” toggle for a night. If you need an addon with sorting while you wait, AdiBags and ArkInventory are steady stand-ins. Once Bagnon updates, swap back and keep only one controller active.

Settings That Keep Bags Stable

Once everything opens, a few habits keep bags smooth through future patches.

• Use Character-Specific Settings Only If Needed — Per-character profiles can drift after structural changes. Start global, then enable per-char only where it adds real value.
• Trim Plugins — One bag controller plus one skin is enough. Add stylistic extras later, one at a time, so you can spot the add-on that tips things over.
• Keep Config Handy — Type /bagnon config to adjust columns, size, sorting, and bank behavior without hunting across menus.
• Use Clean Reinstall After Big Breaks — When behavior turns strange right after a major patch, delete the two addon folders and reinstall fresh. That ensures you aren’t running a half-updated library set.
• Capture Details When You Need Help — If you still see “bagnon not working” after a clean reset, note the game flavor, Bagnon version, and any Lua error text. That information lets maintainers or fellow players point you at the right fix fast.

Community threads, project issues, and the official download page line up with the fixes here: keep BagBrother enabled, reset the layout file when frames go missing, avoid double controllers with ElvUI, and match the zip to your branch. Once those are handled, most bag woes vanish.

If you’re mid-session and just need a safe fallback, enable the built-in combined bags until the addon catches up. It’s a two-click pause button while you sort the root cause. When everything’s stable again, return to Bagnon and stick to a single controller to keep it that way.

Searches like “bagnon not working” tend to boil down to three roots: wrong flavor, missing BagBrother, or a second bag system trying to do the same job. The steps above tackle all three with minimal fuss so you can get back to looting instead of debugging.