PvPBanger Banger Dungeons Forever is a dungeon browser that renders the map images the client already has installed. No artwork is bundled, no map is downloaded, and nothing is drawn where the client cannot supply a tile.
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
- Nineteen classic dungeons - Ragefire Chasm, Wailing Caverns, The Deadmines, Shadowfang Keep, Blackfathom Deeps, The Stockade, Gnomeregan, Razorfen Kraul, Scarlet Monastery, Razorfen Downs, Uldaman, Zul'Farrak, Maraudon, The Temple of Atal'Hakkar, Blackrock Depths, Blackrock Spire, Dire Maul, Stratholme and Scholomance, with the floor list and floor names each one actually has (Shadowfang Keep has seven, Dire Maul six, Blackrock Spire seven).
- Client-resident maps - the browser reads the client's own map-art layer textures for a 4x3 grid of 256-pixel tiles and draws them, so the window is labelled "client textures | original PvPBanger UI | no artwork bundled".
- Floor switching and panning - pick a dungeon, pick a floor, pan and zoom inside a resizable window with saved zoom and pan.
- Bosses and loot from the client - encounter names and mechanics descriptions come from the Encounter Journal functions when the client exposes them, and loot lists from the same source; bosses or drops the client will not report stay visibly unknown rather than being invented.
- YOU marker and floor following - when the client reports a usable map position and the artwork matches a known floor, the window shows
YOU: x, y | floor nand follows your floor. Manual browsing turns following off and "Use current dungeon" turns it back on. - Explicit unavailability - a missing map, an unmatchable artwork set, ambiguous floors or a withheld position each produce a stated reason instead of a wrong dot.
- Coverage scan -
/pvpbmaps scanreports how many complete floors and texture tiles the client actually has, per dungeon, plus whether the modern and legacy Encounter Journal, the map API and the texture file lookup are available.
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_Dungeons 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.1 archive, not from the manifest:
| Command | What it does |
|---|---|
/pvpbmaps |
Open the dungeon browser (open does the same) |
/pvpbmaps scan |
Scan client map coverage per dungeon and floor |
/pvpbmaps location |
Report your live position, or the exact reason it is unavailable |
/bangerdungeons |
Open the browser (second alias) |
/pvpb dungeons |
Open the browser from the control panel |
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