What belongs in an item index?
An item page should answer three concrete questions: what the object is, what effect the source attributes to it, and how a player can encounter or use it. The official Items (Survivors) page is the source for that structure. The Steam store page supplies broad game context, but it cannot replace an item-specific entry or justify a detailed effect that is not listed there.
This hub avoids turning every clue into a confirmed object type. Potato is linked as a dedicated item page because the official Wiki explicitly treats Potato as an Item. Its trivia and community explanations are kept on that page as separate evidence, rather than relabeling the whole category around an Easter Egg.
A reliable item-reading workflow
Open the current Wiki item entry and record the literal name, category, effect, and acquisition information. If a field is absent, mark it unknown. Then check whether the effect is a confirmed mechanic or a player observation. A guide can still tell the reader what to investigate without filling an absent field with a familiar genre assumption.
When an item interacts with Luck, upgrades, or a weapon route, link to the relevant mechanics page. Cross-links should explain why the reader is moving: item effect first, stat interpretation second, build consequence last.
- Do not infer an effect from an item name alone.
- Keep item type and trivia or Easter Egg interpretation separate.
- Record the mode or run context when acquisition is mode-dependent.
- Recheck an item after a 1.0 update before stating exact values.
Item notes that stay useful
This level of separation is slower than copying a list, but it makes the index durable. Readers can see which line is a game fact and which line is a route worth testing.
| Field | Good note | Avoid |
|---|---|---|
| Object | The official source classifies the object as an item | Calling it an Easter Egg because of a community clue |
| Effect | Quote or paraphrase the current item entry | Inventing a hidden bonus from its name |
| Acquisition | State the documented route or mark unknown | Turning a Steam percentage into an unlock condition |
| Build use | Label a testable editorial interaction | Calling one interaction universally best |
Potato is a case study
The Potato page demonstrates the boundary. The official Wiki identifies Potato as an Item and records its achievement relationship and trivia. Gamepressure adds background around the Potato discussion. Those sources can support a carefully labeled explanation, but a community Easter Egg clue should not replace the object classification or become a universal mechanic claim.
Use the dedicated page when the search question is Potato. Return here when you need the broader item list or want to connect an item effect to Luck or an upgrade route.
Next step
For a specific item, start with the official Wiki Items page and then follow the page that explains its interaction. For Potato, open the deep dive. For a stat-shaped effect, compare Luck Mechanics. For an upgrade-shaped effect, read Weapon Upgrade Route.