1 is easy to miss entirely and awkward to look up once you have, which is a common combination in Path of Exile.
Short answer
In practical terms: know what it does, know where it appears, and the rest is context.
- Read the in-game description once, then ignore it.
- Note where it first appears, so you can go back if you need to.
- Expect one number in every guide to be out of date; the method is what matters.
Path of Exile assumes you will read a spreadsheet eventually, and most of its depth is genuinely there. It rewards understanding rather than grinding, which is unusual for Path of Exile. It appears in supplementary material in more detail than it does in the game itself.
Whether it is worth going out of your way for
Most of the disagreement you will find online is two people describing different builds. The wiki entry is thorough and buries the actually useful part six paragraphs down. Two similarly named things exist, and mixing them up explains a lot of contradictory advice. 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. It became noticeably more relevant after a change the patch notes barely mentioned. If you are coming to this after a long break, the terminology has probably moved on.
What it is often confused with
The name is descriptive if you already know what it does, and opaque if you do not. It shows up in more places than its introduction suggests, once you know to look. The short version is near the top on purpose; the reasoning is there if you want to know why.
- Ask what it is for before asking how to get it.
- It rewards attention rather than preparation.
- Region and platform change more than people expect, so confirm both.
- Do not build a plan around it before you have seen it work.
- Treat wiki trivia sections as trivia rather than mechanics.
- Prefer the in-game option over an external tool when both exist.
Why people keep asking about it
Knowing this does not make you better at Path of Exile, but it does make the rest of it legible. Its role has changed across updates, so older discussion describes something slightly different. 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.
Early impressions of it are usually wrong in the same specific way. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. The in-game description is technically accurate and practically useless.
How it has changed over time
Most guides mention it in passing and none of them stop to define it. What follows assumes you are on a current install and have not modified it. It is the kind of thing veterans forget they ever had to learn.
If you only remember one thing about it, remember where it appears. The developers have changed their mind about this at least once, which explains the older advice. Community shorthand around it has drifted far enough from the original meaning to cause arguments.
What it is
The game introduces it quickly and assumes you picked it up, which is where the confusion starts. Treat anything stated without a version number as provisional. Whether it is worth going out of your way for depends entirely on how you are playing.
Where people go wrong
- Assuming a guide from an older season still describes the current version.
- Treating a rare edge case as the normal behaviour and planning around it.
- Grinding a method that was patched months ago because a thread still ranks well.
PoE 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.
Is it important?
More than its screen time implies, less than the discussion around it implies. Somewhere in the middle.
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.
If you only take one thing from this: the answer near the top is the part that matters, the rest is context.