Journal

Desk notes

Short pieces from the computer game desk: patch checklists, how we plan a Steam night, and what we learned covering twelve-title evenings after a reset. Full text is on this page so you do not need a second click. These are working notes, not paid rankings or forecasts.

Changelog checklist used before a Steam launch night

6 min · Patch checklists

Why we still check the client before we write the name

How a slow first changelog check saves the rest of the night’s copy, including the crash line that never made the studio notes.

Read full article

Late Steam session after a midweek maintenance window

5 min · On the wire

Covering a Steam night after patch heat

What we carry, what we leave, and when we wait for the hotfix instead of guessing the store close.

Read full article

Launch notes on the Patchwire writing desk

4 min · Hotfixes

Filing twelve titles without losing the limited window

A practical note from our last September night, including who kept time and who checked expansion names.

Read full article

Patch checklists

Why we still check the client before we write the name

By Haru Nilsen · 6 min read

Changelog screen before a Steam launch night

The first line of a launch night is not for the recap. It is a client proof: who moved the version string, who came in heavy on a silent crash, and whether a substitute hotfix or language pack is even on the list. We still run that check as if it were a closed-door session — one build, a pause, a change in the notebook before anyone queues into a live title.

If the proof is wrong, we move a name or a build before the store opens. That habit keeps the rest of the evening calm. It is also why our morning files need fewer corrections after a late Friday Steam grind, when late replacements and silent nerfs are common.

Want the same approach on your next window? Send the hotfix time and a draft changelog, and we will build a checklist around it. We still will not publish a leak as a result.

Talk about a patch · See the release files

On the wire

Covering a Steam night after patch heat

By Callum Prest · 5 min read

Late session after a Steam maintenance window

Heat is not a problem if you decide what the night is for. On the September 17 double window we used the first two store refreshes as a timing check and hid in the shade of a quieter title only when a colleague asked for a quiet word. The kit stayed small: two notebooks, one capture tool, no live stream unless the studio already had one.

The useful rule: if you cannot carry it through a full download without stopping, it does not come. That is how the evening stays about the person at the launcher. We still write from a confirmed hotfix if the servers are too packed to sit, and we say so in the first paragraph so readers know we were not in the live client.

Open the GTA VI file · Browse stills

Hotfixes

Filing twelve titles without losing the limited window

By Sione Mata'afa · 4 min read

Title list on the Patchwire reports desk

Our reset-night bench is one laptop, booked in twenty-minute blocks between downloads. We write with a written result, two people, and a tagged still folder. Twelve titles take an evening if the names are already checked and the captions are sleeved with the date.

If you are sending a set, we send a changelog list and a caption sheet. If you are visiting, the next open window is announced on the calendar page and by newsletter. Limited openers get the same name check as the gold master; that is how side modes stop disappearing from the recap.

Current calendar · Reserve a question