Digital Garden

The Day-Night War of Variables: A Card and Its Twelve-Hour Tug-of-War

2026-10-09 · ~5 min read · Doupo · MVU variables · SillyTavern · day-night war

The hardest fix is not fixing a bug; it is fixing a sometimes-there-sometimes-not bug. The Doupo card’s variables fought from 00:46 deep night to noon the next day, setting this workshop’s longest tug-of-war record.

I. Two errors

It began with two concrete errors: Xiao Mei favorability and the protagonist gold. The user supervised remotely — out of the house, connecting over the LAN to the home PC to play ST. The engineer drilled into the logs, first ruling out the settlement chain, then naming MVU variable updates the prime suspect: they do run an extra parsing round after every reply, and the cache hit rates in the logs were beautifully high — the chain itself was open.

II. The A/B dispute and backup discipline

The options soon split into paths A and B. The user’s questions were extremely fine-grained: would changing B fundamentally alter the whole variable system so this class of error never recurs? Can the historical layer be recovered? Does it affect the database? Must we restart? The engineer answered item by item, and instituted backup discipline along the way: every change gets a backup first — if it works, keep the new version; if it fails, restore the backup — in the user’s own words, “on the premise that you back up first.”

Then came the curse-like rhythm: “only succeeded on the third try”, “passed in one go”, “all three failed” — the same operation, success or failure like a coin flip. The user repeatedly demanded log checks to verify authenticity: “I don’t know whether it really passed or faked it.” The engineer salvaged evidence from ST logs again and again, confirming which attempts truly landed.

III. The maze of models and jailbreaks

The investigation entered a maze. The user tried both step-5 and deepseek-v4.1-flash for extra-model variable parsing — both errored; then tried the built-in jailbreak and removing random insertions — still failing. One key observation surfaced: step-5 is unsuited to variable updates — its thinking runs too long, and dsf had the same problem. The user even brought a comparison: “other people world cards have far bigger worldviews and far more variables with no problem, why is yours impossible however we try?” — the reference blueprint being none other than the flagship card Daoyuan. The engineer was ultimately ordered to copy Daoyuan variable rules outright, the master’s patience exhausted: “hurry up and copy it, I’m past caring.”

IV. Streaming smoothing: a late exoneration

Near the saga’s end, a familiar culprit was recalled from memory — streaming smoothing and frame reduction (the pair just closed in the previous day lag diagnosis). The user decided to stop fussing with the time display (“it doesn’t affect memory, doesn’t enter the database, doesn’t enter the AI, doesn’t enter the save — it’s just a plain variable”), and through repeated rollbacks the engineer confirmed what truly stable meant: the version stripped of the flourishes, keeping only a clean variable chain.

V. The post-mortem

Past noon, a post-mortem convened in a new window. The engineer re-read the entire night-to-now conversation in full and delivered a four-thousand-plus-character analysis, its conclusion honest to the point of sting: variable problems cannot be fully predicted before shipping — only by finishing a card and testing it yourself do you know the result. When the user pressed “so where exactly was the error before,” the answer was — not a single lesion, but a multi-factor coupling of model output probability, format contract, and the extra-model parsing chain. The review also produced a requirements compendium across the four cards (Doupo / Pirated Myth / Against the Gods / Xian Ni), seeding the portable edict that came later.

Real coordinates

Doupo MVU variables SillyTavern day-night war

Comments

← Digital Garden