English for Video Game Developers: Key Terms for Programming, Design, and Publishing

If you build games for a living, you already know the code is universal. But the team chat, the design docs, and the press release? Those are written in English. And no matter how clean your C# is, if you can’t explain why a feature matters in a stand-up meeting, the project slows down.

I’ve seen talented developers struggle not with logic, but with language. They freeze during calls with publishers. They write unclear commit messages. They get lost in design reviews. The fix isn’t a better IDE — it’s better professional English.

Below are the key terms you’ll actually use, split by the three stages of making a game: programming, design, and publishing.

Programming: The Build and the Bug

Most game code is written in C++, C#, or Python. The conversations around it are in English. Here are the terms that show up daily.

Build — This can be a verb ("We build every night") or a noun ("The build is broken"). A “build” is a compiled version of the game. If someone says “the build is red” or “the build failed,” something is wrong. If it’s “green,” you’re good.

Bug — A flaw in the code. “Bug” is universal, but you’ll also hear “crash” (the game closes), “glitch” (visual or audio hiccup), and “edge case” (a rare situation that breaks something). A good developer doesn’t just fix the bug — they write a repro step so others can see it.

Merge / Pull Request (PR) — When you finish a feature, you request to merge your code into the main branch. The team will “review your PR.” If they ask you to “squash your commits,” they want you to combine several small commits into one clean one.

Quick tip: When writing a PR description, skip the technical details and start with what the player experiences. Example: “This PR fixes the camera clipping through walls when the player crouches near a door.” That helps designers and QA understand immediately.

Design: Gameplay and Player Feel

This is where programmers and designers talk past each other — unless the programmer understands the designer’s vocabulary.

Gameplay — How the game feels to play. If someone says “the gameplay is stiff,” they mean the controls or animations don’t feel responsive. If they say “it’s fluid,” it works well.

Loop — Short for “game loop.” The core cycle a player repeats: fight, level up, get gear, fight again. A “tight loop” is addictive. A “broken loop” makes players leave.

UI / UX — User Interface (buttons, menus) and User Experience (how easy it is to navigate). A designer might say “the UI is confusing” or “the UX needs polish.” Don’t argue — ask for specific screenshots.

Player Onboarding — The first 10 minutes of your game. This is when a player learns the rules. If the onboarding is poor, players quit. If it’s great, they stay for hours.

Real example: A programmer once told me, “I fixed the collision bug.” The designer asked, “Does the player slide off walls now?” The programmer hadn’t thought about the player feel — just the math. Knowing the word “collision” isn’t enough. You need to connect it to the player experience.

Publishing: Localization and the Press Kit

Once the game is ready to ship, English gets even more important. You’re no longer talking to teammates. You’re talking to the world.

Localization — This isn’t just translation. It’s adapting your game for different cultures. A joke that works in English may offend in Japanese. A “localization kit” is a document you give to translators. It explains context: This character is sarcastic, or This sound effect is meant to be funny.

Press Kit — A folder of materials journalists use to write about your game. It needs a “one-liner” (one sentence that describes your game), “screenshots,” “fact sheet,” and “contact info.” If your press kit is messy, journalists skip you.

Launch Day / Ship Date — The day the game goes live. Everything is “crunch” (working extra hours) before launch. A “day-one patch” is an update released on launch day to fix last-minute bugs.

One Last Thing

You don’t need to speak perfect English to make a great game. You just need enough to communicate clearly with your team, your players, and your publisher. Start with these terms. Use them in your next stand-up. Write your next PR description with the player in mind.

And if you want to know where your English really stands — not guessing, but measured — try the English Measure test. It covers reading, listening, writing, and speaking. No charge, no catch. Just a clear picture of what you do well and what needs work.

👉 Take the free English test for game developers