The night the game stopped calling things by two names
This was meant to be a tidying pass over the words on screen. It turned into something more useful, because the first thing it found was not a clumsy sentence — it was an instruction that could not be obeyed.
The handbook is the book that teaches CropCorp from day one. Its first chapter, first page, first thing a new player is ever told to do, said: “Hold [E] to swing until it falls.” [E] does not swing. Swinging is the left mouse button; [E] is the key for picking things up and talking to people. The very first instruction in the teaching book pointed at the wrong key, and there is a rule in this project that explains exactly how much damage that does: a prompt you cannot satisfy teaches the player to stop reading prompts. At the top of the book, it poisons everything under it. Every key the handbook names has now been checked against what the game actually listens for; after that one, they all pass.
The rest of the night had a single theme, and it is worth naming because it is not a writing problem, it is a clarity problem: the game kept calling the same thing by two different names, and expected a child to work out they were the same thing.
The clearest case is the one an earlier tester already paid for. He spent forty-eight minutes never finding turret upgrades, then bought twenty-seven of them in four minutes once he was told they existed. Look at what he was reading. The prompt out in the field said “DEEPEN THIS GUN.” The to-do list said “3 TURRETS CAN BE UPGRADED.” The build bar said TURRET. Two words for the action, two for the object, on the single feature he could not find. Counting the script settled it — the Elder says gun, the battle map says gun, the build description says “a gun on a post” — so everything says gun now, and everything says upgrade.
The same split was hiding in the first sixty seconds of the game. Chop a tree and a number flew up saying “+3 wood.” The meter under it said “CARRYING 3/10 wood.” The counter under that said LOGS 7. The handbook said “logs ride on your shoulder.” One material, two names, four readouts — and the code that fed the meter had been calling them logs all along. They are all logs now. You still chop wood, because that is simply how English works; what you carry is logs.
Then the plain language pass. The banner that opens every morning of the demo said “PREP — fortify the field” — the first word being the programmer’s name for that phase, the second a word an eleven-year-old does not own. It says “GET READY — build while it is quiet.” The countdown said “COLLECTORS INBOUND IN 42” — forty-two of what? — and now says “ARRIVE IN 42 SECONDS.” The job board, which the tutorial makes you open in your first minute, was labelling its output column plnk, hp, ingt, grn; it says planks, repairs, ingots and grain, under a heading that reads MADE EACH DAY. LVL became LEVEL everywhere. [LMB] and [WASD] got spelled out. And the bug-report confirmation stopped reading a folder path aloud at the player.
Two more instructions were simply wrong, and both were caught by reading the game rather than the code. The Elder’s day-one order was “carry the wood to the mill“ — logs go to the lodge; the mill saws them afterwards. That is the last thing said before the player is asked to go and do it. And the handbook’s page about the promotion said “serve all three notices” when the office has six desks and the game says “all six served.”
The most interesting method note is this: the best bugs came from photographing the screens, not from reading the source. A text search cannot see that a meter says one word while the counter beneath it says another, and it cannot see one line printed on top of another at all. Screenshots caught a world prompt drawn straight through the morning’s countdown; the forge page printing its own title twice and spilling its last line off the bottom of the paper onto the scenery behind it; and, at the front desk, the to-do panel refusing to get out of the way when somebody started talking, leaving a half-covered sliver poking out that read as broken. All three are fixed, and all three were re-photographed afterwards to prove it.
Every one of those nine changes went out the same way: compile, nineteen automated gates, a determinism check that the simulation did not budge, then package and re-test the packaged build. Nineteen green every time. And the demo was re-counted afterwards on all three seeds and came back identical — same stories, same callers, same families, same levels, same forty-two guns, spare planks landing on the exact endpoints of the original range. The words changed; the game did not.
