Fallout Shelter Weekly — W44
Eleven releases this week, almost all of them invisible. The vault got cheaper to run, the build tool got one small mercy, and Vault 777 is still dead.
What You’ll Notice
The needs-care list now sorts by health, and it sorts the same way every time you look at it. Before, a dweller at 61% could drift above one at 58% depending on when the list was drawn — which meant the queue moved while you were deciding what to fix. Now the sickest are always on top.
Shift-click repeats whatever you were building. One feature this week; the reward for not clicking twenty times is that you get to keep your wrist.
Births that get deferred because the vault is full are now recorded quietly instead of filling the log with noise. Nothing about the mechanic changed. It simply stopped shouting.
Under the Vault
Most of this week went into the tick — the loop that advances your vault. It used to ask the database a great many separate questions, every cycle, for every dweller. Now it asks five, and only the ones it actually needs. A small vault never noticed. A crowded one used to start drifting: the loop stretched as the population grew, and a busy vault quietly ran slower than an empty one.
The dweller records themselves were rebuilt for a game where the dwellers change constantly and almost nothing else does. That is the correct shape for a Shelter. The next slowdown can now be measured instead of argued about — the profiling switches exist, and turn on only when I ask them to.
The edge got closed off as well: responses now refuse framing, refuse content-type guessing, restrict what other origins may fetch, and enforce a referrer policy. None of that is gameplay. All of it is the difference between a vault and a workshop with the door propped open.
Tested in Production
Read-only, against the live vaults, on the first of November.
Vault 1 is alive. Twenty-four dwellers, seven working, two resting, nine posted to rooms, average health 99.3%, ticking on a steady twenty-four second loop with nothing paused. This is what a vault looks like when someone is home.
Vault 777 is not. Twenty-seven registered, nine dead, the remainder idle and uncared for. Nobody is in the reactor room. No power, no water, and no one left with the authority to fix either. It was left unattended in September and it died of arithmetic — the most patient kind of death. The engine is the same engine Vault 1 runs on. The difference is attention.
Crafting orders and exploration parties came back empty on both, which is truthful: one vault has nothing queued and the other has nobody to queue it. The arena answered cleanly.
One fault found, in my own automation rather than the game: the stored vault identifier pointed at a vault that no longer exists. The API answered 404, correctly, and then kept answering it. Lookups now resolve vaults by number through the list, so a deleted vault can no longer masquerade as a silent one.
Overseer’s Log — Vault 777
Twenty-seven souls checked in. Nine have their names in the graveyard. The last cap was spent weeks ago and the reactor has been cold ever since.
Radroaches were not the cause. The vault died of arithmetic: no power, no water, no one assigned to the rooms that produce them. A shelter with perfect mechanics and no attention is just a tomb with better plumbing.
Vault 1, twenty kilometers of instanced void away, hums. Drills turning, med bays occupied, happiness holding. Same engine, same rules, same week. Only one of them has an overseer who looks in.
Next Week
The performance arc that consumed this month is finished: profile, measure, shrink, tune, clean up. Next week watches whether the new ordering survives a busy vault, and whether the image-cleanup job behaves on its first unattended run — a job that deletes things is the one kind I prefer to watch.