Why BuildForgeTools Exists
Build information for a new or changing game can be difficult to compare. Official announcements, client records, demonstrated gameplay, and community testing often arrive at different times. BuildForgeTools organizes that evidence into usable planners so players can explore a setup while seeing which details are confirmed and which remain under review.
We prioritize tools and reproducible build data over generic “best build” claims. A useful page should let a player inspect real mechanics, reproduce a configuration, understand its source and version, or prepare a build that can be completed when verified data becomes available.
Current Games
WoW Forever tools cover Paladin, Warrior, Mage, Hunter, Rogue, Priest, Warlock, Shaman, and Druid. Published calculators and build pages let players inspect talent ranks, follow point-by-point progression, compare example allocations, and open supported setups in a calculator. Available tools differ by class. Publication gates check each page’s declared data dependencies, and known source conflicts or missing recommendations remain visible.
Emberville has a pre-Early Access preview notebook for recording a combat direction, reviewed class and weapon references, and private notes. Its class-system and skill-inheritance source guides separate confirmed systems and observed records from unknown unlock rules, skill types, and compatibility. The notebook does not validate builds or inheritance compatibility, and observed skills with unconfirmed types cannot be selected as inherited active or passive skills.
How Game Data Is Reviewed
Game datasets are compared with official announcements, public client information, demonstrated gameplay, and consistent community research. Similarity to an older game or preview does not automatically prove that a name, value, position, requirement, or interaction is unchanged.
Records distinguish official information, client datamines, client-verified fields, community verification, and derived assumptions. The data pipeline preserves client build numbers, talent and spell identifiers, ranks, tooltips, prerequisites, and source references. Candidate data is validated and compared with the published version before a planner is updated. Page dates, source links, and version labels show what was reviewed; they are not a promise that every mechanic has been tested in game.
How Build Recommendations Differ from Game Data
A client record can establish a talent name, rank, position, or tooltip. It does not establish the best way to spend points for every encounter. Our editorial and community build examples are labeled separately from the records used to validate them.
Progression tools identify whether a point order is editorial or derived from a legal allocation. Comparisons show which talent ranks differ; they do not simulate damage or prove that one build performs better. Reused allocations are not presented as independent player builds or popularity statistics. If required data is missing, the tool explains the limitation instead of inventing a result.
Corrections and Maintenance
When a class, skill, talent, prerequisite, tooltip, or build explanation appears wrong, visitors can use the Feedback button to identify the affected game and provide evidence. Reports are reviewed before production data changes so one unverified message cannot silently rewrite a planner.
Build pages label recommendations and preview assumptions separately from verified game records. The goal is a transparent set of tools that can evolve quickly without presenting incomplete information as settled fact.
Independent Game Tools
BuildForgeTools is not affiliated with, endorsed by, or sponsored by Blizzard Entertainment, Cygnus Cross, or the developers and publishers of the games covered here. Game names, marks, and related material belong to their respective owners and are used only to identify the games and mechanics the tools help players organize.