TimeEngine

An Integrated Game Development Environment (IGDE) — eliminating multi-app workflow bloat by unifying engine runtime, asset design, code IDE, and profiling into one performant workspace.

---

📌 Overview

TimeEngine is a cross-platform Integrated Game Development Environment (IGDE) designed for 2D game development and deterministic simulation research.

💡 The IGDE Vision

Traditional game development forces creators to constantly context-switch between fragmented external software — digital art suites (Photoshop, Inkscape), external code IDEs, particle editors, and separate engine runtimes.

TimeEngine aims to eliminate this multi-app overhead by building an all-in-one, high-performance in-editor ecosystem where designers and programmers can author code, craft procedural 2D assets, profile memory/frame timings, and execute game logic inside a single native workspace.

Note

Development Status: The full IGDE multi-app replacement vision (in-engine vector/raster art creation) and deterministic time manipulation (snapshot rewind & time dilation) are core architectural goals currently under active development. See ROADMAP.md.

---

🖼️ Editor Showcase

---

🚀 Getting Started

Prerequisites

• C++20 Compliant Compiler (MSVC, GCC, or Clang)
• Git

Setup & Building from Source

1. Clone the repository:

   git clone --recursive https://github.com/1SHAMAY1/TimeEngine.git
   cd TimeEngine

2. Initialize Submodules (Required for all platforms):

   bash Scripts/SetupSubmodules.sh

3. Generate Workspace / Project Files:

   • Windows (MSVC): Scripts\Windows\MSVC\GenerateProjectFiles.bat
   • Windows (MinGW): Scripts\Windows\MinGW\GenerateProjectFiles.bat
   • Windows (Clang): Scripts\Windows\Clang\GenerateProjectFiles.bat
   • Linux: Scripts/Linux/GenerateProjectFiles.sh
   • macOS: Scripts/Mac/GenerateProjectFiles.sh

4. Build & Launch: Open the generated project solution/workspace or run the respective platform build script (e.g., Scripts/Windows/MSVC/BuildDebug.bat or Scripts/Linux/BuildDebug.sh). Launch TimeEditor executable to enter the workspace.

---

📚 Documentation & Developer Guides

• 🏛️ ARCHITECTURE.md — Core subsystems, ECS components, rendering backends, vendor wrappers, and MCP automation specs.
• 📄 ROADMAP.md — Feature milestones and time-manipulation architecture plans.
• 🤖 llms.txt / llms.md — LLM architecture summary, coding rules, vendor wrapping guidelines, and MCP server tools.
• 🤝 CONTRIBUTING.md — Guidelines for code style, submodules, and PR submissions.

---

📄 License

This project is licensed under the MIT License.