Ruby

When Ruby actually fixes a draft

Ruby is an A-tier EXP choice in the current 2026 ranked meta because EXP lane still rewards two things above everything else: sustain and crowd control. That part of the patch suits her. What does not suit her is being treated like a blind first-phase answer into every ranged poke lane on the board.

Pick Ruby when the enemy draft wants to walk into you. Melee-heavy fronts, dive junglers, and short-range carries give her the kind of fights she can control. She is also a clean answer when your team already has a real tank and needs a second engager who can peel after the first contact. In those games Ruby does two jobs at once: she slows the first entry with Be Good!, then punishes the second entry with the pull and stun chain from S2 into ult.

Pick her when your support or roamer can follow a grouped engage immediately. Pharsa, Cecilion, Estes, and Mathilda all turn her pull into something more than displacement. If your team has no follow-up damage and no one to stand in front of her, Ruby's control window becomes cosmetic and the pick loses half its value.

Avoid Ruby when the enemy can stop her approach before she reaches pull range. Valir is a problem because the lane becomes a patience test you do not control. Kaja turns every front-foot step into a suppression threat. Phoveus punishes the passive dash pattern that makes Ruby feel safe in normal matchups. Baxia and anti-heal heavy comps do not remove her from the game, but they do change it from a long-trade lane into a short-trade lane. If you still intend to brawl through that, you are picking the wrong hero.

The simplest draft test is this: if the fight you expect is front-to-back and crowded, Ruby makes sense. If the fight you expect is long-range poke into disengage, she does not.

The one thing that makes Ruby work

Ruby is not a lifesteal fighter in the normal sense. She is a displacement engine with sustain attached.

Her passive is the whole story. Basic attacks do not trigger her lifesteal pattern, but her skills do, and every skill cast gives her a short dash plus temporary defense that stacks. That means the hero is built to cast, slide, recast, and stay just awkward enough to pin down. If you stand still and try to auto like a standard bruiser, you have turned off the part of the kit that matters.

Be Good! is lane control first and damage second. The swing plus shockwave lets Ruby tag a wave and the enemy EXP laner at the same time, and the slow is what sets the next angle. Don't Run, Wolf King! is the actual trade reset. The double swing interrupts movement, tugs people back into your space, and buys time for the passive dash out. I'm Offended! is not just engage. It is the button that turns a messy front line into a straight line your team can punish.

That is why Ruby feels oppressive in the right game and mediocre in the wrong one. She does not win by stat-checking the lane. She wins by making the enemy spend movement and spacing twice in the same trade while she spends one cooldown rotation and slides out.

Laning: the first five minutes

1. Start with S1 and make the first wave do double duty. Hit the melee minions and clip the enemy EXP laner with the same Be Good! cast. Ruby does not need a flashy level 1. She needs the wave moving on her terms and the opponent slowed long enough to think twice about stepping forward for the next last hit.
2. Take S2 at level 2 and hold it until they cross your line. The mistake is throwing Don't Run, Wolf King! the moment it comes up. Let them walk into the minion wave first, then use the pull and double stun when they have already committed their step. That is the trade Ruby wins most often because the return path is simple: cast, dash sideways, reset.
3. Save Flicker or Vengeance for the first real skirmish, not for lane vanity. Flicker matters when it converts an ult into a numbers advantage around Turtle. Vengeance matters when the enemy jungler finally joins the lane and tries to burst through your control window. Burning either spell for a tiny solo kill before minute 5 usually turns the next objective fight into a bad one.

Freeze the lane if your jungler is pathing top side. Thin the wave and keep the fight near your turret if the enemy mid is missing. Ruby can survive pressure better than many EXP laners, but she still loses if she spends S2 into fog and the counter-gank arrives before the passive dash is back.

The two-item window that decides her game

Ruby's first real spike is War Axe plus Dominance Ice, usually around the 8 to 10 minute mark in a stable EXP game.

War Axe gives her exactly what early Ruby wants: HP, cooldown reduction, spell vamp, and a stacking damage passive that rewards staying in contact. Ruby does not burst people in one clean rotation. She keeps touching the fight long enough for the stack count to matter, then forces you to keep fighting while her cooldowns come back. War Axe is the item that makes those repeated half-commits hurt.

Dominance Ice is what turns that pressure into control. The armor matters, but the real mechanical shift is in the passives. Anyone hitting Ruby has their attack speed cut, and anyone trading sustain into her gets their shield and HP regen reduced. Once this item lands, matchups that were merely annoying in lane become manageable, and marksmen who thought they could stand and fire through her entry suddenly cannot.

This is the window where Ruby stops being "hard to kill" and becomes "hard to play into." Before these two items, she can start fights but cannot always stay in them. After them, she can take first contact, live through the answer, and force a second crowd-control cycle before the enemy carry is comfortable again.

