abdooowd/ex-void

Purpose and Runtime

Ex-Void is a native C space-exploration game built on raylib. The executable begins at src/main.c; game lifecycle and top-level orchestration are centered in src/code/game.c with public contracts in include/game.h.

Application Lifecycle

src/main.c initializes and runs the game through the game module rather than embedding gameplay directly. src/code/game.c likely owns the main loop, frame progression, and shutdown boundary; include/config.h provides project-wide compile-time game settings.

State-Based Game Flow

Game modes are separated into state modules. Setup/initialization behavior is implemented in src/code/states/setup_state.c and gameplay behavior in src/code/states/play_state.c, with interfaces in include/states/setup_state.h and include/states/play_state.h. The state transition/dispatch layer is represented by include/tables/gamestate_table.h, making state selection a central control-flow boundary.

Actor System

World entities use an actor abstraction defined by include/actor.h and implemented in src/code/actor.c. Actor behavior can be supplied through overlays/interfaces in include/actor_ovl.h and src/code/actor_ovl.c, separating generic actor lifecycle/storage from actor-specific logic. Registered actor types are indexed through include/tables/actor_table.h.

Concrete Content Modules

Individual game content lives under src/actors/. The current concrete actor is src/actors/actor_test/actor_test.c, with its local declaration in src/actors/actor_test/actor_test.h. New actor implementations are expected to integrate with the generic actor and actor-table layers rather than the game loop directly.

Shared Platform and Diagnostics Boundary

Common primitive types, utility APIs, and error handling are isolated under include/lib/types.h, include/lib/utils.h, and src/lib/errors.c. Debug facilities are separately exposed by include/debug.h and implemented in src/code/debug.c, providing a diagnostic boundary outside game-state and actor logic.

Generation and Build Infrastructure

The repository includes scaffolding tools for extending its two principal abstractions: tools/new_actor/new_actor.py generates actor modules, while tools/new_state/new_state.py generates state modules. Makefile is the build entry point; raylib is the material external runtime dependency.