# Continuumatrice Essence symbols (CCG card catalogue) Continuumatrice uses **Essence** for card resources, not Magic: The Gathering mana. The canonical Essence symbol order is: ```text M S O G E A Q C B R L V T P N ``` These are **15 distinct symbols**. `N` is explicitly **colorless Essence**. The other 14 codes currently have **no names, canonical colors or game rules assigned in the client**. Do not infer them from the corresponding MTG letters. All Essence codes are uppercase. ## Native Continuumatrice XML v4 The parser supports arbitrary XML `` entries, so no change to the existing XML v4 schema format is needed. These three native property names are defined in `libcockatrice/card/game_specific_terms.h`: | Property | Meaning | | --- | --- | | `essencecost` | Card's explicitly authored Essence cost, e.g. `{M}{S}{N}` | | `essence` | Card's explicitly authored Essence identity/types, e.g. `MSN` | | `essencevalue` | Optional numeric aggregate value for existing cost-curve UI; this is not calculated from cost | **Test-only sample**, not a playable/canonical card: ```xml CTESTEssence Import Test Essence Sample Card Test Essence symbol rendering only. Test Card {M}{S}{N} MSN CTEST 1 ``` Do not automatically derive `essence` or `essencevalue` from `essencecost` until gameplay rules define the correct relationship. The card database **stores metadata**, not mutable match resource balances. Previously authored XML ``, ``, and `` properties remain readable by the inherited `CardInfo` API for compatibility, but new Continuumatrice cards should use the native properties. Format compatibility does **not** mean MTG `W` or `U` are accepted as Essence symbols. ## Icons and custom asset assignment All 15 Essence letters have small bundled SVG **placeholder** icons under: ```text cockatrice/resources/icons/essence/ M.svg S.svg O.svg G.svg E.svg A.svg Q.svg C.svg B.svg R.svg L.svg V.svg T.svg P.svg N.svg ``` Each is rendered using an independent `icons/essence/` asset namespace. In the currently selected Continuumatrice theme you may override any SVG with an SVG, PNG, JPG or JPEG using the same stem: ```text ~/.local/share/Continuumatrice/themes//icons/essence/ M.svg S.png N.svg ``` The current bundled placeholders show just the letter. `N` is neutral gray; the others use a shared neutral treatment. They are **not** final Essence artwork or a commitment to elemental color assignments. The chart interface uses a separately generated *chart-only* palette so fifteen statistical series can be distinguished. ## Features updated - Card database properties: native Essence cost, identity and optional value, with fallbacks for older XML. - Card information display and deck editor column headers: `Essence`, `Essence Cost`, `Essence Value`. - Cost parser: single Essence symbols in bare form (`MSN`) or braces (`{M}{S}{N}`); numeric tokens may be preserved as generic amounts. - Deck identity: unique, ordered Essence codes (including `N`). - Search filters: filter for specific Essence codes, or `colorless` meaning `N`. An empty identity is not automatically `N`. - Analytics: counts all 15 Essence cost symbols. Production counts only literal `Add {M}`-style grants to avoid guessing any resource rules. Hybrid, phyrexian, and other MTG-specific mana-cost syntax are **not** introduced as Essence mechanics. Nor is automatic calculation of resource costs, card affordability, or game turn rules included. ## Build and verification From `feature/continuumatrice-essence`: ```bash cmake -S . -B build --fresh -G Ninja -DCMAKE_BUILD_TYPE=Release \ -DWITH_CLIENT=ON -DWITH_SERVER=ON -DWITH_ORACLE=OFF -DTEST=ON cmake --build build --target continuumatrice continuum-servatrice essence_types_test --parallel 16 ctest --test-dir build -R EssenceTypesTest --output-on-failure ./build/continuumatrice/continuumatrice ``` Verify that all fifteen icons render, `N` loads and filters separately from `C`, the XML importer accepts `essencecost` and `essence`, and the analytics show no WUBRG assumptions. **Status:** Source-level implementation committed. User-side Qt compilation and visual/runtime testing remain required.