V Rising Forge Worklog and Recent Site Changes

Recent site changes

These notes are intentionally plain. They are here to show what was actually changed, not to sound bigger than the work really was.

• August 18, 2026: tightened the Help hub with direct diagnostic-tool routing, and cleaned duplicate social metadata on a remaining high-traffic database page so the public routing layer looks more deliberate and less template-like.
• August 17, 2026: added a new Boss Unlock Payoff Checker and linked it from the homepage, Tools hub, feed, sitemap, and boss-routing entry points so “can I fight this boss?” now separates from “should I fight this boss now?” as its own reusable progression decision.
• August 17, 2026: added a new Base Relocation Planner and linked it from the homepage, Tools hub, feed, sitemap, and the castle path so plot-value pain, inside-flow pain, expansion pressure, and rebuild timing now route into one reusable castle decision tool instead of being flattened into “move or do not move” guesswork.
• August 17, 2026: added a new Servant Readiness Planner and linked it from the homepage, Tools hub, and Castle hub so servant timing, castle readiness, and Greater Blood Essence pressure now have a repeat-use decision tool instead of living only inside the broader servants article.
• August 17, 2026: added a new Progression Bottleneck Checker and linked it from the homepage, Tools hub, the Progression section, feed, and sitemap so the site now has a repeat-use tool for the broad “I am stuck but I cannot name the lane yet” progression problem before readers open the wrong boss, route, or base page.
• August 17, 2026: added a new Workstation Bottleneck Checker and linked it from the homepage, Tools hub, the Workstation Database, feed, and sitemap so the site now has a repeat-use tool for the very common production problem where materials exist but the real block is still unclear between unlock timing, inputs, base flow, and conversion.
• August 17, 2026: added a new Route Exit Checker and linked it from the homepage, Tools hub, search index, feed, and sitemap so the site now has a repeat-use tool for the very common problem of not knowing whether the route should end now or whether one more segment is still worth the return risk.
• August 17, 2026: added a new Server Rule Fit Checker and linked it from the homepage, Tools hub, Help, Common Problems, sitemap, feed, and public index data so server-rule, PvP-pressure, teleport-limit, loot-rate, and modded-world mismatches now route into one reusable decision tool instead of being scattered across broad support pages.
• August 17, 2026: refreshed the homepage maintenance summary and current-pass review blocks so the front page now reflects the live August 17 tool-and-routing pass instead of older August 8 wording, keeping the public maintenance trail closer to the actual worklog.
• August 17, 2026: expanded the public database from 116 to 125 entries by adding eight Castle Chain rows for unload-loop, storage-to-refining, base-fit, room-grouping, servant-timing, production-adjacency, rebuild-timing, and proof-recheck decisions, then surfaced those rows on the Castle Database page so home-loop friction now routes into visible castle data instead of only broad base advice.
• August 17, 2026: expanded the public database from 108 to 116 entries by adding eight Boss Chain rows for Clive, Grayson, Keely, Rufus, pull-prep, unlock-value comparison, proof-priority, and patch-sensitive boss recheck decisions, then surfaced those rows on the Boss Database page so boss searches now route into unlock value, prep, proof, and recheck logic instead of only location answers.
• August 17, 2026: expanded the public database from 100 to 108 entries by adding eight Resource Chain rows for Iron, Cotton, Blood Essence, Whetstone, Sulphur, Mucus, Copper, and Greater Blood Essence decisions, then surfaced those rows on the Resource Database page so material pressure now connects to route size, payoff, and proof boundaries instead of only “where to farm” answers.
• August 17, 2026: expanded the public database from 92 to 100 entries by adding eight Route Chain rows for 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, then surfaced those rows on the Route Database page so route shape now has visible data depth instead of only broad travel notes.
• August 17, 2026: expanded the public database from 84 to 92 entries by adding eight Progression Chain rows for early boss sequencing, station unlock order, gear catch-up, travel friction, resource bottlenecks, castle flow gates, servant timing, and patch recheck decisions, then surfaced those rows on the Progression Database page so sequencing pressure now has visible data depth instead of broad “what next?” advice alone.
• August 17, 2026: expanded the public database from 76 to 84 entries by adding eight Gear Chain rows for early weapon confidence, first Iron upgrades, armor comfort, Cloth armor payoff, Whetstone weapon steps, Copper tools, servant readiness, and server-rule gear checks, then surfaced those rows on the Gear Database page so upgrade pressure now routes into visible data instead of vague “get better gear” advice.
• August 17, 2026: expanded the public database from 68 to 76 entries by adding eight Workstation Chain rows for Tannery, Furnace, Grinder, Sawmill, Blood Press, Alchemy, Tailoring, and Servant-room decisions, then surfaced those rows on the Workstation Database page so station pressure now has visible data depth instead of only broad lane copy.
• August 17, 2026: expanded the public database from 60 to 68 entries by adding eight Recipe Chain rows for Leather, Whetstone, Copper, Iron, Cloth, Sulphur, Greater Blood Essence, and Servants, then surfaced those rows on the Recipes Database page so the new planner is backed by visible data instead of only a standalone tool.
• August 17, 2026: added a new Recipe Chain Planner and linked it from the homepage, Tools hub, Pages index, Recipes Database, sitemap, feed, and worklog so recipe-chain pressure now has a reusable decision page for unlocks, workstation checks, gear handoffs, and stop rules.
• August 17, 2026: added a new Recipes Database lane and linked it from the homepage, Database hub, Pages index, sitemap, feed, and worklog so crafting-chain pressure now has its own reusable entry point instead of being buried inside resource articles.
• August 17, 2026: added a new Progression Database lane and linked it from the homepage, Database hub, Pages index, sitemap, and worklog so unlock sequencing now has its own reusable entry point.
• August 16, 2026: added two new database entity lanes for Workstations and Gear, then connected them into the homepage, Database hub, Pages index, sitemap, and maintenance trail so the site moves closer to a reusable Heartopia-style reference structure instead of only article categories.
• August 16, 2026: completed an additional weekly original refresh by expanding Best V Rising Mods with client-versus-server scope checks and a five-minute rollback rule, so the mods page behaves more like a maintained setup guide than a static recommendation list.
• August 16, 2026: completed the third weekly original refresh slot by expanding Efficient Castle Layout with a 10-tile irritation test and a one-move-before-rebuild rule, so the page now helps solo players fix the repeated walking tax before copying a larger layout.
• August 16, 2026: completed the second weekly original refresh slot by expanding Where to Get Iron with a first-ore-segment triage table and a leave-now haul rule, so the page now helps players decide when a mine run has already paid off instead of only naming the Haunted Iron Mine.
• August 16, 2026: completed the first weekly original refresh slot by expanding the Clive the Firestarter guide with a 90-second quarry pre-pull check and a post-kill Sulphur stop rule, giving the page more original route judgment without changing the live screenshot count.
• August 16, 2026: added category-specific weekly original slots to Bosses, Resources, Progression, Castle, and Mods, so each section now names the next worthwhile original update direction and the reason a thin filler page should be held back.
• August 16, 2026: turned the weekly 2-3 original article rule into a visible Editorial Desk schedule for the week of August 17, 2026, then added a publishing preflight table on Updates so new weekly slots must pass player-problem, original-layer, and maintenance-trail checks before they go live.
• August 16, 2026: added a public weekly publishing cadence: 2-3 original guide articles or substantial refreshes per week when the topics add real player value, with filler keyword pages explicitly pushed behind proof work, database depth, screenshots, or stronger rewrites.
• August 16, 2026: revised the Database, Tools, and Visual Coverage copy so those core entry pages read less like generic modules and more like practical guidance for a player choosing the next route, tool, or proof check.
• September 20, 2026: refreshed Where to Get Iron with a three-run progression ladder, failed-run diagnosis table, and save-specific repeatability notes, then refreshed Efficient Castle Layout with a two-minute base audit, production handoff test, and storage groups that survive expansion. Both updates add decision value without pretending live screenshot proof is complete.
• August 16, 2026: tightened the official-visual wording across the guide templates, then repaired the remaining “illustrative guide visual” labels on the castle, boss-order, and Tanner flow diagrams so the site keeps the same boundary language everywhere instead of mixing in older generic phrasing.
• August 15, 2026: added explicit illustrative-visual boundary labels to the six first-batch guide diagrams, so Clive, Iron, Castle Layout, Mods, Boss Order, and Tanner can use topic-matched visuals without presenting them as V Rising Forge gameplay proof or changing the 0 of 54 live screenshot count.
• August 15, 2026: added a new public First Screenshot Batch operations page so the first six live-proof uploads now have one visible deck for exact filenames, grouped capture sessions, and post-upload checks instead of being scattered across support pages.
• August 15, 2026: added five new database lane pages for Bosses, Resources, Routes, Castle, and Mods, then connected them into the homepage and main database page so the site now has narrower data entry points instead of relying on one mixed board alone.
• August 15, 2026: pushed the homepage and Database further toward a product-style launcher by adding a clearer database snapshot, a reusable starter-view shelf, and stronger route-first wording around what the data layer is for.
• August 15, 2026: regrouped the Tools Hub around Plan, Compare, Track, and Recover moments, then strengthened Updates and Contribute so patch checks, feedback, screenshot leads, and missing data all route into public maintenance pages more cleanly.
• August 15, 2026: rebuilt the Player Testing Queue into a more product-like maintenance dashboard with a live queue snapshot, a front-of-queue visual shelf, clearer next-file routing, and stronger links into screenshot planning, patch checks, and public proof flow.
• August 15, 2026: rebuilt the Visual Coverage page into a more dashboard-like public control room, adding a proof snapshot, a visual queue for the next three trust lifts, and clearer links into screenshot planning and live testing while keeping the real screenshot total honestly at 0 of 54.
• August 14, 2026: expanded the public database to 60 entries, thickened the weakest coverage buckets, and surfaced the thin-type signals directly in the database quality report so the next useful rows are easier to choose.
• August 14, 2026: added a live maintenance snapshot and first screenshot queue to the homepage, then updated the database and worklog date signals so the front page now shows the current review state without hiding the proof gap.
• August 13, 2026: reshaped the homepage and Tools Hub toward a more Heartopia-style database product entry: database-first calls to action, clearer search prompts, reusable tool routing by player moment, and a roadmap that prioritizes deeper data and real screenshots over adding more loose tool pages.
• August 13, 2026: added a Screenshot Capture Planner that maps the next proof slot to a real filename, folder, and guide claim so the public visual workflow stays aligned with the proof board and worklog instead of drifting into placeholder territory.
• August 13, 2026: added a Patch Recheck Planner that turns a balance patch, map concern, resource change, castle issue, mod update, or server-rule shift into a first recheck page, backup tool, urgency rule, and public boundary against unsupported current-version claims.
• August 13, 2026: added a Payoff Converter that turns a material haul, boss unlock, castle improvement, travel fix, or setup change into one after-run action, one next guide, one backup path, and a clear boundary against fake inventory or recipe precision.
• August 13, 2026: added a Run Recovery Planner that helps players decide whether to retry, downshift, bank progress, or switch to a safer guide after a failed run, with recovery notes tied to route type, failure reason, pace, and proof boundary.
• August 13, 2026: added a Route Chain Planner that starts from one selected route and recommends a next guide plus backup guide by follow-up problem, pace, route type, stage fit, risk, proof boundary, and handoff into prep or tracking.
• August 13, 2026: added a Run Prep Checklist that turns one selected database route into a practical pre-run plan covering guide review, route size, inventory caution, risk control, server context, return rules, after-run actions, and proof boundaries.
• August 13, 2026: added a Route Risk Comparator that compares two guide-linked routes by stage, region, risk, payoff, verification boundary, and linked guides so players can choose between two plausible runs without opening a pile of loosely related articles.
• August 13, 2026: added a Crafting Goal Planner that turns Leather, Iron, Cloth, Sulphur, Castle Heart, servant, or mod setup goals into one unlock check, one material route, one castle conversion check, and a stop rule while explicitly avoiding fake exact recipe quantities until verified recipe rows exist.
• August 10, 2026: added a Session Planner that turns stage, available time, risk preference, and the current blocker into one main objective, one optional secondary target, and a leave-now rule, keeping the tool layer focused on real play-session decisions instead of generic article browsing.
• August 10, 2026: added a browser-saved Progress Tracker that reads the same structured site database as the Database and Map pages, lets players mark bosses, resources, castle checks, travel decisions, and setup tasks as complete, and keeps the privacy boundary clear by storing those checks locally only.
• August 10, 2026: added the first reusable data layer with a filterable Database, a searchable map marker board with browser-saved checked state, and richer Resource Route Finder inputs for stage, route size, and goal. These additions move the site toward a small V Rising reference product instead of only a collection of articles.
• August 10, 2026: added a reusable Tools Hub with Boss Order Planner, Resource Route Finder, and Castle Layout Checklist pages so the site now has a tool-and-decision layer in addition to guide articles, topic hubs, proof boundaries, and official reference images.
• August 9, 2026: added seven compressed official Stunlock press screenshots to the reference image library, connected them to homepage, Proof, category hubs, and selected guide pages, and kept the boundary visible that these are official visual references only, not V Rising Forge site-tested screenshot proof.
• August 9, 2026: deepened the Beginner Route, Resource Farming Route, and Castle Planning topic hubs with more player-decision cards, stage-fit checks, failure-diagnosis notes, rebuild caution, safe-first versus greedy-route guidance, and proof-status boundaries so the hubs behave more like useful route planners instead of thin link collections.
• August 9, 2026: added a public Start Here Route Planner and connected it to the homepage, sitemap, feed, and search index so visitors who arrive with a vague blocker can choose the right first guide by player problem, save stage, route risk, and proof status instead of guessing from the main menu.
• August 9, 2026: added three indexable topic hubs—Beginner Route, Resource Farming Route, and Castle Planning—then connected them to the homepage, Wiki, sitemap, feed, and search index so broad player searches can route into existing guide clusters without creating thin one-off pages.
• August 9, 2026: added a guide-maintenance trail to all 22 generated guide pages so every article now exposes page-specific review focus, proof boundary, version caution, and next-review trigger language instead of relying only on a generic updated date.
• August 9, 2026: added intrinsic width and height attributes to official WebP reference images and video-card poster images, then added a regression check so future official media updates do not reintroduce layout-shift-prone image tags.
• August 9, 2026: added failure-recovery and stage-fit tables to the six first-batch priority guides, giving each page concrete "if this goes wrong / likely problem / recover this way" advice so the guides read more like practical player help before real screenshots are connected.
• August 9, 2026: added a real-play test plan block to the six first-batch priority guides so each page now says what the next gameplay check should record, what a valid screenshot must prove, and when a screenshot should not be published as proof.
• August 9, 2026: expanded Disclosure with an ad-layout preflight table covering top-of-page, mid-guide, mobile, and official-media/proof areas so future ad placement does not bury the first useful answer or imitate guide actions.
• August 9, 2026: expanded the site-wide official media layer again by adding mixed image-and-video sections to the five main category hubs and official route/wiki image cards to Map and Wiki, bringing the public HTML to 50 official image cards and 34 video cards while keeping iframe count at 0 and live screenshot proof at 0 of 54.
• August 9, 2026: replaced official V Rising iframe embeds with poster-based video cards on the homepage, Proof, Updates, Worklog, and generated guide pages, so blocked video players no longer leave large blank areas while every card stays labeled as official reference context rather than V Rising Forge site-tested proof.
• August 9, 2026: expanded guide-page official reference images beyond the first six priority pages by adding category-aware default official image blocks, so more pages show real game context without changing the 0 of 54 live screenshot total.
• August 9, 2026: tightened the public layout CSS so desktop tables wrap inside their cards, article and sidebar columns can shrink on small screens, and the homepage hero now uses a single-column content flow instead of leaving a large empty block beside longer right-column content.
• August 8, 2026: expanded the homepage official-reference block to four cards so visitors now see route, castle, forge, and night-movement context on the front page while the live screenshot total stays at 0 of 54.
• August 8, 2026: connected one official reference image to each of the six first-batch priority guides, with a visible boundary that the image is real V Rising visual context, not V Rising Forge site-tested proof and not a replacement for the planned first live screenshot.
• August 8, 2026: added four more official V Rising / Stunlock reference screenshots to the Proof gallery—Oakveil woods, a castle room, a forge room, and a night bridge scene—while keeping them separate from site-tested gameplay proof and leaving the live screenshot total at 0 of 54.
• August 8, 2026: added a public reader-screenshot review flow to Contact so a submitted image is treated as a lead first, then checked for claim match, version and server context, privacy safety, public page wiring, and a future re-check trigger before it can move a proof slot from pending to connected.
• August 8, 2026: added a visible screenshot evidence note template to the six first-batch priority guides so every future live image must record the tested game version, world or server rules, filename, exact claim, limits, and re-check trigger before it can be treated as useful evidence.
• August 8, 2026: added an official visual reference gallery to the Proof page using compressed images from official V Rising / Stunlock public pages, while keeping the connected site-tested proof count at 0 of 54 so sourced reference images are not misrepresented as in-house gameplay captures.
• August 8, 2026: extended the player testing queue with a version-review table covering all 22 guides, so each pending patch check now has a named trigger instead of a generic “check later” label.
• August 8, 2026: exposed the first-batch capture handoff directly on the six priority guides so each page now names the first file, repository folder, public asset path, reader claim, and the site-wide changes expected after a real screenshot is connected.
• August 8, 2026: fixed a homepage hero-grid overflow where the section cards could widen the right panel past the visible shell; the two-column layout now allows both columns and their cards to shrink cleanly instead of hiding part of Resources or Mods.
• August 8, 2026: added a sixth-stage player testing queue so the next live route check, the next proof filename, and the next public maintenance trail all stay visible before a screenshot is counted as live.
• August 8, 2026: added a fifth-stage first live screenshot gate so the first real gameplay or setup WebP must appear on the public guide, match the planned proof slot, update Proof and search state, and be named in the Worklog before it counts as live proof.
• August 8, 2026: added a fourth-stage mobile and user-experience pass by tightening small-screen navigation, touch targets, table scrolling, article spacing, focus states, and a new mobile UX regression check for every public HTML page.
• August 8, 2026: added a third-stage advertising and privacy readiness pass by updating Privacy and Disclosure with a Google services notice, consent-readiness language, an AdSense launch gate, no-ad utility-page boundaries, and stronger checks against placeholder ads.txt or premature ad code.
• August 8, 2026: added a second-stage player decision pass to the six review-priority guides, giving Clive, Iron, Efficient Castle Layout, Mods, Boss Order, and Tanner a page-specific 30-second check before readers commit to a fight, farm route, rebuild, mod install, boss target, or unlock troubleshoot.
• August 8, 2026: completed the first-stage visual evidence preparation pass for the six review-priority guides by adding or confirming original explanatory diagrams on Clive, Iron, Efficient Castle Layout, Mods, Boss Order, and Tanner while keeping all live screenshot counts at 0 until real gameplay WebP files are added.
• August 8, 2026: clarified that the existing route diagrams, castle sketches, and mod-flow visuals are allowed as explanatory visuals, but they are still not counted as live screenshot proof on the Proof board.
• August 8, 2026: added a search-intent review table to the Editorial Desk so popular queries are explained as routing decisions first, with new pages reserved for distinct player needs instead of keyword filler.
• August 8, 2026: added a visible popular-search routing table to the Wiki hub so broad terms, map searches, Clive, castle layouts, mods, V Rising 1.2, and Mucus searches point readers to the best first page without relying only on the search box.
• August 8, 2026: added a search-intent regression check for high-value queries such as vrising, v-rising, v rising map, clive location, castle layout, mods, V Rising 1.2, and Mucus so future search changes cannot quietly send readers to the wrong first page.
• August 8, 2026: tuned search-result ordering so broad game-name searches now surface the Wiki hub first, version searches surface Updates first, map searches surface the Map hub first, and focused resource searches still lead to the matching guide when one exists.
• August 8, 2026: corrected the search intent hint for Mucus so visitors are sent directly to the existing compact Gloomrot loop guide instead of being told the site still lacks a focused Mucus page.
• August 8, 2026: improved the search page so no-result and overly broad searches now point readers toward the right hub, patch-status page, proof board, worklog, or correction route instead of pretending every keyword already has a finished guide.
• August 8, 2026: added a homepage next-work roadmap so the site now names the first live screenshot batch, deeper content on already-strong pages, and patch-sensitive re-checks as the next visible maintenance priorities.
• August 8, 2026: added a screenshot acceptance check to Visual Coverage so future captures must prove one exact claim, orient the reader, avoid private data, and update the public guide, caption, proof board, and worklog together before being counted as live proof.
• August 8, 2026: added a public Editorial Desk queue so readers can see why the next maintenance work focuses on the first live screenshot batch, high-intent guide gaps, patch-sensitive checks, and correction-driven fixes instead of pretending every page is equally complete.
• August 8, 2026: added an About-page content roadmap that names the current public gaps around live screenshots, boss depth, resource coverage, and patch-sensitive mod notes so missing work is explained instead of hidden or padded into thin pages.
• August 8, 2026: added a homepage maintenance note that separates what the August 8 site-level pass actually changed from what it did not claim, especially around older guide re-testing and planned screenshots that are still not live proof.
• August 8, 2026: aligned homepage, category hubs, Search, About, Contact, Editorial Desk, Map, Wiki, Updates, sitemap, feed, and content search data to the same public August 8 maintenance signal while preserving the separate August 7 official-news check on Updates.
• August 8, 2026: expanded the player-note blocks on the six review-priority guides so Clive, Iron, Efficient Castle Layout, Mods, Boss Order, and Tanner now include more specific route-reset, exit, rollback, rebuild, and next-click judgment before the first real screenshots are connected.
• August 8, 2026: synced the public visual-coverage math across Visual Coverage, Worklog, homepage trust copy, sitemap, feed, and maintenance checks so the site now says 18 mapped guide pages, 54 planned proof slots, and 0 live screenshots consistently.
• August 8, 2026: added a public maintenance trail to the Worklog that keeps the screenshot queue, review queue, and visible site changes tied together instead of leaving the proof process isolated on a single page.
• August 7, 2026: added a Copper Ore guide to the Resources section with source-specific wording for node access, Bandit Copper Mine route sizing, smelting payoff, and when the real blocker has moved from ore to tools, Furnace, Whetstone, or another recipe step.
• August 7, 2026: added a Rufus the Foreman boss guide so the early Bosses chain now covers the Bandit Logging Camp route, woodworking and ranged-utility timing, and when to use the unlock instead of turning the camp into a full clear.
• August 7, 2026: added a Keely the Frost Archer boss guide so the Tanner/Tannery unlock path now has a direct boss-route page for Bandit Trapper Camp timing, safe pull setup, and turning the unlock into Leather production.
• August 7, 2026: added a Grayson the Armourer boss guide so the Whetstone page now has a direct boss-route follow-up for the Bandit Armory trip, unlock timing, safe pull setup, and when random Whetstone loot should give way to the recipe route.
• August 7, 2026: added a Whetstone guide to the Resources section, then gave it source-specific follow-up, save-check, and responsibility wording so the growing resource library does not lean on repeated category boilerplate.
• August 7, 2026: added a Servants guide to the Castle section so the site now covers first Servant Coffin timing, capture-readiness checks, Greater Blood Essence spending tradeoffs, and when the servant system should wait until the base is stronger.
• August 7, 2026: added a Greater Blood Essence guide as the natural follow-up to the basic Blood Essence page, with spend-or-save guidance for rare inputs, Tristan-related progression caution, and a clearer bridge from early Castle Heart fuel to midgame essence needs.
• August 7, 2026: added a new Blood Essence farming guide so the Resources section gains another core player-problem page focused on Castle Heart fuel, passive versus dedicated farming, Blood Press caution, and session-safe fuel buffers.
• August 7, 2026: added a public Editorial Desk page and connected article bylines, responsibility blocks, structured author data, About, sitemap, feed, and search data to it so guide authorship and review ownership are clearer before future AdSense review.
• August 7, 2026: added a tighter sidebar screenshot handoff to the priority guides so the article sidebar now exposes the first expected file, the mapped repo folder, the reader confirmation target, and the next go-live checks without making visitors hunt through the full proof board first.
• August 7, 2026: tightened the priority-guide article pages again so each first-screenshot check now shows the exact first file, repo folder, public asset path, and the specific reader confirmation the page should earn once that image goes live.
• August 7, 2026: tightened the proof-board auto blocks so the first upload order, capture kits, and go-live checks now say not only which file belongs next, but what the reader should be able to confirm and which public signals should flip with the first live image.
• August 7, 2026: expanded the Visual Coverage page with a clearer screenshot go-live standard so the proof board now says not only what is planned, but what must change publicly before a slot is counted as live.
• August 7, 2026: refreshed the homepage maintenance layer again so the front page now surfaces the new proof-confirmation brief work and a visible next-up maintenance queue instead of only listing recent edits.
• August 7, 2026: clarified the Visual Coverage totals so readers can distinguish the site-wide 8-guide/24-slot visual roadmap from the first 6-guide/18-slot upload queue.
• August 7, 2026: tightened the Contact page with a 30-second pre-report check so readers can separate patch drift, save-rule mismatch, scope mismatch, and proof-status questions before filing one public correction.
• August 7, 2026: refreshed the homepage maintenance trail so the front page now shows the latest proof-board and correction-route work more directly instead of leaving the newest trust updates buried in support pages alone.
• August 7, 2026: added a "when not to start here" homepage table under the four-page shortlist so readers can switch to the real blocker page instead of forcing every session through the same broad recommendations.
• August 7, 2026: added a second homepage judgment table under the editor-pick routes so Clive, Sulphur, and Castle Layouts now explain who each page is best for, when not to start there, and which page should replace it.
• August 7, 2026: added the same homepage judgment layer under Iron, Cotton, and Mucus so the resource picks now explain who they help most, when the real blocker is elsewhere, and which page should replace the farming route first.
• August 7, 2026: added a homepage first-click mistake table under the four main entry lanes so Progression, Resources, Castle, and Mods now explain the most common misclick and the better replacement page.
• August 7, 2026: added a homepage search-intent table under the hero search box so readers are pushed toward narrow blocker queries like boss names, material names, base problems, or patch-sensitive setup terms instead of very broad searches.
• August 7, 2026: added a light homepage section-choice table under the Bosses, Resources, Castle, and Mods cards so the hero panel now explains when each section is a good first click and when it is the wrong starting point.
• August 7, 2026: replaced the homepage hero stats with a clearer current-site-state block so the front page now explains the live guide count, main sections, public proof roadmap, and current zero-live-screenshot status in one honest summary.
• August 7, 2026: added a homepage trust-boundary section so the site now says more plainly what already feels strongest today and which parts still need live screenshot proof or future patch-sensitive re-checks.
• August 7, 2026: connected the homepage trust blocks more directly into About so readers can now move from the short front-page summaries into a longer explanation of why review scope, proof gaps, and correction routes stay visible.
• August 7, 2026: added a clearer trust-page handoff layer inside Updates, Proof, and Contact so the support pages now route readers more directly toward patch status, proof state, editorial policy, or the public correction path instead of making them infer the next stop.
• August 7, 2026: added the same trust-page handoff layer to Worklog so the maintenance log now routes readers more clearly toward Updates, Visual Coverage, About, or Contact depending on the doubt that still remains after they confirm the public change trail.
• August 7, 2026: connected Search into the same trust-page system so search readers can now jump more directly toward Updates, Visual Coverage, About, or Contact once the keyword result itself is no longer the real question.
• August 7, 2026: connected the Bosses, Resources, Castle, Progression, and Mods hubs into the same trust-page system so each high-entry section now routes readers more directly toward Updates, Visual Coverage, About, or Contact when the hub itself is no longer the real answer.
• August 7, 2026: connected the Map and Wiki hubs into the same trust-page system so broad route and directory-style entry pages now hand readers more directly toward Updates, Visual Coverage, About, or Contact when the hub itself no longer answers the remaining doubt.
• August 7, 2026: added a shared trust-page handoff card to generated guide pages so individual articles now point readers more directly toward Updates, Visual Coverage, About, or Contact when the guide is close but one exact doubt still remains.
• August 7, 2026: tightened the proof briefs on priority guides so the next screenshot note now says not only what to capture, but what a reader should be able to confirm once that image is live.
• August 7, 2026: added guardrails so public HTML and published article sources cannot drift back to the old draft-like visual proof heading.
• August 7, 2026: renamed public visual-proof gap headings from draft-like wording to "Planned visual proof" so pages stay honest about missing screenshots without reading like unfinished notes.
• August 7, 2026: removed draft-only pre-publish link lists and internal source notes from published article sources, then added a source-hygiene check to keep future published drafts from carrying those internal markers.
• August 7, 2026: strengthened the public date-signal check so Article structured data must keep a real published date instead of only a latest modified date.
• August 7, 2026: added missing published-date fields to Clive, Iron, Boss Order, Beginner, and Waygate article sources so structured data can separate original publication dates from the latest review dates.
• August 7, 2026: synced the visible review dates for the Clive and Iron first-batch guides after their field-check updates so the pages, sitemap, and search data all reflect the same maintenance pass.
• August 7, 2026: added a version-status field check to the Updates hub so V Rising 1.2 searches stay tied to official naming, source impact, guide re-check need, and actual added reader value.
• August 7, 2026: added a wiki-to-guide handoff check to the Wiki hub so broad wiki searches must become one boss, resource, progression, castle, map, or mods next click instead of another directory loop.
• August 7, 2026: added a one-route map check to the Map hub and updated the map draft source note so route planning no longer depends on a removed or incompatible Steam Community map reference.
• August 7, 2026: added a quarry payoff field check to the Sulphur guide so readers decide whether the first safe node lane already pays for a craft, utility step, or Clive follow-up before forcing a full clear.
• August 7, 2026: added a Cotton-to-Cloth conversion check to the Cloth guide so readers process the first useful haul into a named armor, tailoring, or production gain before starting another farm run.
• August 7, 2026: added a first-Cotton haul field check to the Cotton guide so readers decide whether the first Dunley farm lane already pays for a named Cloth, armor, or production step before widening the route.
• August 7, 2026: added a first-plot field check to the early base location guide so readers test repeated resource, boss, return-home, and compact-room loops before placing a castle heart.
• August 7, 2026: added a carry-check field check to the Waygate guide so readers test the expected inventory, server teleport rules, physical return path, and haul size before treating fast travel as a return plan.
• August 7, 2026: added a first-hour save check to the beginner guide so new players can confirm the base dump point, next unlock reason, named craft payoff, and cleaner next trip before wandering wider.
• August 7, 2026: added a copy-before-build field check to the castle layouts guide so base-design readers test the return, storage, crafting, and exit loop before treating a pretty layout as a real blueprint.
• August 7, 2026: added a paid-off loop field check to the Mucus farming guide so readers decide whether to bank a compact Gloomrot-side haul before stretching into a wider rumor route.
• August 7, 2026: added a first-mod setup field check to the mods guide so readers test one category, dependency chain, install scope, clean launch, and rollback path before expanding a mod stack.
• August 7, 2026: added an unlock-confirmation field check to the Tanner guide and replaced an internal editor placeholder with a public proof-queued note so the page no longer exposes draft-only wording.
• August 7, 2026: added a next-kill field check to the boss order guide so readers confirm the exact unlock, follow-up material run, and first post-kill base job before chasing another V Blood.
• August 7, 2026: added a daily-loop field check to the efficient castle layout guide so readers can test one real return-unload-craft-exit route before committing to a full rebuild.
• August 7, 2026: added a first-haul field check to the Iron guide so the resource page now judges a run by the named upgrade target, cheaper exit, and clearer second-trip plan instead of only by ore volume.
• August 7, 2026: added a first-run field check to the Clive guide so the boss-location page now tells readers to verify the entry lane, safe exit, and post-kill Sulphur job before treating the route as repeatable.
• August 7, 2026: added a before-you-count-a-screenshot-as-proof note to the Visual Coverage page so planned slots are not treated as live proof unless the WebP file exists, the guide references it, and the caption names what it proves.
• August 7, 2026: added a before-you-choose-a-guide check to the homepage so broad visitors are pushed to name the real blocker before choosing Progression, Resources, Map, Castle, Updates, or Mods.
• August 7, 2026: added a before-you-trust-a-version-rumor check to the Updates hub so version-intent searches now ask for the official source date, save or server impact, and the exact guide page that would need a real re-check.
• August 7, 2026: added a before-you-open-another-wiki-link check to the Wiki hub so broad wiki searches now ask readers to name the exact blocker before continuing through directory links.
• August 7, 2026: added a before-you-follow-a-marker check to the Map hub so map searches now ask for the trip goal, safe return path, and one nearby chained value before a close marker turns into a bad detour.
• August 7, 2026: added a before-you-add-a-mod check to the Mods hub so install searches now ask about patch timing, one-category testing, dependencies, and client-versus-server scope before readers stack too many changes at once.
• August 7, 2026: added a before-you-chase-the-boss check to the Bosses hub so boss-location searches now ask what the kill unlocks, what nearby resource value the route can carry home, and which page should come next.
• August 7, 2026: added a before-you-grind check to the Progression hub so stuck-save searches now push readers to name the next unlock, station, or craft before spending another run on random materials.
• August 7, 2026: added a before-you-rebuild check to the Castle hub so base-design searches now push readers to test one small storage, refining, or corridor fix before tearing down a castle that still mostly works.
• August 7, 2026: added a before-leaving-base resource-run check to the Resources hub so material searches now push readers to name the craft goal, paid-off segment, exit point, base-flow payoff, and patch-drift risk before farming blindly.
• August 7, 2026: added visual-proof instructions to Contact and the guide-correction issue form so reader screenshots are tied to one exact claim without exposing private account, server, or payment details.
• August 7, 2026: added a visual-filter honesty note to Search so proof filters explain the difference between live screenshots, planned visual review, and review-priority pages before a visitor mistakes pending evidence for finished proof.
• August 7, 2026: synced the screenshot file-naming rule into the Updates source-policy section so patch-sensitive evidence now follows the same short, numbered, proof-tied naming standard as the proof board, homepage, and About page.
• August 7, 2026: added the screenshot naming rule to the homepage and its source note so the site's most visible entry point now agrees with the proof board about short, numbered, evidence-tied filenames.
• August 7, 2026: added the screenshot file-naming rule to the About page so the public proof policy and the visual roadmap now say the same thing about numbered, literal filenames.
• August 7, 2026: added screenshot file-naming rules to the proof-board legend so future captures stay short, numbered, and tied to the thing the image actually proves.
• August 7, 2026: added a small legend to the proof board so the screenshot labels now explain what each field means before the six-page visual queue starts listing details.
• August 7, 2026: added a suggested screenshot file name to the source-and-verification panel on proof-ready guide pages so the next capture brief now includes the file shape as well as the shot title.
• August 7, 2026: added short shot titles to the first-batch guide verification panels so the priority pages now show a tighter capture brief directly inside the page check block.
• August 7, 2026: added a proof-reason line to the source-and-verification panel on priority guide pages so each page explains why its first visual proof matters before the image is even added.
• August 7, 2026: added a short "Proves:" line to each first-batch proof card so the visual roadmap now states exactly what each opening shot should demonstrate to a reader.
• August 7, 2026: expanded the proof-roadmap cards again with a concrete first-frame capture script so the six review-priority guides now spell out the exact opening shot each page should use when the real images are finally captured.
• August 7, 2026: expanded the evidence-roadmap cards on the visual coverage page with a short "why it matters" note for each review-priority guide so the proof board explains not just what is missing, but why each capture would change trust.
• August 7, 2026: added an evidence-roadmap section to the visual coverage page so the six review-priority guides now show the exact kind of proof each page still needs, not only the fact that screenshots are pending.
• August 6, 2026: added a page-responsibility sidebar block to generated guide pages and a public responsibility check so each guide shows who maintains it, what the review scope covers, where fan-site limits apply, and how to send exact corrections.
• August 6, 2026: added an Updates source-ranking table and public source-policy check so official Stunlock posts, support guides, editorial route review, community documentation, and reader corrections stay clearly separated.
• August 6, 2026: added a public editorial-method check and expanded the About page with a guide-claim review table so readers can see how a recommendation is judged before it is treated as a working answer.
• August 6, 2026: added a branded social share card and public social-image metadata check so every HTML page exposes consistent Open Graph and Twitter image previews without using placeholder gameplay screenshots.
• August 6, 2026: split Contact page feedback into direct guide-correction and policy-feedback form links, then added a public feedback-route integrity check so reader reports keep a clear path from guide pages, category hubs, and Contact into the right GitHub issue form.
• August 6, 2026: tightened guide-page "On this page" sidebars into shorter editor-curated navigation and added a public article-nav quality check so future pages do not expose oversized template-like heading lists.
• August 6, 2026: added a public breadcrumb visibility check so pages with BreadcrumbList JSON-LD also keep the same user-visible breadcrumb trail and section links on the page.
• August 6, 2026: added a public date-signal consistency check and aligned primary JSON-LD dateModified fields so visible review dates, sitemap lastmod values, and machine-readable page dates stay in sync.
• August 6, 2026: added a public trust-footer check so every HTML page keeps the site identity, independent fan-site disclosure, correction contact path, and About, Privacy, Terms, and Disclosure links visible.
• August 6, 2026: added a public crawl-and-feed surface check so robots.txt, sitemap.xml, the homepage RSS alternate link, and feed.xml stay parseable, deduplicated, and aligned with public canonical pages.
• August 6, 2026: added a public FAQ visibility check and aligned the Updates FAQ copy with its FAQPage JSON-LD so every structured FAQ question and answer is visible to readers, not only to search systems.
• August 6, 2026: added a public search-snippet uniqueness check so titles, meta descriptions, canonical URLs, Open Graph URLs, and social preview copy stay unique and aligned instead of drifting into duplicated template snippets.
• August 6, 2026: added a public external-link governance check so outbound links stay on approved source domains, use HTTPS, keep descriptive anchor text, avoid tracking or affiliate-style query parameters, and use safe rel values when opened in a new tab.
• August 6, 2026: added a public structured-data integrity check and tightened the homepage WebSite schema description so JSON-LD stays parseable, canonical-aligned, and useful for search systems.
• August 6, 2026: added a public reader-value path check so future guide pages need visible scope, decision help, save checks, verification status, patch checks, and correction paths instead of only keyword-focused copy.
• August 6, 2026: added a public template-footprint check so future indexable pages cannot rely on low-value AI clichés or heavily repeated non-maintenance copy without being caught before publishing.
• August 6, 2026: added a thin-content risk check so future indexable pages need enough visible substance, section structure, and internal routing before they can pass the public maintenance workflow.
• August 6, 2026: added a screenshot asset quality check so future live proof files must be referenced by a public proof checklist, use WebP, meet minimum size and dimensions, and pass validation before being counted as ready.
• August 6, 2026: replaced generic version-check placeholders in article sources with clearer reviewed-versus-pending language and added a public verification-claims check so pending pages cannot quietly overstate current-patch verification.
• August 6, 2026: tightened Privacy and Disclosure around AdSense readiness, current third-party service status, ad-free support pages, ads.txt timing, and future ad-placement boundaries before any live ad code is added.
• August 6, 2026: added an ad policy boundary check so future ad markup is kept off search, 404, policy, proof, contact, worklog, and other low-value utility pages unless their purpose changes.
• August 6, 2026: added a public accessibility basics check so generated pages are reviewed for image alt text, non-empty link and button names, usable form-field hints, and page language attributes before publishing.
• August 6, 2026: added a public placeholder-text check to catch leftover task markers, unresolved draft labels, editor-note phrasing, sample-copy phrasing, and unfinished release markers before they can remain visible on public HTML pages.
• August 6, 2026: added generated Open Graph and Twitter Card metadata across HTML pages so shared links expose cleaner titles, descriptions, URLs, and site identity instead of relying on default previews.
• August 6, 2026: added a generated RSS feed for recent guide and support-page updates, plus a homepage alternate-feed link so maintenance changes are easier to follow outside the page itself.
• August 6, 2026: added a content-index and sitemap integrity checker so search data, generated guide pages, sitemap URLs, lastmod dates, and noindex support pages stay aligned after future updates.
• August 6, 2026: added a page SEO structure checker for titles, descriptions, canonical URLs, robots directives, one-H1 structure, and JSON-LD on indexable pages.
• August 6, 2026: added an internal link and anchor checker to the maintenance workflow so broken page links, missing asset paths, and bad in-page anchors are caught before publishing.
• August 6, 2026: tightened guide search with a canonical URL, visible review date, and normalized matching for common V Rising spelling variants such as vrising, v-rising, waypoint, teleport, and base design.
• August 6, 2026: added structured WebPage data to Privacy, Terms, and Disclosure so policy pages expose clearer canonical identity, current review date, publisher, and game context.
• August 6, 2026: expanded the 404 page with noindex guidance and problem-based recovery links so visitors who hit a missing guide can return to Progression, Resources, Map, Castle, Mods, or Contact instead of dead-ending.
• August 6, 2026: added lastmod dates to the generated sitemap and refreshed the static-site README page list so crawl-support files match the current 14-guide site.
• August 6, 2026: expanded the Terms page with clearer guide-limitations, external-link, public-feedback, official-support, and advertising-separation language so the policy layer better matches a real maintained guide site.
• August 6, 2026: expanded the Search page with a problem-first lookup table and broad-search caution notes so visitors can move from map, boss, resource, castle, or mod keywords into the right practical page faster.
• August 6, 2026: aligned the homepage review-pass labels and first-click recommendation dates with the current public maintenance pass so the homepage no longer mixes August 3 or August 4 wording into current-trust sections.
• August 6, 2026: refreshed the Visual Coverage page so its public review date, default counters, and no-live-screenshots status match the current 14-guide site instead of showing stale source-level numbers.
• August 6, 2026: tightened the Map hub with a 30-second pre-run route check, common map-mistake corrections, and updated public worklog counts so the page better helps players decide before leaving base.
• August 6, 2026: added a new Waygate and Fast Travel guide that separates positioning from hauling, explains teleport-restriction caveats, and connects travel friction back into base location, resource routes, Updates, and Progression.
• August 6, 2026: added a new V Rising Beginner Guide for new and returning players, connected it into Progression, sitemap, search data, and the homepage first-click path, while keeping its screenshot status honest until real images are added.
• August 6, 2026: made Privacy, Terms, and Disclosure indexable trust pages, added policy-page checks, and added a shared source-and-verification status block to generated guide pages so review limits, visual proof status, and correction paths are clearer before ad review.
• August 6, 2026: tightened the Contact page with clearer correction handling, public-versus-private feedback boundaries, and a more explicit note that this fan site is not official V Rising or Stunlock support.
• August 6, 2026: tightened the homepage and About page trust layer so visitors can see the current maintenance date, the human-maintenance standard, and the reason thin AI-looking pages are delayed instead of padded out.
• August 6, 2026: tightened the Updates page around V Rising 1.2 search intent, kept the official source chain separate from editorial review, and added a clearer rule for when a dedicated version page would actually be worth publishing.
• August 6, 2026: tightened the Wiki hub around when a directory is not progress, when a specific guide should be the first click, and how broad wiki searches should turn into one usable reading path.
• August 6, 2026: tightened the Map hub around route discipline, when close markers should not become extra objectives, and when the real answer is a boss, resource, castle, or progression page instead of more pins.
• August 6, 2026: tightened the Castle Layouts guide around stage mismatch, when a small fix beats a full redesign, and the difference between a larger showcase shell and a castle that still works every session.
• August 6, 2026: tightened the Early Base Location guide around choosing the plot that shortens the next ten hours, the difference between a good-enough early home and a forever-home fantasy, and when the real problem is layout rather than map position.
• August 5, 2026: tightened the Mucus guide around the difference between a repeatable compact Gloomrot loop and a fake-perfect rumor route, with clearer stop-extending judgment and stronger guidance for when average runs are still good enough.
• August 5, 2026: tightened the Sulphur guide around the first paid-off quarry loop, the difference between a Clive trip and a pure resource run, and the point where leaving with a good-enough haul is smarter than forcing a full clear.
• August 5, 2026: tightened the Cloth guide around the difference between “I still need more Cotton” and “I already have enough, but my production loop is wasting it,” with clearer stop-farming judgment and stronger handoff into castle flow.
• August 5, 2026: tightened the Cotton guide around the first paid-off Dunley haul, the good-enough leave-now threshold, and the difference between a clean first lane and a greedy region-wide overstay.
• August 5, 2026: tightened the Mods guide around safer first-pass setup judgment, when modding is not actually the answer, and the difference between a small testable stack and a fake-safe pile of overlapping installs.
• August 5, 2026: tightened the Tanner guide around the current unlock answer, the Tanner-versus-Tannery naming confusion, and the difference between a missing unlock and a missing materials-or-placement step.
• August 5, 2026: tightened the Efficient Castle Layout guide around naming the single worst loop first, choosing the small fix before a full rebuild, and showing where “ugly but fast” is the better solo answer than a tidy slow shell.
• August 5, 2026: tightened the Boss Order guide around bottleneck-first decision-making, the real next-step payoff, and when a support run is the better answer than forcing another boss.
• August 5, 2026: tightened the Clive guide around the first paid-off quarry run, the cleaner pull pocket, the post-kill Sulphur stop point, and the difference between a good Clive trip and a greedy quarry overstay.
• August 5, 2026: tightened the Iron guide around the first paid-off haul, the leave-now threshold, solo versus group route judgment, and the difference between a good-enough mine run and a greedy overstay.
• August 5, 2026: tightened the Disclosure page so it states more plainly what monetization is live now, what is only future-ready, and what should visibly change the day ads, affiliates, or sponsorships become active.
• August 5, 2026: tightened the Updates page with a clearer “what this page can confirm” filter and rolled its editorial review date forward without pretending the official source anchor changed with it.
• August 5, 2026: tightened the Contact page with a clearer feedback filter and a “pick the smallest useful route” guide so corrections are easier to send as one exact reviewable issue instead of one vague bundle.
• August 5, 2026: tightened the About page with a clearer “when a page deserves to stay” standard so the site explains more directly why some ideas should be delayed instead of padded into thin keyword pages.
• August 4, 2026: added a homepage “what we do not fake” block so the site can explain its editorial guardrails in plain language instead of only describing the pages it already has.
• August 4, 2026: added lighter “common wrong start” warnings to the Bosses, Resources, Castle, Progression, and Mods category pages so readers can avoid opening the right-looking section for the wrong underlying problem.
• August 4, 2026: added a homepage “common wrong first clicks” block so visitors can avoid starting with one narrow material, boss, mod, or castle page when the real blocker belongs in a broader section first.
• August 4, 2026: added a Mods category onboarding block so new visitors can choose faster between a safer starting mod stack, update checks, gameplay progression, and the site's review standards instead of guessing from a narrow mod hub.
• August 4, 2026: added a Progression category onboarding block so new visitors can choose faster between Boss Order, Tanner, Resources, and Castle instead of guessing the right first move from a broad progression hub.
• August 4, 2026: added a Castle category onboarding block so new visitors can choose faster between layout flow, base location, resource support, and broader progression instead of guessing from a mixed building hub.
• August 4, 2026: added a Resources category onboarding block so new visitors can choose faster between Iron, Cotton, Progression, and Castle instead of guessing the right starting page from a mixed resource hub.
• August 4, 2026: added a Bosses category onboarding block so new visitors can choose between a direct boss page, Boss Order, Resources, or Castle without guessing the right starting lane.
• August 3, 2026: added a homepage first-three-click onboarding block so new visitors, returning players, narrow-intent readers, and trust-first readers can choose a shorter starting path instead of guessing from a long mixed homepage.
• August 3, 2026: added a homepage correction-path block so visitors can move from “this guide looks wrong” to updates, the correction form, worklog, or contact without guessing the next page.
• August 3, 2026: clarified visible article-level correction wording so outdated-guide reports now read more like direct actions and less like vague support language.
• August 3, 2026: added section-level correction guidance to category hubs so readers can report one bad route, unlock step, layout note, or mod detail without guessing where feedback should go.
• August 3, 2026: expanded category review-pass blocks so section hubs now show not only which pages are worth opening first, but what each checked page was reviewed for in the current pass.
• August 3, 2026: changed visible article-level correction links from a generic Contact handoff to the direct guide-correction issue form so readers can report one bad claim with fewer clicks.
• August 3, 2026: added GitHub issue forms for guide corrections and support-page feedback so the site's public correction route now has a more structured intake path.
• August 3, 2026: added a homepage block for the guide pages re-checked in the current pass so visitors can see which high-intent articles were reviewed and what each page was checked for.
• August 3, 2026: added a homepage block for the support pages re-checked in the current pass so visitors can see which public trust pages were reviewed and what each page was checked for.
• August 3, 2026: strengthened the About page with a clearer normal review workflow, a better explanation of what makes a correction easy to confirm, and a stronger handoff into the Contact page.
• August 3, 2026: strengthened the Contact page with a faster correction format, one concrete example report, and a clearer public route for sending guide fixes.
• August 3, 2026: added a visible correction-report link to the always-shown article follow-up box so readers can flag changed routes or outdated setup details without relying on hidden maintenance panels.
• August 3, 2026: added a direct “Report a correction” shortcut to article maintenance panels so readers can send changed route, unlock, material, layout, or mod details without hunting for the Contact page.
• August 3, 2026: added explicit “Why checked now” labels to the public first-click blocks so visitors can see the editorial reason behind each recommended page instead of only seeing a list of links.
• August 3, 2026: rolled the live editorial review date forward across generated guides, category hubs, homepage cards, and structured data so the public maintenance signal matches the current site pass.
• August 3, 2026: refreshed static support pages and policy pages so About, Contact, Privacy, Terms, Disclosure, Map, Wiki, Proof, Updates, and Worklog all reflect the current maintenance date more clearly.
• July 31, 2026: separated editorial review dates from official source-anchor dates on support hubs, especially Updates, so maintenance signals stay current without pretending official patch facts changed more recently than they did.
• July 31, 2026: tightened Map and Wiki support pages with clearer review-status labels and stronger support-page routing, so broad-entry pages now feel more like maintained public resources and less like static directory shells.
• July 31, 2026: added section-level “This week in …” maintenance blocks to Bosses, Resources, Progression, Castle, and Mods so category hubs now show what was tightened recently instead of only listing guides.
• July 31, 2026: tightened the homepage by removing repeated start-here blocks, adding a plain “This week on the site” maintenance summary, and shifting the dynamic homepage cards toward strongest current first clicks instead of a generic latest-guides feel.
• July 31, 2026: renamed public screenshot and queue wording across Search, Visual Coverage, Updates, About, and Worklog so support pages read more like a maintained guide site and less like an internal task board.
• July 31, 2026: separated gameplay/source check dates from editorial review dates across guide pages, category cards, search data, and Article structured data so recent maintenance is visible without pretending every route was re-tested in-game.
• July 31, 2026: moved the main navigation from Screenshot Status to Updates so ordinary visitors land on a more useful patch-and-review hub first, while screenshot status remains available as a noindex support page.
• July 31, 2026: added save-check tables to all core guide pages so readers can compare each recommendation against their own boss route, resource run, castle layout, progression state, or mod setup before committing.
• July 31, 2026: strengthened Contact, Privacy, and Disclosure pages with clearer current-status tables, correction-request details, and public feedback handling notes.
• July 31, 2026: added quick choice tables to Bosses, Resources, Progression, Castle, and Mods category pages so each hub can route visitors by current situation before they scan the full guide list.
• July 31, 2026: replaced a repeated homepage path block with a session problem finder table so visitors can choose the right guide by current blocker instead of scanning a long article list.
• July 31, 2026: expanded route-decision tables across the core guide set, including Sulphur, Cotton, Cloth, Mucus, base location, and castle layout pages.
• July 31, 2026: added guide-scope, session-checklist, and player-note support blocks to the remaining core guides so more pages explain what they solve before the main article starts.
• July 31, 2026: tightened Map and Wiki hubs with clearer stuck-player decision tables, so broad hub pages now hand readers into practical routes faster.
• July 30, 2026: added Privacy, Contact, Terms, and Disclosure pages, connected them into the site footer, and routed public correction feedback through the Contact page and GitHub project route.
• July 30, 2026: moved the internal search page toward a lower-risk SEO role by setting it to noindex while keeping it available as a working on-site navigation tool.
• July 30, 2026: added a clearer latest-page-note layer inside article maintainer notes so ordinary guides now state more directly why the page was tightened recently and what should trigger the next return review.
• July 30, 2026: split article-page sidebar support links away from normal content follow-ups, so public update links, screenshot-status jumps, and patch-context links are easier to scan on ordinary guides.
• July 30, 2026: strengthened the public handoff layer so Updates, Screenshots, and Worklog now push visitors more clearly toward the right next page instead of behaving like isolated support pages.
• July 30, 2026: turned the search page into a clearer triage layer by adding best-first-click guidance, decision-page suggestions, and better pivot routes when a keyword is only close to the real problem.
• July 30, 2026: upgraded search results so they rank stronger practical pages first and show page type, current focus, and next useful context more clearly on each result card.
• July 30, 2026: made article status blocks more actionable by exposing current focus, next screenshot files, and screenshot folders more directly inside priority and screenshot-ready guides.
• July 30, 2026: added a clearer reader-triage layer on category pages so visitors can tell faster which page to open first, which page helps with the next decision, and which page still needs a little more caution.
• July 30, 2026: surfaced the first six-page screenshot batch more clearly across the homepage, proof page, worklog, and priority guide templates so the current screenshot run is easier to judge publicly.
• July 29, 2026: expanded the first screenshot batch from 4 pages to 6 priority guides so the public trust layer matches the strongest user-intent pages better.
• July 29, 2026: added exact first-pass screenshot targets, folder paths, and upload order for Clive, Iron, Efficient Castle Layout, Boss Order, Tanner, and Mods.
• July 29, 2026: refreshed the screenshot workflow so the rebuild and acceptance checks match the new six-guide screenshot batch.
• July 29, 2026: kept the public screenshot status page honest by leaving the site at 0 live screenshots instead of pretending planned screenshots are already real.
• July 28, 2026: tightened the public support layer through Updates, About, Screenshots, and category routing so the site reads more like a real guide project and less like isolated articles.

