Divinum

Divinum Getting Started Guide

Start Divinum with a practical route for controls, demo carryover checks, combat basics, runes, bosses and map notes.

Use this starting route to make early Divinum decisions without relying on incomplete item, boss or map lists. The goal is to confirm what your version shows, then move into focused guide pages.

Quick Answer

  • Confirm your platform, controller and display setup before judging combat feel.
  • Treat the demo as useful practice, but verify full-game progress and save behavior in the current build.
  • Learn dodges, blocks, parries, launcher timing and aerial recovery before chasing damage.
  • Record rune effects and locations exactly as they appear.
  • When blocked, decide whether the problem is route knowledge, boss execution, input comfort or missing exploration.

First Route

  1. Open the Steam page and confirm the current build, platform and price in your region.
  2. Check resolution, aspect ratio, controller input and Steam Deck behavior before a long session.
  3. Play until the first route branch or repeated death, then write down the exact blocker.
  4. Review combat basics before changing rune choices.
  5. Track any rune, boss, secret or map gate with enough detail to verify later.

What To Check First

Player questionBest next page
Can my setup run it comfortably?Technical FAQ
What combat terms matter?Combat guide
Which rune should I use?Runes and builds
What blocked my route?Map and exploration guide
Is this a known issue?Updates and bugs

Early Mistakes To Avoid

Do not assume every route blocker is a bug. In a metroidvania structure, a closed path may mean missing movement, a combat trial, an unexplored branch or a real issue. Before reporting a bug, record the area, progress state, controller, platform and whether restarting the room changes the result.

Do not copy unverified rune or boss lists into your notes. Exact names and locations should come from the current game build, an official source or a repeatable player report with enough context.

Starting FAQ

Should I play the demo first?

The demo is useful for learning movement and combat feel, but full-game guidance should be checked against the released build.

What should I write down?

Record route blockers, rune names, effects, boss attacks, platform, input method and the source of the claim.

When should I check updates?

Check updates when a problem looks technical, repeatable or different from earlier notes, especially for display, controller, save or progression reports.

Sources