Architecture & Distribution

TL;DR — most users only need Luna.

If you just want the UI Toolkit component library, install com.cupkekgames.luna from the Asset Store. Done. Luna ships with its deps bundled as transitives — the foundation primitives plus data and graphs, which power Luna's catalog-keyed nav-graph navigation. The gameplay domain packages (rpgstats, inventory, gamesave, etc.) are still not required.

Gameplay domain sibling packages are only required by the GameFull sample (and by you, if you want to build a full game on top of the same systems Luna ships with). They're entirely optional.

This page documents the full CupkekGames ecosystem — 49 packages organized into three tiers (foundation primitives, direct foundation dependents, domain layer), the dep graph between them, and the editor windows that automate sibling-package installs.

Distribution at a glance

Luna's package.json > dependencies declares the foundation primitives it needs plus data and graphs (as of 2.3.2). The Asset Store listing bundles those alongside Luna, so installing Luna is a single one-package import.

Foundation primitives

Single-concern, (near-)leaf packages. These were extracted from the former core package. Three declare small internal deps: keyvaluedatabases → editorui, packagemanager → editorui, input → keyvaluedatabases (+ com.unity.inputsystem).

Direct foundation dependents

Domain layer

Luna-free packages: all foundation primitives, foundation dependents (prefabloaders, assetfinder, services), plus data, graphs, gamesave, scenemanagement. The rest depend on luna (directly or transitively — newtonsoft pulls it via addressableassets/settings).

Transitives note: because Luna depends on data and graphs, installing Luna also pulls their own deps — data brings assetfinder + services, and graphs sits on data + editorui. The whole chain ships bundled with the Asset Store package.

Distribution model

• Asset Store ships only com.cupkekgames.luna. Its deps (foundation primitives + data + graphs) are bundled alongside as transitive deps.
• CupkekGames UPM scoped registry at https://www.docs.cupkek.games/upm serves all 49 packages. Tarballs live in each repo's GitHub Releases under the Cupkek-Games GitHub org; the registry is a dynamic Next.js route handler that reads them at request time and returns npm-compatible packument JSON. Updates surface natively in Unity's Package Manager UI.

End-users don't manage manifest entries by hand. They use the editor window described below.

Package Manager window

Tools > CupkekGames > Package Manager — the dedicated editor window for the sibling-package install flow. Lives in com.cupkekgames.packagemanager (the bootstrap package — install it first via git URL or local file: path, then it writes the scoped registry into your Packages/manifest.json so the rest resolve via the registry).

• Compact one-line rows: status icon + display name + package id + tag chips + version (when installed) + Install button (when missing).
• Header toolbar: <installed>/<total> installed count badge + Refresh + Install GameFull Packages (N).
• One-click bulk install. Writes the CupkekGames scoped-registry block to your Packages/manifest.json (idempotent — checked first, only written if missing) then issues a single UnityEditor.PackageManager.Client.AddAndRemove for all package ids. Unity resolves the whole graph atomically — one manifest write, one domain reload.
• Last-error footer shows the reason if an install fails.
• Auto-opens once on first project load when any GameFull-tagged packages are missing (gated by EditorPrefs so it doesn't nag every reload).

The package list lives in com.cupkekgames.packagemanager/Editor/CupkekGamesPackageRegistry.cs (each entry has PackageId, DisplayName, Tags). The installer wraps Client.AddAndRemove + manifest-bootstrap in Editor/CupkekGamesPackageInstaller.cs.

LunaUI Panel

Tools > CupkekGames > LunaUI Panel — the per-sample setup helper. Distinct from the Package Manager window.

• Two-pane split: list of imported samples on the left, detail pane on the right.
• For Essentials sample: shows info about the reusable starter assets (theme, UXML primitives, sprites, audio, prefabs).
• For Showcase sample: shows info about the 9 component clusters, the flagship LunaShowcase scene, and the Essentials sample-import requirement (with a one-click Import Essentials Sample button if missing).
• For GameFull sample: shows a one-line CupkekGames-package summary with an Open Package Manager button (handing off to the Package Manager window for actual installs); Essentials sample import status with an Import Essentials Sample button if missing; Unity / external dep checks (Input System, Addressables, Localization, Newtonsoft, Ink); Add/Remove demo scenes for Build Settings; troubleshooting tips.
• Auto-opens when a sample is imported (uses Unity's [InitializeOnLoadMethod] + EditorPrefs to detect new imports across domain reloads).

Implementation: Editor/LunaUIWindow.cs.