How electronicarts/cnc_tiberian_dawn works
Project Type and Purpose
• This is a Win32 desktop game engine (classic real-time strategy) written in C/C++ with assembly stubs.
• The README confirms it’s the original Command & Conquer engine, extended for Steam Workshop support, relying on DirectX 5, GCL (networking), and SOS (audio HMI).
File Structure and Architectural Layers
Files and folders into these major layers:
• Core Engine Layer
– Graphics/rendering: DISPLAY.CPP/H, TEXTBLIT.H, GSCREEN.*, GAUGE.*, FLASHER.*
– Audio: AUDIO.CPP/H, SOUNDDLG.*, SOS stubs
– Input & UI: MOUSE.CPP, KEYFRAME.CPP, DIALOG.*, CONTROL.*, GADGET.*
– Memory & Resources: HEAP.*, RAWFILE.*, MIXFILE.*, BFILE.MAK, MAKEFILE
– Assembly support: *.ASM, e.g. COORDA.ASM, IPXPROT.ASM
• Game Logic Layer
– Units & Entities: INFANTRY.*, AIRCRAFT.*, TURRET.*, UNIT.CPP/H, OBJECT.*
– Map & Pathfinding: MAP.*, FINDPATH.CPP, TERRAIN.*, CELL.*
– Combat & Simulation: COMBAT.*, BULLET.*, DAMAGE in UNIT/OBJECT
– AI/Campaign: LOGIC.CPP/H, MISSION.*, SCENARIO.*, TRIGGER.*
• Networking Layer
– IPX: IPX.CPP/H, IPX95.*, IPXMGR.*, IPXCONN.*
– TCP/IP: TCPIP.*
– Abstract comm: CONNECT.*, CONNMGR.*, GCL stubs
• UI & Tools Layer
– Dialogs/config: CONFDLG.*, NETDLG.*, VISUDLG.*, OPTIONS.*
– Level editor: MAPEDIT.*, MAPEDDLG.*
– Utilities: TOOLS/MIXFILE.EXE
• External Dependencies & Build
– DirectX 5 SDK (graphics/audio)
– GCL for network transport
– SOS HMI library for audio management
– Watcom, TASM, MASM for build toolchain
README Insights
• Game engine core is missing; requires Red Alert engine libs.
• Build environment: Win32, Watcom C/C++, TASM, MASM.
• No modern layering (e.g., no client-server split)—it’s a monolithic, event-driven engine.
Defining Components & Relationships
a. Main Components
1) Presentation Layer (UI & Input)
2) Engine Core (Rendering, Audio, Resource Management)
3) Game Logic & Simulation
4) Networking Stack
5) External Libraries & Tools
b. Interactions
– Input subsystem → Game Logic → Rendering & Audio subsystems
– Game Logic ↔ Map & Pathfinding services
– Game Logic ↔ Networking → External network (other players)
– Resource Manager → Disk I/O → Data files (mix, raw)
– Rendering & Audio → DirectX 5 SDK
c. Architectural Patterns
– Layered architecture (UI → Logic → Engine → OS)
– Component-style entity modules for units, terrain, triggers
d. Key Technologies & Libraries
– DirectX 5 for graphics and sound
– GCL (Greenleaf Communications Library) for network messaging
– SOS (Sound Operating System) for advanced audio control
– Watcom/TASM/MASM compilers for legacy build