Holy
Build around raid healing and the support tools your group expects from a Holy Paladin.
Explore raid-oriented Paladin talent paths for group content.
Community build example using the imported WoW Forever Beta talent snapshot.A raid Paladin build usually focuses on dependable contribution across a full encounter. The role comes first, while supporting talents help the wider group.
Pick the specialization that matches your assignment, then use the planner to compare complete and hybrid talent paths.
BuildForge turns an idea into a link your group can review before raid time.
Start with healing, tanking, or damage support so every talent choice has a clear purpose.
Use the talent tree to check prerequisites and compare the value of supporting branches.
Copy the build URL and send the exact allocation to raid leaders or teammates for discussion.
Three historical 51-point examples provide planning references, not current Level 30 raid allocations.
The Holy 31/20/0 page lists every selected rank in a healing-oriented historical reference. Protection has a separate 20/31/0 Shield example for a defensive group role. Retribution retains a historical 0/20/31 Judgment allocation for comparison; its Crusade ranks refer to a node absent from the reviewed 70245 tree. All three exceed the live Level 30 cap, so their current-plan buttons start a blank calculator rather than loading those 51 points.
These examples are not encounter-tested raid standards or currently playable complete Beta builds. The imported 69913 dataset and later official changes are shown separately. Treat the full allocations as historical references, check the talents relevant to your group in the current client, and plan within the level currently available.
Start with the assignment: primary healing, tanking, off-tanking, damage, or support. Then review what the encounter actually asks the Paladin to survive or provide. A talent that looks attractive in isolation can be less useful when another player already covers the same support, while a less obvious defensive or utility choice may matter throughout the encounter. The planner records the decision but cannot replace that group context.
Share the URL before raid time and ask reviewers to comment on individual ranks rather than replacing the whole build with a vague label. After a beta update, compare the saved setup with the current tree, confirm changed tooltips in game, and copy a new link if prerequisites or rank limits moved. That workflow keeps a raid build tied to evidence and a specific assignment instead of presenting one static page as permanent advice.