PvPBanger BuffBack Forever

PvPBanger BuffBack Forever watches for a buff you receive from another player and offers to give one back. It reads only public aura data, never guesses a hidden caster, and the return cast is always your own click or keypress on a secure button.

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

• Class-aware return buffs - twenty buff families across druid, mage, paladin, priest, warrior and shaman, matched to the receiving class. The primary buff is the highest rank you actually know; fifteen utility families (Divine Spirit, Shadow Protection, the paladin blessings, Thorns, Dampen and Amplify Magic, Fear Ward, Water Breathing and Water Walking) are opt-in and never replace your normal class buff unless you switch them on.
• Alert window - shows the sender, what they gave you, the suggested return and the current state, with Buff, Next and Dismiss buttons and a draggable position.
• One secure action - every return goes through a single SecureActionButtonTemplate button with its own binding (Banger Buff Back: next pending player). Party and raid senders are targeted by unit; anything else arms an exact-name target macro that restores your previous target afterwards. Arming is refused in combat with a stated reason.
• Audio and repeat control - sound on or off, sound kit preview, repeat delay of 30, 60, 120 or 300 seconds, and alert scale from 85 to 130 percent.
• Confirmation, not assumption - an entry is cleared when the return aura actually lands on that player, not when the button is pressed. Pending entries expire after 1800 seconds by default.
• Detection that this client allows - registering the combat-log event raises ADDON_ACTION_FORBIDDEN on Forever even inside a protected call, so detection scans public aura data for player, target, focus, mouseover, party and raid units and states plainly that hidden casters cannot be identified.
• Honest refusals - a class with no safe standard return buff is told so, a party-only buff is refused for a non-group sender, and settings show the key-binding state and the live diagnostics instead of failing silently.

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