Last month I wrote about the correctness pipeline behind sephiriabuilds.xyz — version stamps, evidence grades, the stuff that keeps a game wiki from rotting. This post is the operational half nobody writes about: the weekly routine that tells me when the stamps are stale, and the gate that stops a page from shipping until it has been checked against the current patch.
The game is Sephiria, an action roguelite that ships balance patches every few weeks. If you run a wiki or builds site for any game like this, this routine is the difference between "site" and "liability".
The watch: three signals, one hour a week
1. The version bump (Steam RSS)
The official signal. Steam exposes a news RSS per app; the version string in the feed is the heartbeat. 1.0.30 sitting unchanged for a week means the meta is stable and I can spend the week elsewhere. A bump means the next two evenings are spoken for.
A bump triggers one question, and it is not "update the site". It is: which mechanics did the patch notes touch? Most patches change numbers on a handful of items. The pages whose mechanics appear in the notes get re-checked; everything else stays untouched. A patch that buffs dagger evolutions does not invalidate the greatsword page, and pretending it does is how wikis end up with meaningless "updated!" dates everywhere.
2. The competitor diff (sitemap scraping)
Once a week I pull the sitemaps of the other wiki-ish sites covering the game and diff them against last week. This catches the thing RSS cannot: what the competition is building.
Concrete example from earlier this week: the sitemap diff showed two competitor sites both adding co-op guide pages. Around the same time the game's Google Trends "related queries" list had sephiria coop climbing the breakout list. Two independent signals pointing at the same content gap — that page is now on my site too (more on it below). One signal alone would have been noise; two is a to-do.
The diff is dumb and cheap: fetch sitemap, hash the URL set, compare to last week's hash, eyeball the delta. No Ahrefs, no paid anything.
3. The community pulse (Reddit + Steam guides)
Search-adjacent communities move faster than any index. The r/sephiria feed surfaces what players are actually confused about this week; the Steam community guides list shows what other documenters are covering. Neither is a command — both are inputs to the same backlog.
The combo that matters: a question recurring in the community and no page on my site answering it. That is the exact shape of the co-op page.
The gate: no page ships without a patch check
Every page on the site declares the game version it was checked against. Before anything publishes, it goes through the same check:
- Read the official patch notes 1.0 → current.
- Find every mechanic the page depends on. A build page depends on its weapon line, its artifacts, its damage type; the best builds hub depends on all of them.
- If a patch touched a dependency, the claim gets re-verified against the new numbers — or the page says explicitly what is unverified.
That last part is the one I care most about, because the honest answer to "is this current?" is sometimes "mostly". The newest page on the site, a Meteor build built around the Red Snake Eyes artifact, was verified against a co-op VOD on video and then re-checked against every patch note through 1.0.30 — and its frontmatter still says the mid-path sword names are unverified, because nobody has shown them on camera. A weaker site would guess. Guessing is how a wiki earns the "AI slop" complaints players throw at half the search results for this game.
What shipped this week
The routine produced two pages that went live today:
- A Sephiria co-op guide — how drops split between players, what reviving actually costs, and the two warnings the store page does not mention: dodge timing desyncs past 100ms ping, and controller support that is full on paper and spotty on some hardware. Born directly from the competitor-sitemap + Trends double signal.
- The Meteor build page above — evidence-graded, patch-checked, honest about its gaps.
Neither page would have existed this week without the watch. The version RSS was quiet; the ecosystem was not.
The payoff, honestly stated
The routine is maybe an hour a week when nothing ships, plus an evening per patch. In exchange:
- no page on the site claims a patch it was not checked against
- content gaps surface as double-signal to-dos instead of "someone in Discord said we should…"
- and when a player lands from search, the trust bar under the title answers the only question that matters: is this still true in the patch I'm playing?
That is the whole trick. Most game wikis die of rot, not of hosting or design. The watch is cheap; the rot is not.
Top comments (0)