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.

Every roster has one entry that is quietly excellent and permanently unpopular. A difficult pick with a high ceiling is worse than an easy one until you have put the hours in. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts.

Good places to start

Role coverage inside a team matters more than the individual rating of any one pick. Tier lists describe a skill bracket, and most of them do not say which one. If your result differs from what is described here, note what is different first rather than starting over. Balance passes usually move numbers rather than reworking a kit, so the character still plays the same way.

New additions are typically overtuned at release and corrected within two patches. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. The strongest pick in professional play is often the worst pick in a solo queue.

How the roster breaks down

It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. The short version is near the top on purpose; the reasoning is there if you want to know why. If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about.

  • Check the patch date on any ranking you are reading.
  • Ignore tier lists that do not state the skill bracket they describe.
  • Read the whole sequence once before doing the first step.
  • Watch one match of the pick before committing time to it.

The picks that punish beginners

Screenshots age faster than text, which is why this describes rather than shows. Call of Duty is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. There is no hidden trick here that the game is keeping from you. Anything that behaves differently on console than on PC is flagged where it matters.

The community wisdom on this is roughly half right, and the half that is wrong costs the most time. The awkward part is rarely the step itself, it is knowing which step comes first. Nothing here assumes a particular playstyle beyond wanting the thing to work.

Why tier lists disagree

Most of the disagreement you will find online is two people describing different builds. The developers have changed their mind about this at least once, which explains the older advice. Where two approaches both work, the one with fewer moving parts is the one to keep.

Everything below is framed around the current state of Call of Duty rather than a launch-week impression. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. What follows assumes you are on a current install and have not modified it.

What changes between patches

A single check up front replaces a lot of guessing later. Do the cheap check before the expensive one — that ordering alone saves most of the frustration. Where something depends on your platform or region, that is called out rather than glossed over.

Where people go wrong

  • Ignoring the platform-specific note and then wondering why the steps do not line up.
  • Trusting a video thumbnail that promises a result the video never actually shows.
  • Rushing the last step, which is usually the one with the actual requirement in it.

Call of Duty 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 many are there in total?

The number moves every season. What matters more is that the roles behind them have stayed stable.

Are tier lists worth reading?

The reasoning is. The ordering is a snapshot of one patch at one skill level.

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.

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