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

Short answer

Pick by role first, personality second, tier list a distant third.

Role coverage inside a team matters more than the individual rating of any one pick. New additions are typically overtuned at release and corrected within two patches. Anything that behaves differently on console than on PC is flagged where it matters.

Good places to start

Balance passes usually move numbers rather than reworking a kit, so the character still plays the same way. Every roster has one entry that is quietly excellent and permanently unpopular. Most of the disagreement you will find online is two people describing different builds. The strongest pick in professional play is often the worst pick in a solo queue.

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. A difficult pick with a high ceiling is worse than an easy one until you have put the hours in.

What changes between patches

What follows assumes you are on a current install and have not modified it. Do the cheap check before the expensive one — that ordering alone saves most of the frustration. If your result differs from what is described here, note what is different first rather than starting over.

  • Watch one match of the pick before committing time to it.
  • Pick a role before picking a character.
  • Check the version you are actually running before assuming anything is broken.
  • Learn one forgiving option properly before adding a second.
  • Check the patch date on any ranking you are reading.
  • If a menu path does not exist for you, your build is older or newer than the one described.

How the roster breaks down

If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. Nothing here assumes a particular playstyle beyond wanting the thing to work. The short version is near the top on purpose; the reasoning is there if you want to know why. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts.

Where something depends on your platform or region, that is called out rather than glossed over. A single check up front replaces a lot of guessing later. Apex Legends is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look.

Why tier lists disagree

The awkward part is rarely the step itself, it is knowing which step comes first. The community wisdom on this is roughly half right, and the half that is wrong costs the most time. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of.

It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Treat anything stated without a version number as provisional. Screenshots age faster than text, which is why this describes rather than shows.

The picks that punish beginners

The developers have changed their mind about this at least once, which explains the older advice. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. If you are coming to this after a long break, the terminology has probably moved on.

Where people go wrong

  • Assuming a guide from an older season still describes the current version.
  • Trusting a video thumbnail that promises a result the video never actually shows.
  • 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.

Apex FAQ

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.

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

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

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.

Why do other guides describe this differently?

Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.

Come back to the caveats list if it does not work first time — the answer is almost always in there.