Start with working defaults
VOID gives you a useful starting point so you can build first and dig deeper only when the project actually needs it.
Tools for building games without fighting your tools.
VOID is a game-development ecosystem built around one idea: useful foundations should not become walls. VOID Engine and VOID Language can work together, but each is designed to stand on its own.
VOID gives you a useful starting point so you can build first and dig deeper only when the project actually needs it.
The important boundaries stay visible. Extend or replace the pieces that matter without turning the whole project into an engine fork or a runtime rewrite.
VOID Engine and VOID Language share a philosophy, not a dependency. Use the engine, the language, or both.
Engine + Language
VOID Engine and VOID Language are independent projects designed to work beautifully together. Use one, or both. Either way, the goal is the same: give game developers more control, less friction, and a foundation that gets out of your way.
VOID
A high-performance 2D game engine with a pluggable renderer, built for flexibility and control. Designed to scale from small prototypes to ambitious projects.
VOID
A modern, C#-inspired language built for game development, with its own compiler and runtime. It keeps familiar high-level code while compiling through C to native binaries, and it owns the runtime pieces underneath features such as threading, GC, exceptions, and native interop.
Key features
A growing set of tools and ideas designed around control, performance, and simplicity.
OpenGL is the built-in backend, not a hard boundary. Higher-level rendering stays backend-neutral so another renderer can fit later.
VOID keeps the parts of modern managed code that make game systems easier to express, while its own compiler and runtime handle the machinery underneath.
VOID lowers to portable C and uses the system toolchain to produce native programs without requiring the .NET runtime.
Less framework friction and less unnecessary complexity.
Cross the C boundary directly when game code needs native libraries or lower-level control. VOID libraries can expose stable native entry points too.
The compiler answers the editor's questions too, so diagnostics, completion, navigation, and signatures stay aligned with real builds.
Choose your path
Explore the engine, discover the language, or use both as the foundation for what comes next.