If your team already has anti-heal elsewhere and the enemy composition is not sustain-heavy, Queen's Wings is the alternative second item worth respecting. The HP, cooldown reduction, spell vamp, and low-HP damage reduction all fit Ruby's second-entry style. But in most ranked drafts, War Axe plus Dominance Ice is the safer and more useful default because it changes both the duel and the teamfight.

Teamfight positioning and target priority

The common Ruby mistake is opening every fight with Flicker-Ult just because the combo exists. That is highlight behavior, not consistent winning behavior.

Ruby is usually better as the second touch in a fight, not the first. Let the tank or jungler force the first turn of heads, then enter once the enemy backline has taken one step forward or one step sideways. That is when her pull changes from a gimmick into a punish.

1. Stand one skill-length behind your first engager. Close enough to follow instantly, far enough that you do not eat the same first wave of crowd control. Ruby wants to arrive after the enemy commits, not before.
2. Pull across your team, not deeper into theirs. If your ult drags people toward a wall, a turret, or the rest of your lineup, it is good. If it drags you past the midpoint with no help behind you, it is self-sabotage. The direction of the pull matters more than the number of targets.
3. Use the passive dash sideways more often than forward. After S1 or S2, the instinct is to chase with the dash. In real teamfights the better dash is usually diagonal or sideways, because it keeps the enemy carry inside your control radius while moving you out of the cleanest return damage angle.

If your support is Mathilda, Angela, or Estes, Ruby can take a much greedier first step because there is actual follow-through behind it. If your support is Diggie into anti-engage or your backline is the real win condition, hold Ruby as peel and let the enemy walk into S2 first. She is one of the few EXP laners who can play either job in the same draft.

Itemization: locked slots and real flexes

Ruby's build is not six locked items. It is a skeleton with a few conversations that matter every game.

Boots first. Tough Boots is the default when the enemy has layered magic CC or a Valir style lane that tries to keep you out forever. Warrior Boots are better when the real problem is physical poke and repeated side-lane trading. Magic Shoes only make sense when the enemy has low hard CC and you know you can spend the extra cooldown speed aggressively instead of using it to die faster.

War Axe is the non-negotiable first damage item. Ruby wants the HP, cooldown reduction, spell vamp, and stacking combat pattern. If you skip it, you delay the point where her repeated short trades start converting into actual lane control.

After that, the flex conversation is simple:

• Dominance Ice when the enemy has sustain, shields, attack-speed carries, or any EXP matchup you expect to last longer than one spell rotation.
• Queen's Wings when you are the second engager and expect to drop low in the middle of your own crowd-control chain rather than before it starts.
• Brute Force Breastplate when the enemy comp is mobile and you need movement speed plus control duration reduction to stay glued to the second target after your first catch.
• Athena's Shield against burst mages who are trying to end your engage before Ruby can start healing through the fight.
• Blade Armor against crit-heavy marksmen who insist on hitting the front line first.
• Immortality when the game is being decided by one late Lord fight and your job is simply to force the enemy carry to answer you twice.

Oracle is the item players buy too casually on Ruby. It is still usable for the balanced defenses and cooldown reduction, especially with heal or shield supports, but do not pretend it is mandatory. The tooltip boosts received shield and HP regen effects. That is valuable in the right team, but it is not a free pass to ignore the actual threat profile in front of you.

Mistakes that lose Ruby games

Dashing on autopilot into Phoveus. Ruby's passive dash is what keeps her clean in normal fights, but it also feeds exactly the kind of target Phoveus wants to see. If he is in the game, every passive slide needs intent. Cast, hold the angle, and only dash when it changes the trade. Mindless movement turns a playable matchup into a free ult battery for him.

Starting on Valir after he still has ult. This is the classic impatience throw. Valir wants Ruby to overcommit into the cleanse and knockback. Make him spend that button first. Walk at him with S1 slow, threaten S2 range, and commit the real engage only after the reset is gone.

Using S2 for poke instead of for commitment. Don't Run, Wolf King! is Ruby's most important lane cooldown because it decides who owns the distance after contact. If you throw it for a tiny health lead and the enemy jungler appears five seconds later, the lane is over. Save S2 for the step that matters.

Taking long trades into Baxia or stacked anti-heal. Ruby can still function into anti-heal, but the fight pattern changes. Against Baxia, Dominance Ice mirrors, or heavy ranged anti-heal, your job is not to prove your sustain is bigger. Your job is to take one clean crowd-control trade, back off on the passive dash, and re-enter on the next cooldown cycle.

Forcing the first Turtle fight with no wave control. Ruby is strong around early objective scrambles, but only if the side wave is already solved. Rotating first while a stacked wave crashes into your turret means you lose gold, EXP, and sometimes the turret plate on top. Clear, move, then look for the pull angle. Do not turn good skirmish strength into bad macro.

Key tips