Anti-Mage + Rubick

Why this works

Stealing a big teamfight spell seems like the perfect way to set up a hard carry, but these two heroes often operate on completely different timelines. Anti-Mage needs to be left alone to farm his core items, often playing on the opposite side of the map from his team. Rubick, meanwhile, thrives on early action and skirmishes where he can use Telekinesis and stolen spells to create advantages. He is too fragile to provide the durable frontline or hard save that helps an Anti-Mage survive ganks during his most vulnerable farming phase.

This dynamic often leaves the game in a strange state. Rubick will try to make plays and control the tempo, but Anti-Mage is rarely ready to join those early fights and capitalize. By the time Anti-Mage is farmed and looking for targets, the control Rubick offers is less about a clean setup and more about adding to general chaos. An enemy lifted by Telekinesis can be a good target, but it's not always the one Anti-Mage wants to Blink on. Their core game plans don't actively support each other, making success feel more incidental than planned.