Sephiria Artifacts

Artifacts are not just a list of bonuses. Their value depends on shape, location, neighbors, and the weapon that turns the bonus into action. A player who takes every attractive item can end a run with many strong words and no connected plan. This hub focuses on the decisions that remain useful even when item pools and values change: inspect the footprint, identify the effect, protect the important region of the bag, and record what the current build actually did.

A useful Artifact record

For each item, keep five fields: the displayed name, the footprint or placement shape, the visible effect, the build job, and the conditions under which it was tested. Add the source URL when the name came from a community guide or Steam Community post. If a field is unknown, use “not confirmed” rather than a guessed value. This gives the catalog a way to survive an update without silently rewriting history.

An Artifact can be valuable because it improves the next room, because it completes a pattern, or because it gives the run a defensive fallback. These are different jobs. A temporary survival pickup may be correct during a dangerous chapter even when it would be cut from a damage showcase. A guide should explain the decision context so readers do not copy an item into a completely different route.

Placement before collection

When a reward appears, inspect it beside the current inventory. Ask which slots it occupies, which bonus it receives from the present Tablets, and what it displaces. If the answer is unclear, keep the item unplaced until you understand the trade. The official inventory system makes arrangement part of the game, so a catalog that ignores footprint is incomplete even if every name is spelled correctly.

Use a screenshot for unfamiliar effects, but do not crop away the version or menu context. A future player should be able to tell whether the result came from a run, a journal entry, or a community spreadsheet. That distinction is especially important for item names that changed during Early Access.

Link Artifacts to other hubs

The Artifacts Guide defines the record fields. Artifact Synergies covers combinations without promising a tier list. Artifact Farming tracks how to pursue a target while preserving current-route caveats. Pair every page with the Tablets and Weapons hubs; an Artifact claim without its placement and weapon context is not a complete build recommendation.

That stopping point also gives the page a natural update boundary: retest the core arrangement first after a patch, then investigate optional pieces.

Evaluate an Artifact in context

Start by asking which action the Artifact is meant to support. A piece that helps a close-range action may be awkward in a ranged plan, and a piece that looks efficient in an empty inventory may compete with the space needed for a Tablet. Record the job, required shape, and the part of the run where the benefit was visible. This is enough to compare two options without inventing a universal ranking.

The Synergies Guide treats combinations as hypotheses. Add one supporting piece, test the same checkpoint, and keep the result if it improves the stated job without creating a new failure. The Farming Guide handles repeated attempts and resource notes when a player needs a particular category rather than a guessed item name.

Keep the inventory readable

A good layout has a visible center of gravity. The player should know which spaces are essential, which can be replaced, and which are reserved for a future test. When every square is filled, a new reward becomes a forced deletion rather than an informed choice. Leave a small margin when the route is still being learned, and record the reason if the final build intentionally accepts a tight fit.

Separate evidence types

The Steam listing supports the broad inventory concept. A community screenshot can suggest a layout, while the current game confirms whether the layout still works. Label those sources separately and avoid copying a table or image. A future patch may preserve the idea but change the exact value, shape, or activation rule.

Decide when to stop collecting

Stop adding pieces when the build can perform its stated job and the next pickup would only make the explanation less clear. A small, verified arrangement is easier to compare than a crowded end-of-run snapshot. If the run continues, keep later discoveries in a separate note so readers can distinguish the tested core from optional experimentation.