Foundational Rules

Design Principles

These principles guide every decision in Abyssal Engine.

Build games, not demos

Morninghollow is the proving ground. Features are added when they solve real production problems in a real game.

Composition over inheritance

Actors stay light. Behavior is added through Components, Fragments, and services.

Documentation is architecture

Clear, maintained docs are part of the system, not an afterthought.

Public teaches, Internal builds

Public documentation helps users and AI. Internal records protect development history.

Cooperate, don't compete

Abyssal works alongside Unreal, Unity, Godot, and Blender. Native formats remain authoritative.

AI assists creativity

Tools like WingChat and WingsVoice augment human creators without replacing final decisions.

Practical Modularity

Generalize only after a real problem has taught the shape of the module. Small focused systems are preferred over large frameworks.

Core Law

Public documentation teaches the engine. Internal documentation builds the engine.

Related Reading