PvPBanger Cooldowns Forever

PvPBanger Cooldowns Forever does not draw a cooldown display of its own. It adjusts the four cooldown viewers the client already has, so the live cooldown data, the tracked spell list and the Edit Mode placement all stay Blizzard's.

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

• Four viewers - Essential, Utility, Tracked buff icons and Tracked buff bars, each found by its client frame name and skipped politely when this client has not created it yet.
• Independent sizing - a scale slider per viewer from 50 to 150 percent, stored separately, so one viewer can shrink without touching the others.
• Shared opacity - one slider from 20 to 100 percent across all four viewers.
• Placement left to Blizzard - using Edit Mode for position is stated in the window, because this module never moves a viewer.
• Scan - reports whether the cooldown-viewer API exists, whether the Blizzard_CooldownViewer addon is present, which viewer frames have been created and how many child frames each has, plus the spell count per Enum.CooldownViewerCategory set where the client exposes it.
• Combat behaviour - every scale and alpha write is refused while the player is in combat lockdown, queued instead, and re-applied on PLAYER_REGEN_ENABLED; viewers that appear later are picked up by an OnShow hook.
• Reset - restores the shipped sizes and opacity and says explicitly that Blizzard spell selections and positions were preserved.

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