@indiegems/gem-web-sdk 14.0.1 → 14.0.2

package/docs/api/reference.json

@@ -2,7 +2,7 @@
   "schema_version": 2,
   "source": {
     "repo": "IndieGems/gem-web-sdk",
-    "version": "14.0.1"
+    "version": "14.0.2"
   },
   "entries": [
     {
@@ -5242,7 +5242,7 @@
           "group": "player",
           "signature": "interface PlayerBoost",
           "documented": true,
-          "summary": "The player's Boost — **for display only**.\n\nReached as `gem.player.boost`, and always present on a `gem.player`: when\nthe arcade has not said (an older arcade, a backend without boosts, a read\nthat has not landed), it reads as not boosted — `active: false`, no\nmultipliers — which is exactly what an unboosted player's reads as too.\n\n```js\nconst tickets = gem.player?.boost.multipliers.find((m) => m.currencySlug === 'ARCADE_TICKETS');\nif (tickets && tickets.multiplier > 1) showBadge(`${tickets.multiplier}x`);\n```\n\n⚠️ **Show it; never gate on it.** A \"2x\" badge on a reward screen is what\nthis is for. Content, difficulty, matchmaking, prices and power must be the\nsame for a boosted and an unboosted player: the value is advisory, may lag,\nand can be forged inside your own page. The platform applies the real\nmultiplier when it pays, whatever you render.",
+          "summary": "The player's Boost — **for display only**.\n\nReached as `gem.player.boost`, and always present on a `gem.player`: when\nthe arcade has not said (an older arcade, a backend without boosts, a read\nthat has not landed), it reads as not boosted — `active: false`, no\nmultipliers — which is exactly what an unboosted player's reads as too.\n\n```js\nconst coins = gem.player?.boost.multipliers.find((m) => m.currencySlug === 'ARCADE_TICKETS');\nif (coins && coins.multiplier > 1) showBadge(`${coins.multiplier}x`);\n```\n\n⚠️ **Show it; never gate on it.** A \"2x\" badge on a reward screen is what\nthis is for. Content, difficulty, matchmaking, prices and power must be the\nsame for a boosted and an unboosted player: the value is advisory, may lag,\nand can be forged inside your own page. The platform applies the real\nmultiplier when it pays, whatever you render.",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -6482,7 +6482,7 @@
           "group": "platform",
           "signature": "currencySlug: string",
           "documented": true,
-          "summary": "The platform currency's slug, as `gem.platform.currencies.get()` lists it —\n`GEMS` or `ARCADE_TICKETS`. It decides what flies — gems or tickets — and\nwhich of the player's totals the payout moves.",
+          "summary": "The platform currency's slug, as `gem.platform.currencies.get()` lists it —\n`GEMS` or `ARCADE_TICKETS`. It decides what flies — gems or coins — and\nwhich of the player's totals the payout moves.",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -6514,7 +6514,7 @@
           "group": "platform",
           "signature": "origin?: { x: number; y: number }",
           "documented": true,
-          "summary": "Where the flight starts, in CSS px of YOUR viewport: the centre of the\ncurrency's icon (or hero) your screen draws beside the reward — the gem\nfor Gems, the ticket for Tickets. Measure that element's own box, not a\nrow or panel around it. Leave it out and the Gem Arcade flies the payout\nfrom the middle of your frame once the platform confirms it.",
+          "summary": "Where the flight starts, in CSS px of YOUR viewport: the centre of the\ncurrency's icon (or hero) your screen draws beside the reward — the gem\nfor Gems, the coin for Coins. Measure that element's own box, not a\nrow or panel around it. Leave it out and the Gem Arcade flies the payout\nfrom the middle of your frame once the platform confirms it.",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -9556,7 +9556,7 @@
           "group": "player",
           "signature": "readonly boost: PlayerBoost",
           "documented": true,
-          "summary": "The player's Boost — how much faster they earn Gems and Tickets right now,\nand for how many more days. **For display only.**\n\nAlways present: when the arcade has not said, it reads as not boosted\n(`active: false`, no multipliers).\n\n```js\nconst gems = gem.player?.boost.multipliers.find((m) => m.currencySlug === 'GEMS');\nif (gems && gems.multiplier > 1) rewardScreen.showBadge(`${gems.multiplier}x Gems`);\n```\n\n⚠️ **Show it; never gate on it** — no content, difficulty, matchmaking,\nprice or power may depend on it. It is advisory, may lag, and can be\nforged inside your own page; the platform applies the real multiplier\nwhen it pays. See [PlayerBoost](api-reference-game.md#playerboost).",
+          "summary": "The player's Boost — how much faster they earn Gems and Coins right now,\nand for how many more days. **For display only.**\n\nAlways present: when the arcade has not said, it reads as not boosted\n(`active: false`, no multipliers).\n\n```js\nconst gems = gem.player?.boost.multipliers.find((m) => m.currencySlug === 'GEMS');\nif (gems && gems.multiplier > 1) rewardScreen.showBadge(`${gems.multiplier}x Gems`);\n```\n\n⚠️ **Show it; never gate on it** — no content, difficulty, matchmaking,\nprice or power may depend on it. It is advisory, may lag, and can be\nforged inside your own page; the platform applies the real multiplier\nwhen it pays. See [PlayerBoost](api-reference-game.md#playerboost).",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -10429,7 +10429,7 @@
           "group": "platform",
           "signature": "readonly only?: readonly string[]",
           "documented": true,
-          "summary": "While shown, show ONLY these: platform currency slugs as\n`gem.platform.currencies.get()` lists them (`GEMS`, `ARCADE_TICKETS`),\nmatched exactly, and the literal `'score'` for the achievement score. Only\nfor a screen about one currency, such as a ticket store; leave it out and\nevery wallet shows, which is always safe. The Gem Arcade draws no wallet\nover a game, so it has nothing to narrow and ignores it.",
+          "summary": "While shown, show ONLY these: platform currency slugs as\n`gem.platform.currencies.get()` lists them (`GEMS`, `ARCADE_TICKETS`),\nmatched exactly, and the literal `'score'` for the achievement score. Only\nfor a screen about one currency, such as a Coins store; leave it out and\nevery wallet shows, which is always safe. The Gem Arcade draws no wallet\nover a game, so it has nothing to narrow and ignores it.",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -11161,7 +11161,7 @@
           "group": "start",
           "signature": "readonly platform: PlatformApi",
           "documented": true,
-          "summary": "The player's standing in PLATFORM currencies (Gems, Tickets): their\nbalances, `gem.platform.currencies.get()`, and how much more this game can\ngrant them, `gem.platform.earnAllowance.get()` (display only).\n\nA player surface only. In a context with no player — a game server — the\nplatform refuses the read.",
+          "summary": "The player's standing in PLATFORM currencies (Gems, Coins): their\nbalances, `gem.platform.currencies.get()`, and how much more this game can\ngrant them, `gem.platform.earnAllowance.get()` (display only).\n\nA player surface only. In a context with no player — a game server — the\nplatform refuses the read.",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -11365,7 +11365,7 @@
           "group": "start",
           "signature": "cueReward(cue: RewardCue): boolean",
           "documented": true,
-          "summary": "Tell the arcade a platform-currency reward is on its way, so it **shows it\nlanding**: in the Gem Arcade the currency flies from `origin` into the Gem\nbutton, wherever on your frame it sits, which pops as each mark lands, and\nthe player's total moves once the platform confirms the grant. The Gem\nArcade draws no wallet over your game: the player sees their Gems and\nTickets in the Gem menu. A payout you do not cue still flies, from the\nmiddle of your frame, so cue the ones the player earns on screen.\n\nCall it the moment your game decides to award — when your server has moved\n(or is about to move) the progression mapped onto a platform currency —\nand pass the centre of that currency's icon (or hero) on your screen, so\nthe flight starts from the mark the player is looking at:\n\n```js\nconst { x, y, width, height } = rewardGem.getBoundingClientRect(); // the gem's own box\ngem.cueReward({\n  currencySlug: 'GEMS', // or 'ARCADE_TICKETS', from the ticket\n  expected: 15,\n  origin: { x: x + width / 2, y: y + height / 2 },\n});\n```\n\n**This is the platform-currency animation, and the only one.** The display\nof every platform currency — Gems and Tickets alike — belongs to the\narcade: a game draws no flight or celebration of its own for one and keeps\nno counter of one. **If this returns `false`, do nothing** — there is no\nfallback celebration.\n\n**The arcade never takes your word for the amount.** What lands, and the\nplayer's new total, come from the platform itself; `expected` is drawn as\nprovisional, and a cue the platform never confirms fades on its own — a\ngrant clamped to zero, say, or one the receipt reports `suppressed`. So\nthe cue can only ever make the wallet move for a reward that really\nlanded — which it does on every channel, dev and test included.",
+          "summary": "Tell the arcade a platform-currency reward is on its way, so it **shows it\nlanding**: in the Gem Arcade the currency flies from `origin` into the Gem\nbutton, wherever on your frame it sits, which pops as each mark lands, and\nthe player's total moves once the platform confirms the grant. The Gem\nArcade draws no wallet over your game: the player sees their Gems and\nCoins in the Gem menu. A payout you do not cue still flies, from the\nmiddle of your frame, so cue the ones the player earns on screen.\n\nCall it the moment your game decides to award — when your server has moved\n(or is about to move) the progression mapped onto a platform currency —\nand pass the centre of that currency's icon (or hero) on your screen, so\nthe flight starts from the mark the player is looking at:\n\n```js\nconst { x, y, width, height } = rewardGem.getBoundingClientRect(); // the gem's own box\ngem.cueReward({\n  currencySlug: 'GEMS', // or 'ARCADE_TICKETS', from the coin\n  expected: 15,\n  origin: { x: x + width / 2, y: y + height / 2 },\n});\n```\n\n**This is the platform-currency animation, and the only one.** The display\nof every platform currency — Gems and Coins alike — belongs to the\narcade: a game draws no flight or celebration of its own for one and keeps\nno counter of one. **If this returns `false`, do nothing** — there is no\nfallback celebration.\n\n**The arcade never takes your word for the amount.** What lands, and the\nplayer's new total, come from the platform itself; `expected` is drawn as\nprovisional, and a cue the platform never confirms fades on its own — a\ngrant clamped to zero, say, or one the receipt reports `suppressed`. So\nthe cue can only ever make the wallet move for a reward that really\nlanded — which it does on every channel, dev and test included.",
           "deprecated": null,
           "params": [
             {
@@ -11388,7 +11388,7 @@
           "group": "start",
           "signature": "setWalletVisible(visible: boolean, options?: WalletVisibleOptions): boolean",
           "documented": true,
-          "summary": "Show or hide the player's wallets — Gems, Tickets, the achievement score —\nthat an embedder draws over your game.\n\n**The Gem Arcade draws no wallet over a game** (since 2026-10-11): the\nplayer sees their balances in the Gem menu, and payouts fly into the Gem\nbutton. So under the Gem Arcade this changes nothing on screen — it is\naccepted and harmless, and a game that already calls it keeps working.\nCall it for an embedder that does draw wallets over your game: hide them\nwhile you play, show them on your menus.\n\n```js\nlevel.onStart = () => gem.setWalletVisible(false);\nmenu.onOpen = () => gem.setWalletVisible(true);\n```\n\n**It is screen state, not a toggle.** Each call is the whole answer and\nreplaces the last. Where an embedder draws wallets, shown ones arrive as\nrectangles in `gem.viewport.reserved` and hiding them gives that space\nback; the Gem Arcade sends none for wallets. `only` narrows what shows,\nwhere an embedder honours it; the Gem Arcade does not.\n\n**Never draw a platform balance yourself**, and never show a pending state\nfor one: the arcade takes every figure from the platform. If this returns\n`false`, do nothing in its place.",
+          "summary": "Show or hide the player's wallets — Gems, Coins, the achievement score —\nthat an embedder draws over your game.\n\n**The Gem Arcade draws no wallet over a game** (since 2026-10-11): the\nplayer sees their balances in the Gem menu, and payouts fly into the Gem\nbutton. So under the Gem Arcade this changes nothing on screen — it is\naccepted and harmless, and a game that already calls it keeps working.\nCall it for an embedder that does draw wallets over your game: hide them\nwhile you play, show them on your menus.\n\n```js\nlevel.onStart = () => gem.setWalletVisible(false);\nmenu.onOpen = () => gem.setWalletVisible(true);\n```\n\n**It is screen state, not a toggle.** Each call is the whole answer and\nreplaces the last. Where an embedder draws wallets, shown ones arrive as\nrectangles in `gem.viewport.reserved` and hiding them gives that space\nback; the Gem Arcade sends none for wallets. `only` narrows what shows,\nwhere an embedder honours it; the Gem Arcade does not.\n\n**Never draw a platform balance yourself**, and never show a pending state\nfor one: the arcade takes every figure from the platform. If this returns\n`false`, do nothing in its place.",
           "deprecated": null,
           "params": [
             {
@@ -13795,7 +13795,7 @@
           "group": "platform",
           "signature": "readonly balance: number",
           "documented": true,
-          "summary": "The player's exact balance, as of this read.\n\nA snapshot: the player can earn or spend this currency elsewhere at any\nmoment, so it is a figure to compare a price against, never a promise that\na purchase will go through. The platform re-checks at spend time.\n\n**Do not draw it as a counter.** Platform-currency display belongs to the\narcade: its wallet is the one place a player's Gems or Tickets total is\nshown, and a game keeps no balance of either on screen.",
+          "summary": "The player's exact balance, as of this read.\n\nA snapshot: the player can earn or spend this currency elsewhere at any\nmoment, so it is a figure to compare a price against, never a promise that\na purchase will go through. The platform re-checks at spend time.\n\n**Do not draw it as a counter.** Platform-currency display belongs to the\narcade: its wallet is the one place a player's Gems or Coins total is\nshown, and a game keeps no balance of either on screen.",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -13875,7 +13875,7 @@
           "group": "platform",
           "signature": "get(options?: PlatformCurrencyReadOptions): Promise<readonly PlatformCurrency[]>",
           "documented": true,
-          "summary": "Read the player's balance of every active platform currency.\n\n```js\nconst gems = (await gem.platform.currencies.get()).find((c) => c.slug === 'GEMS');\nbuyButton.disabled = !gems || gems.balance < price;\n```\n\nUse it to decide whether the player can afford a price. Do not show it as\na Gems or Tickets total: the arcade's wallet already does, and is the only\nplace one is shown.\n\nIt is a snapshot, and a balance can change while your game is paused. If\nyou keep anything worked out from it — a greyed-out Buy button — read it\nagain on every `onPause(false)`; nothing tells your game that it changed.",
+          "summary": "Read the player's balance of every active platform currency.\n\n```js\nconst gems = (await gem.platform.currencies.get()).find((c) => c.slug === 'GEMS');\nbuyButton.disabled = !gems || gems.balance < price;\n```\n\nUse it to decide whether the player can afford a price. Do not show it as\na Gems or Coins total: the arcade's wallet already does, and is the only\nplace one is shown.\n\nIt is a snapshot, and a balance can change while your game is paused. If\nyou keep anything worked out from it — a greyed-out Buy button — read it\nagain on every `onPause(false)`; nothing tells your game that it changed.",
           "deprecated": null,
           "params": [
             {
@@ -35056,7 +35056,7 @@
           "group": "platform",
           "signature": "readonly balance: number",
           "documented": true,
-          "summary": "The player's exact balance, as of this read.\n\nA snapshot: the player can earn or spend this currency elsewhere at any\nmoment, so it is a figure to compare a price against, never a promise that\na purchase will go through. The platform re-checks at spend time.\n\n**Do not draw it as a counter.** Platform-currency display belongs to the\narcade: its wallet is the one place a player's Gems or Tickets total is\nshown, and a game keeps no balance of either on screen.",
+          "summary": "The player's exact balance, as of this read.\n\nA snapshot: the player can earn or spend this currency elsewhere at any\nmoment, so it is a figure to compare a price against, never a promise that\na purchase will go through. The platform re-checks at spend time.\n\n**Do not draw it as a counter.** Platform-currency display belongs to the\narcade: its wallet is the one place a player's Gems or Coins total is\nshown, and a game keeps no balance of either on screen.",
           "deprecated": null,
           "params": [],
           "returns": null,
@@ -35136,7 +35136,7 @@
           "group": "platform",
           "signature": "get(options?: PlatformCurrencyReadOptions): Promise<readonly PlatformCurrency[]>",
           "documented": true,
-          "summary": "Read the player's balance of every active platform currency.\n\n```js\nconst gems = (await gem.platform.currencies.get()).find((c) => c.slug === 'GEMS');\nbuyButton.disabled = !gems || gems.balance < price;\n```\n\nUse it to decide whether the player can afford a price. Do not show it as\na Gems or Tickets total: the arcade's wallet already does, and is the only\nplace one is shown.\n\nIt is a snapshot, and a balance can change while your game is paused. If\nyou keep anything worked out from it — a greyed-out Buy button — read it\nagain on every `onPause(false)`; nothing tells your game that it changed.",
+          "summary": "Read the player's balance of every active platform currency.\n\n```js\nconst gems = (await gem.platform.currencies.get()).find((c) => c.slug === 'GEMS');\nbuyButton.disabled = !gems || gems.balance < price;\n```\n\nUse it to decide whether the player can afford a price. Do not show it as\na Gems or Coins total: the arcade's wallet already does, and is the only\nplace one is shown.\n\nIt is a snapshot, and a balance can change while your game is paused. If\nyou keep anything worked out from it — a greyed-out Buy button — read it\nagain on every `onPause(false)`; nothing tells your game that it changed.",
           "deprecated": null,
           "params": [
             {

package/docs/arcade-avatars.md

@@ -274,7 +274,7 @@ renders the item, and the command waits until it is `ready`.
 
 ## 5. Sell it
 
-An avatar is for sale only when you put it on sale, priced in Tickets, Gems or both:
+An avatar is for sale only when you put it on sale, priced in Coins, Gems or both:
 
 ```sh
 gemctl item sell red-knight --tickets 50 --gems 300
@@ -329,7 +329,7 @@ const offers = await gem.avatars3d.offers(); // what is on sale, priced by the p
 for (const offer of offers) {
   const tile = shop.addTile(offer.displayName, platformIconUrl(offer.iconUrl));
   for (const { currencySlug, price } of offer.prices) {
-    tile.addButton(`${price} ${currencySlug === 'GEMS' ? 'Gems' : 'Tickets'}`, async () => {
+    tile.addButton(`${price} ${currencySlug === 'GEMS' ? 'Gems' : 'Coins'}`, async () => {
       const result = await gem.avatars3d.purchase({ itemId: offer.itemId, currencySlug });
       if (result.outcome === 'declined' && result.reason === 'already_owned') {
         gem.openAvatarPicker({ tab: '3d' }); // they have it: let them put it on
@@ -370,7 +370,7 @@ up, or under an Arcade that does not sell 3D avatars, it resolves `unavailable`
 platform with your game's token, so a shop can show what is on sale.
 
 **Purchases are real on every channel.** On `dev` and `test` a purchase spends the player's real
-Gems or Tickets and grants a real avatar they keep, exactly as on `release`. Test with your
+Gems or Coins and grants a real avatar they keep, exactly as on `release`. Test with your
 organization's test accounts.
 
 ## 7. Read the worn avatar, and load it at runtime

package/docs/arcade-economy.md

@@ -1,9 +1,9 @@
-# Gems, Tickets and Achievement Points
+# Gems, Coins and Achievement Points
 
 The arcade runs three things across every game, and a player should be able to tell them apart at
 a glance:
 
-> **Gems = progress. Tickets = cosmetics. Achievement Points = prestige.**
+> **Gems = progress. Coins = cosmetics. Achievement Points = prestige.**
 
 You do not have to use any of them. A game with no platform currency and no achievements is a
 complete game, and the currencies your core loop runs on — gold, XP, energy, materials, cards — are
@@ -14,7 +14,7 @@ most of them are enforced at upload, so a design that ignores them is refused ra
 
 ## 1. The three, side by side
 
-|                    | **Gems** (`GEMS`)                                      | **Tickets** (`ARCADE_TICKETS`)                  | **Achievement Points**                                    |
+|                    | **Gems** (`GEMS`)                                      | **Coins** (`ARCADE_TICKETS`)                  | **Achievement Points**                                    |
 | ------------------ | ------------------------------------------------------ | ----------------------------------------------- | --------------------------------------------------------- |
 | What it is         | the arcade's progression currency                      | the arcade's cosmetics currency                 | permanent prestige: the **Achievement Score**             |
 | Which games pay it | any game with a server or a serverless function        | any game with a server or a serverless function | an achievement, from any game with a server or a function |
@@ -23,7 +23,7 @@ most of them are enforced at upload, so a design that ignores them is refused ra
 | A Boost raises it  | yes — the grants and the caps                          | yes — the grants and the caps                   | never                                                     |
 
 A player earns Gems across the arcade's games and spends them on progress anywhere: upgrades, unlocks,
-extra attempts, resources, characters, cards. A player earns Tickets by playing almost anything and
+extra attempts, resources, characters, cards. A player earns Arcade Coins by playing almost anything and
 spends them on how they look: skins, outfits, visual effects, decorations, emotes, profile
 cosmetics. Achievement points are what a player has done, summed across every game into the
 Achievement Score; they are never bought, boosted or spent, and nothing takes them away except the
@@ -41,15 +41,15 @@ platform-wide currency of your own:
 | If your design has…                                                                       | Use                                                       |
 | ----------------------------------------------------------------------------------------- | --------------------------------------------------------- |
 | a premium or meta currency that speeds up or unlocks progress                             | **Gems**: price that progress in `GEMS`                   |
-| a cosmetics currency, or a shop of skins                                                  | **Tickets**: price the cosmetics in `ARCADE_TICKETS`      |
+| a cosmetics currency, or a shop of skins                                                  | **Coins**: price the cosmetics in `ARCADE_TICKETS`      |
 | a trophy count, a mastery rank or a completion percentage that says "this player is good" | **achievements**, whose points join the Achievement Score |
 
-⚠️ **Do not build a second Gems or a second Tickets.** A game-local premium or cosmetic
+⚠️ **Do not build a second Gems or a second Coins.** A game-local premium or cosmetic
 meta-currency — "Crystals" that buy your upgrades, "Shards" that buy your skins, earned and hoarded
 the way a player would earn and hoard the arcade's — competes with the arcade's own, splits the
 player between two wallets that mean the same thing, and sidesteps every rule on this page: the Gem
 Source approval, the cosmetics-only line and the platform's caps. The release review checks for one.
-A currency that is part of play is fine: coins picked up in a level and spent in that run's shop,
+A currency that is part of play is fine: gold picked up in a level and spent in that run's shop,
 energy that paces a session, materials a crafting tree consumes.
 
 ## 3. Which kind of game is yours
@@ -64,7 +64,7 @@ There are four shapes:
 | **No-Gem**     | no          | no             | a game that stays out of Gems entirely                                                  |
 
 The shapes describe what a game does, not what it may do: a Gem Source that starts pricing its own
-progress in Gems is Balanced. Every shape may pay Tickets, price its cosmetics in Tickets and carry
+progress in Gems is Balanced. Every shape may pay Coins, price its cosmetics in Coins and carry
 achievements. **Gems can be your game's soft currency** — award them for play and price your
 progression in them.
 
@@ -85,7 +85,7 @@ What may move it:
 - **Your game server** — a platform-allocated dedicated server, through the progression add and max
   routes.
 - **Your serverless function**, called by the player it pays, on a progression that sets
-  `function_may_grant: true`. It may pay Gems and Tickets and unlock achievements for **that player
+  `function_may_grant: true`. It may pay Gems and Coins and unlock achievements for **that player
   only**, and never for a guest. A function a player calls may also change only that player's own
   state — any write it aims at another player is refused. Opting in makes the function's own checks
   the only thing deciding a reward was earned, so read
@@ -97,7 +97,7 @@ So a browser-only game with neither a server nor a function pays nothing platfor
 rule read strictly, not a gap: a browser credential is public, and anything it could pay, a modified
 client could pay itself.
 
-**How much to pay: about 500 Tickets an hour.** A game pays about **500 Tickets per hour of ordinary
+**How much to pay: about 500 Coins an hour.** A game pays about **500 Coins per hour of ordinary
 play**, unboosted, averaged over a typical session of its repeatable loop — runs, levels, matches,
 to-dos. A one-time prize, such as finishing the tutorial or a first-time milestone, comes on top and
 stays modest. Work the rate out from what each firing pays and how often a player fires it, and keep
@@ -122,29 +122,29 @@ currency may price is a platform setting on that currency, its **spend scope**:
 
 - **Gems — `any`.** Price progress in `GEMS`: an extra life, an upgrade, a character, a pack of
   cards, another attempt.
-- **Tickets — `cosmetic_only`.** A Tickets price is accepted only on an item your config declares
-  `category: cosmetic`, or on a recipe that grants cosmetic items and nothing else. A Tickets price
+- **Coins — `cosmetic_only`.** A Coins price is accepted only on an item your config declares
+  `category: cosmetic`, or on a recipe that grants cosmetic items and nothing else. A Coins price
   on anything that grants a currency, moves a progression, grants a non-cosmetic item, opens into
   other items (a bundle or a loot box) or rolls a loot table is refused at upload — a loot table
   even when every entry in it is cosmetic.
 
-So a Tickets price on an item is always the pair `currency: ARCADE_TICKETS` and
+So a Coins price on an item is always the pair `currency: ARCADE_TICKETS` and
 `category: cosmetic`; on a recipe, every item it grants declares `category: cosmetic`.
 
-**How much to charge: 500 Tickets is worth about $1.** Price a Tickets cosmetic at what it would be
-worth in dollars, times 500: a $1 emote is 500 Tickets, a $3 outfit 1,500, a $10 skin 5,000. At the
+**How much to charge: 500 Coins is worth about $1.** Price a Coins cosmetic at what it would be
+worth in dollars, times 500: a $1 emote is 500 Coins, a $3 outfit 1,500, a $10 skin 5,000. At the
 earn rate in [§4](#4-earning-needs-server-authority), that is about an hour of play for each dollar.
-Tickets are never sold for money, so the dollar is your yardstick only: never show a dollar figure
-beside a Tickets price. The release review lists every Tickets price with its dollar value and hours
-of play, and a price under 100 or over 10,000 Tickets blocks release unless the creator has approved
+Coins are never sold for money, so the dollar is your yardstick only: never show a dollar figure
+beside a Coins price. The release review lists every Coins price with its dollar value and hours
+of play, and a price under 100 or over 10,000 Coins blocks release unless the creator has approved
 it for that game.
 
 **`category` defaults to `progression`**, so an item is a cosmetic only because you said so. The
 platform takes that at your word and the release review checks it: an item that changes what a
-player can do, labelled `cosmetic` so it can sell for Tickets, breaks platform policy.
+player can do, labelled `cosmetic` so it can sell for Coins, breaks platform policy.
 
 **A cosmetic can still wait for progress.** "Reach level 10 to unlock the dragon skin" is a recipe
-with a prerequisite and a Tickets price, and the platform refuses a locked player with
+with a prerequisite and a Coins price, and the platform refuses a locked player with
 `recipe_locked` before it takes anything ([game-economy-tutorial.md](game-economy-tutorial.md)).
 
 **Take the scope from the refusal, not from this page.** The platform owns each currency's scope and
@@ -152,10 +152,10 @@ can change it. A refusal names the scope that applied, and `gemctl platform conf
 currencies your game may price in at all. A scope changed after you published stops the prices it
 no longer admits: the purchase is refused and the price leaves the catalog, with nothing charged.
 
-**The arcade sells cosmetics of its own for Tickets, and never sells prestige.** Besides your game's
-shop, the arcade has a Tickets shop of its own profile cosmetics. Every arcade item is either a
-**shop** item — a cosmetic priced in Tickets — or **earned**: a default, a free claim, an achievement
-or Achievement Score reward. An earned item can never be given a price, in Tickets, Gems or anything
+**The arcade sells cosmetics of its own for Coins, and never sells prestige.** Besides your game's
+shop, the arcade has a Coins shop of its own profile cosmetics. Every arcade item is either a
+**shop** item — a cosmetic priced in Coins — or **earned**: a default, a free claim, an achievement
+or Achievement Score reward. An earned item can never be given a price, in Coins, Gems or anything
 else, so what a player shows off for what they did cannot be bought.
 
 ## 6. Every number is the platform's, and it moves
@@ -195,14 +195,14 @@ player got.
 
 ## 7. What a player buys with money: Gems and Boosts
 
-Nothing sells Tickets or achievement points, alone or in a bundle. The arcade's own store sells
+Nothing sells Coins or achievement points, alone or in a bundle. The arcade's own store sells
 Gems, and the Gems a player bought there spend in your game exactly as the ones they earned do: your
 game cannot tell the two apart and prices nothing differently for either. Your game sells neither,
 and never sends a player to the store. The real-money
 product that changes what your game pays is a **Boost**, which a player buys from the arcade, never
 from your game:
 
-- **It multiplies what Gems and Tickets grants pay, and the ceilings with them.** A player on a 2×
+- **It multiplies what Gems and Coins grants pay, and the ceilings with them.** A player on a 2×
   Boost earns twice as much per grant, may earn twice as much per window and per day, and may hold
   more. When it ends, what they earned stays theirs.
 - **It never touches achievement points.** An unlock credits the same points for every player.
@@ -211,7 +211,7 @@ from your game:
 - **None is on sale yet.** The first Boost, `booster_x2_30d`, is inactive until the arcade launches
   it, so today every player earns at the unboosted rate. Design for both.
 
-⚠️ **Show a Boost; never gate on one.** Your game may tell a player they are boosted — "2× Tickets"
+⚠️ **Show a Boost; never gate on one.** Your game may tell a player they are boosted — "2× Coins"
 beside a reward, from `gem.player.boost`
 ([what-a-game-must-do.md](what-a-game-must-do.md#the-signed-in-players-boost-show-it-never-gate-on-it))
 — and must never make content, difficulty, power, access, prices, matchmaking or odds depend on
@@ -222,7 +222,7 @@ rule is [platform-rules.md](platform-rules.md#8-a-players-boost-is-for-display-n
 ## 8. The arcade owns the display of every platform currency
 
 The arcade draws the player's platform currencies in its own chrome while your game runs, and
-animates every payout into the right total. Gems and Tickets follow the same rules:
+animates every payout into the right total. Gems and Coins follow the same rules:
 
 - **No counter.** Keep no balance, running total or wallet of a platform currency on any screen of
   yours. Read `gem.platform.currencies.get()` to decide whether a price is affordable, never to draw
@@ -230,17 +230,17 @@ animates every payout into the right total. Gems and Tickets follow the same rul
   `onPause(false)` if you keep anything worked out from it, such as a greyed-out Buy button.
 - **No celebration of your own.** At a payout, cue the arcade's wallet with `gem.cueReward`, naming
   the currency that paid — `currencySlug: 'GEMS'` from the gem on your reward screen,
-  `'ARCADE_TICKETS'` from the ticket. If it returns `false`, do nothing
+  `'ARCADE_TICKETS'` from the coin. If it returns `false`, do nothing
   ([inventory-and-catalogs.md](inventory-and-catalogs.md#showing-the-reward-land-in-the-arcades-wallet)).
 - **No "daily max" of your own making.** Your game cannot see what every other game paid the player,
   and must not compute a maximum. To show how much more your game can pay, read
   `gem.platform.earnAllowance.get()` (one consolidated figure, display only); the arcade still tells
   the player when they reach the maximum.
-- **No top-up or payment screen of your own.** Never draw a "get more Gems" or "buy Tickets" offer,
+- **No top-up or payment screen of your own.** Never draw a "get more Gems" or "buy Coins" offer,
   a checkout, a wallet top-up, or anything shaped like the arcade's purchase sheet: a game screen
   that looks like platform payment chrome is an imitation of it, and players cannot tell the two
   apart. Your shop's own Buy button is yours. When a purchase is refused for
-  `insufficient_funds`, say so in your shop's own words ("Not enough Tickets") and stop there.
+  `insufficient_funds`, say so in your shop's own words ("Not enough Coins") and stop there.
 - **No amount at all when you are not connected to the arcade.** Hide every platform price and
   reward unless `gem.awaitBridge()` settled `connected`.
 - **Draw a currency with the art the SDK ships**: the icon beside an amount, the hero only on a
@@ -251,11 +251,12 @@ never computes the score, restates it, or turns it into a currency of its own.
 
 ## 9. What the arcade does not have
 
-- **No Stars, Coins, Tokens or Supporter Seals.** All four are retired. None of them can be
+- **No Stars, Tokens or Supporter Seals, and not the old `COINS` currency** (retired; not today's
+  Coins, `ARCADE_TICKETS`). All four are retired. None of them can be
   granted, priced in or bought: a config naming one is refused at upload, and a mapping onto one
   that is still live reads `suppressed`. The Achievement Score is the arcade's measure of prestige.
-- **No Gems or Tickets for money from a game**, alone or in a bundle. Only the arcade's own store
-  sells Gems, and nothing sells Tickets.
+- **No Gems or Coins for money from a game**, alone or in a bundle. Only the arcade's own store
+  sells Gems, and nothing sells Coins.
 - **No achievement points or earned items for anything a player pays for.**
 - **No content behind a Boost.** A Boost is shown, never checked.
 
@@ -265,7 +266,7 @@ never computes the score, restates it, or turns it into a currency of its own.
 | ---------------------------------------------------------- | --------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
 | a mapping refused, naming the currencies your game may pay | the platform does not let your game grant that currency         | target one it lists — `gemctl platform config` has the current set                           |
 | a receipt `suppressed`, reason `not_allowlisted…`          | the platform stopped letting your game grant that currency      | target a currency `gemctl platform config` lists; paid balances stay                         |
-| a price refused, naming the spend scope `cosmetic_only`    | a Tickets price on something that is not a cosmetic             | price it in `GEMS`, or mark the item `category: cosmetic` if it changes only looks           |
+| a price refused, naming the spend scope `cosmetic_only`    | a Coins price on something that is not a cosmetic             | price it in `GEMS`, or mark the item `category: cosmetic` if it changes only looks           |
 | a receipt `suppressed`, reason `functions_not_opted_in`    | your function wrote a paying progression that has not opted in  | read [serverless-functions.md](serverless-functions.md), then set `function_may_grant: true` |
 | a receipt `suppressed`, reason `function_gems_not_enabled` | an older receipt, from before functions could pay Gems          | nothing — a function pays Gems now, so its next firing pays                                  |
 | `403 function_foreign_entity_write`                        | a function a player called wrote another player                 | take the player from the call's context, never its input                                     |
@@ -277,7 +278,7 @@ never computes the score, restates it, or turns it into a currency of its own.
 - [`inventory-and-catalogs.md`](inventory-and-catalogs.md) — platform grants (§13) and selling for a
   platform currency (§16), in full.
 - [`game-economy-tutorial.md`](game-economy-tutorial.md) — a shop, step by step, including a
-  cosmetic sold for Tickets.
+  cosmetic sold for Coins.
 - [`daily-challenges.md`](daily-challenges.md) — the commonest thing that pays a platform currency.
 - [`achievements.md`](achievements.md) — achievements, their points and the Achievement Score.
 - [`serverless-functions.md`](serverless-functions.md) — paying a player from a game with no

package/docs/brand-art.md

@@ -1,20 +1,21 @@
-# The Gems, Tickets and trophy art
+# The Gems, Coins and trophy art
 
-The SDK ships the platform's own art for its two currencies, **Gems** and **Tickets**, and for
-**trophies**. You need it only if your game draws Gems, Tickets or a trophy on its own screens. Read
+The SDK ships the platform's own art for its two currencies, **Gems** and **Coins**, and for
+**trophies**. You need it only if your game draws Gems, Coins or a trophy on its own screens. Read
 §1 before you pick a file: each currency has two kinds of art, and which one you use depends on what
 the screen is for.
 
-**Currency display belongs to the arcade.** The arcade draws the player's Gems and Tickets totals in
+**Currency display belongs to the arcade.** The arcade draws the player's Gems and Coins totals in
 its own chrome while your game runs, and it animates every payout of either into its total. Your game
-draws Gems or Tickets only in the three places §5 allows — an amount on offer or just paid, a reward
+draws Gems or Coins only in the three places §5 allows — an amount on offer or just paid, a reward
 screen, and how much more your game can still pay (the earn allowance) — and never a balance of its
 own. §5 is the creator's ruling and is not optional.
 
-> **The Tickets art is generated art, open to a designer pass.** It was generated on 2026-09-28
-> (gemforge asset `e540c7ac-850c-4ef0-9b9c-f11227098ce6`): a solid tangerine ticket with a vertical
-> gradient, so it never reads as the rainbow gem or the gold trophy. It replaced the first art of
-> 2026-09-27, a ticket cut from the gem's rainbow glass. If a designer redraws it, the new art
+> **The Coins art is a 3D render, open to a designer pass.** Since the currency was renamed from
+> Tickets to Coins (2026-10-21) it is a solid tangerine coin — a raised rim, a cream ring and an
+> embossed gem-cut, with one vertical gradient — so it never reads as the rainbow gem or the gold
+> trophy. It replaced the tangerine ticket of 2026-09-28. The files keep their `ticket-*` names, as
+> the currency keeps its slug `ARCADE_TICKETS`. If a designer redraws it, the new art
 > replaces these files **under the same names** in a later SDK release, so a game that imports them
 > picks it up on its next SDK update. Lay your screens out from the sizes on this page, not from the
 > drawing.
@@ -25,8 +26,8 @@ own. §5 is the creator's ruling and is not optional.
 | --------------- | --- | -------- |
 | Gems **inline**, beside a number: a price, a "+15" reward label, a small chip | the **icon**, `gem-icon-20-*` or `gem-icon-32-*` | 16–40 CSS px |
 | Gems as **the subject of a reward presentation**: a victory or reward screen where the gem is what the player looks at, such as a victory overlay with a sunburst behind the reward | the **hero**, `gem-hero-*` | 64–256 CSS px |
-| Tickets **inline**, beside a number | the **icon**, `ticket-icon-20-*` or `ticket-icon-32-*` | 16–40 CSS px |
-| Tickets as **the subject of a reward presentation** | the **hero**, `ticket-hero-*` | 64–256 CSS px |
+| Coins **inline**, beside a number | the **icon**, `ticket-icon-20-*` or `ticket-icon-32-*` | 16–40 CSS px |
+| Coins as **the subject of a reward presentation** | the **hero**, `ticket-hero-*` | 64–256 CSS px |
 
 The role decides first and the size follows from it. A price tag is inline even if you make it
 large; a reward screen is a presentation even on a small phone.
@@ -40,8 +41,8 @@ large; a reward screen is a presentation even on a small phone.
 
 The **trophy** comes only as a hero (§3). There is no trophy icon.
 
-The Gems and Tickets marks differ in **shape** — a faceted gem, and a ticket with a notch in each
-end — as well as colour, so a player can tell the two apart without seeing colour. Keep the currency's
+The Gems and Coins marks differ in **shape** — a wide faceted gem, and a round coin with a ring
+inside its rim — as well as colour, so a player can tell the two apart without seeing colour. Keep the currency's
 name beside or behind every amount (in words, or for a screen reader) all the same.
 
 ## 2. The Gems icon
@@ -89,12 +90,12 @@ every quality setting and moved a 20 px icon's facet colours visibly. The render
 and the pipeline lives with the platform's art sources; if the gem changes, the platform re-renders
 both sizes and a new SDK release ships them. Never edit the files by hand.
 
-### The Tickets icon
+### The Coins icon
 
-The same two renditions and four ratios, under the same rules: the ticket spans the full width of its
-box, with clear rows above and below it (more of them than the gem, because a ticket is wider than it
-is tall), and each size is drawn on its own grid with its own outline weight — 1.5 px at 20, 2 px at
-32.
+The same two renditions and four ratios, under the same rules, except that the coin is about as tall
+as it is wide: it is centred with clear rows above and below it (about a twelfth of the box each, so
+it carries the same weight as the wide, low gem), and each size is drawn on its own grid with its own
+outline weight — 1.5 px at 20, 2 px at 32.
 
 | Rendition | For a CSS box of | File | Pixels |
 | --------- | ---------------- | ---- | ------ |
@@ -107,14 +108,14 @@ is tall), and each size is drawn on its own grid with its own outline weight —
 | | | `ticket-icon-32-2x.png` | 64 × 64 |
 | | | `ticket-icon-32-3x.png` | 96 × 96 |
 
-It is the hero's ticket — solid tangerine, a notch in each end and a perforated stub (see the note at
-the top of this page) — downscaled onto each file's own pixel grid, inside the gem icon's violet
-outline. The arcade's wallet draws the same ticket from the same master, and a simplified vector
+It is the hero's coin — solid tangerine, turned a little so its edge shows, a cream ring and an
+embossed gem-cut (see the note at the top of this page) — downscaled onto each file's own pixel grid,
+inside the gem icon's violet outline. The arcade's wallet draws the same coin from the same master, and a simplified vector
 version of it at 16–20 px.
 
 ## 3. The hero art
 
-Three marks — the gem, the ticket and the trophy — each at five sizes. Every file is a square PNG with a
+Three marks — the gem, the coin and the trophy — each at five sizes. Every file is a square PNG with a
 transparent background, no outline, and the mark centred with a small margin, so the files swap for
 one another at any size without moving your layout.
 
@@ -274,11 +275,11 @@ an engine or a tool that cannot bundle files and needs to ask the platform what
 **A bundled game should prefer the renditions in this package**: they come in two sizes and four
 densities, and they cost no request at play time.
 
-## 5. The rules: Gems and Tickets display belongs to the arcade
+## 5. The rules: Gems and Coins display belongs to the arcade
 
-The creator's ruling (2026-09-24): **"Gems display belongs to the arcade."** Tickets, the platform's
-second currency, is held to the same ruling: read every rule below about Gems as a rule about Tickets
-too, with the ticket in place of the gem. Amended 2026-09-30 for the earn allowance (the platform's
+The creator's ruling (2026-09-24): **"Gems display belongs to the arcade."** Coins, the platform's
+second currency, is held to the same ruling: read every rule below about Gems as a rule about Coins
+too, with the coin in place of the gem. Amended 2026-09-30 for the earn allowance (the platform's
 decision of that date); the ruling's other rules are unchanged. In rules:
 
 - **Keep no Gems counter.** Your game shows no Gems balance, running total or wallet of its own, on
@@ -306,8 +307,8 @@ decision of that date); the ruling's other rules are unchanged. In rules:
   the flight leaves from the gem the player is looking at. On a canvas, convert from canvas pixels
   with the canvas's `getBoundingClientRect()`.
 
-  A Tickets payout is cued the same way, from the ticket, with `currencySlug: 'ARCADE_TICKETS'`. The
-  slug decides what flies — gems or tickets — and which total the platform moves. In the Gem Arcade
+  A Coins payout is cued the same way, from the coin, with `currencySlug: 'ARCADE_TICKETS'`. The
+  slug decides what flies — gems or coins — and which total the platform moves. In the Gem Arcade
   every payout flies into the Gem button, in whichever corner of your frame it sits; no wallet is
   drawn over your game.
 - **If `cueReward` returns `false`, do nothing.** There is no fallback celebration. `false` means the
@@ -323,8 +324,8 @@ decision of that date); the ruling's other rules are unchanged. In rules:
   `gem.platform.earnAllowance.get()` ("40 Gems left to earn today"). The icon may sit beside that
   figure. It is still not a balance, a counter or a running total, and it is never a number your game
   computes. Your server's order response is the receipt, not your screen.
-- **The ticket means Tickets, the platform's cosmetics currency** — never your own currency, and
-  never a raffle, an entry or a pass. The gem rule above applies to it word for word.
+- **The coin means Coins, the platform's cosmetics currency** — never your own currency (a game's
+  own gold or coins included: draw those with your own art), and never a token, a chip or a pass. The gem rule above applies to it word for word.
 - **The trophy means an achievement**: use it where your game shows what a player has earned.
   Whether the trophy also becomes the mark of the player's Achievement Score — the sum of their
   achievement points, which the arcade now shows — is an open design question; until it is answered,

package/docs/changelog.md

@@ -16,6 +16,12 @@ Its entries are grouped under up to five headings:
 - **Rebuild**: a type changed. Recompile against the new version; code that compiles today keeps compiling unless the entry says otherwise.
 - **New capability**: something a game can now do. Nothing changes unless you use it.
 
+## 14.0.2
+
+Upgrading from 14.0.1. Impact: none.
+
+Nothing in this release asks anything of a game.
+
 ## 14.0.1
 
 Upgrading from 14.0.0. Impact: none.

package/docs/daily-challenges.md

@@ -321,7 +321,7 @@ Four things to know before you ship one:
   the player does to their time zone.
 
 **When a completion pays a platform currency, show it where it happened.** The arcade shows the
-player's Gems and Tickets in its own chrome, and without a cue a payout flies from the middle of
+player's Gems and Coins in its own chrome, and without a cue a payout flies from the middle of
 your frame, not from the payout the player is looking at. At the moment your game shows the challenge complete, call
 `gem.cueReward` with the currency that paid (`GEMS` or `ARCADE_TICKETS`) and the centre of its icon
 beside the payout on your completion screen, and the payout flies from there into the Gem button: