Wiki Index

A central directory designed to support a growing library of RE:Heads, Please! pages.

The index organizes the Wiki by player intent. Use a category hub for broad discovery, an entity page for one verified item, coin, or accessory, and a guide when the question asks for a sequence or decision process. This separation keeps internal links useful and prevents a single page from competing with several unrelated searches.

Choose the right section

Codes covers status checks, redemption, expiration, rewards, and common errors without publishing unverified strings. The Database provides structured Items, Coins, and Accessories records, plus indexes for values, rarity, locations, acquisition, and verification. Guides explain beginner decisions, progression, farming, controls, and mechanics. Tier List pages provide editorial comparisons whose criteria and limits should be read before using a rank.

Entity pages and topic pages

An entity URL answers a question about one named record. It keeps the local image, category, verification state, updated date, documented fields, acquisition note, and related entries together. A topic URL explains a broader system such as rarity, inventory, rolling, controls, or comparison. If the question changes from “What is this entry?” to “How does this system work?”, follow the relevant guide rather than expecting the entity page to cover the whole category.

How to use the Wiki

1. Start with the hub that best matches the current goal.
2. Use the search box or database category when an exact name is known.
3. Read verification badges and update dates before relying on change-sensitive information.
4. Follow related pages only when they answer the next distinct question.
5. Check the latest in-game information whenever a requirement, value, location, menu, or result differs.

Information standards

The Wiki leaves unknown details unfilled instead of inventing precise probability, value, cost, or official status. A current interface result is stronger evidence than memory or an isolated screenshot. Rankings remain editorial, codes require current verification, and database entries publish only the fields available through the project’s reviewed data workflow.