When will beta testers receive the free Legacy points?
In Kaivax's 1 October announcement, Blizzard plans to give all testers 16 Legacy points during a future beta week, allowing perk testing without extensive progression first. It expects the grant to remain until the beta ends. No activation date was given. Checked on 2 October: this is a planned grant, with no activation confirmation in the cited post.
The announcement does not explain whether existing points will be added to or topped up, how the grant interacts with reward unlocks, or whether Legacy reset prices will change. It makes no promise of a launch grant. Keep those questions open until Blizzard explains the implementation or you can inspect it in the client.
The grant, spending cap and earned total are different
For normal progression, Blizzard's 23 September system explanation distinguishes account-wide challenge points from each character's perk choices. Non-Hardcore characters share earned points; each spends independently. The launch spending cap is 16 per character, while 65 challenges are available. Account progress also unlocks collection rewards. These rules describe the underlying system, not the grant's implementation.
If your beta balance changes, record the displayed earned, available and spent values separately wherever the interface distinguishes them. A screenshot of one counter cannot answer all three questions. Our Legacy system guide covers the broader progression model; this page focuses on preparing a useful test.
Choose an observable perk effect before allocating points
Blizzard's explainer gives practical examples: Frequent Flier affects flight cost and speed; Master Chef can produce additional cooking results; Permanence extends party, raid and camping buffs. Use the current tooltip for ranks and conditions when choosing a test.
Choose one question your guild actually needs answered. A crafter might compare recipe output, while an organiser might check a recurring buff's duration. Keep the whole allocation visible: prerequisite choices may matter to the result. Avoid changing several perks alongside equipment and then attributing every difference to one node.
Build a comparison someone else can repeat
Our suggested exercise starts before changing the allocation. Save the client build, character level, relevant tooltip and current point spending. Record a baseline under clearly described conditions, then repeat the same activity after applying the choice. Check that the allocation was actually saved before measuring again.
- For travel: use the same endpoints and record fare and journey time separately. Keep reputation discounts and other relevant conditions in your notes.
- For crafting: record the exact recipe, number of crafts and total output. A lucky extra result from one craft cannot establish a proc rate.
- For buffs: record the spell, displayed starting duration, perk rank and any other duration modifier. Include a screenshot that makes the comparison readable.