What this database is for
The database is the evidence layer behind the wiki's guides and tools. It separates extracted facts from editorial recommendations: class weights, race tendencies, attribute descriptions, trait effects, party bonuses, event branches, regional biomes, dungeon conditions, equipment rules, and guild-start options each have their own table. Use it when you need to verify a number, trace a recommendation, or compare the current build with an archived release.
Which table answers your question
For a recruitment decision, begin with Classes andRaces, then inspect the candidate'sTraits. Class weights describe the attributes a role favours; race tendencies can reinforce or penalise parts of that profile; traits add behaviour and economic consequences. The Synergies table answers a separate party-level question and should be checked after the individual shortlist is credible.
For a delve, use Regions to identify the biome and possible environmental rolls, then open Dungeon conditions for the actual penalties and counters. Region condition tags are not the same thing as the executable biome-to-condition pool. Keeping those two layers separate prevents a flavour label from being mistaken for a mechanic.
How evidence is labelled
Each data entry carries a verified version and source reference where the extractor can provide one. “Datamined” means the value was recovered from the shipped web bundle; it does not mean every internal implementation detail has been reproduced or that a formula inferred from one table applies everywhere. Guide prose labels developer statements, current executable behaviour, and community workarounds separately so they do not quietly become equivalent claims.
When the interface text and executable behaviour disagree, the wiki records the mismatch rather than hiding it. When a value cannot be verified, the page should say so instead of filling the gap with a familiar rule from another game. This standard is more useful than completeness at any cost because it tells you which decisions are safe to make from the available evidence.
Versioned pages are snapshots
The unprefixed URL is the current build. An address beginning with a version prefix is an archived snapshot and is clearly marked at the top of the page. Archived URLs are useful for understanding a saved game, old screenshot, or past discussion, but their numbers should not be mixed with the current dataset. Thechangelog summarises releases and links the comparison path.
A practical verification routine
- Confirm the version badge before copying any number.
- Open the narrowest table that answers the question.
- Read captions and caveats around derived recommendations.
- Cross-check the related system, such as class plus race or region plus condition.
- Use a guide only after the underlying data is understood.
If you find a mismatch in the current build, send the page URL, displayed version, and a screenshot or reproducible in-game observation through Contact. That gives the maintainer enough context to distinguish an extraction error, a patch change, and an interface-only discrepancy.