I’m building Kvas, an open-source 3D game engine written in Rust. I’d love help from game developers, Rust developers, graphics programmers, tool builders, and anyone interested in using AI coding agents to contribute to open source.
- GitHub: github.com/Nopass0/kvas
- Documentation: Kvas documentation
- Roadmap: Planned features and current limitations
What’s already in Kvas
Kvas already includes:
- A Rust workspace with an ECS, engine runtime, renderer, audio crate, editor, and standalone player.
- A 3D scene editor with a hierarchy, inspector, transform tools, project browser, and English and Russian interfaces.
- A renderer built with
wgpu, with PBR materials, shadows, HDRI, procedural skies, particles, and post-processing. - A visual node editor for materials and shaders, with live previews and a library of procedural materials.
- Rapier physics and Rust game scripts with hot reload.
- Sample projects, build tools, and a bilingual documentation site.
Kvas is actively developed. Some features are experimental or incomplete. Official DLSS or FSR integrations and hardware ray tracing are not claimed as finished; check the roadmap for status and limitations.
Why welcome AI-assisted contributions?
AI coding agents can help contributors understand unfamiliar code, implement focused changes, add tests, improve documentation, and investigate performance. Kvas provides contribution instructions and a pre-commit workflow that checks the workspace, tests, coverage, and doctests.
Please review AI-generated changes before submitting them. Pull requests should explain what changed and how it was verified. Performance claims should include benchmark evidence.
Where help would make a difference
The roadmap includes work on:
- Profiling and optimizing script execution, ECS queries, rendering, and asset loading.
- Physics quality, fixed-step simulation, character controllers, and regression scenes.
- A more complete integrated code editor and better editor workflows.
- Audio, animation, and layered image-editing tools.
- Onboarding, tutorials, examples, and cross-platform validation.
You don’t need to take on a large feature. A focused bug fix, a reproducible issue report, a test, a guide, or a small performance investigation can all help.
Join in
Start with the README and contribution guide. Check open issues before starting larger changes. When reporting graphics problems, include your operating system, GPU and graphics backend, reproduction steps, and relevant logs.
If you’re interested in building a Rust game engine with contributions from both people and AI agents, explore Kvas on GitHub and share what you’d improve first.

Top comments (0)