Heroes / how to use the guide

How to use the hero database: role, abilities and a purposeful build

A clear path through a hero: recognise abilities by their icons, compare roles, understand Aghanim and Shard, choose purchases and watch Ruslan's published match.

Ruslan UkrainskyiMy thoughts. Rodya’s face.Author’s breakdown · Ruslan / OOPS DOTA

On a hero page, I want to gather what you need before and after a match: abilities with original icons, role options, explained purchases and my published examples. The portrait in the draft can then become a clear plan.

Teamfight from an OOPS DOTA recording: hero positions and available actions
OOPS DOTA / Ruslan Ukrainskyi · my own gameplay recordingChoose a hero in the atlas →

Start with the hero's job, not the final inventory

Before choosing items, answer three questions: what does the hero do in lane, what job do they perform in a fight, and what do they need for that job? Control, damage, helping an ally and pressure on buildings are different tasks. Someone else's picture of six slots is of little use without this context.

In the atlas, you can find a hero by name and open a detailed guide. For a first introduction, choose one hero and one role. Trying their abilities in the client is more useful than immediately combining a dozen incompatible options from different guides.

  • Name your main way to contribute.
  • Find the ability that starts your action.
  • Identify the resources and conditions it needs.
  • Choose purchases only afterwards.

‘I recommend a hero for a task. A nice portrait is a reason to open the page, but the decision starts with abilities and role.’

Ruslan Ukrainskyi · OOPS DOTA

The icon identifies the ability. The description explains the action

Hero pages show abilities with original images. That makes it easier to find the button in the client and notice the difference between an ordinary ability, an innate effect and an upgrade. The description and available Valve data sit beside them.

Read more than the promised damage. Who can you cast on? What does it give the team? Does it need channeling? What can stop the action? If the description is complex, open Demo Hero and check one ability at a time.

A role means resource priority and work in the team

A hero can have several viable roles. My recommendation indicates a starting plan, not a ban on other positions. On Zeus, for example, position four, mid and an attack-based carry option need different economies and purchases.

A support should not copy a midlaner's budget just because an expensive item appears on the page. A position-one hero usually has different farm priority. When changing roles, recheck the lane, responsibilities and when the team expects your help.

  • Check which position the chosen build is written for.
  • Compare the budget it needs with your role's resources.
  • Agree with the team which task you are taking.
  • A situational option does not become the main one because of one successful game.
My Viper / position 4EXPLORE THE EXAMPLE ↗
My Viper / position 4

In this match I play position four, but deal a lot of damage. My impact still depends on working with the team.

OOPS DOTA / Ruslan Ukrainskyi
Zeus: compare positions and plans ↗Understand role priorities ↗

Read Aghanim and Shard for this specific hero

The same item can open very different options on different heroes. That is why it matters to see what belongs to Aghanim’s Scepter and Aghanim’s Shard beside the abilities. I do not recommend buying an upgrade just because you recognise it from another match.

Before buying, state the new action: what will I be able to do afterwards? If the answer is ‘become stronger’, reread the description. A more specific task makes it easier to compare the upgrade with a save, mobility or another slot you need.

A build is a route with choices

Each item in the plan has an explanation: which problem it solves and when to consider it. That helps you change the order. If you cannot press an important button in time, protection or a positioning item may be needed before another damage boost.

Game data and my recommendations are separate. An editorial starting plan is a way to get to know a hero. General builds from public matches depend on the sample and role. A personal purchase order is one author's experience. These three things are useful in different ways, and I do not want to present one as another.

When a patch changes a hero, we separately recheck affected abilities, upgrades and builds, then update the source and check date on the page. This is editorial work: one new game version does not mean all 127 guides have already been revised. For decisions in today's match, check exact values in the current client.

Watch a match, then check one moment in your own

If I have published an episode on the hero, it appears beside the guide. You can watch how decisions worked in a real match. Not every hero has a recording yet; new games will be added as they are released, without empty promises or someone else's matches under my name.

Crystal Maiden and Viper already have their own episodes and short moments. After watching, choose one situation: positioning before the ultimate, buying a defensive item or acting after a fight. Compare it with your own replay. That question is more useful than trying to repeat the entire match.

Crystal Maiden: full episode and Shorts ↗Viper: full episode and Shorts ↗
YOUR TURN / PRACTICE SCENARIO

You found a mid build for Zeus, but play position four. How can you use it sensibly?

Choose an action and read the explanation.

Sources and context

This is my approach to reviewing decisions. I check game data against the current patch and distinguish practice scenarios from events in my own match.

OOPS DOTA hero atlas ↗Valve: hero abilities and stats ↗Dota2ProTracker: public builds and match samples ↗Crystal Maiden: Ruslan's published match ↗

Continue the breakdown

All heroes ↗Continue in the Dota database ↗Crystal Maiden match breakdown ↗Crystal Maiden match breakdown ↗Viper: watch the full episode ↗Choose an item for its purpose ↗

Less fog. More answers.