A Cursemark weapon is a delivery shape, not a tier. The important question is not which name sits at the top of a June ranking; it is whether the weapon’s first safe attack puts your equipped Runes where the target will actually be. Choose by reach, contact count, footprint, and recovery, then prove the pairing in one controlled room before you invest Essence.
Early Access boundary: this guide was checked on August 13, 2026 against the official Steam build history through July 18. That history matters: Shadow Blade, Brumal Scythe, and Wave of Decay received direct launch-week changes; attack-count scaling and several Rune penalties changed; 24 status-focused Runes and Talismans arrived July 3; nearly all Spells and Talismans were buffed July 16. Any fixed S-to-D list published near launch is now a testing queue, not a verdict.
Measure four things before you name the build
Test the unmodified weapon first. Use the Training Dummy when available—the July 18 patch made it respond to Auras—but remember that a stationary target cannot prove crowd control, pathing, or boss safety. Record four observations:
- Reach: the farthest distance at which the first hit lands without stepping forward into a counterattack.
- Cadence: how many attacks can be completed before you need to dodge, and which hit generates the Energy or effect you care about.
- Footprint: whether the hit is a point, line, arc, wave, trail, burst, or series. This predicts where projectiles and status applications will appear.
- Recovery: the time between the committed hit and your next movement, Ward, Spell, or Ultimate. Damage that removes your defensive response is not free damage.
Then add one Rune and repeat the same sequence. Do not change a Talisman, blessing, second Rune, and weapon at once. The success signal is an observable difference attributable to that Rune: another projectile, a tighter spray, a status icon, a trail, a barrier, a repeated hit, or a changed recovery loop. If the screen merely becomes busier, the pairing is not yet proven.
Use the seven weapons as seven delivery tests
The seven launch-period weapon names map to the seven visible disciplines. The descriptions below preserve the useful experiential part of early guides while discarding the permanent ranking. Every “keep” decision still requires the installed tooltip and one-room test.
| Weapon | Delivery pattern to test | Rune jobs it can make visible | Main failure signal |
|---|---|---|---|
| Knight’s Sword | A straightforward three-hit sequence that mixes slashes with a final thrust | Baseline on-hit, combo, critical, and sequence effects | You need a special mechanic to solve a problem the neutral sequence does not address |
| Divine Spear | A narrow thrust with reach and a deliberate pause between attacks | Forward sprays, concentrated on-hit payloads, range, and single-target effects | The pause prevents Energy recovery or leaves you exposed after every miss |
| Dragon Claws | Fast close-range contacts plus a fire-bearing follow-up and dash interaction | Status stacking, per-hit triggers, short-range bursts, and attack-count effects | The build needs you to remain inside an enemy pattern that your defense cannot survive |
| Thunderous Strike | A sequence whose later hit carries much of the payoff | Combo-finisher, critical, follow-up, and Energy tests | The target moves or interrupts you before the payoff hit lands |
| Brumal Scythe | A broad Ice attack with a lingering trail | Area control, trail, Freezing, size, and path-based damage | Slow cadence or excessive reach leaves close enemies inside the dead zone |
| Wave of Decay | A Rot wave that emphasizes area and Poison rather than a fast melee string | Status spread, wave size, Energy gain, and ranged area effects | The room dies slowly while the weapon fails to fund the next Spell or defensive action |
| Shadow Blade | A fast Umbral sequence with sustain associated with the finishing hit | Rapid status application, life-steal readback, per-hit effects, and flexible modifiers | The individual hits are too weak or the final sustain trigger does not occur reliably |
This table deliberately does not choose one winner. Early writers favored Divine Spear because a thrust can concentrate an Embershot-style spray, while later player discussions preferred Shadow Blade’s speed or Brumal Scythe’s area and Energy behavior. Those disagreements are useful: they tell you that attack geometry and build goal matter more than a universal rank.
Match the Rune’s trigger to the hit that carries it
Read each Rune as a sentence with three missing fields: when does it trigger, where does the result appear, and what makes it happen again? Fill those fields from the live test before upgrading.
| Rune behavior | Promising weapon shape | Proof to watch for | Reason to reject the pairing |
|---|---|---|---|
| Payload emitted on weapon contact | A thrust for concentration or a fast string for repeated contacts | The payload overlaps the target on each qualifying hit | An arc scatters most of the effect into empty space |
| Effect grows with attack count or sequence | A reliable combo whose final hit you can finish safely | The later hit shows the promised change after the exact required count | Interruptions reset the sequence before the payoff |
| Trail or persistent area | A wide sweep, movement-linked attack, or wave | Enemies remain inside the effect long enough for more than one tick | Knockback or movement pushes targets out immediately |
| Burning, Freezing, Electrified, or Poisoned source | Frequent contacts for buildup or a broad hit for room coverage | The correct status indicator appears on the intended target | The status is applied but no other slot benefits from it |
| Critical or conditional damage | A weapon whose cadence lets you collect enough observations | The condition and resulting damage change appear together | You are inferring a rate from one lucky hit or an old guide’s percentage |
| Repeat, rebound, seek, or spiral | A projectile-producing action with room to travel | The generated object follows the new path without losing its target | Extra range, size, or wandering makes it miss nearby enemies |
| Barrier, heal, or defensive reaction | The Ward or Spell that is available during your most dangerous recovery | The defensive resource increases at the moment the trigger occurs | The Rune sits on an Ultimate that is unavailable for ordinary failures |
The official store gives the clearest design examples: an attack can carry chain lightning, an enemy can erupt into a poison cloud, a fireball can multiply, an Ice pillar can appear, and a Ward can blind or heal. None of those examples says every weapon uses the effect equally well. The weapon decides the delivery opportunity; the Rune decides what is delivered.
Test Rune order instead of assuming fusion is commutative
Experienced players have reported that the order of fused or slotted Runes can change whether a later effect appears. That observation is useful but not universal proof. Treat order as a variable and test it:
- Photograph or write down the current weapon, Rune order, levels, Talismans, and blessings.
- Use the same target and perform ten identical first-hit or full-sequence trials.
- Record only visible outputs: contact count, spawned objects, statuses, criticals, barrier change, and Energy change.
- Swap the order of the two Runes without changing anything else.
- Repeat the same trials. If the later effect disappears or moves, keep the working order and retest after the next patch.
Do not spend rare upgrade charges before this check. Community players recommend fusing a useful pair before leveling so later investment benefits the combined item, but costs and upgrade behavior must be read in the current Forge. Confirm the fused name, both components, level, and slot after closing the menu. The July 18 patch fixed fused Runes appearing as unfused, so a stale display can no longer be treated as normal.
Reach and attack size deserve their own failure test. A larger effect sounds strictly positive, but a high-hour player report warns that extended reach can place a generated hit beyond a close enemy. July 18 also fixed a negative attack-size modifier that could reduce a body to zero. Stand close, at normal range, and at maximum range; keep the modifier only if all three positions still produce the intended contact.
Do not use every ability slot as Rune storage
Weapon, Spell, Ward, and Ultimate Runes share a build, but they do not share availability. A Rune on the weapon can contribute whenever the attack is safe. A Spell Rune depends on Energy and cast opportunity. A Ward Rune depends on timing and the Ward’s rules. An Ultimate Rune may remain idle through several rooms while its charge builds.
Give each slot a trigger budget:
- Weapon: the repeatable engine. Put the status source, Energy loop, or common on-hit effect here when the weapon’s geometry supports it.
- Spell: the conversion or room solution. Use it to cash in a status, reach a target the weapon cannot, or clear a formation that punishes melee.
- Ward: the recovery bridge. Its Runes should solve the period when attacking or casting would otherwise cost health.
- Ultimate: the reserved exception. Put a Rune here only when the resulting boss phase, elite pack, or emergency payoff justifies its low trigger frequency.
The June 26 patch fixed duration-based Wards applying their Runes globally and repaired Rune of Ecstacy interactions on Spells, Wards, and Ultimates. If an old build depends on a Ward effect benefiting everything at all times, rebuild it from the current tooltip and observed trigger. A former bug is not a synergy.
Build status around source, support, and payoff
The July 3 update added twelve Talismans and twelve Runes centered on Burning, Freezing, Electrified, and Poisoned. Its examples range from the fire-focused Wildfire and ice-focused Glacier to Nimbus for lightning; Pernicious, Thrumming, Vorticose, Shadowstone, and several status-oriented Talismans broaden the same pool. That expansion makes three-part status builds practical, but it also makes accidental half-builds more common.
- Source: one action applies the status reliably. Prove the icon or effect appears at your normal range.
- Support: one Rune or Talisman improves application, duration, spread, or the associated attack pattern. Prove it changes the visible result.
- Payoff: one action benefits from the afflicted target, converts the status into control, or keeps you safe while damage accumulates.
If you have two sources and no payoff, replace one source. If the payoff is on an Ultimate that rarely charges, move a smaller payoff into the Spell or weapon loop. If the status is strong on groups but slow against a single target, keep a direct-damage alternative rather than demanding that one setup solve every room.
Do not carry old status values forward. The July 3 notes reduced Freezing’s maximum base slowdown and altered caps and scaling elsewhere; July 16 then changed difficulty and buffed most Spells and Talismans. Describe what the current client does—slows, spreads, ticks, chains, or controls—before attaching a number.
Run one acceptance test for each weapon
Use these as acceptance tests, not recommended rankings:
- Knight’s Sword: complete the three-hit sequence against one normal enemy and one moving enemy. Keep it when the final thrust and attached effects land without forcing a trade.
- Divine Spear: attach one forward payload, hit from maximum safe reach, then repeat at close range. Keep it when the effect remains concentrated and the post-thrust pause is defensible.
- Dragon Claws: count status applications during one safe combo and one dash approach. Keep it when the fast contacts create a payoff before the enemy’s close-range response begins.
- Thunderous Strike: test whether the payoff hit survives interruption and whether its Energy or critical result is visible. Keep it when you can finish the sequence in the rooms that matter.
- Brumal Scythe: draw an enemy through the frost trail rather than swinging at a stationary target. Keep it when pathing produces extra control or damage without making the initial attack too slow.
- Wave of Decay: compare a line of enemies with a lone durable target and watch Energy. Keep it when the wave solves the formation and still funds the rest of the kit.
- Shadow Blade: isolate the finishing hit and watch health, status, and Energy separately. Keep it when the sustain or rapid application actually occurs often enough to cover its lower per-hit impact.
A weapon passes only if its strength appears under the conditions you will repeat. A perfect Training Dummy result that collapses against moving enemies is a laboratory note, not a build.
Use patch history to diagnose a misleading result
| What looks wrong | Patch-aware interpretation | Next test |
|---|---|---|
| Shadow Blade sustain differs from an early guide | Health Steal was increased June 11 | Isolate the finishing hit and watch the current health readback |
| Brumal Scythe feels faster or stronger than its old rank | Damage changed June 11; speed changed June 13 | Retest cadence, trail contact, and close-range safety |
| Wave of Decay no longer behaves like a D-tier description | Range changed June 11; damage, range, and speed changed June 13; Energy gain changed June 23 | Compare room coverage and Energy against another weapon in the same route |
| Attack-count or sequence Rune math disagrees with a launch build | Status splitting and Fragments/Echoes scaling changed across June 21–22 | Count current hits and read the penalty instead of copying the old sequence |
| A status setup suddenly has more viable parts | Twenty-four status Runes and Talismans arrived July 3 | Rebuild around one source, one support, and one payoff |
| A Spell/Talisman comparison reverses an older conclusion | Nearly all Spells and Talismans were buffed July 16 | Repeat the one-variable test on the installed build |
| A fused Rune looks separated or an Aura ignores the dummy | Both display/interaction bugs were fixed July 18 | Verify the patch, reopen the item, and retest once before rebuilding |
Lock the build only after three readbacks agree
A Rune pairing is ready for serious investment when three different tests tell the same story:
- Dummy or isolated target: the trigger, order, footprint, and resource change are visible without combat noise;
- ordinary room: the weapon completes its job while you retain a safe response to movement and multiple enemies;
- durable target: the build sustains its source-support-payoff loop after the opening burst instead of waiting on one Ultimate.
If one test fails, change one variable and repeat. If two fail, do not rescue the build with more upgrades; the delivery shape and Rune job disagree. Cursemark rewards wild combinations, but the reliable ones are still mechanical sentences: this hit creates the condition, this slot converts it, and this defensive action keeps the sentence running.
Sources and build boundary: the system premise—Runes can alter attacks, Spells, Wards, and Ultimates—and the screenshots come from the official store listing. The weapon, status, Ward, fusion-display, and Training Dummy diagnostics stop at the July 18, 2026 item in the patch archive. Readable community tests inform weapon patterns and experiments, but no ranking, hidden percentage, or boss claim is presented as a lasting fact.