If you have run into Lore in Rainbow Six Siege and moved on without quite understanding it, this is the explanation.

Short answer

It is worth understanding once properly, because a lot of other things in Rainbow Six Siege refer back to it.

  • Read the in-game description once, then ignore it.
  • It rewards attention rather than preparation.
  • Region and platform change more than people expect, so confirm both.

Siege rewards knowing the building more than knowing the gun, which is why map knowledge outranks aim here. Two similarly named things exist, and mixing them up explains a lot of contradictory advice. It rewards understanding rather than grinding, which is unusual for Rainbow Six Siege.

What it is

Screenshots age faster than text, which is why this describes rather than shows. Its role has changed across updates, so older discussion describes something slightly different. Knowing this does not make you better at Rainbow Six Siege, but it does make the rest of it legible. A single check up front replaces a lot of guessing later.

It is more consequential in the late game than the early one, which is why first impressions mislead. The name is descriptive if you already know what it does, and opaque if you do not. Treat anything stated without a version number as provisional.

Why people keep asking about it

It shows up in more places than its introduction suggests, once you know to look. The game introduces it quickly and assumes you picked it up, which is where the confusion starts. Do the cheap check before the expensive one — that ordering alone saves most of the frustration.

  • Check which version of Rainbow Six Siege any discussion of it is describing.
  • Do not build a plan around it before you have seen it work.
  • Read the whole sequence once before doing the first step.
  • Expect its role to have shifted at least once across updates.

How it connects to the rest of Rainbow Six Siege

It is the kind of thing veterans forget they ever had to learn. It became noticeably more relevant after a change the patch notes barely mentioned. Anything that behaves differently on console than on PC is flagged where it matters. Most guides mention it in passing and none of them stop to define it.

Whether it is worth going out of your way for depends entirely on how you are playing. The developers have changed their mind about this at least once, which explains the older advice. Its practical value is narrow and real, rather than broad and theoretical.

Whether it is worth going out of your way for

The wiki entry is thorough and buries the actually useful part six paragraphs down. The short version is near the top on purpose; the reasoning is there if you want to know why. It appears in supplementary material in more detail than it does in the game itself.

If you only remember one thing about it, remember where it appears. If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. The in-game description is technically accurate and practically useless.

What it is often confused with

Community shorthand around it has drifted far enough from the original meaning to cause arguments. There is no hidden trick here that the game is keeping from you. There is a persistent myth attached to it that has never been true in any version.

Where people go wrong

  • Grinding a method that was patched months ago because a thread still ranks well.
  • Skipping the prerequisite because it looked optional in someone else's summary.
  • Downloading a helper tool for something the game already does in its own menu.

Siege FAQ

Where can I read more?

The official material covers it in more depth than the game does, and considerably more reliably than aggregated fan pages.

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.

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.

Anything that shifts with the next Rainbow Six Siege update will show up as a changed number, not a changed approach.