Data methodology
A database is only as useful as its field definitions.
A searchable game database can look precise while hiding the two things a player needs most: where a value came from and what it does not include. This page explains how New Game HQ builds a database page, how a row is checked, how missing values are handled, and how to tell whether a record applies to your build.
- Record goal
- One entity, one decision
- Source order
- Game UI, official notes, repeatable observation
- Missing value
- Shown as unknown, never as zero
- Row check
- Version and date on the page
What a database does
Each row should answer a lookup, not decorate a list.
A New Game HQ database page exists to make one kind of comparison faster: which material comes from which node, which character fits which role, which crop fits the remaining season, which recipe uses a component you already own, or which item is still missing from a collection. The page is organized around the question, not around the order a source happens to list its rows.
That is why a database page is more than a table. It should tell you which field changes the decision, which field is only identification, which values are stable, and which values are likely to move after a patch. A table without field definitions asks you to guess what a column means.
A database page is also not a walkthrough. If the answer depends on a route, a boss, or a sequence, the page links to the focused guide that handles the route. The database tells you which record to use; the guide tells you what to do with it.
Where records come from
We start with what the game and the developer actually show.
Records are built from the current game interface, official store pages, official patch notes, developer posts, and repeatable in-game observations. A community reference can reveal a question or a naming convention, but it is not promoted to a confirmed value without a second check.
The order matters:
A record that only exists in a community table is marked as reported or left out. A record that appears in the game but not in any official note is still useful; the page records the build and the date so the reader knows which version the row belongs to.
Fields and definitions
Every column has a job, a source type, and a limit.
Most New Game HQ records use a small set of fields. The exact fields differ by game, but the roles are consistent:
The name, icon, category, and stable identifier that let a reader recognize the record and find it again.
The level, material, unlock, location, or prerequisite that decides whether the record is available to this player.
The value the game shows: range, damage, yield, duration, cost, or another number that changes a comparison.
Where the record is obtained: a node, vendor, drop, recipe, mission, or collection.
The player action the record supports: craft, farm, donate, sell, skip, or verify before spending.
What the row does not establish: a hidden formula, a later upgrade, a platform difference, or a value that needs a live check.
If a source lists a field that does not change a decision, it is usually left out. A shorter row with a clear decision is more useful than a wide row that copies every field from a menu.
Grouping and duplicates
One entity should not become three rows because three sources named it differently.
Records are grouped by the stable identity the game uses, not by the wording of a source. A rename, an abbreviation, a quality variant, and a crafted form can be separate records when the game treats them separately, and one record when the game treats them as the same item. The page’s grouping should match the decision: if two rows always lead to the same action, they belong together; if they change the action, they stay separate.
We also avoid turning a category into a fake entity. A “best weapon” row, a “general material” row, or a “recommended build” card is not a game entity. Those belong in a focused guide where the recommendation can explain its conditions, not in a database where every row is supposed to be a stable record.
Unknown values
Unknown is a value. Zero is a claim.
When the game does not show a number, the page does not invent one. An unknown drop rate is shown as unknown, not as zero and not as a plausible percentage. An unlock that cannot be confirmed is shown as an open check, not as a level requirement borrowed from another game or an older build.
This rule can make a database look less complete than a competitor’s. That is intentional. A missing value is honest; a filled-in guess is expensive for the player who plans around it. When a value becomes available in a later build, the row is updated and the check date changes.
Version and date
The page date tells you which build the rows belong to.
Every database page shows a record snapshot date. That date is the last time the page’s records were checked against the current build, not the date the page was first written. A page with an old date is not automatically wrong, but it is a signal to check the live game before relying on a value that patches can change.
When a patch changes a field, the page is updated in place and the snapshot date moves. When a patch adds a new entity type, the page may keep its current scope and link to a new page instead of becoming an unbounded list. A database page should stay predictable: the same fields, the same decision, a newer check.
What we exclude
Some data is intentionally not published.
- Datamined values, hidden formulas, and internal identifiers that the game does not show to players.
- Leaked or pre-release values presented as current facts.
- Another site’s table order, descriptions, or complete page structure.
- Player counts and activity numbers without a date and a source.
- Personal information, account data, or anything collected from a reader.
A database can be useful without exposing the game’s internals. The goal is a player decision, not a data dump.
Coverage and gaps
A published count describes the page, not the game.
When a page says it covers 74 materials, that number describes the records that passed the page’s check. It does not promise that the game contains exactly 74 materials, and it does not promise that every variant is included. A page can be complete for its stated scope and still leave a later area, a seasonal variant, or a platform-exclusive item for a future update.
Coverage gaps are stated on the page when they affect a decision. If a database only covers the first region, the page says so. If a tool only supports one mode, the tool says so. A clear scope is more useful than a vague promise of completeness.
How to read a row
Start with the requirement, then the effect, then the source.
Read a row in the order that changes a decision. First, check whether the requirement is met: level, material, unlock, location, or prerequisite. Second, compare the effect that matters for the current job, not every number in the row. Third, confirm the source, because a perfect effect is useless if the item cannot be obtained before the season ends or the route closes.
If the row includes a decision or boundary note, read it before spending. That note is where the page says what the number does not tell you: a hidden cooldown, a platform difference, a later upgrade, or a value that needs a live check. The note is part of the record, not a disclaimer added afterward.
Report a wrong row
Send the row, the build, and what your screen shows.
If a row is wrong, include the page URL, the record name, your platform and build, and the value or source you see instead. A screenshot of the menu or tooltip is enough if it shows the field that differs. If the row is missing entirely, name the entity and where it appears in the game.
Reports are checked against the current build. An accepted correction updates the record and the snapshot date. A report that cannot be reproduced stays open and is not used to overwrite a confirmed value. Use the corrections page for a row correction, or the contact page for a privacy, copyright, or accessibility request.
For the guide side of the same process, see how we test.