PvPBanger Bounties Forever

PvPBanger Bounties Forever shows the pvpbanger.com bounty board inside the game. It reads a snapshot you paste in, keeps it per realm and region, and warns you when that snapshot is stale. It never posts a claim, never uploads a screenshot and never fetches from the website by itself.

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

• Five tabs - List, Alerts, Nameplates, Sync and Capture, in an original PvPBanger window with search over target, realm or region and a filter to your own realm only.
• Snapshot import - paste the website's exported list and it is parsed as PVPB1/PVPB3 records; the parser tolerates clipboard tabs expanded to spaces, URI-encoded fields and the optional faction column. An expired snapshot says so and asks for a fresh import rather than showing stale rows.
• Honest labelling - the list states on its face that it is a website snapshot and that posted rewards are not verified payments.
• Alerts - an on-screen popup with horn or cash sound kits at 25, 50 or 100 percent volume, an adjustable repeat delay from 10 to 3600 seconds, a self-icon option and a /pvpbalerts test preview.
• Nameplate badges - a badge under a listed player's nameplate, built only from the modules' own textures so it cannot depend on a third-party nameplate addon, with its own settings page.
• Claim helper - a toast that builds the claim link for a row, selects it for Ctrl+C and offers a screenshot button. Nothing is submitted: you take the link to the website yourself.
• Peer sync - optional friend-to-friend list exchange over PVPB2 addon messages, off by default, paused during combat and refused with a stated reason when the client restricts addon messaging. Manual import keeps working when sync is unavailable.
• Realm grouping - region detection from the client (US or EU) with per-region realm groups and a manual override field, so realm matching is normalised rather than dotted.

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_Bounties 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