How to Verify a POE2 Time-Lost Jewel Interaction

A value that appears unchanged does not settle the interaction. Isolate the jewel, preserve a baseline, and classify the result without guessing at the underlying rule.

Start with the evidence boundary

Prevent a community-reported possibility from becoming an unsupported mechanic claim.

• The community signal establishes that players are uncertain about the interaction, but it is demand context rather than factual authority.
• The captured official patch index shows update activity through 0.5.5e but supplies no Time-Lost Jewel mechanic, formula, affected-node list, display rule, or rounding rule.
• Treat both the proposed effect and integer-rounding explanation as hypotheses to test.

Define one interaction claim

Turn a vague expectation into a result that can be observed and recorded.

• Copy the relevant in-game jewel wording exactly as it appears in the current version.
• Identify one displayed passive value that you expect to respond to the jewel.
• Write the expected observation without inventing a percentage, threshold, or formula.

Freeze the baseline

Make the before-and-after comparison attributable to one changed variable.

• Record the current game version, passive-tree state, equipment, skills, and other relevant configuration details.
• Capture the jewel wording and the target value before changing the jewel state.
• Preserve screenshots or notes so both states can be compared directly.

Run a one-variable comparison

Test the jewel while minimizing competing explanations.

• Observe the target value with the jewel absent.
• Change only the jewel state, then observe the same target value again.
• Repeat the comparison under the same recorded setup before classifying the result.

Classify the result conservatively

Separate observations from explanations that the closed sources do not establish.

• A repeatable displayed difference supports only the tested jewel, value, layout, and version.
• An unchanged display does not distinguish among no interaction, a threshold or rounding possibility, and display behavior.
• A result that cannot be repeated remains unresolved and should not guide further commitments.

Apply a commitment gate

Keep an uncertain interaction from driving irreversible build decisions.

• Proceed only with conclusions demonstrated by the recorded comparison.
• Preserve a workable configuration that can be restored if the test fails or later evidence changes the interpretation.
• Repeat the verification after a relevant update because the interaction is patch-sensitive.

Decision checklist

• Record the current game version.
• Copy the jewel wording from the current in-game item.
• Choose one displayed passive value to test.
• Capture the baseline with the jewel absent.
• Change only the jewel state.
• Capture the same value with the jewel present.
• Repeat the comparison under the same setup.
• Label unchanged or inconsistent results as unresolved.

Worked example

A player expects a Time-Lost Jewel to change a displayed passive value. They record the current version, screenshot the jewel wording and target value, and save the existing setup. They compare the target with the jewel absent and present without changing anything else. The display remains unchanged in repeated comparisons. Because the supplied evidence contains no formula or rounding rule, they record an unresolved result instead of assigning a cause, preserve the original setup, and postpone further build commitments until mechanic-level evidence becomes available.

Common mistakes

• Treating the community report as confirmation of the mechanic.
• Changing passives, gear, or skills during the jewel comparison.
• Inferring a formula from one displayed result.
• Calling an unchanged integer proof of rounding.
• Extending one tested result to every jewel, passive, layout, or version.
• Committing additional build resources before the interaction is resolved.

Related guides