Most advice about modern warfare 2 character assumes a starting point it never states.

Short answer

The direct answer is above the fold; the reasoning underneath is there for when the direct answer does not fit your situation.

The first attempt should be about understanding the shape of the problem. The accepted community answer is broadly right and wrong in a specific way that matters here. Call of Duty is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look.

When your situation differs

There is a version of this that takes ten minutes and a version that takes an evening, and both are valid. The step people skip is the one that makes the rest work. Screenshots age faster than text, which is why this describes rather than shows. Advice written for launch conditions is the most common source of confusion here.

It is worth separating what the game does from what players have concluded it does. Half of what gets described as a bug is a design decision people dislike. Most guides optimise for efficiency, which is not always what you want from a game.

The order that matters

The mechanic behind it is simpler than the discussion around it suggests. What follows assumes you are on a current install and have not modified it. Edge cases are genuinely rare, which is why the simple answer is usually the correct one.

  • Check which version any conflicting advice was written for.
  • Try the obvious thing before the clever one.
  • Check the version you are actually running before assuming anything is broken.
  • Write down where you started, so you can describe the problem if you need help.

What to do next

Nothing here depends on a setting you are unlikely to have. Version numbers matter more here than anywhere else in the discussion. Doing something the slow way once teaches more than doing it the fast way ten times. If something feels harder than described, the difference is usually a missing prerequisite.

Where the game contradicts its own documentation, the game wins. The right approach depends on where you are, and most advice assumes a starting point it never states. Trying the obvious thing first is underrated and costs almost nothing.

What to do instead

A single check up front replaces a lot of guessing later. Consensus forms early and updates slowly, which is why the top result can be years stale. Small habits compound faster than any single technique.

Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Knowing what to skip is worth as much as knowing what to do. A recommendation without a reason cannot be adapted when your situation differs.

Worth knowing alongside this

The awkward part is rarely the step itself, it is knowing which step comes first. Testing this yourself takes a few minutes and settles it definitively. Advice that worked for someone else may have depended on something they never mentioned.

Where people go wrong

  • Reading a summary of the patch notes instead of the patch notes.
  • Confusing a server-side outage with something broken locally.
  • Rushing the last step, which is usually the one with the actual requirement in it.
  • Skipping the prerequisite because it looked optional in someone else's summary.

Call of Duty FAQ

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.

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.

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.

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

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

When in doubt, do the cheap check first.