Game Development English Vocabulary: 80 Essential Terms

Game development has one of the most specialised English vocabularies in software engineering — blending computer graphics, physics simulation, network programming, game design theory, and community communication. Whether you read Unreal documentation, write patch notes, or present a sprint demo, this guide covers the 80 terms you need.

Core Game Architecture

Game Loop

The game loop is the central loop that drives every game. On each iteration (frame), it processes input, updates game state, and renders the scene. A typical loop runs 30–144 times per second.

“The enemy AI is too expensive — it’s slowing the game loop and causing frame drops.”

Frame Rate / FPS (Frames Per Second)

FPS is how many frames the game renders per second. 30 fps is acceptable for many games; 60 fps is smooth; 120+ fps is high-end. Frame rate is capped by CPU/GPU performance and game loop complexity.

Delta Time

Delta time (deltaTime) is the elapsed time since the last frame. Movement and physics calculations use delta time to remain frame-rate independent — objects move at the same speed regardless of FPS.

“We multiply movement speed by deltaTime so the character doesn’t move faster at 144 fps.”

Tick

A tick is one cycle of the game simulation. In multiplayer games, the tick rate defines how often the server updates game state. Higher tick rates improve precision at the cost of bandwidth.

Engine

A game engine is a framework providing core systems: rendering, physics, audio, input, scripting, and asset management. Major engines: Unity (C#), Unreal Engine (C++ / Blueprint), Godot (GDScript / C#), GameMaker (GML).

Entities and Object Systems

Entity-Component-System (ECS)

ECS is an architectural pattern where:

Entity — a unique ID (no data or logic)
Component — pure data attached to an entity (e.g., Position, Health, Renderer)
System — logic that processes entities with specific components

ECS promotes composition over inheritance and improves data-oriented performance.

Prefab

A prefab is a reusable template for a game object — it stores a configuration of components that can be instantiated multiple times. Modifying the prefab updates all instances.

“We have a prefab for each enemy type — spawn ten orcs by instantiating the OrcPrefab ten times.”

Scene

A scene (or level) is a container for all game objects, lights, cameras, and settings in a specific game area or state.

Script

In Unity and Godot, a script is a component containing logic — responding to events, controlling behaviour, communicating with other components.

Rendering

Shader

A shader is a small program executed on the GPU that determines how surfaces look — colour, reflectivity, transparency, and special effects. Types:

Vertex shader — transforms 3D positions to 2D screen coordinates
Fragment (pixel) shader — determines the colour of each pixel
Compute shader — general-purpose GPU computation

“The water effect uses a custom vertex shader to simulate wave displacement.”

Material

A material defines how a surface looks — it references a shader and assigns textures and parameters (colour, metalness, roughness).

Texture

A texture is an image mapped onto a 3D mesh surface. Common types: diffuse (colour), normal (surface detail), roughness, emission.

Normal Map

A normal map is a texture that encodes surface direction variations, creating the illusion of fine surface detail without adding polygons.

Level of Detail (LOD)

LOD is a technique where higher-detail meshes are used for objects close to the camera, and simpler meshes for distant objects. Reduces rendering load.

Draw Call

A draw call is a command sent from the CPU to the GPU to render a mesh. Too many draw calls per frame is a major performance bottleneck. Batching and instancing reduce draw calls.

Light Baking

Light baking pre-computes static lighting and stores it in lightmaps — substantially cheaper than real-time lighting for static environments.

Post-Processing

Post-processing is a set of screen-space effects applied after the 3D scene is rendered: bloom, ambient occlusion, motion blur, colour grading, depth of field.

Physics

Rigid Body

A rigid body is a physics object that simulates mass, gravity, forces, and collisions without deforming. Standard for characters, vehicles, and projectiles.

Collider

A collider is an invisible shape attached to a game object that defines its physical boundary for collision detection. Common shapes: box, sphere, capsule, mesh.

Raycasting

Raycasting is casting an invisible ray from a point in a direction to detect what it hits. Used for shooting mechanics, visibility checks, and surface detection.

“The gun fires a raycast from the camera position — if it hits an enemy collider, we apply damage.”

Physics Simulation

Physics simulation is th calculation of movement, gravity, friction, and collisions each frame. Computationally expensive — physics objects are kept to the minimum necessary.

Multiplayer & Networking

Netcode

Netcode is a general term for the networking code in a multiplayer game — synchronising game state between clients and server.

Client-Side Prediction

Client-side prediction allows the local client to apply player input immediately (without waiting for server confirmation) to reduce perceived latency. The server later reconciles the authoritative state.

“Without client-side prediction, input lag at 150ms ping feels unplayable.”

Lag Compensation

Lag compensation allows the server to rewind game state when validating a hit, accounting for the client’s latency. Enables fair hit registration in fast-paced shooters.

Dedicated Server / Listen Server

A dedicated server runs game logic independently with no player. A listen server is hosted on one player’s machine and that player also plays. Dedicated servers provide better performance and anti-cheat.

Authoritative Server

An authoritative server is the single source of truth for game state. Clients send inputs; the server validates and simulates the result. Prevents cheating.

P2P (Peer-to-Peer)

In P2P networking, clients communicate directly with each other — no central server. Common in fighting games (using rollback netcode). Cheaper to run but more susceptible to cheating.

Rollback Netcode

Rollback netcode predicts opponent inputs locally, renders frames speculatively, and rolls back and resimulates if the prediction was wrong. Standard in competitive fighting games. Reduces perceived latency significantly.

Game Design Vocabulary

GDD (Game Design Document)

A GDD is the master design document that describes the game’s mechanics, systems, characters, story, art direction, and technical requirements.

Vertical Slice

A vertical slice is a polished, playable demo that represents the full game experience at a small scale — used to validate design, pitch to publishers, or secure funding.

Core Loop

The core loop is the fundamental cycle of actions that repeats throughout the game: play → reward → upgrade → play again. A well-designed core loop drives engagement and retention.

Metagame

The metagame (meta) is the layer of strategy above the core game — deck building, loadout optimisation, roster selection. In competitive games, “the meta” refers to the current dominant strategies.

EconomY (In-Game Economy)

The in-game economy governs how players earn and spend virtual currency and resources. Balance is critical — inflation (too much currency) or deflation destroys player motivation.

Loot Box

A loot box is a randomised reward obtained through play or purchase. Controversial due to comparisons with gambling mechanics. Regulatory scrutiny varies by country.

Battle Pass

A battle pass is a tiered seasonal reward system. Players unlock cosmetics by completing challenges or accumulating XP. A model popularised by Fortnite.

Post-Mortem

A game post-mortem is a retrospective article or presentation reflecting on what went well and what went wrong during development. Published by developers after launch.

Performance & Profiling

Profiler

A profiler is a tool that measures where time and memory are spent each frame. Unity and Unreal both include built-in profilers.

Hotspot

A hotspot (or bottleneck) is a section of code spending a disproportionate amount of time. Profiling identifies hotspots so optimisation effort is well-targeted.

Garbage Collection (GC)

Garbage collection is automatic memory reclamation. In managed languages (C#, GDScript), frequent GC pauses cause GC spikes — frame rate stutters. Object pooling reduces GC pressure.

Object Pooling

Object pooling pre-allocates a set of objects (e.g., bullets, particles) and reuses them instead of creating and destroying objects each frame — eliminates GC overhead.

Profiling Build / Release Build

A profiling build includes debugging symbols and telemetry. A release build is optimised for performance. Always profile in a release-like configuration to get accurate numbers.

Audio

AudioMixer / AudioBus

An AudioMixer (or bus) routes audio signals through a shared channel where effects and volume control can be applied globally — for music, SFX, and voice separately.

Spatial Audio / 3D Audio

Spatial audio simulates the direction and distance of sounds based on the listener’s position and orientation in the 3D world.

Procedural Audio

Procedural audio generates sound dynamically based on game state (e.g., footstep sound varies by surface material), rather than playing fixed recordings.

Distribution & Release

Patch Notes

Patch notes are the official documentation of changes in a game update. Structure: version number, date, sections for New / Changed / Fixed / Known Issues.

SKU (Stock Keeping Unit)

A SKU in gaming refers to a specific version of the game: standard edition, deluxe edition, Game Pass version, etc.

Gold / Gold Master

Going gold means the game is complete and approved for manufacturing/distribution. The final approved build is the gold master.

Early Access

Early Access (Steam) or Game Preview (Xbox) allows developers to sell an unfinished game and use player feedback to continue development.

Live Service / GaaS (Games as a Service)

A live service game continues generating content and revenue after launch through updates, seasons, and in-app purchases. Requires ongoing operational support (GaaS — Games as a Service).

Useful Phrases

In design reviews:

“The core loop feels rewarding — collect, upgrade, fight — but the upgrade step needs more friction to increase time between loops.”
“The boss’s health pool is too high — players lose the sense of progress.”

In post-mortems:

“The scope of the procedural level generation system was underestimated — it caused three months of delays.”
“What went well: the animation team shipped ahead of schedule. What didn’t: netcode was integrated too late to test properly.”

In patch notes:

“Fixed a crash that occurred when loading the inventory screen on low-end hardware.”
“Adjusted the respawn timer from 5s to 3s based on community feedback.”

Practice

Test your game development vocabulary with the Game Development exercise set — 5 exercises covering game design terms, engine vocabulary, and multiplayer concepts.

Explore the full Game Developer learning path for exercises, interview prep, and scenario practice.