Methodology and boundaries
About ForeverForge
This is an unofficial fan project designed to publish useful macro text without hiding uncertainty about a changing pre-release client.
Four separate layers
- EvidenceWhat an ability, talent, racial, form, stance, pet command, or client API actually exposes in a recorded build.
- Canonical macro recordsExact text plus purpose, targeting order, requirements, sources, build scope, test state, and limitations.
- Generated player filesReadable text and JSON exports produced from canonical records.
- Website viewsSearchable, derived presentation data that never becomes the authority for macro content.
Why the library may look incomplete
Forever class mechanics and talents may change across beta builds. The project therefore allows empty and partially complete class packs rather than filling gaps with copied Classic assumptions. “Researched” is not presented as “client-tested,” and a target build is not the same as a tested build.
What the site does not do
It does not automate combat, make rotation decisions, circumvent protected actions, write directly into your game installation, or claim official affiliation. The first release also has no accounts, uploads, tracking, or public-edit database.
Contributing evidence
Reports should identify the exact macro, exact Forever client build, observed behaviour, and reproduction steps. Do not include account identifiers or private filesystem details. A repository issue link will be surfaced when the project owner configures one.
Start with the current state
Review the nine-class matrix before assuming a macro category is complete.
Trademark notice
World of Warcraft and Blizzard Entertainment are trademarks or registered trademarks of Blizzard Entertainment, Inc. ForeverForge is not endorsed by, sponsored by, or affiliated with Blizzard Entertainment.