Skip to content
Community226

Brand Identity in Games

Any game featuring SOLMAMY branding inherits Brand Book’s color system, logo/mark policy, and general voice principles exactly as defined — see Brand Book — Color System, Logo & Mark, Voice & Tone. This chapter does not restate them; it states only what’s specific to presenting them inside a game. SOLMEME is a separate entity (see Brand Book — Terminology), not a form of SOLMAMY’s own branding.

  • The mascot (Sol Mamy) is the only visual mark available for in-game branding — no separate game-specific logo should be designed (Brand Book — Logo & Mark).
  • Core brand color (cyan/teal, per Brand Book — Color System) should anchor any in-game brand-facing UI (menus, loading screens, branded overlays). Real, measured hex values now exist (Pearl-white #E7E4E7, Cyan/Teal #12CFE4, Pink #E1599C), tagged Proposed, pending owner confirmation (Brand Book — Color System). A game may treat these as a real working direction, not yet as finally adopted Canonical values — the gap that remains is a quick confirmation step, not a from-scratch color question.
  • Whether/how the Vault Defender game concept (or any other game concept) should visually reference the Lunar Vault Module — this is a real, unaddressed cross-reference gap between the fictional game concept and the mascot’s own canonical prop, and is not resolved by this document.
  • Any game-specific typography, iconography, or UI-brand-language beyond the general rule above.
  • Final owner confirmation of the specific measured hex values above (Brand Book’s own open item, inherited here — see Brand Book — Color System).
  • Do not design a game-specific logo or mark as an alternative to the mascot.
  • Do not present the measured hex values above as finally adopted Canonical color before Brand Book’s own confirmation step closes — inherit the same Proposed status, not settled fact.

Part of the SOLMEME Brand Documentation System. Content status (Canonical/Proposed/Open/etc.) is this book’s own axis; ownership/rights are separate — see OWNERSHIP_AUTHORITY.md at the documentation system’s root.