What Game Update Names Teach About Naming a Product Release

A software client once asked me to help announce "version 4.2.1" to customers and journalists. I asked what changed. The answer was a rebuilt reporting module that customers had begged for over two years. The version number said nothing about it, and the press release they had drafted buried it in paragraph four. Nobody covered it.

Game studios figured out long ago that a number is for engineers and a name is for the audience. The big update to a live game ships with a version number in the patch notes and a name on the store page, the trailer and the social posts. How they choose those names, and what happens when a name promises more than the update delivers, is one of the clearest lessons in release messaging I know.

Why a number alone never travels

Journalists and customers repeat words, not decimals. A name gives people a handle they can use in a sentence: "have you played the Caves and Cliffs update?" is something a player says to a friend. "Have you played 1.17?" is something only a fan says.

That is why Minecraft's major updates carry names like Caves and Cliffs, Trails and Tales, and The Wild Update, while every patch note still lists the version number. Both exist, for two different audiences. My client had only the number, so the only people who noticed the release were the ones who read changelogs.

Names that set the right promise

A good update name tells the audience what to expect in a word or two. Hello Games has shipped years of free updates to No Man's Sky, with names like Foundation, NEXT, Beyond, Origins and Worlds. The first big one, Foundation, came in late 2016 after a launch that many players felt overpromised. The name was modest on purpose. It said, more or less, "we are fixing the base." When NEXT arrived in 2018 with multiplayer and a large overhaul, the name signalled a fresh start without claiming perfection.

The lesson for a company announcement is that the name should match the scale of what you are delivering. Calling a minor bug fix release "Horizon" invites disappointment. Calling a major rebuild "Update 7" wastes it.

I use a quick test with clients: if a customer heard only the name and nothing else, what would they expect? Write that down. Then compare it with the actual release notes. If the gap is large in either direction, change the name, not the notes.

When the name has to survive a delay

The most useful case study is what happened to Caves and Cliffs. Mojang announced it in 2020 as one large update. In early 2021, they said the update would be split into two parts, because the full content would not be ready for the original summer date. Part I shipped in June 2021 as version 1.17, Part II followed in November 2021 as version 1.18.

They kept the name and added a part number, and they explained why in plain terms well before the original date. That decision protected the promise. Players who had been waiting for the full update still got it, and the name stayed attached to the whole thing, rather than half of it shipping under the big name and the rest disappearing under a different one.

The common corporate instinct, when a named release slips, is to quietly rename it or drop features without mentioning it. I have watched that go badly more than once. Customers remember the original name and they notice what is missing. Splitting openly and keeping the name is almost always better. It mirrors the approach I describe in writing a statement before the story breaks: say the uncomfortable thing first, in your own words.

Codenames that leak, and names that age

Game studios also teach a lesson about internal names. Codenames used during development often leak, and once they do, the audience may prefer them to the official name. If a project codename is something you would be embarrassed to see in a headline, change it before the first external meeting, not after. I now ask every client what their internal name for an upcoming release is, because there is a fair chance a journalist will hear it.

Names also age. Long running games and expansions build a family of names over years, such as Destiny 2's Forsaken, Shadowkeep, Beyond Light, The Witch Queen, Lightfall and The Final Shape. Each name stands alone, yet together they tell a story about where the game is heading. A company that releases two named versions a year should think of the names as a set. Pick a style that can sustain ten of them, the same way you would pick a voice you can keep, which I wrote about in picking a brand voice you can keep for years.

A naming checklist for your next release

One caution: consistency can tip into sameness. If every release name follows the same formula, the names stop carrying meaning. I covered when that happens in when consistent messaging starts to sound robotic. And if your release comes with technical notes for users, the plain writing advice in what game patch notes teach about writing clearly covers the other half of the job.

Name one release this week

Look at the next release your team has planned and write down two things: the version number engineers will use, and a two or three word name for customers. Run the name through the table above. Then rewrite the first line of the announcement so the name and the single most wanted change appear in the same sentence. If my client had done that with their reporting module, the release would have had a headline.