This comes up often enough in Rainbow Six Siege that it deserves a straight answer rather than a thread to scroll through.

Short answer

Do the simple thing first. It is correct more often than the complicated thing people recommend instead.

  • Note the exception cases — they are specific rather than vague.
  • Check which version any conflicting advice was written for.
  • Keep a save or backup from before you start — it costs nothing and occasionally saves an evening.

Siege rewards knowing the building more than knowing the gun, which is why map knowledge outranks aim here. Testing this yourself takes a few minutes and settles it definitively. The accepted community answer is broadly right and wrong in a specific way that matters here.

What to do instead

Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Edge cases are genuinely rare, which is why the simple answer is usually the correct one. It is worth separating what the game does from what players have concluded it does. Nothing here assumes a particular playstyle beyond wanting the thing to work.

Nothing here depends on a setting you are unlikely to have. Most of the disagreement online comes from people describing different versions of Rainbow Six Siege. The developers have changed their mind about this at least once, which explains the older advice.

Why it works this way

The mechanic behind it is simpler than the discussion around it suggests. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. Where two approaches both work, the one with fewer moving parts is the one to keep.

  • Do not build a routine around an edge case.
  • Try the straightforward approach before the elaborate one.
  • Check the version you are actually running before assuming anything is broken.
  • Revisit after a major patch if the behaviour changes.

When the usual advice fails

The awkward part is rarely the step itself, it is knowing which step comes first. A single check up front replaces a lot of guessing later. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Everything below is framed around the current state of Rainbow Six Siege rather than a launch-week impression.

Where something depends on your platform or region, that is called out rather than glossed over. Anything that behaves differently on console than on PC is flagged where it matters. Screenshots age faster than text, which is why this describes rather than shows.

The practical answer

If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. Most of the disagreement you will find online is two people describing different builds. What follows assumes you are on a current install and have not modified it.

Rainbow Six Siege is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. There is no hidden trick here that the game is keeping from you.

Worth knowing alongside this

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. The community wisdom on this is roughly half right, and the half that is wrong costs the most time.

Where people go wrong

  • Assuming a guide from an older season still describes the current version.
  • Grinding a method that was patched months ago because a thread still ranks well.
  • 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.

Siege 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.

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.

Is there a faster method?

Sometimes, at the cost of reliability. Where that trade exists it is described rather than recommended blindly.

Does this change between platforms?

The behaviour does not. Where menu paths or prompts differ, that is noted above.

Work through it in the order above and bandit welcome pack stops being a question you have to look up again.