The fastest way to misunderstand Sephiria Artifacts is to sort them into good and bad without looking at the bag. The official store says Artifacts are collected and arranged, then empowered by Tablets. That means the first useful classification is not rarity; it is whether the item improves the current action, completes a layout, or provides a fallback when the run changes.
The five fields to inspect
Effect
Read the displayed text and identify the stat, action, trigger, or condition it changes. Copy the wording exactly when documenting it.
Footprint
Count the occupied squares or shape shown by the game. A strong effect that blocks the only useful Tablet region may be a poor trade.
Job
Label the item as damage, defense, mobility, resource, or combo support. A clear job makes the next reward easier to judge.
Context
Record weapon, chapter, difficulty, and whether the item was tested solo or in co-op. These fields prevent false comparisons.
Placement questions
Before placing an Artifact, look at the Tablet bonuses that touch the proposed region. Then look one move ahead: if the next item has a different shape, can the current layout still be repaired? Do not optimize every square during a dangerous room. A safe temporary placement is better than losing a run while chasing a perfect arrangement. Reorganize after the threat is clear.
If an item has an unfamiliar trigger, test it in a controlled situation. Make one change, observe the result, and record the patch context. A single lucky critical hit does not prove an activation rule. If the game gives no visible confirmation, mark the entry as needing in-game verification and avoid giving it a precise number.
How to publish a catalog responsibly
An item page should show the displayed name, source, last checked date, version, and a confidence label. Use “official” for a store or developer statement, “in-game checked” for an observation recorded in the current build, “community reported” for a dated player source, and “needs testing” where the evidence is incomplete. Never convert a community spreadsheet into a permanent number without verifying its version.
The catalog can still be useful when incomplete. A player may search for a name, learn where it fits, and see exactly what remains unknown. That is better than a polished table that silently mixes Early Access and 1.0 values.
Finally, record the negative result. If a placement looked promising but created a crowded retreat, say so beside the successful alternative. Negative evidence helps players choose an Artifact by function and gives the next patch a clear behavior to retest.
This record is also useful when a player changes weapons. Keep the Artifact observation, then rerun the same placement with the new weapon instead of assuming that a shared inventory effect transfers unchanged.
A practical placement test
Place the Artifact where the intended interaction is visible, then use the same room or action three times. Watch for the displayed effect, the action’s reliability, and any cost in movement or space. If one of those changes is uncertain, do not convert the result into a number. Capture the visible state and repeat after checking the current version.
Replace by function, not rarity
When the inventory is full, compare the outgoing Artifact’s job with the incoming piece’s job. A rare-looking replacement is not automatically better if it removes the only safe recovery option. Use the Builds page to define the run objective, then keep the piece that makes that objective more repeatable. This approach remains useful even when the live item pool changes.
Make the record searchable
Use the displayed name only after checking the current menu, and add a plain-language role such as reach, survival, control, or setup. Include the footprint or arrangement only when it is visible and versioned. This gives a player a useful search path while keeping an uncertain catalog field clearly separate from an observed effect.