Reading the database

Updated 2026-10-07
Short answer

Use these pages to inspect extracted records and follow source references. Base values and table links do not establish final combat results, usable skills or drop probabilities.

Answer
Read the value together with its field name and evidence note.
Evidence
Local extracted records feed the adapter, paired field manifests and published entity pages.
Rule
A source relationship is not a tested gameplay formula.
Confidence
Verified producer mappings; runtime formulas and unresolved bindings remain unverified. This is a database guide, not a gameplay-tested strategy.
Updated
2026-10-07

Base values and codes

Hero stats are the extracted base values. They are not a calculation of your current character after equipment or other progression. Final formulas and units without a verified definition remain unverified.

Equipment rating, slot and class codes are raw source values. Compare records using the displayed code and field name; do not assume a code is a named rarity or a percentage. Modifier types and values are paired from the same record.

Effects and skill references

An effect with unresolved numeric placeholders is marked unverified. Its original template is retained for inspection rather than filled with guessed damage, duration or percentages.

Class-matched skill groups share the hero's source class code and show the lowest listed level in each group. This does not establish that a particular hero can equip that skill. An unpublished base-skill ID is shown as unavailable. SkillTypes references are not treated as skill IDs; their runtime binding remains unverified.

Stage rewards are source references

Stage pages follow monster and reward-table references to published records. Unpublished monster details retain their IDs without invented pages. Reward references, including zero-weight records, do not establish eligibility or drop probabilities. Listed rewards and source rates do not establish farming efficiency.

Inspect real examples

Common questions

Does unverified mean the extracted value is missing?

No. A stored value can be visible while its unit, formula, code label or runtime binding remains unverified. Read the specific evidence note on the page.

Can I calculate final damage or drop chances from these pages?

The database does not establish the required runtime formulas or probability rules. Those results remain unverified.

Sources

  • Local extraction and publication pipeline — data/runs/1079186399771818186/check-20261004-1558/normalized; site/scripts/wog-adapter.mjs; site/data/wog/hero-fields.json; site/data/wog/table-fields.json.
  • Published examples below — Each example links to the entity produced from the local records; source properties are shown on its page.