Divinum Runes And Builds
Divinum rune data foundation with publish gates for verified effects, trade-offs and locations.
Steam confirms collectible Runes that alter combat and can include trade-offs. Row-level rune records are held until each effect and location is confirmed, because a rune guide becomes misleading quickly if it guesses names, penalties, or boss sources.
Tracked Fields
- Name
- Effect
- Trade-off
- Location
- Source boss or trial
- Build tags
- Verification status
How Records Will Be Added
Each rune entry needs at least one direct gameplay check. A complete record should include the exact in-game name, the positive effect, the cost or drawback, where the rune was found, and the build type it supports. If a rune appears in the demo but changes in the final release version, the release version should replace the demo value.
Build recommendations need the same standard. A rune can be marked for damage, control, defense, mobility, or exploration only after the guide has seen how it changes a real encounter. Early labels should stay descriptive, not ranked, until enough late-game routes are verified.
Publish Rule
Only records with confirmed names and effects should appear in the public catalog. Unconfirmed discoveries belong in the private research log until a second pass checks the trade-off and the route where the rune is obtained.
First Update Targets
The first post-launch update should prioritize starter runes, any rune available in the demo, and one clear example build. After that, the page can expand into route-specific setups once boss and trial sources are proven.