Game Engine Language

Game development has its own dense vocabulary that spans engine-specific APIs (Unity's MonoBehaviour, Unreal's ACharacter), architectural patterns (Entity-Component-System), real-time systems concepts (fixed timestep, frame budget), graphics terminology (PBR, LOD, culling), and networking concepts (tick rate, lag compensation). A developer moving into games — or working on an international team — needs fluent, precise English for all of these, not just general programming vocabulary.

Unity scripting uses C# with a MonoBehaviour-based component model: scripts attach directly to GameObjects, and lifecycle methods like Start/Update drive behaviour. Unreal Engine centres on Blueprints — a visual scripting system built on nodes and wires — layered on top of a C++ Actor/Pawn/Character class hierarchy. Both engines share underlying concepts (game loop, components, events) but use different terminology: Unity's "prefab" vs Unreal's "Blueprint class," Unity's "GameObject" vs Unreal's "Actor."

ECS is a data-oriented architecture pattern used in engines like Unity DOTS, Bevy (Rust), and Flecs, favoured for its cache-locality and parallel-processing performance over traditional object-oriented GameObject models. Its vocabulary — entity, component, system, archetype, query — appears constantly in engine documentation, conference talks, and job interviews for performance-focused or systems-programming game roles.

deltaTime is the elapsed time since the previous frame, used to scale movement and animation so gameplay stays consistent regardless of frame rate: "multiply velocity by deltaTime for frame-rate-independent movement" is one of the most common sentences in game programming documentation and code review comments.

Core terms: vertex/fragment shader, rasterization, depth buffer, PBR (physically based rendering) with roughness/metallic parameters, frustum culling and occlusion culling, and Level of Detail (LOD). These terms appear in shader code comments, GPU profiler output, and rendering pipeline documentation across every modern engine.

Start with: client-server vs. peer-to-peer, authoritative server, tick rate, latency/RTT/jitter/packet loss, client-side prediction and server reconciliation, and lag compensation ("rewind time"). These terms are used constantly in networking code reviews, postmortems, and design documents for any real-time multiplayer game.

No — each exercise set includes full explanations that teach the underlying concept alongside the English vocabulary. Beginner sets (Unity Scripting) assume no game engine background; Advanced sets (ECS, Graphics & Rendering, Multiplayer) assume general programming knowledge but explain game-specific concepts from first principles.

This category focuses on engine-specific and architectural vocabulary through interactive exercises. For broader game industry vocabulary, see the Game Development vocabulary page; for interview preparation, see Game Dev Interview Questions.

Both improve rendering performance but work differently: frustum/occlusion culling decide whether to draw an object at all (is it visible?), while LOD decides how much detail to use when drawing an object that IS visible (is it far enough away to use a simpler mesh?). A well-optimised scene uses both together.

Because real-time multiplayer games must hide network latency from players while still keeping a server authoritative. "Reconciliation" describes correcting a client's locally predicted state once the server's authoritative result arrives; "rewind time" (lag compensation) describes the server checking hit detection against where a target appeared on the shooter's screen, not their current position. Both terms describe techniques for making a laggy network feel responsive and fair.