ForeverTalent Planner Covers Nine Classes With Daily Beta Data
By Indie Kings | October 4, 2026
Updated October 4, 2026: The planner at wowforevertalent.com is a free no account FOREVERTALENT PLANNER for WoW Forever talent builds across nine classes. The site states it is an independent fan project, not Blizzard verified.
Image: BlizzCon 2016 cosplayer. Credit: Wikimedia Commons, CC BY 2.0, Dutch Boyd.
A Free Planner For Nine Classes
The site calls itself FOREVERTALENT PLANNER, according to the fetch dated October 4, 2026. The fetch describes it as an independent planner for WoW Forever. The planner covers talent builds for nine classes with a point budget stated on the site.
The cost model is simple on the fetched page, with free access and no account needed. The fetch records no account requirement for either party when viewing or sharing. That no account structure applies to planning and to opening a shared link.
The class coverage is broad, with all nine classes listed with three trees each. The fetch lists Warrior as Arms, Fury and Protection. The fetch lists Paladin as Holy, Protection and Retribution. The fetch lists Hunter as Beast Mastery, Marksmanship and Survival.
The fetch lists Rogue as Assassination, Combat and Subtlety. The fetch lists Priest as Discipline, Holy and Shadow. The fetch lists Shaman as Elemental, Enhancement and Restoration. The fetch lists Mage as Arcane, Fire and Frost. The fetch lists Warlock as Affliction, Demonology and Destruction. The fetch lists Druid as Balance, Feral Combat and Restoration.
The point budget is stated as 51 talent points on the fetched page. The fetch ties points to character level from level 10 to level 60. The fetch states that level 30 provides 21 points and level 60 provides 51 points. The starting state shown in the fetch for Warrior trees is 0 of 51 with required level 10.
The Warrior view in the fetch names Arms, Fury and Protection trees at zero points each. Visible talent names in that view include Improved Heroic Strike and Deflection. No effect is described here beyond those names, per the fetch limits. The photograph in this article shows a 2016 cosplayer, not the planner site or any talent tree.
The data basis is stated as the 2 October Forever export, per the site fetch. The fetch states that data is updated daily with a changelog snapshot. The site marks the data as a beta snapshot, so final status is not claimed here. The site states it is an independent fan project.
The table below restates planner mechanics as documented on the site. Each standing value cites the site fetch as its source. No outside source is used for these rows.
| Feature | How the site describes it | Standing |
|---|---|---|
| Classes covered | all nine with three trees each | Per site fetch |
| Point budget | 51 points, level 10 to 60 | Per site fetch |
| Cost model | free, no account | Per site fetch |
| Drafts | one per class, preserved across classes | Per site fetch |
| Refunds | click learn, right-click refund, invalidating refunds blocked | Per site fetch |
| Row gating | five more points per deeper row, same tree only | Per site fetch |
| Compare to Classic | old description plus status flags | Per site fetch |
| Saves | browser local storage, named builds on device | Per site fetch |
| Sharing | copy link and copy for AI, link beats local draft | Per site fetch |
| Backup | JSON download and restore, nothing uploaded | Per site fetch |
| Data freshness | daily updates, 2 October export snapshot | Per site fetch |
| Blizzard verification | independent fan project, not Blizzard-verified | Site's own statement |
The table is a planning aid, not a recommendation of any class. The site does not require an account to read these values. The values above reflect the October 4, 2026 fetch.
How Points Move
The site describes a direct learn action by clicking a talent to learn a rank. The site describes a refund action by right click or Shift click to refund. Touchscreens use tap to inspect then tap to learn, per the fetch. Keyboard input uses Tab plus Enter or Space, per the fetch.
Row access is gated by prior spending in the same tree. Deeper rows need five more points in earlier rows of the same tree. Points in another tree do not count toward that gate. That same tree rule keeps each tree self contained for progression.
Arrows mark full rank prerequisites on the fetched page. A talent with an arrow needs the source talent at full rank first. The page blocks refunds that would invalidate later choices. That block preserves legal build order.
Draft scope is one draft per class on the site. Trying Mage preserves the Warrior setup, per the fetch example. Each class keeps its own draft in the browser. Moving between classes does not overwrite the prior class draft.
Level control runs from level 10 to level 60 on the site. Level 30 provides 21 points in the documented example. Level 60 provides 51 points in the documented example. Required level 10 appears as the starting requirement in the Warrior view.
The site presents 51 as the full budget at the top level. The Warrior example shows 0 of 51 at the start. Each tree starts at zero before points are assigned. Spending raises the total toward the stated budget.
The interaction model stays consistent across the nine classes. Click learns and right click refunds where permitted. Invalidating refunds stay blocked to protect later picks. Prerequisite arrows remain visible as gating cues.
Accessibility inputs are listed alongside mouse and touch. Tab moves focus and Enter or Space activates, per the fetch. Tap to inspect helps touchscreen users review before learning. These inputs apply to the planner controls as documented.
The planner does not recommend builds in this guide. Talent names are cited only as visible labels. Effects, ranks and power are not described here. Readers should check each talent entry on the site itself.
Compare To Classic
Compare to Classic mode highlights changes against older text. The mode shows the older description plus new, changed, moved or removed status. That pairing lets a reader see prior wording next to the current flag. The flag set comes from the site fetch.
Removed entries appear below their original tree, per the fetch. That placement keeps tree context while marking absence from the tree. The list position is below rather than inside the active grid. The status flag identifies the removal from that tree.
The site warns that removal from a tree alone does not establish that an ability disappeared from the game. That warning matters for readers tracking abilities across systems. A tree removal is a tree fact, not a game wide fact. The site states the limit in its own wording.
Recorded descriptions apply to their stated rank, per the fetch. A rank one note does not speak for rank two unless stated. Missing ranks stay unverified on the site. That rank boundary prevents overreading a single entry.
The compare view is a research aid for change spotting. Old description text sits beside the status label. New, changed, moved or removed labels sort the difference. Readers can trace what the site has flagged without guessing.
The mode does not claim final game data, since the site marks its set as a beta snapshot. Daily updates and a changelog snapshot track revisions. The 2 October export snapshot anchors the fetched version. Later exports may revise flags or text.
No build advice follows from the compare flags in this guide. A changed flag does not mean stronger or weaker here. A moved flag does not mean better or worse here. The flags are reported as site labels only.
The Honesty Rules
The site states explicit honesty rules for gaps in its data. Missing ranks stay unverified rather than filled by guess. Source estimates are labeled as estimates where used. Unknown percentages or durations are never calculated. These rules shape how the planner displays incomplete beta data.
The no calculation rule is central to the angle of this guide. The site does not derive a number to fill a gap. An unknown percent stays unknown on the page. An unknown duration stays unknown on the page. That restraint keeps estimates visible as estimates.
Source estimates stay labeled on the site, per the fetch. A reader can tell estimate from record. Recorded descriptions apply only to their stated rank. Old setups need a check of effect, rank and prerequisites per talent. That per talent check is listed as a site rule.
Tree removal limits are part of the same honesty set. Removal from a tree does not establish ability removal from the game. The site warns against that leap in its own text. The guide repeats the warning without adding game claims.
The table below restates those honesty rules in the site wording. The left column names the rule area. The right column gives the wording on the site. All rows derive from the October 4, 2026 fetch.
| Rule | Wording on the site |
|---|---|
| Missing ranks | stay unverified |
| Source estimates | labeled as estimates |
| Unknown numbers | never calculated to fill gaps |
| Tree removal | does not establish ability removal |
| Old setups | check effect, rank and prerequisites per talent |
The rules apply across classes and trees on the site. A gap in one tree follows the same unverified handling. A gap in another class follows the same no calculation handling. Consistency is the point of listing them together.
This guide adds no numbers beyond the site statements. Point totals and level thresholds come from the fetch. Daily update frequency comes from the fetch. All else is marked or omitted.
Saves And Links
Draft auto save uses browser local storage on the site. The draft persists on device without an account. Each class keeps its own preserved draft. Opening the planner later returns to the stored draft unless a link takes precedence.
Named builds save on device only and are excluded from shared links. A named build stays local to that browser. Sharing does not carry named builds along. That exclusion is stated in the fetch.
JSON backup download and restore is documented on the site. The backup file moves as a local file. Restore reads that file back into the planner. Nothing is uploaded during that process, per the fetch.
Sharing uses copy link and copy for AI, per the fetch. Copy link creates a shareable link for the current setup. Copy for AI creates text form for model input. No account is needed for either party, per the fetch.
Link precedence is explicit on the site. Opening a link takes precedence over a local draft. The shared setup loads first when a link is opened. Local drafts remain subject to that override rule.
Privacy scope stays local by design in the fetched description. Saves remain on device rather than on an account. Backup stays as a user held file. Nothing is uploaded in the described flow.
Draft preservation across classes reduces rework during comparison. A Warrior setup remains after previewing Mage. A Mage setup remains after returning to Warrior. One draft per class keeps the sets separate.
The level and point state travels with the draft as shown. Level 10 to 60 bounds the planner range. Level 30 maps to 21 points in the site example. Level 60 maps to 51 points in the site example.
Beyond The Trees
Extra sections on the site extend beyond talent trees. The fetch lists abilities, quests and class changes. The fetch lists racials, legacy perks and dungeons. The fetch lists map, items and professions. The fetch lists PvP, builds, updates, sources and changelog, plus a talent FAQ.
The talent FAQ sits with those sections as a reference. It addresses planner use as documented. This guide does not restate that FAQ beyond attribution. Readers should read the site FAQ directly.
Abilities and quests give context around talent picks without changing point rules. Class changes track revisions tied to daily updates. Racials and legacy perks sit outside the 51 point budget. Dungeons, map, items and professions broaden the reference set.
PvP and builds sections are listed on the site as separate areas. Updates, sources and changelog document provenance and revision. The changelog snapshot supports the daily update claim. Sources list where the site says its inputs came from.
The site solicits support via a buy me a coffee link. That mention appears once here without a hyperlink. No donation is recommended in this guide. The planner remains described as free with no account.
All section names above come from the site fetch. No section content is quoted at length here. No effect text is reproduced here. The list serves as navigation guidance only.
What Is Not Established
Several points remain not established from the fetch alone. Final talent values are not established because the site marks a beta snapshot. Launch timing is not established in this guide. Any beta date beyond the export snapshot is not established here.
Talent power is not established in this guide by design. No talent effect is described beyond names. No rank strength is compared. No build is recommended.
Game wide ability status is not established by tree removal alone. The site warning controls that reading. Removed from tree means removed from tree on the site. It does not establish removal from the game.
Estimates stay estimates where the site labels them. Unverified ranks stay unverified. Unknown numbers stay uncalculated. Those limits are repeated to prevent gap filling.
The table below groups common gaps with their standing. Each standing cites the fetch or marks verification need. No outside claim is added.
| Claim | Standing in this guide |
|---|---|
| Final talent numbers | Not established, beta snapshot per site fetch |
| Launch date or beta date | [NEEDS VERIFICATION] |
| Best build or spec choice | Not established, no recommendation in this guide |
| Talent effect beyond name | Not described, names only per limits |
| Game wide removal from tree removal | Not established, site warns tree removal alone does not establish it |
| Account or paywall for planner | Not required, free with no account per site fetch |
The guide omits what the fetch does not support. Anything else outside the verified block carries a verification tag or is omitted. That rule keeps the tool description tight. Readers can verify current text on the site itself.
FAQ
Is the planner free and account free per the site?
Yes, the fetch describes free access with no account needed for planning and for opening a shared link.
How many points and levels does the site describe?
The fetch states 51 talent points across level 10 to 60, with level 30 at 21 points and level 60 at 51 points.
How do learn, refund and gating work on the site?
Click learns a rank and right click or Shift click refunds, with row gating at five more points per deeper row in the same tree and invalidating refunds blocked.
What does Compare to Classic show?
It shows older description text plus new, changed, moved or removed status, with removed entries below their original tree.
How do saves and sharing work?
Drafts autosave in browser local storage with one draft per class, named builds stay on device, JSON backup downloads and restores locally with nothing uploaded, and an opened link takes precedence over a local draft.
What stays unverified on the site?
Missing ranks stay unverified, source estimates stay labeled, unknown numbers are never calculated, and tree removal alone does not establish game wide removal.
Bottom Line
The planner is a free no account tool for nine classes with 51 points and one draft per class. Compare mode, local saves, JSON backup and share links support review without an account. Data follows a daily update flow from a 2 October export snapshot.
The honesty rules are the reason to take the display literally. Unverified stays unverified and estimates stay labeled. Unknown numbers stay unfilled by calculation. Tree removal stays a tree fact until more is shown.
Use the site for layout and change spotting across the nine class trees. Check effect, rank and prerequisites per talent for old setups. Treat the beta snapshot as a snapshot, not a final record.
Sources: the planner site described here is FOREVERTALENT PLANNER at https://wowforevertalent.com/, fetched October 4, 2026, with daily updates and a 2 October export snapshot.