Rune says #smash or #multi-hit but my class lacks the skill?
✍️ Alice・愛麗沙
That rune is not dead. “Smash” (강타/強擊) and “multi-hit” (연타/連擊) are names shared by two different systems. Rune and emblem effects reference damage judgements — official game-guide territory: a single hit dealing 40%+ of your attack power judges as a smash (KR-community threshold), six hits inside three seconds judge as multi-hit — and none of this cares whether any of your skills carries a “#smash” tag. Any class with the right setup can trigger them. The system that actually reads skill tags is gems: a Star Prism’s three tag-damage lines are the thing you match against the tags printed on your skills. So the reading order is: for runes, check the damage judgement (nearly everyone qualifies); for gems, check the skill tag (table lookup required). The most expensive outcome of confusing the two is dismantling or shelving a legendary rune because “the tag doesn’t match” — rune fusion is irreversible, and that rune isn’t coming back.
One name, two systems
The clearest specimen of this misconception is a nearly ten-thousand-view thread on the Taiwan server’s main board: a player pulled an emblem rune with a multi-hit effect, searched their class’s skill list, found no skill tagged “#multi-hit”, and concluded the rune was useless to them. The correction arrived in the replies — they’d been misled by the little tags printed under skill descriptions. The same confusion recurs in Korean communities too; this isn’t a translation artifact, it’s a consequence of the game genuinely reusing one name across two systems.
The first “smash/multi-hit” is a damage judgement. This isn’t community jargon — the official game guide has a dedicated article: when you and an enemy trade blows, various judgements fire based on stats and combat conditions, and a single attack can qualify for several judgements at once. The official definition of smash is “a single instance of damage reaching a certain ratio of your attack power”; multi-hit is “a certain number of hits within a short window.” Notice what’s absent from both sentences: any mention of skill tags. Judgements look at the outcome of the hit that just landed, not at the label on the skill that produced it.
The second “smash/multi-hit” is a skill tag — the one or two small words under each skill’s description. Across the entire game, exactly one system consumes those tags: gems. A Star Prism’s tag-damage lines only apply to skills whose tags match. That system genuinely requires a table lookup, and “can my class even use this line” is a legitimate question there — but it governs gems, not runes.
A Korean player who field-tested Blind Rage put the distinction on the record in one sentence, translated: “this option has nothing whatsoever to do with skill tags.” Rune effects read damage judgements; when the judgement lands, the stack builds. Your skill list’s cosmetics are irrelevant.
Where the gates sit: official definitions, community numbers
The official text stops at “a certain ratio” and “a certain number” — the actual thresholds have never been published. What circulates is KR-community measurement, medium confidence, not independently re-verified on the Taiwan server:
| Hit type | Trigger gate | In-bucket rate | Confidence |
|---|---|---|---|
| Smash | A single hit must deal ≥40% of your attack power before smash enhancement applies | per +100 ≈ +1.18% | MED |
| Multi-hit | 6+ hits within 3 seconds, then later hits count as multi-hit | per +100 ≈ +1.18% | MED |
| AoE | One strike must hit 2+ targets before AoE enhancement applies | per +100 ≈ +1.18% | MED |
| Combo | Four combo bands: 1–10 pays 1/4, 11–50 pays 2/4, 51–100 pays 3/4, only 101+ pays in full | per +100 ≈ +0.57% | MED |
All four enhancements share one bucket with the same divisors (multi/smash/AoE 8500, combo 17500), but each hides its own trigger gate. Any calculator that assumes they always apply in full will systematically over-report damage. Gate numbers are KR-community findings, medium confidence.
Read this table against the official definitions and the original question answers itself. A rune that stacks on multi-hit needs six hits inside three seconds — and damage-over-time ticks, pursuit procs, and the rune’s own bonus hits all count toward that number. So “can a slow greatsword sustain multi-hit” or “can a fast, light-hitting class ever trigger smash” is not a skill-list lookup; it’s a question about whether your damage profile clears the gate. The corrective write-up that finally got traction on the TW board (82 GP) said exactly this: with a suitable setup, any class can trigger multi-hit — same evidence chain this article stands on.
The honest flip side: judgements are not free. The smash gate (≥40% of attack power in one hit) is unkind to many-small-hits builds; the multi-hit gate is harsh on very slow-swinging setups. Which content breaks which judgement, and the bucket math underneath, is its own article on the zh side of this site — the table above is the part that travels.
The bill this misconception runs up
The misunderstanding costs nothing; acting on it does. The bleakest reply in the original thread, paraphrased: pulled a legendary, saw the “wrong” words on it, mood ruined — and since fusion can’t be undone, into the warehouse it goes.
Run the numbers. Rune fusion is one-way, and a failure destroys two of the three input runes. A legendary misjudged as a dud ends, at best, warehoused; at worst, fed as fusion fodder — when it may have been the copy you won’t pull again all season. For emblem runes the stakes are worse still: their acquisition paths are far narrower than weapon or armor runes.
The correct procedure is three steps: read whether the effect names a judgement (smash/multi-hit/pursuit family) or some other condition; if it’s a judgement, check your damage profile against the table above; only if your setup genuinely can’t clear the gate (a pure-support build that never produces smash judgements, say) does fodder become a conversation. The step where you bin a rune because a tag doesn’t match should never exist.
So when do tags actually matter?
To head off the overcorrection: skill tags are not decorative — they’re just not the rune system’s business. The moment you genuinely match tags is gem setup: a Star Prism pays roughly +2% per tag line, three lines per gem, and a line whose tag matches none of your main skills pays nothing. Per-class recommended tags are collected in this site’s gem data from KR community sheets — classes the source skipped are marked missing rather than invented.
One sentence to file the whole division of labor under: runes ask “was that hit heavy enough, fast enough, wide enough” — gems ask “what label is on this skill.” The first question includes nearly everyone. Only the second needs the lookup table.
What would overturn this article
Two things. First, the gate numbers (40%, six-in-three-seconds) are KR-community measurements — a training-dummy test producing different numbers, with the enhancement panel and method in the screenshots, gets the table changed. Second, “rune effects ignore skill tags” rests on one direct field test plus inference from the official definitions — a counterexample, a rune measurably firing only for tagged skills, would gut this article’s core claim, and we’d rewrite it and date the correction.