Small game tools. Big terrain ahead.

01 / Reusable building blocks

Lib/game/core/fixed_step.noqeri plans deterministic fixed-step updates from monotonic nanoseconds; input/button, math/vec3 and physics/aabb provide basic input state, vector math and collision helpers. These are libraries, not a window manager or renderer.

02 / Asset and validation tools

Tools/game/validate-obj.mjs validates a bounded subset of OBJ geometry. Files in examples/game_sdk and test fixtures demonstrate intended usage, but an asset validator is not the runtime loader for a finished 3D game.

node Tools/game/validate-obj.mjs examples/game_sdk/assets/cube.obj

03 / Raster, shader and platform pieces

CPU raster source exists for 2D/3D and bounded WGSL shader generation. The envisioned SDL3/OpenGL 3.3 game workflow needs native ABI, event loop, driver and real-device verification; do not treat the source tree as proof of a shipped engine.

04 / What qualifies a real game SDK

Before promising a complete game development platform, Noqeri needs verified native FFI, executable builds on supported hosts, a continuous update/render loop, asset loading, safe memory ownership, end-to-end input and hardware qualification. Multiplayer and editor features are explicitly later milestones.

05 / Learn through small examples

Treat current utilities as experimental programming exercises and build toward first independent rendered frames. The compiler can still be useful for general-purpose work without a finished game engine.