Design Documentation

Welcome to the LunyScript design documentation. This section covers the architecture, technical decisions, and implementation details.

Design & Vision

• Problem Statement - Why LunyScript exists and what problems it solves
• Vision - Long-term vision and desired outcomes
• Author - About the author and personal experience
• FAQ - Frequently asked questions

API Design

• Script Runner Singleton Pattern - Lazy-init singleton and lifecycle dispatcher architecture
• Coroutine & Timer Design - Timer, Coroutine, and throttling API design
• On vs When API Refactor - Semantic distinction between lifecycle and external events

📐 Architecture

A Diagram Says More Than a Thousand UMLs

LunyEngine is an engine-agnostic Developer SDK that opens engine ecosystems. We need to stop re-inventing gameplay wheels in every engine separately! ^{The native service adapters are (ultra-)thin API mappings.}

Technical Documentation

• Philosophy - API design philosophy and principles
• Engine Differences - How engines differ and how LunyScript unifies them
• Architecture - System architecture and layer structure
• Code Comparison - Side-by-side comparison: LunyScript vs traditional approaches
• Repository Structure - How LunyEngine/LunyScript are divided into repositories.
• Extending LunyScript API - How LunyScript API supports shareable extensions.

Design Risk Assessment

• Cross-Cutting Concerns - Architectural concerns requiring upfront design
• Cross-Engine Concerns - Feature requirements and portability risks

🔗 Quick Links

• ← Back to Home

---

AI Usage Info

^{AI-assisted development. AI usage is adheres to FOSS principles: → FOSS-compliant AI-Usage}