Why we still read patch notes, even for games we don't play

There's a particular kind of craftsmanship visible in a good patch note: 'Fixed an issue where the third bounce of a grenade could clip through geometry on the northern bridge of Map 7.' Nobody has to write that sentence with that much precision. Someone chose to.

We read patch notes the way some people read restaurant reviews of places they'll never visit — not for the content, but for the evidence of care. A studio that documents a niche physics bug that affected 0.1% of matches is a studio that's still paying attention after launch, long after the marketing budget moved on.

It's the same instinct behind our own changelog. Most users will never read 'fixed a rounding error in the multi-currency export.' We write it down anyway, because the discipline of naming the fix precisely is the same discipline that prevents the next one.