The roster question people are really asking is which few to learn first, not how many exist.

Short answer

Learn two: one that is forgiving and one that fits how you already want to play. Breadth comes later.

Role coverage inside a team matters more than the individual rating of any one pick. Every roster has one entry that is quietly excellent and permanently unpopular. Treat anything stated without a version number as provisional.

How the roster breaks down

Balance passes usually move numbers rather than reworking a kit, so the character still plays the same way. The strongest pick in professional play is often the worst pick in a solo queue. Where something depends on your platform or region, that is called out rather than glossed over. A difficult pick with a high ceiling is worse than an easy one until you have put the hours in.

Tier lists describe a skill bracket, and most of them do not say which one. There is no hidden trick here that the game is keeping from you. New additions are typically overtuned at release and corrected within two patches.

The picks that punish beginners

None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. Anything that behaves differently on console than on PC is flagged where it matters. The developers have changed their mind about this at least once, which explains the older advice.

  • Ignore tier lists that do not state the skill bracket they describe.
  • Expect a new release to be nerfed within a month.
  • If a menu path does not exist for you, your build is older or newer than the one described.
  • Check the patch date on any ranking you are reading.
  • Pick a role before picking a character.

Good places to start

If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. If you are coming to this after a long break, the terminology has probably moved on. A single check up front replaces a lot of guessing later. The short version is near the top on purpose; the reasoning is there if you want to know why.

If your result differs from what is described here, note what is different first rather than starting over. Nothing here assumes a particular playstyle beyond wanting the thing to work. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different.

Why tier lists disagree

Dota 2 is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. Most of the disagreement you will find online is two people describing different builds.

Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. Everything below is framed around the current state of Dota 2 rather than a launch-week impression. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see.

What changes between patches

The awkward part is rarely the step itself, it is knowing which step comes first. Screenshots age faster than text, which is why this describes rather than shows. Where two approaches both work, the one with fewer moving parts is the one to keep.

Where people go wrong

  • Assuming a guide from an older season still describes the current version.
  • Treating a rare edge case as the normal behaviour and planning around it.
  • Ignoring the platform-specific note and then wondering why the steps do not line up.

Dota 2 FAQ

Do I need any mods or third-party tools for this?

No. Everything described here works with the base game on any supported platform.

How long does this take?

Minutes if it goes cleanly, an evening if you hit the edge case in the caveats list. Neither is unusual.

Does this work the same on console and PC?

The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.

What if none of this works for me?

Then something in your setup differs from the assumption — version, region or platform. Check those three before anything else.

If you only take one thing from this: the answer near the top is the part that matters, the rest is context.