01

The inventory is part of the build

The official store page describes a strategic inventory system in which artifacts are collected, arranged, and empowered by tablets. That means a page about an artifact should explain both its effect and the space or adjacency decision it creates.

02

Compare synergy, not rarity

A rare artifact that cannot be activated by your current route may be weaker than a common effect that supports every room. Record the weapon, tablet, and inventory position used when you test a combination.

03

What each catalog entry needs

Every future artifact page should include its effect, max level if verified, tablet interactions, common partners, unlock source, and a last-tested version. Until those fields are captured in-game, mark the entry as pending rather than filling gaps with guesses.

04

Read an artifact in context

Check what the artifact changes, what it costs in inventory space, and whether a tablet can activate or amplify it. The best entry explains the action it improves rather than calling it universally strong.

Group artifacts by the job they solve: damage, room control, mobility, sustain, or build access. A player can then find a substitute when the ideal item does not appear.

05

A catalog entry that stays useful

Store the exact name, effect text, level behavior, tablet interaction, common partners, and last-tested version. Add an image from the Journal when possible so readers can identify the item in a crowded selection.

If the effect or cap is not verified in the current client, mark it as pending and link the evidence request instead of inventing a value.

06

Build a real artifact record

An artifact name by itself is not enough. A useful record starts with a clear screenshot and the exact effect text, then adds its inventory footprint, rarity, tag family, tablet interaction, likely partner, and last-tested version. That layout lets a player identify an item quickly and decide whether it belongs in the current grid.

The most important detail is the replacement. If a run misses a rare artifact, readers need to know which common effect preserves the same job: room control, sustain, burst, mobility, or build access. This is where a wiki becomes more useful than a gallery of item names.