Start with three questions
Can your current character use the build? What will stop its main damage mechanic? What does your party need you to do? Answer those before copying a full level-60 allocation.
| Your situation | First decision | What to check next |
|---|---|---|
| Learning a dungeon with unfamiliar enemies | Start with a build you can operate reliably, and keep a fallback plan | Record which targets actually show poison or bleed immunity; do not generalize one encounter to the whole dungeon |
| Trying Assassination | Check the required weapons and the available poison tools | Read your current Mutilate and Venom tooltips; a level-60 showcase does not establish what your Beta character has learned |
| Trying Subtlety | Check what works after the opener | Decide how you will handle a target that dies before your bleed has time to act |
| Providing interrupts for the party | Put the interrupt on an accessible binding | Agree on the caster to interrupt and how you will return to your original target |
| Playing with a Warrior | Agree who handles armor reduction | Compare the actual debuffs before spending resources maintaining both |
Our decision table is an editorial workflow. It adds preparation steps to the source material without claiming that we played these encounters.
What the sources actually establish
Blizzard’s October 1 class highlights, Rogue section at 3:38, describe continuous energy recovery, Venom as a poison-focused finisher, and a combined Combat weapon talent. This confirms the direction of those mechanics, not a damage ranking or a list of every current value.
SimonizeShow’s September 16 BlizzCon-demo analysis discusses preserving points when briefly switching targets, poison upkeep, armor-debuff overlap, and enemies immune to a build’s effects. These are dated community observations. His poison-scaling statement references a Discord message we have not independently checked, so this guide does not reproduce a scaling coefficient.
| Evidence | Suitable use | Unsuitable use |
|---|---|---|
| Official class overview | Understand the announced play style | Invent learning levels, exact tuning or a best-in-slot list |
| September demo analysis | Identify a mechanic worth checking | Assume every demo behavior survives the October update |
| Your client tooltip and combat log | Record what happens in your specific build | Claim all levels, mobs or realms behave identically |
A five-minute preparation sheet
Fill in this sheet before the first pull. The time is a planning allowance, not a measured setup benchmark.
- Snapshot: note client version, character level, specialization, weapons and the date. Save the talent planner link alongside it.
- Weapon effects: inspect the current poison indicators. If your client displays duration or charges, check both. Put supplies where you can find them before a boss rather than assuming a buff lasts for the whole run.
- Party responsibilities: name one interrupt target and one backup interrupter. Agree whether you or the Warrior maintains the armor debuff. An identical-looking debuff icon is not proof of stacking.
- Target switching: on a safe encounter, build points on A, select B without generating points, then return to A. Note what remained. Test interrupting B separately; do not add an attack macro that also generates points and then blame the target change.
- Fallback: if the combat log reports immunity to your main effect, stop refreshing that effect. Use the direct attacks and utility actually available to your character. Change a build only through an option your client allows and in an appropriate safe moment.
Example: you have points on the melee target and a caster starts a dangerous spell. Tell the group you are interrupting, select the caster, interrupt if usable, then return. If the points disappear, record whether another ability generated points during the switch before concluding the behavior changed.
Why a level-60 build may fail at level 30
The October 1 maintenance announcement plans to raise the Beta cap to 30 after service resumes. In this site’s standard planner, level 30 has 21 points; level 60 has 51. A guide built around a 31-point talent cannot simply be loaded as a complete level-30 plan.
Open the Rogue planner. Keep the level fixed, then compare the early talents that your current snapshot includes. Ask what the build does before its late talent becomes available. If a recommendation relies on an unavailable finisher, assess the earlier gameplay on its own rather than spending points toward an unreachable showcase.
The calculator’s data snapshot remains identified in the tool. It validates its own point rules; it does not certify that a spell is learned or that the latest client has the same tuning. Use the spellbook to inspect the source record, then check your client.
Compare two builds without confusing the result
Choose a repeatable, safe target and change one variable at a time. This is a proposed recording method, not a test result.
| Keep the same | Record for each attempt | Reason |
|---|---|---|
| Character level, weapons and main equipment | Build link and client version | A weapon upgrade can conceal the effect of a talent change |
| Target type and starting resources | Time, deaths, interrupts and recovery downtime | A faster kill that causes a death may not improve your actual session |
| Party buffs and debuff responsibilities | Poison/bleed uptime and any immune messages | A change in party support can make the same build look different |
| Number of attempts and route | Exceptional pulls or extra enemies | One lucky crit or accidental extra pull is not a stable comparison |
For a short quest session, count completed objectives and recovery time. For a dungeon, check missed interrupts, avoidable deaths and contribution to the group, as well as damage. Do not turn a popular build’s share rate into a performance claim.
Sources and what we added
- Blizzard · Class Highlights, Part 1, October 1, 2026: official Rogue overview.
- SimonizeShow · Rogue demo analysis, September 16, 2026: relevant sections at 1:00, 1:33, 3:01, 3:30 and 10:56. We reviewed the available auto-generated transcript; it can mishear names, so no new exact tuning is transcribed here.
- Blizzard · October 1 maintenance notice: planned cap change, not proof that maintenance has finished.
Forever Atlas wrote the decision table, preparation sheet, switching example and comparison method. The underlying game mechanics and the creator’s observations retain their attribution. See our editorial method.