Four labels, four different promises
Official sources include the Steam store, Steam achievement records, the game's site, patch notes, and posts from the official Divinum account. They are used for release, platform, feature, and published achievement data.
Developer replies come from accounts marked as the developer on Steam or a clearly identified developer post. They are useful for explaining mechanics and product intent that the store page does not cover.
Community reports are firsthand claims from a named public post or comment. They can answer experience questions, but one person's run does not become a universal result.
Reports differ when traceable sources point to materially different answers or when an old plan has not been confirmed in the release build.
Comments find the question; stronger evidence settles it
Steam and Reddit are excellent at revealing what players cannot find, what feels unclear, and which feature assumptions cause wasted troubleshooting. A player asking why Fury does not activate is a strong demand signal. The marked developer's reply is the evidence that settles how Fury works.
We do not convert upvotes into truth. Nor do we repeat an unsourced reply because several later websites copied it. Independence matters: ten pages repeating one comment are still one source.
Why some answers stay incomplete
Divinum launched on 28 August 2026. Early data changes quickly, and some public questions have only one or two responses. The current completion-time page uses a 4-7 hour range because a Steam player reported four hours and a reviewer reported a little over seven. Two runs are not enough for a reliable average.
Steam also leaves descriptions blank for several achievements. The checklist preserves those blanks instead of guessing a trigger from the achievement name. An incomplete answer with an honest boundary is more useful than a confident spoiler that turns out to be wrong.
No invisible hands-on claim
This site does not present its research as personal playtesting. When an answer comes from a player, reviewer, developer, store record, or achievement page, that source is named. If a future article includes direct testing, it will say what version and platform were tested.
That boundary affects the kinds of pages we publish. A mechanic explanation supported by the developer is reasonable. A room-by-room walkthrough built from scattered comments is not. We would rather leave a search unanswered than assemble a route no one has verified.
Updates and corrections
Every evidence page carries a checked date. A planned feature remains planned until a current patch note or release-build source confirms it. A changing Steam percentage keeps the sync date beside it.
Send corrections to contact@divinumguide.com. Include the page, the sentence that needs attention, and the strongest original source you have. Screenshots help, but a public patch note or developer reply is easier for every reader to verify.
Primary records used for the launch edition
- Steam store metadata for launch platforms, categories, languages, and cloud/controller listings.
- Steam global achievements for names, public descriptions, icons, and dated rarity percentages.
- The developer's Reddit demo thread for combat intent and difficulty context.
- The developer's Steam reply on the demo's focus and the full game's exploration.
- The MetroidvaniaGuru discussion for a named full-game completion report and genre assessment.