Pixel Engine

Architecture, conventions, and tools for building Unity games.

Getting Started

• Installation — add the package to your project
• Project Setup — scaffold folders, templates, interfaces
• First Module — create your first module

Conventions

Style & Formatting

• Naming | Formatting | Language Rules | Expression Bodies | Code Quality | File Structure | Comments

Patterns & Architecture

• Unity Patterns (Event-Driven) | Module Pattern | Script Templates | Architecture Interfaces

Systems

• Simulation / Presentation | Multiplayer Architecture

Reference

• Anti-Patterns | Project Conventions | Cheat Sheet

Tools

• Tools Overview — all Pixel Engine/ menu items
• Module Generator — generate modules from the editor

Principles

1. Event-driven, not polling — react to state changes via events, delegates, and callbacks. Never poll in Update() for something that can be an event.
2. Clarity over cleverness — code is read far more than it is written.
3. Consistency — follow the same patterns everywhere. When in doubt, match the surrounding code.
4. SOLID — single responsibility, open/closed, Liskov substitution, dependency inversion.

Unity Documentation References

• Event Functions | Execution Order | MonoBehaviour
• UnityEvent | ScriptableObject | Coroutines
• Awaitable | Custom Update Manager