
Ninja
A limited collab-style attacker with ramping or burst patterns that reward a planned rotation on bosses.
Quick read
Magic Shadowkin collab DPS built around a scripted rotation. His numbers shine when the team respects cooldowns, buffs, and mechanic timing—greed in the wrong window is how runs fall apart, not a missing subroll.
- Clan boss-style long fights, farms you can repeat on a clean loop, and Shadowkin faction lines that need a real carry.
- Books and gifts on the skills the timer cares about—engine and big-hit lines in the mode you actually sim.
- Pairs with buffers, a reliable decrease defense, and turn order you verify in a combat log—not with second help you never tested.
Overview
Ninja is the kind of champion you build a calendar around. His numbers can look high on paper, but the in-game story is a rotation: align buffs, respect his passive cadence, and do not spam buttons when a mechanic punishes haste. When it works, it is clean; when it does not, the replays usually show a choreography mistake, not bad luck.
If you missed the acquisition window, you can still read this page as a template for stacking and ramp heroes: gear is half—the other half is not skipping setup turns.
What this page is: fan notes, not a datamine. Skill names, numbers, and set names can change with patches.
What his kit is doing (plain language)
- Ramping / burst (era-dependent): the profile in your client is the truth—read it after major patches before you re-spend books .
- Team-fed windows: a Ninja plan usually expects allies to arrive on the same page for debuffs and turn order .
- Greed tax: the stages that punish hasty buttons are teaching stages—slow down and script the turn first .
Booking priority (rule of thumb): the skills the loop actually uses in your best mode first; cute side paths after the core is stable in a timer .
Strengths
- Excellent for learning boss choreography and buff windows at a high skill ceiling for willing accounts .
- Strong in organized teams that already respect cooldown discipline and sim culture on the roster .
- A defining memory on accounts active during a promo window—your timeline may differ .
Stat priorities (what to roll)
| Goal | What usually matters | Why |
|---|---|---|
| The plan fits the sim | Speed in comp context and C. rate to the real threshold you target in a rotation you intend to keep | Drift kills Ninja-style plans faster than a single bad sub saves . |
| Big hits or DoT lines (build-dependent) | C. damage, ATK% or whatever the active tooltip asks for in the era you play | Patch notes move this; reread the text before a book decision . |
| The setup sticks | Accuracy on the debuff lines the team truly needs him to own in that draft | Misses look like R N G; often it is a stat or order error . |
| Lives the script | HP / DEF to the stage hit profile in the runs you count as serious | Dead on a ramp is a wipe in a plan that is not a pug carry story . |
Gear and artifact sets (practical options)
Sets in this game are suggestions—primary stats, right crit thresholds, and a speed tune you can repeat in a key usually beat a famous six-piece lie on paper .
- Offense and crit: a clean path to a real crit target and C. DMG in the ratio to the way you actually nuke in replays .
- Lifesteal, regen, or defense: only when a replay shows a solvable survivability hole in this rotation; not a fashion choice .
- Perception and accuracy: sane if a debuff on him is part of the earned plan in a tune you truly run .
Main stats to eye (typical boss DPS pattern ): often Speed boots and C. rate gloves; chest and other pieces to the threat; banners and bizarre secondaries only with a proven measured short in a log .
Masteries (“talents”) — two common loadouts
General PvE (boss, farm, Faction DPS slot)
- Offense path: nearly always a crit keystone and a sustain or pierce branch choice the era supports in a build you and a credible current guide agree on.
- Support and Defense (minor): rare dips for a wipe class the mastery row fixes cheaper than new gear this week .
Arena and mixed (less common; account-specific)
- PVE-first on a one-page roster is a sane default; PVP Ninja is a different kettle of sims on most accounts .
Best teams and where he fits (examples)
| Mode | Team idea (archetype) | What Ninja is doing |
|---|---|---|
| Clan Boss and long bosses | Stable phases and a rotation you can rehearse | Ramping or burst in a tight choreography the squad rehearses together . |
| Dungeons (tuned teams)** | Debuff and buff leads and a DPS who pays out in a known window | Carry DPS in a plan the key timer rewards . |
| Faction (Shadowkin) | A strong DPS slot when the bench is thin | Identity and numbers in a tight row of champions . |
| **Farm once stable ** | Repeatable keys on a squad past the “survive first”* phase | Turns a clean theory line into a timer you own every week . |
Your pulls and the patch decide reality—patterns are not a warranty .
Books, “gifts,” and where to invest
Lego tomes and similar: treat tomes as long horizon currency* on** a* champion with* a* rotation* that* you* truly intend to* field* in* a* mode the* account farms frequently — book the* core* loop first before* a* fun* rare line you press once a month for* a* screenshot * .
Gifts, passes, and side systems: push a measured gap—missing ACC a sim and a key timer both prove, a real speed short in a repro run, not a fuzzy “more ATK”* bump on a champion with a bigger ceiling in a clean rotation * than** a* marginal raw stat on paper *.
Blessings, accessories, and endgame systems
- *Blessings and relic rows that close a replayed gap in a serious mode you intend to keep running; re-sim turn order if a row changes tempo in a lump you did not intend .
Weaknesses and common mistakes
Button mashing in a boss that rewards a pause and a set beat in a rotation you never wrote down *.
Books before a stable loop in a mode the account does not actually play yet *.
Treating a Ninja or a Ninja-style stack hero as a vacuum stat stick ignoring turn order in a squad he depends on *.
