Death Knight.
Build around the action.

01 / THE FIRST EXPERIMENT

A starting build with one job.

Pick one tree and learn its resource rhythm before mixing several damage types. Blood is our suggested first investigation for players who want a readable direct-strike plan; this is not a measured survival comparison.

A starting experiment, not a guaranteed best-in-slot setup or a prescribed point allocation. Inspect the current normal builder and your realm’s tooltip before committing.

02 / CHOOSE THE ROLE FIRST

Three talent directions.

03 / DEFAULT CATALOG EXAMPLES

Read the trigger.
Then choose the effect.

These are real Death Knight records from the default public Echo Builder, checked on 3 November. Availability and usefulness are different questions; this is a shortlist to investigate, not a promised draw.

Stonefist BarrageDeath Strike, Heart Strike, Obliterate or Scourge Strike+

These are named strike routes. Match the card to the strike that exists in your active setup.

Default catalog record 201012 · genuine icon / original explanation

Arcane BombardmentRune spending+

A Rune-spend event is not a Runic Power-spend event. This distinction is the first compatibility test.

Default catalog record 201152 · genuine icon / original explanation

Ember SparkRunic Power spending+

The second resource supports a different trigger. Compare the two events before deciding which effect gets more reliable opportunities.

Default catalog record 200972 · genuine icon / original explanation

04 / FIX THE BOTTLENECK

A stat decision order.

Use this qualitative order to decide what to inspect next. It is not a set of simulated weights, universal caps or an instruction to ignore your active tree.

1. 01A stable rune and runic-power sequence
2. 02Enough survival for safe strike windows
3. 03Strength / attack power for the intended melee engine
4. 04Haste or named cooldown support when resource timing permits
5. 05Additional critical / proc value after the cycle is reliable

A cooldown can become ready while the relevant rune is unavailable. Judge a speed improvement by the resource state at the moment you want to press the action.

05 / THE LOOP

Make the next press useful.

Spending a Rune and spending Runic Power are different events. Arcane Bombardment and Ember Spark do not describe the same part of your cycle.

The mistake to catch early.

Seeing an available Runic Power spender and assuming it advances a Rune-spend Echo. Track the actual resource consumed by the action.

When an interaction seems absent, read the precise trigger and class record first. An effect with the same name on another class can use a different condition. PTR examples can also differ from the default catalog.

One useful experiment.

Follow one complete resource cycle. Note the rune-spend event, the runic power gained and the later spend. Then attach an Echo to one clearly identified step rather than calling the whole sequence a generic proc engine.

Keep the encounter, role and ordinary sequence as consistent as practical. Write down what changed and what remained awkward. Your own observation is more useful than pretending this guide measured a universal winner.