PvPBanger Inventory Forever

PvPBanger Banger Bags Forever themes the combined bag the client already opens and adds an account-wide view of where your materials actually are. Blizzard keeps the item buttons, drag and drop, splitting, merchants and every secure action.

This download does not bundle its own copy of the core. In the Forever pack the ten folders ship side by side and this folder declares ## Dependencies: PvPBanger, so PvPBanger (Forever Core) must be installed and enabled alongside it or the client will not load this module.

What it does

• One predictable geometry - the skin owns a fixed column count and minimum row count so the bag frame cannot jump between unrelated native frame instances while Blizzard rebuilds the combined bag. Bag scale, columns and drawer size are adjustable within stated bounds.
• Five scopes - Current Bags, All Stored, Characters, Banks and Guild Bank, so the same view can show what this character carries or what the whole account holds.
• Account-wide storage index - bag scans, bank scans and guild-bank scans are stored per character and per guild, refreshed when a bank, guild bank or bag slot actually changes rather than on a timer.
• Tooltip ownership totals - item tooltips gain a "PvPBanger owned" total with an optional per-location breakdown and an optional freshness age per location.
• Item location search - /pvpinv find <item> prints how many are held and where, across characters, banks and the guild bank, and the window has the same search.
• Nothing invented - the module states that Blizzard handles live item actions while PvPBanger handles theme, stored views, search and totals.

Forever client target

- Interface 16001 in a _Camelot.toc manifest, so the Retail client cannot load it and this pack cannot load Retail settings. - Mainline 12.x UI API surface per the repo's own compatibility note: Interface 16001 with GetBuildInfo reporting 1.60.x, project id WOW_PROJECT_MAINLINE (1). - Optional APIs are probed, not assumed; anything the client lacks is reported instead of guessed at.

Installation

1. Exit the game completely. AddOn folders are read at launch. 2. Open your Forever client's Interface/AddOns folder. The Forever reference notes record the product as wow_classic_beta, so the directory is usually _classic_beta_; use whatever folder your launcher actually updates. This is not the Retail _retail_ folder. 3. Extract the archive and copy PvPBanger and PvPBanger_Inventory into Interface/AddOns, so each folder sits directly inside AddOns with no extra outer folder. 4. Do not copy the ZIP itself into AddOns - the game does not read archives. 5. Start the game and enable the folders in the character-select AddOns list. 6. Type /pvpbforever and copy the report. It prints the client build, the Interface number, the saved-variable names, every optional API that is present or missing, and any event registration the client refused.

Slash commands

Grepped from the shipped Lua in the 0.18.3 archive, not from the manifest:

Dependency plan

This project sets one Required Dependency: PvPBanger Forever Core, matching the ## Dependencies: PvPBanger line in its own _Camelot.toc. Without the core folder present and enabled, the client will not load this module at all - the .toc dependency is hard, not a suggestion. No other addon is required; optional dependencies are listed in the module's .toc and are used only when they exist.

Support

Issues, feedback and release notes: pvpbanger.com