PvPBanger Core Forever

PvPBanger Core Forever is the shared base every other PvPBanger Forever module loads. It is not a bar or a tracker on its own: it supplies the saved settings, the movable-HUD registry, the control panel, the minimap button, the window theme, the camera module, the guild-layer module and the error reporter that the feature addons draw on.

This package bundles no feature module. Install it first, then add only the Forever modules you want. Each feature module declares a dependency on PvPBanger.

Forever client target

Interface 16001, declared in a _Camelot.toc manifest. A Retail client cannot load these files, and a Forever install cannot pick up the Retail suite by mistake. The client reports Interface 16001 while presenting the mainline 12.x UI API, with GetBuildInfo reporting 1.60.x. Every optional API is probed rather than assumed: where this client lacks something (Toy Box, Mount Journal, aura data, tooltips, the quick-keybind frame, chat link handling, guild addon messages, guild roster, any layer API), the affected slot is hidden or reports unavailable, and /pvpbforever names what is misWhat it does

Control panel (/pvpb): category tabs listing every installed module with an ON/OFF switch and its own action button (SETTINGS, OPEN, FIND or TEST). Config windows raise, restyle and close on Escape, and lazy windows join combat suppression when first created.

Edition report (/pvpbforever): prints edition, Interface number, the client build from GetBuildInfo, the saved-variable names, which optional APIs are present or missing, any event registration the client refused, and which modules loaded.

HUD movers: unlock, move and lock HUD widgets, or hold Ctrl and drag one while it is locked; saved positions reset from /pvpb reset. /pvpb hud opens the settings and /pvpb lock or /pvpb unlock drives one widget by name.

Minimap button: a debounced click handler that toggles the panel on left click and opens a menu on right click, with show/hide, snooze and position controls (/pvpbminimap).

Error report (/pvpbbugs): a capturable report of Lua errors, including errors thrown by other addons, attributed to the addon the stack points at. !BugGrabber and BugGrabber are read when present and declared optional.

Camera module (/pvpbcam): an experimental extended-zoom request of cameraDistanceMaxZoomFactor 4.0 that shows the requested factor and the factor the client reports back as two separate numbers, with Restore previous and Restore default. It never lowers a value you already hold above 4.0.

Guild Layers (/pvpbgl): opt-in guild-channel presence sharing, showing participating guildmates, their zone, the layer label they typed themselves, when the report arrived, and a click-to-request invite. Sharing is off until you start it; there is no layer detection and no invented layer number.

Shared runtime: the Forever compatibility layer (probed globals, guarded secret-value reads, safe event registration, highest-learned-spell-rank resolution for ranked spells), the locale table, the dark original/Horde/Alliance themes, Escape-to-close input handling and a PvPBanger key-binding header.

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 the PvPBanger folder into Interface/AddOns, so it 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 folder in the character-select AddOns list.

Beta notice: this is a Beta Forever build for client Interface 16001, published for testing rather than as a release.sing.

PvPBanger Core Forever is the shared base every other Forever module loads. It is not a bar or a tracker on its own: it supplies the saved settings, the movable-HUD registry, the control panel, the minimap button, the window theme, the camera module, the guild-layer module and the error reporter that the feature addons draw on.

This is the core package and it bundles no feature module. The ten Forever folders ship together in the pack and each feature folder declares ## Dependencies: PvPBanger, so install this folder first and add only the modules you want.

What it does

• Control panel (/pvpb) - category tabs (BangerBar, PvP, Bounties, Dungeons, Tools) listing every installed module with an ON/OFF switch and its own action button (SETTINGS, OPEN, FIND or TEST). Config windows raise, restyle and close on Escape, and lazy windows join combat suppression when first created.
• Edition report (/pvpbforever) - prints edition, Interface number, the client build from GetBuildInfo, the saved-variable names, which optional APIs are present or missing, any event registration the client refused, and which modules loaded.
• HUD movers - unlock, move and lock HUD widgets, or hold Ctrl and drag one while it is locked; saved positions reset from /pvpb reset. /pvpb hud opens the settings and /pvpb lock|unlock <widget> drives one widget by name.
• Minimap button - a debounced click handler that toggles the panel on left click and opens a menu on right click, with show/hide, snooze and position controls (/pvpbminimap). Bounty badges appear only when the Bounties folder is installed.
• Error report (/pvpbbugs) - a capturable report of Lua errors, including errors thrown by other addons, attributed to the addon the stack points at. !BugGrabber and BugGrabber are read when present and declared optional, so neither is required. /bugnet toggles the net.
• Camera module (/pvpbcam) - an experimental extended-zoom request of cameraDistanceMaxZoomFactor 4.0 that shows the requested factor and the factor the client reports back as two separate numbers, with Restore previous, Restore default and the client's own zoom-out where it exists. It never lowers a value you already hold above 4.0, and /pvpbcam scan and /pvpbcam graphics report what the client exposes.
• Guild Layers (/pvpbgl) - opt-in guild-channel presence sharing: participating guildmates, their zone, the layer label they typed themselves, when the report arrived, and a click-to-request invite. Sharing is off until you start it; there is no layer detection and no invented layer number. Reports older than 90 seconds show Stale, sending is throttled, and replay protection is separate from the 300-second timestamp window.
• Shared runtime - the Forever compatibility layer (probed globals, guarded secret-value reads, safe event registration, highest-learned-spell-rank resolution for ranked spells), the locale table, the dark original/Horde/Alliance themes, Escape-to-close input handling and a PvPBanger key-binding header.

Forever client target

- Interface 16001, declared in a _Camelot.toc manifest. A Retail client cannot load these files, and a Forever install cannot pick up the Retail suite by mistake. - Mainline 12.x UI API surface. The repo's own compatibility note records that Forever reports Interface 16001 while presenting the mainline 12.x UI API, with GetBuildInfo reporting 1.60.x. The project id is WOW_PROJECT_MAINLINE (1); there is no Forever constant in the client. - Every optional API is probed rather than assumed. Where this client lacks something - Toy Box, Mount Journal, aura data, tooltips, the quick-keybind frame, chat link handling, guild addon messages, guild roster, any layer API - the affected slot is hidden or the module reports "unavailable", and /pvpbforever names what is missing.

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 plus the module folder 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

No required dependency. This is the core. It declares no Dependencies line and files the other modules against it; the optional dependencies it does list (!BugGrabber, BugGrabber, Blizzard_QuickKeybind) are read only when present.

Support

Issues, feedback and release notes: pvpbanger.com