Variant reference

Timeless Jewel conqueror explained

Understand why the conqueror or variant line must stay attached to every Timeless Jewel seed check.

Timeless Jewel conqueror explainedSeed checksSocket context

What to check first

Start with the facts that change the result before deciding whether the seed deserves a full socket scan.

01

Why the conqueror matters

The conqueror or variant is part of the input set. A seed note without it can point to the wrong keystone context or an incomplete trade check.

02

Same seed is not enough

Do not compare two Timeless Jewels by seed number alone. Family, variant, passive, and socket context decide whether the result is useful.

03

Best page for exact proof

Use this page for the concept, then open the calculator when the question becomes one exact passive and seed result.

Seed research workflow

Keep the jewel, seed, passive, and socket together so the result stays reproducible.

Step 1

Read the full item line

Capture the jewel family, conqueror or variant, and seed before checking a passive.

Step 2

Keep variant in the URL

When you calculate or share a result, preserve the selected conqueror so the recipient opens the same context.

Step 3

Use Any only for stat search

The tree scanner can use Any for stat searches that exclude keystones, but a single-seed keystone read still needs a specific conqueror.

Search tasks covered

Use this family page for focused seed checks, then move to the calculator or build pages when the task changes.

timeless jewel conquerortimeless jewel conqueror explainedpoe timeless jewel conquerortimeless jewel variants

How to verify a seed

Use the page as a short worksheet before you trust a trade listing, screenshot, or build note.

Start from a real passive

Open the calculator only after you know which passive or notable matters to the build. For Timeless Jewel conqueror explained, a result on an unreachable branch is usually a distraction, even when the text looks strong.

Preserve the full input set

Keep the jewel family, conqueror or variant, seed number, and passive node together. If one of those details changes, the result should be checked again instead of copied from memory.

Move to the scanner when context matters

A single passive check is fast, but many Timeless Jewel decisions depend on a cluster of nearby nodes. Use the tree scanner when a socket has more than one candidate notable worth counting.

Seed note format

A useful note should tell you what was checked, what changed, and which page should be opened next.

Input line

Write the jewel family, conqueror or variant, seed number, socket region, and passive node in one place. This makes the result easy to reproduce when a trade listing disappears or a build note is shared later.

Observed change

Record the changed passive text and whether the result is a keystone, notable, small passive, or added modifier. Keep the wording narrow so the note does not imply value outside the checked socket.

Next action

Mark the seed as check, scan, keep, or reject. A family guide should usually hand off to the calculator for one passive or to the tree scanner when nearby nodes decide the value.

Reference checks

Use these notes to keep the page tied to supported data and a clear next action.

Note

Family variant names

The shipped data includes Xibaqua, Zerphi, Ahuana, Doryani, Kaom, Rakiata, Kiloava, Akoya, Deshret, Balbala, Asenath, Nasima, Venarius, Maxarius, Dominus, Avarius, Cadiro, Victario, Chitus, Caspiro, Vorana, Uhtred, and Medved.

Note

Keystone caution

When the result involves a keystone, avoid shortcut comparisons. Re-open the exact family, conqueror, passive, and seed before writing a recommendation.

Note

Build handoff

If the variant is known but the best socket is not, move to a build note or tree scanner instead of staying on a single passive.

Mistakes to avoid

Most bad Timeless Jewel reads come from separating a seed from the build path that makes it valuable.

Avoid

Do not judge by seed number alone

Timeless Jewel conqueror explained only becomes meaningful when the jewel family, conqueror or variant, passive node, and socket context are checked together.

Avoid

Do not ignore reachability

A result can look powerful on paper and still be wrong for the character if the useful node sits outside the real path.

Avoid

Do not lose the source result

Save the calculator or tree-scanner URL when a seed looks promising so the exact input set can be opened again later.

Recommended handoff

Choose the next step based on whether you need one passive, a whole socket, or build-level context.

Continue research

Move from the family guide into exact seed checks without losing the query trail.