Keeping Teammates Up
Healing throughput matters less than reaching the right target through crowd control and pressure.
A support-oriented Holy Paladin setup for WoW Forever PvP.
Historical 51-point 69913 reference; the live Beta cap is Level 30. Start a new plan instead of loading this full allocation.A Holy Paladin in PvP is usually keeping someone else alive under pressure, so the priorities differ from a raid healing setup even though the tree is similar.
Healing throughput matters less than reaching the right target through crowd control and pressure.
A support build that dies first helps nobody. The historical Protection support points show one future direction, not a current-cap allocation.
Where you stand decides whether you can heal through an enemy push or get separated from your group.
This page describes a direction rather than a verified PvP allocation. The 31/20/0 healing build is a historical 51-point reference and cannot fit the current Level 30 cap.
The published allocation supplies a concrete healing tree, while PvP changes the questions used to evaluate it.
The 31/20/0 Holy healing build records a historical 51-point allocation with 31 Holy and 20 Protection points. Its full page lists every selected rank and explains the healing-oriented structure, but those points exceed the live Level 30 cap and its 69913 tree predates later official tuning. Positioning, interruption pressure, target access, and personal survival can change the value of a rank even when the older talent name is unchanged.
Start a blank current-cap planner route, identify the Holy talents required for the support role, and then review which early Protection tools are actually available. Save a separate share link for each experiment instead of silently treating the published 51-point reference as a playable preset.
Decide whether the Paladin is the primary healer, a secondary support, or part of a hybrid plan. Check how many teammates must stay in range, which opponents can interrupt or control the healer, and what defensive answer remains when pressure switches targets. Those questions define the job of the build more clearly than a general promise of stronger healing.
Before sharing a setup, verify the current client tooltip for every talent that affects survivability, casting reliability, or team utility. Keep the 31/20/0 page as a historical reference and create separate links for current experiments. When a test reveals a conflicting rank, prerequisite, or effect, use the Feedback form to report the talent and the evidence so the data can be reviewed without turning one match result into a site-wide claim.