V Rising Database Changelog
Reviewed on August 17, 2026. This changelog tracks changes to the V Rising Forge database layer: entries, field definitions, risk labels, guide links, proof status, and quality reporting.
Data updates need a trail
A database feels more trustworthy when readers can see when the data layer changed and what kind of change was made.
Not every edit is a data update
Style changes, wording cleanup, and navigation tweaks can matter, but this page focuses on changes that affect how database rows should be interpreted.
Proof remains separate
A changelog entry does not mean a boss route, resource loop, or mod setup was live-tested. Proof still belongs on the linked guide and Proof page.
What Changed in the Data Layer
These entries are written for readers and reviewers, not just for development history. Each item explains the player-facing value of the database change.
| Date | Change | Reader value | Proof boundary |
|---|---|---|---|
| August 17, 2026 | Expanded the public database from 116 to 125 entries with eight Castle Chain rows. | Readers can now filter unload-loop, storage-to-refining, base-fit, room-grouping, servant-timing, production-adjacency, rebuild-timing, and proof-recheck castle decisions as reusable home-loop rows. | Castle-chain rows are routing data and do not claim live screenshot proof, exact layout proof, or current-patch verification. |
| August 17, 2026 | Expanded the public database from 108 to 116 entries with eight Boss Chain rows. | Readers can now filter Clive, Grayson, Keely, Rufus, pull-prep, unlock-value comparison, proof-priority, and patch-sensitive boss recheck decisions as reusable boss rows. | Boss-chain rows are routing data and do not claim live screenshot proof, exact boss route proof, or current-patch verification. |
| August 17, 2026 | Expanded the public database from 100 to 108 entries with eight Resource Chain rows. | Readers can now filter Iron, Cotton, Blood Essence, Whetstone, Sulphur, Mucus, Copper, and Greater Blood Essence decisions as reusable material-route rows. | Resource-chain rows are routing data and do not claim live screenshot proof, exact node locations, drop rates, or current-patch verification. |
| August 17, 2026 | Expanded the public database from 92 to 100 entries with eight Route Chain rows. | Readers can now filter safe entry lanes, first bankable hauls, boss-plus-resource overlap, haul-home travel rules, short-session routes, failed-run recovery, proof-priority routes, and patch-sensitive route checks as reusable decision rows. | Route-chain rows are routing data and do not claim live screenshot proof, exact route proof, or current-patch verification. |
| August 17, 2026 | Expanded the public database from 84 to 92 entries with eight Progression Chain rows. | Readers can now filter early boss sequence, station unlock sequence, gear catch-up, travel friction, resource bottleneck, castle flow gate, servant timing, and patch recheck decisions as reusable progression rows. | Progression-chain rows are routing data and do not claim live screenshot proof, exact boss-order verification, or current-patch verification. |
| August 17, 2026 | Expanded the public database from 76 to 84 entries with eight Gear Chain rows. | Readers can now filter early weapon confidence, first Iron upgrades, armor comfort, Cloth armor payoff, Whetstone weapon steps, Copper tools, servant readiness, and server-rule gear checks as reusable decision rows. | Gear-chain rows are routing data and do not claim exact stat values, live screenshot proof, or current-patch item verification. |
| August 17, 2026 | Expanded the public database from 68 to 76 entries with eight Workstation Chain rows. | Readers can now filter Tannery, Furnace, Grinder, Sawmill, Blood Press, Alchemy, Tailoring, and Servant-room chains as reusable database entries instead of only reading broad station notes. | Workstation-chain rows are routing data and do not claim exact recipe quantities or live patch-verified ratios. |
| August 17, 2026 | Expanded the public database from 60 to 68 entries with eight Recipe Chain rows. | Readers can now filter Leather, Whetstone, Copper, Iron, Cloth, Sulphur, Greater Blood Essence, and Servant chains as reusable database entries instead of only reading a standalone planner. | Recipe-chain rows are routing data and do not claim exact recipe quantities or live patch-verified ratios. |
| August 14, 2026 | Added the Database Quality Report. | Readers can see coverage by type, stage, risk, linked guide depth, and verification status. | The report measures structure and coverage; it does not verify live routes. |
| August 14, 2026 | Added the Database Field Guide. | Readers can understand type, stage, region, route risk, goal, guide link, and verification labels before trusting a row. | Field definitions clarify labels; they do not create screenshot proof. |
| August 14, 2026 | Added the Decision Matrix. | Readers can choose the right first page when the blocker is boss, resource, castle, travel, mod, patch, or proof related. | The matrix routes clicks; it does not confirm current gameplay state. |
| August 14, 2026 | Expanded the public database from 55 to 60 entries. | Combat prep, crafting, progression, travel, and mods received extra decision rows so the board works more like a repeat-use planning layer than a thin article index. | Rows remain editorial routing data unless live proof is connected. |
| August 13, 2026 | Expanded the public database into a 55-entry routing board. | Bosses, resource routes, castle decisions, progression checks, travel, combat prep, crafting, and mods are represented as reusable data entries. | Rows remain editorial routing data unless live proof is connected. |
| August 13, 2026 | Added saved views, shortlist planning, route ladder, risk warnings, recent opens, and proof status summaries to the database page. | Readers can reuse the database across multiple sessions instead of only searching once. | Local planning features do not inspect a save or verify a route. |
When a Database Change Deserves a Changelog Entry
A public changelog should not be padded with trivial edits. It should record changes that affect how players read, trust, filter, or act on the data.
New data rows
Add a changelog item when new bosses, resources, routes, castle decisions, travel checks, progression rows, combat prep rows, or mod rows are added.
Field changes
Log changes when a field definition, risk label, stage label, region scope, verification phrase, or guide-link rule changes.
Proof status changes
Log proof changes when a pending row becomes connected to real screenshots or when a row needs to be downgraded after a patch concern.
Quality reporting changes
Log changes when the database gains a new quality report, coverage view, missing-data tracker, or public explanation layer.
What Should Not Be Treated as a Database Update
Minor wording cleanup, decorative layout changes, button text changes, or navigation reshuffling should not inflate this changelog unless they materially change how a reader interprets the data.
Rumors also should not become changelog items unless they are handled as caution, source review, or a reason to recheck a specific field. The safer path is to link readers to Updates, Official Resources, or the Patch Recheck Planner before changing database confidence.
The Changelog Records Data Changes, Not Gameplay Proof
This page is a maintenance record. It does not prove a boss location, resource route, castle layout, mod setup, or patch claim by itself. If the question is whether a specific claim has been tested, check the linked guide, Proof, Player Testing Queue, and Worklog.
Database Changelog FAQ
What counts as a database changelog item?
A database changelog item is a meaningful data-layer change, such as adding entries, changing field definitions, updating risk labels, linking new guides, changing proof state, or adding a public quality report.
Does the changelog prove every entry is current?
No. It records what changed in the site data layer. It does not replace live gameplay testing, patch verification, screenshots, or official sources.
Why not put this only in the general worklog?
The general worklog covers the whole site. This changelog focuses only on the database layer so readers can track data-specific changes without reading every site update.