PvPBanger Services Forever

PvPBanger Service Finder Forever answers one question: where is the thing I need, and how sure are we. Every row carries the provenance of its coordinates, and only a row the client reported - or you confirmed - counts as verified.

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

• Fourteen categories - repair, general goods and food and drink, ammo and weapons and armour, reagents and enchanting supplies, profession trainers and supply vendors, class trainers, innkeepers, banks, auction houses, flight masters, mount vendors, recipe vendors, PvP vendors, and anvils, forges and crafting facilities.
• Three provenances, kept apart - client means the client showed us the NPC and its services while you stood at it, mapzeroth means a flight-master node taken from the vendored Mapzeroth engine (MIT, v2.0.5) and matched to the client's taxi data, and user means you added or corrected it. Map data never counts as verification.
• Discovery from real interaction - a row is written only from what the client actually reported while you were at the NPC: the frame that opened, the client's own answers such as the repair check, and the unit it named. It never reads a stock list and never marks a row verified for something it did not see. The recorded position is your own map position at that moment, and the row says so.
• Arrow and waypoint guidance - a draggable arrow that points only when the destination is on your current map, where the client gives both positions in the same space. A destination on another map gets a waypoint when the client accepts one and a plain statement that cross-zone routing is unavailable - never a bearing computed from two unrelated maps. Your own waypoint is saved before our pin and restored on stop, but only if ours is still the one selected.
• Coverage report - /pvpbfind coverage prints the total locations, how many are confirmed by the client or you, how many come from map data, the top zones and the count per category, and states that flight-master rows are unverified map data.
• Combat and popup rules - the window and the arrow refuse to open in combat, and combat never changes a protected frame.

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