Innovate As You Want. A plugin-oriented game engine written in C#.
InnoEngine combines shared mechanisms for assets, scenes, scripting and resource lifetimes with replaceable backends and explicit platform products. Game systems and Editor extensions use the same discovery and authoring infrastructure.
| Start here | Find |
|---|---|
| Get started | Host prerequisites, first Editor session and project workflow |
| Documentation | English task manuals, design explanations and API contracts |
| Architecture | Module responsibilities, dependency direction and ownership |
| Development | Building, validation, local documentation queries and platform extensions |
| Contributing | The shared development rules for humans and agents |
| Acceptance and limitations | Exact evidence scopes and outstanding checks |
APIs and project data evolve together during active development. Product support and device validation are separate; consult the linked acceptance records for the relevant commit and environment.
Apache License 2.0 applies to the engine source code. Bundled fonts retain their respective licenses. The Logo and derived icon font have a separate license permitting use only with InnoEngine.
After a human merge to master, the independent API workflow compares committed input membership and identities before starting SDK preparation or its Windows/macOS matrix. Matching trusted inputs produce NoRelevantChanges. Unknown relationships, new sources, imports and generator changes require actual project evaluation. Each owner/context reuses only matching immutable extraction payloads; the final package is always complete.
Identical API/XML/source-location facts do not change the Docs binding, merge branch ancestry, create a commit or push draft. Changed facts are imported atomically while preserving manual explanations. Engine functional, Native and product acceptance remain independent and unchanged.
Docs draft pushes and PRs into draft check affected pages and dependencies; they do not normally build the entire site. A human draft → main PR validates the complete merge candidate and creates one site artifact. After merge, main publishes that exact artifact when trusted publication inputs match; otherwise it validates once. See the Docs workflow guide.
