Forever’s racial and class changes challenge character plans

If an older guide has already settled your Forever race, class and talents, open that plan once more. The October 15 beta update changes both racial abilities and how classes operate. Some differences appear in character statistics; others affect what a player brings to a group and how combat feels.

This article selects decision-relevant examples from Blizzard’s development notes. It is not a complete changelog or a class ranking. Forever remains in beta, so even a revised plan should leave room for further adjustments.

Race selection is a different calculation

Human Sword Specialization becomes Ruthless: 2% critical strike chance. Orc Axe Specialization becomes Savage: 1% critical strike chance. Tauren Endurance and Dwarf Earth Fury grant 2% increased critical damage and healing, while Skyborne Wind Blessed rises to 3% haste.

There is an easy distinction to miss: the chance of a critical strike and the strength of a critical strike measure different things. Their percentages cannot simply be placed on the same scale. Your class abilities, equipment and preferred activities also affect the result.

Our advice is to consider a race’s full set of tools before changing your character plan. A single percentage cannot tell you how much you value an active ability, movement or the appearance of the character you will spend time with. If a particular weapon type previously decided the choice, that specific reasoning now deserves another look.

Raid-wide buffs change the roster question

Moonkin Aura, Leader of the Pack and Trueshot Aura become raid-wide, alongside several Shaman totem effects. That raises a practical question beyond a small movement in someone’s damage numbers: why is a particular character assigned to a particular party?

When party boundaries no longer distribute every benefit in the familiar way, an old roster template needs its assumptions checked. Our interpretation is that the conversation should consider available effects alongside the players themselves. A class name alone does not tell the group what a particular build contributes.

This does not establish that every party restriction has disappeared, or that multiple sources of the same effect stack freely. Check the description of the ability you actually need. A little attention before the session can prevent a much longer argument when the raid is ready to begin.

For a raid organizer, it is useful to write down the reason behind a placement. “We need this effect here” can be re-evaluated after a patch. “This is how the old spreadsheet arranged it” is much harder to improve because the underlying assumption has been lost.

Mage and Hunter changes deserve a feel test

Mage gains Frost Blast at level 24, a 1.5-second cast with a 40% slow. Hunter Auto Shot requires half a second standing still before firing. Both are good examples of changes that a damage table alone cannot explain.

Try a familiar combat situation and pay attention to when you move, when you stop and what happens after an input. Placing a new spell in an old slot without thinking about its purpose can hide the meaningful difference. A timing adjustment may also feel larger than a numerical adjustment at first, even if it becomes natural with practice.

That is our suggestion for testing, rather than a report of our own play session. Useful feedback describes the situation: for example, the pattern of movement in which a shot feels unclear. “The class is ruined” gives a developer much less to investigate.

Paladin gets more precise Salvation control

Salvation and Mass Salvation replace their Blessing versions, while Revoke removes the effect from a selected group member. This is particularly interesting where different players need different threat management. The latest implementation details are in the beta update.

Blizzard’s separate Paladin deep dive explains the design around Seals and Judgements. It is useful background, but a later development note matters more for individual values. A reference to an upcoming change left in an earlier overview does not establish that the change is still absent from the beta.

Before joining a group, a Paladin player could usefully check the practical setup: are the required abilities on the action bars, do they target as expected, and does the group understand which effect is being discussed? An old name in a macro or a conversation can survive longer than the mechanic it describes.

Keep the character plan editable

Good preparation starts with three questions: which role do you want, who will you play with, and which activities are you looking forward to most? Then consider which current numbers support that choice. A rapidly changing beta value is a fragile foundation for a character you hope to enjoy for a long time.

Writing down your reasoning can help. If every patch sends you towards another class, revisit whether an important feature changed or merely the direction of the conversation. One person values the rhythm of healing, another a role their friends need, and someone else simply wants to continue with a familiar character.

Wednesday’s open stress test offers a brief opportunity to try the game without a beta invitation. It does not guarantee access to every ability or level mentioned here. Use it for an initial impression, and leave firm endgame conclusions until there is broader evidence to support them.