How toxocious/ephemeral works
Project type and purpose
• This is a C++-based game engine (“Core”) plus a desktop game editor (“Editor”), intended ultimately to form the foundation of a Pokémon MMO.
• It is not a web app or microservice, but a native desktop application with a modular, layered engine architecture.
File structure
• Top-level directories:
• Build scripts (Build.lua, Compile.sh, premake5.lua) and configuration (.clang-format, .gitignore).
• Libraries/ – various third-party dependencies (GLAD, GLFW, GLM, ImGui, spdlog, stb_image).
• Projects/Core/ – the engine code, split into Include/ (headers) and Source/ (implementation).
· Sub-folders in Core/Include: Core, Modules (Window, Renderer, Scene, ImGuiLayer, SceneCamera), Renderer (VAO/VBO/EBO, Shader, Texture, Viewport, GameScene, Camera, Grid), Util (FileSystem, Log, Math, OpenGL wrappers).
• Projects/Editor/ – the editor application, also split into Include/Gui/ and Source/Gui/, relying on Core modules.
• Docs/ and Changelogs/ hold governance and change-history documents.
README for additional insights
• Confirms the structure, lists Premake as the build generator, points to Docs/DEPENDENCIES.md for tech stack, and defines the project scope (hand-crafted engine + editor + future server).
• No existing network/server code in the tree yet—focus is on engine/editor.
Key points to capture
• Don’t merge subsystems: show each module separately.
• Layering: Build tools at top, application (Editor), engine layers, external systems (OS, GPU).
• Detail the dependencies between modules and libraries.