PLAYER GUIDE

Using the Database

Search exact values, compare levels, follow entity relationships, and recognize what static data can and cannot prove.

Quick recommendationUse global search when you know a name or mechanic. Use a family catalogue when you want to compare many entries of the same kind. Every useful detail page separates high-value facts from additional technical values and links the entities that depend on each other.

The direct answer

Use global search when you know a name or mechanic. Use a family catalogue when you want to compare many entries of the same kind. Every useful detail page separates high-value facts from additional technical values and links the entities that depend on each other.

Read a detail page

What it is gives the plain-English role.

Verified values contains the most decision-relevant static fields first.

Additional values expands the rest of the safe static fields without exposing raw implementation records.

Related entries connects upgrade levels to parents, events to steps, units to attacks, unlocks to rewards, and status effects to their sources.

What static data cannot promise

A static value is not always the final in-run value. Difficulty, player count, active modifiers, random rolls, temporary effects, and future patches can transform it.

Unnamed records, runtime-only behavior, unknown localization, raw assets, implementation code, and audio are intentionally not turned into guessed public claims.

Use the patch page when the developer has announced a live change newer than a sealed local build.

Open the reference