lwiz/BasicEventEngine
This system is a C++-based game engine framework that provides core subsystems for rendering, physics, networking, and input handling. It features a Python scripting interface that allows users to control engine components, manage resources, and define game logic through scripts. The engine supports a modular architecture with a unified filesystem, structured messaging, and a flexible UI framework, all built on a CMake build system with extensive unit testing coverage.
50.1
Adequate · 5 August 2026
840
lines of production code
Python
primary language
1
bus factor · 5 authors in all
1
measurements over time
How it got here
2015–2017 · Initial engine architecture and subsystems
This period established the foundational architecture of the game engine, transitioning the build system to CMake and restructuring the codebase into modular subsystems for rendering, physics, networking, and UI. The work focused on implementing core infrastructure, including a Python scripting interface, a structured messaging system, and comprehensive unit testing, while introducing key resource types and data handling utilities.
17 changes
2018–2020 · Python scripting integration
This period focused on integrating Python scripting support into the engine, exposing core systems such as rendering, physics, input, and resource management to Python scripts. The work included creating extensive bindings for game objects, UI components, and engine internals, alongside restructuring input handling and filesystem abstractions to support this new scripting layer.
13 changes
Survey your own repository
lwiz/BasicEventEngine was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 5 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit e99ba3f5a8 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.