How malunwen/jce works
JCE is a cross-platform, data-driven game engine with a C++ editor that consumes the same engine code as shipped games. The main workflow is authoring project assets and scenes in the editor, configuring rendering and other systems, then running or building the project on the engine. The README also documents scripting-language bindings and a model-agnostic AI bridge. The graph uses documented architecture and capabilities; source excerpts are partial, so internal links not directly supported by them are omitted.
Main entry points: jce_runtime.h Game runtime · jce_editor_panels.cpp Editor panels · jce_engine.c Application loop · jce_editor.cpp Editor application
Components 16
Editor authoring
- Editor application
editor/src/core/jce_editor.cpp - Editor panels
editor/src/ui/jce_editor_panels.cpp - Asset authoring
editor/src/panels/jce_panel_assets.cpp - Render pipeline editor
editor/src/panels/jce_panel_render_pipeline.cpp
Project pipeline
- Project settings
editor/src/core/jce_editor_project_state.cpp - Build and cook
editor/src/core/jce_build_manager.cpp
Engine runtime
- Asset manager
engine/src/resource/jce_asset_manager.c - Application loop
engine/src/application/jce_engine.c - Scene systems
engine/include/jce/middleware/scene/jce_scene.h - Renderer
engine/src/renderer/jce_render_pipeline.c - Game runtime
engine/include/jce/application/jce_runtime.h
Language and AI
- Script bindings
scripting/c_abi/src/jce_script_api.gen.c - AI assistant panel
editor/src/panels/jce_panel_ai_assistant.cpp - LLM bridge
engine/include/jce/middleware/llm/jce_llm.h
Other components
- Developer
- Model provider
Connections 16
- Developer → Editor application: authors with
README.md - Editor application → Editor panels: presents
- Editor panels → Asset authoring: offers
- Developer → Project settings: configures
- Asset authoring → Asset manager: prepares assets
- Render pipeline editor → Renderer: configures
editor/src/panels/jce_panel_render_pipeline.cpp - Project settings → Build and cook: configures
- Build and cook → Game runtime: builds for
README.md - Game runtime → Application loop: runs on
README.md - Application loop → Renderer: orchestrates
engine/src/application/jce_engine.c - Application loop → Asset manager: delegates assets
engine/src/application/jce_engine.c - Game runtime → Scene systems: uses
- Game runtime → Script bindings: can use
README.md - Editor panels → AI assistant panel: offers
- AI assistant panel → LLM bridge: uses
README.md - LLM bridge → Model provider: invokes program
README.md