THE COBALT TAKE · EDITORIAL ASSESSMENT
Our take: reliable healing begins with reading the next event. Build a clear recovery plan before worrying about whether another healer topped a total-healing chart.
PRE-LAUNCH GUIDE Source reviewed 30 October 2026. Forever launches 4 November. Talent data is versioned; balance and gearing advice remain provisional.
A reason to plan incoming damage rather than wait for a nearly empty health bar.
An emergency decision that needs a clear place in your recovery plan.
A group-healing option to evaluate against the actual damage pattern and available level.
YOUR BUILD, YOUR DECISIONS
Druid talent planner
Explore all three trees with the recorded ranks, positions and prerequisites. Plan a build alongside the guide; an empty planner is not a recommended or simulated allocation.
Balance
0 points16 talents · 5 points unlock each next row
Feral Combat
0 points20 talents · 5 points unlock each next row
Restoration
0 points16 talents · 5 points unlock each next row
Nature's Focus
Rank 0Choose a talent to inspect its requirements.
Read rank effects in the beta reference ↗Click or tap to add. Right-click, Shift-click or press Minus to remove. Tier and prerequisite rules are checked before a change. Undo also restores the previous level.
Start with the first row, then open the talents your plan needs.
Talent data & scope
Functional tree data: ArenaMaster 1.60.1.70532 snapshot, retrieved 2026-10-30. Grid positions and ranks were cross-checked against Eternadex. Later snapshots can differ; this planner retains its stated version. Off-grid legacy entries are excluded from the visible tree. Our planner code and guide text are original. Full in-game effect text opens at the reference.
Read the damage pattern first
Before a dungeon pull, identify who is expected to take damage and what could unexpectedly change that. A tank under steady pressure needs a different response from a party member about to suffer one large hit. Healing becomes easier when you distinguish an ordinary health dip from a genuinely urgent event.
Our recommendation is to name your emergency option before combat starts. That simple habit reduces the chance of spending every tool on moderate damage and finding nothing ready for the encounter's most dangerous moment.
Talents should explain your healing plan
The documented Restoration toolkit combines periodic healing with direct recovery and emergency buttons. Inspect the talents around the spells you will actually use. Points that support long encounters, mobile healing or an urgent response solve different problems; do not treat their tooltips as interchangeable increases to a single healing number.
Some reviewed guidance still contains a level-30 variant, while the tree also supports level-60 planning. Read the variant label. A future capstone should not appear as a required step in the healing routine of a character who cannot yet learn it.
A practical healing priority
Establish useful periodic coverage where you expect damage, then watch whether it is enough. Let a healthy target benefit from healing already applied rather than immediately replacing it with an expensive extra cast. Use direct healing when the next event will arrive before that coverage can finish its work.
Keep Swiftmend and Nature's Swiftness in a recognizable recovery plan where available. The important skill is deciding when waiting becomes unsafe. Avoid turning a priority list into a rigid sequence that ignores the target's condition and the rest of the party.
Mana and gear: think beyond the next cast
Compare healing throughput with a usable resource pool and the length of the encounters you actually run. We are not assigning final numerical stat weights before launch evidence exists. When a run feels expensive, investigate avoidable overhealing and repeated unnecessary refreshes before assuming only more gear can solve it.
Tell the group when you need a recovery break. Keep supplies organized and consider the cost of utility as part of your healing budget. A healer who reaches the next dangerous pull almost empty has already inherited a problem from the previous one.
Use the rest of the Druid kit deliberately
Prepare sensible party frames and reachable controls for dispels, support and emergency targeting. You should not need to stop watching health bars merely to remember where an important utility spell lives. Agree on resurrection responsibilities and keep the relevant supplies ready where a spell requires them.
A control action can prevent more damage than another heal repairs, but it must fit the group's pull. Communicate the intention before redirecting or controlling an enemy. Your best support action is the one the tank and damage players can safely understand.
Review decisions, not just healing totals
After a death, ask whether the dangerous event was recognized, whether the target could have avoided it and whether your first response left a useful follow-up. Do not assume a larger healing total would have fixed a delayed decision. Likewise, a quiet stretch may mean the group played well rather than that you needed to cast more.
Common errors include refreshing before reading existing coverage, holding an emergency tool through the only event that required it and copying a higher-level spell routine into a character's incomplete kit.
QUICK ANSWERS
Restoration Druid questions
Should I cast continuously to maximize healing? +
Cast when the damage pattern requires it. Unnecessary actions can spend the mana and attention needed for the next genuinely dangerous event.
Is Wild Growth part of my low-level routine? +
Only after your character can actually access it. Distinguish a level-60 tree plan from the abilities available while progressing.
EVIDENCE BEHIND THE GUIDE
Sources & review
Reviewed 30 October 2026. Our text and recommendations are original editorial analysis of these references. The planner is a versioned data snapshot; a later beta change can alter a recommendation.
Spec mechanics and preparation; distinguish leveling variants from level-60 projections.
Reviewed 2026-10-30 · Open source ↗Class identity and broad changes; October 13 overview can lag later beta revisions.
Reviewed 2026-10-30 · Open source ↗Talent-tree structure and build context. Its starter recommendations cite an older beta build, not proven launch optimization.
Reviewed 2026-10-30 · Open source ↗