Karty design

Karty brings Go game code, authored levels and a shared runtime together. These pages explain the choices behind that structure and what they mean when you build a game.

• Why Karty? describes the workflow I want and the games it serves.
• Architecture explains the host, client and level, and how they work together.
• Build and preview follows a project from its first preview to a packaged game.
• Asset pipeline follows source files through a build to the running game.
• Packages explains how games share code, objects, materials and UI.
• Processor textures specifies generated level textures and their build-time bounds.
• Web delivery explains release updates, background downloads and offline play.

To start making something, choose a game guide. For the game API and authoring reference, read your project's .karty/docs/.