What is next in visual review

This is the shortest public review list that would make the site feel more trustworthy without trying to finish every screenshot slot at once.

1. Clive the Firestarter location: first image is the quarry entry lane.
2. Where to get Iron: first image is the first useful ore segment.
3. Efficient castle layout: first image is the early compact layout.
4. V Rising boss order: first image is one real unlock chain.
5. How to unlock Tanner: first image is the unlock confirmation.
6. Best V Rising mods: first image is the real plugin path.

Exact first-batch file targets

If the goal is to make the first screenshot pass feel real fast, these are the six exact files that matter most right now.

What should flip after the first capture

The first screenshot is not just a file drop. It should visibly change how the site presents trust to readers.

1. the article page should flip one screenshot slot from pending to captured
2. a live screenshot gallery should appear on that page once at least one real image is connected
3. the visual coverage page should start showing movement in totals and recent live visuals
4. the screenshot filter should be able to surface the page
5. the homepage and category pages should start feeling less preparatory because one real screenshot exists in public

What visitors should trust first

The route logic and page structure are already stronger than the old thin-search style. The pages are most trustworthy where they help players decide when a run is worth doing, when to stop pushing, and what the next practical follow-up should be.

Next public checks

As soon as the first real screenshot lands, the site should be checked in the same public-facing order:

1. open the article page and confirm the visual status block flips from pending to captured
2. check whether a live screenshot gallery appears on that page
3. open /proof/ and confirm the totals and recent proof block move
4. open the screenshot filter and confirm the page becomes discoverable there
5. confirm the homepage and category pages now feel more believable because at least one real screenshot exists publicly