@indiegems/gem-web-sdk 14.0.0 → 14.0.2

package/docs/changelog.md

@@ -16,6 +16,18 @@ 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.
+
+Nothing in this release asks anything of a game.
+
 ## 14.0.0
 
 Upgrading from 13.4.3. Impact: required.

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:

package/docs/game-economy-tutorial.md

@@ -35,8 +35,8 @@ document, because the schema is versioned and a copied list goes stale.
 
 ```yaml
 currencies:
-  - id: coins
-    display_name: Coins
+  - id: gold
+    display_name: Gold
     min_balance: 0
     max_balance: 999999
 
@@ -51,7 +51,7 @@ catalogs:
       - id: buy-potion
         recipe_type: purchase
         costs:
-          - currency_id: coins
+          - currency_id: gold
             amount: 25
         grants:
           - item_definition_id: healing-potion
@@ -106,12 +106,12 @@ them.
 
 ```js
 const store = config.catalogs.find((c) => c.id === 'general-store');
-const balance = (await gem.me.currencies.get('coins')).total; // from the snapshot, not a fourth request
+const balance = (await gem.me.currencies.get('gold')).total; // from the snapshot, not a fourth request
 // `null` means no record — decide at the render what that shows, never `?? 0` at the read.
 
 for (const recipe of store.recipes) {
   const cost =
-    recipe.costs?.find((c) => 'currency_id' in c && c.currency_id === 'coins')?.amount ?? 0;
+    recipe.costs?.find((c) => 'currency_id' in c && c.currency_id === 'gold')?.amount ?? 0;
   const affordable = balance !== null && balance >= cost; // null is "no record", and null >= 0 is true in JS
   const used = usage.usages.find((u) => u.recipeId === recipe.id); // camelCase: SDK shape
   const onCooldown = used?.isOnCooldown ?? false;
@@ -205,10 +205,10 @@ const order = await gem.me.orders.get(result.orderId);
 This is also the answer after a timeout: you got no result back, so list recent orders and look for
 the one you attempted, rather than resending the purchase.
 
-## Selling a cosmetic for Tickets
+## Selling a cosmetic for Coins
 
 Your shop can also sell for the arcade's own currencies, and the platform draws one line through
-them: **Tickets buy cosmetics, Gems buy anything.** Each platform currency has a spend scope — Tickets'
+them: **Coins buy cosmetics, Gems buy anything.** Each platform currency has a spend scope — Coins'
 is `cosmetic_only`, Gems' is `any`. Which currencies your game may price in, and what each may buy,
 is `gemctl platform config`'s answer. Mark a cosmetic in the config, and price it in
 `ARCADE_TICKETS`:
@@ -219,7 +219,7 @@ items:
     display_name: Wizard Hat
     category: cosmetic # it changes how the player looks, never what they can do
     platform_prices:
-      - currency: ARCADE_TICKETS # Tickets
+      - currency: ARCADE_TICKETS # Coins
         price: 40
   - id: dragon-skin
     display_name: Dragon Skin
@@ -265,7 +265,7 @@ if (av.locked) {
 }
 ```
 
-The platform checks the prerequisite **before** it takes any Tickets: a locked player who buys
+The platform checks the prerequisite **before** it takes any Coins: a locked player who buys
 anyway is refused `recipe_locked` and charged nothing. See
 [`inventory-and-catalogs.md`](inventory-and-catalogs.md#16-selling-for-a-platform-currency) for the
 two purchase paths and the full rule.
@@ -285,7 +285,7 @@ const res = await gem.purchases.request({
 if (res.outcome === 'ok' || res.outcome === 'unavailable') {
   gem.me.inventory.refresh(); // `unavailable` means no answer arrived, not that nothing happened
 } else if (res.reason === 'recipe_locked' || res.reason === 'insufficient_funds') {
-  updateShopRow(res.reason); // your shop's own words: "Locked", "Not enough Tickets"
+  updateShopRow(res.reason); // your shop's own words: "Locked", "Not enough Coins"
 } else if (res.reason !== 'cancelled' && res.reason !== 'busy') {
   console.warn('purchase declined:', res.reason); // unknown_currency, no_price_in_currency … are yours to fix
 }
@@ -294,13 +294,13 @@ if (res.outcome === 'ok' || res.outcome === 'unavailable') {
 With your own purchase screen (`gem.me.mutations.purchase`), the same strings arrive as `err.code`
 — see [`inventory-and-catalogs.md`](inventory-and-catalogs.md#why-a-purchase-was-refused).
 
-**Never draw a top-up or payment screen of your own** — no "get more Tickets", no checkout, nothing
-shaped like the arcade's purchase sheet. A player short of Tickets earns more by playing; your shop
-says "Not enough Tickets" and stops there.
+**Never draw a top-up or payment screen of your own** — no "get more Coins", no checkout, nothing
+shaped like the arcade's purchase sheet. A player short of Coins earns more by playing; your shop
+says "Not enough Coins" and stops there.
 
 ## Rewarding a player — still a recipe
 
-When your game _gives_ a player something — "you earned 100 coins," a quest reward — reach for a
+When your game _gives_ a player something — "you earned 100 gold," a quest reward — reach for a
 recipe too, not a direct grant. A reward flow is the same client-authored economy as a shop under a
 friendlier name, and the same rule applies: if the value matters, the server has to be the one that
 awards it. Author a reward recipe in your config and execute it exactly as above.

package/docs/getting-started.md

@@ -50,7 +50,7 @@ either way.
 ```jsonc
 // package.json
 "dependencies": {
-  "@indiegems/gem-web-sdk": "14.0.0"
+  "@indiegems/gem-web-sdk": "14.0.2"
 }
 ```
 
@@ -178,8 +178,8 @@ And draw a settings button of your own — top-right, with your Back button just
 ([the top of the screen](what-a-game-must-do.md#the-top-of-the-screen)) — whose values start from
 the player's Arcade-wide defaults, `gem.prefs.recommended`, until the player chooses their own
 ([what a game must do](what-a-game-must-do.md#game-settings)). The Arcade's menu does not open
-your settings screen; you may also mirror a few of your settings into it with
-`gem.settings.declare`, but never instead of your own button. Outside the Arcade there is no Arcade menu at all, so also give players a way out — a
+your settings screen; declare your settings to it with `gem.settings.declare` too, so its
+Settings screen lists them all, but never instead of your own button. Outside the Arcade there is no Arcade menu at all, so also give players a way out — a
 control that calls `gem.exit()`. A game a player cannot leave is one they leave by closing the tab.
 
 ## 6. Play it

package/docs/inventory-and-catalogs.md

@@ -1,7 +1,7 @@
 # Inventory and catalogs
 
 Games do not have to have an economy. A game with no currency, no items and nothing to buy is a
-complete game. Read this if yours has any of them — a coin count, a bag of items, a shop, a loot
+complete game. Read this if yours has any of them — a gold count, a bag of items, a shop, a loot
 box, a battle pass.
 
 If it does, the platform holds it, the same way it holds a save. Balances and items live on the
@@ -42,8 +42,8 @@ which is the same rule with a save slot in place of a currency.
 
 Hold the distinction, because the whole surface is built on it.
 
-- A **currency definition** is "coins exist, minimum 0, maximum a million." A player's **balance**
-  is an instance: "this player has 250 coins."
+- A **currency definition** is "gold exists, minimum 0, maximum a million." A player's **balance**
+  is an instance: "this player has 250 gold."
 - An **item definition** is "a healing potion, stackable to 99." An **item instance** is "this
   player holds 3 of them," or, for a non-stacking item, "this specific sword, rolled with these
   properties."
@@ -60,7 +60,7 @@ because it never loaded the definitions that name them.
 Everything a player owns is reached through `gem.me`, the signed-in player:
 
 ```js
-await gem.me.currencies.get('coins');
+await gem.me.currencies.get('gold');
 await gem.me.inventory.snapshot();
 ```
 
@@ -69,7 +69,7 @@ scoped to that character:
 
 ```js
 const hero = await gem.characters.get(characterId);
-await hero.currencies.get('coins'); // the hero's coins, not the account's
+await hero.currencies.get('gold'); // the hero's gold, not the account's
 ```
 
 Code written against `gem.me` works unchanged against a character, because it is one interface on
@@ -85,7 +85,7 @@ lookups are memory:
 ```js
 const config = await gem.gameConfig.load(); // a round trip; do it once
 const potion = config.item('healing-potion'); // synchronous, from memory, by id or slug
-const coin = config.currency('coins'); // synchronous
+const gold = config.currency('gold'); // synchronous
 ```
 
 Two things that will bite:
@@ -162,8 +162,8 @@ A balance read is a lookup, not a list to iterate, because **a currency the play
 is absent, not present as zero**:
 
 ```js
-const coins = await gem.me.currencies.get('coins');
-coins.total; // a number, or null when the player has no record of this currency
+const gold = await gem.me.currencies.get('gold');
+gold.total; // a number, or null when the player has no record of this currency
 ```
 
 **`null` is not `0`.** Reach for `total ?? 0` and you have decided that "has never held any" and
@@ -175,7 +175,7 @@ is visible.
 real-money pool. They are off by default and asked for per read:
 
 ```js
-const c = await gem.me.currencies.get('coins', { buckets: true });
+const c = await gem.me.currencies.get('gold', { buckets: true });
 c.buckets; // [{ bucket: 'earned', balance: 200 }, { bucket: 'purchased', balance: 50 }], or absent
 ```
 
@@ -409,7 +409,7 @@ await gem.me.mutations.claimProgression('season-xp'); // collect what milestones
 await gem.me.mutations.resetProgression('season-xp'); // back to the start; claimed rewards stay
 ```
 
-`addProgression` is for things that accumulate — experience, kills, coins collected across a
+`addProgression` is for things that accumulate — experience, kills, gold collected across a
 season. `maxProgression` is for things that are a _best_ — stars on a level, a high score, a
 furthest checkpoint. It raises the value if the new one is higher and does nothing otherwise, so
 replaying a level and doing worse leaves the record alone, and replaying it and doing the same
@@ -439,7 +439,7 @@ so this page does not list them. Name one that is not permitted and the config u
 with an error that enumerates the ones that are.
 
 Gems can be your game's soft currency, awarded through a mapping. A game currency of your own suits
-what lives inside one play loop — coins picked up and spent within a run, energy, crafting
+what lives inside one play loop — gold picked up and spent within a run, energy, crafting
 materials: you control it completely, no other game can spend it, and none of the constraints below
 apply to it.
 
@@ -551,7 +551,7 @@ nobody else can touch them. The arcade also has currencies that span every game,
 That changes what a shop can be. A player earns in someone else's game and spends in yours.
 
 There are two such currencies, and they are not interchangeable: **Gems** (`GEMS`) buy progress and
-**Tickets** (`ARCADE_TICKETS`) buy cosmetics only. [arcade-economy.md](arcade-economy.md) says which
+**Coins** (`ARCADE_TICKETS`) buy cosmetics only. [arcade-economy.md](arcade-economy.md) says which
 to use for what.
 
 ### Awarding one
@@ -583,13 +583,13 @@ A browser-only game cannot award a platform currency without a server **or a ser
 That is the price of the platform never trusting a client. A game with no dedicated server writes
 the source progression from a function the player calls, on a progression that opts in with
 `function_may_grant`, and the platform then pays that player only, in any listed platform currency
-— Gems (`GEMS`) and Tickets (`ARCADE_TICKETS`) alike
+— Gems (`GEMS`) and Coins (`ARCADE_TICKETS`) alike
 ([serverless-functions.md](serverless-functions.md#paying-the-player-who-called)).
 
 ### Showing the reward land in the arcade's wallet
 
 **Platform-currency display belongs to the arcade** (the creator's ruling, 2026-09-24) — Gems and
-Tickets alike. The arcade shows the player's platform currencies in its own chrome — in the Gem
+Coins alike. The arcade shows the player's platform currencies in its own chrome — in the Gem
 Arcade, the Gem menu the player opens from the Gem button over your frame; no wallet
 is drawn over your game — and moves a total when the platform confirms a grant. Your game keeps no counter or balance
 of a platform currency of its own, draws no flight or celebration of its own, and shows no
@@ -609,8 +609,8 @@ gem.cueReward({
 ```
 
 `origin` is the **centre of the gem on screen** — measure the gem element itself, not the row or
-panel around it. A Tickets payout is the same call with `currencySlug: 'ARCADE_TICKETS'`, from the
-ticket: the slug decides what flies and which total moves. **A payout you do not cue still flies**
+panel around it. A Coins payout is the same call with `currencySlug: 'ARCADE_TICKETS'`, from the
+coin: the slug decides what flies and which total moves. **A payout you do not cue still flies**
 in the Gem Arcade, from the middle of your frame, once the platform confirms it — cue it so the
 flight starts where the player is looking. **If `cueReward` returns `false`, do nothing**: there is
 no fallback celebration.
@@ -829,14 +829,14 @@ that looks like the arcade's purchase sheet or wallet. A game screen shaped like
 chrome is an imitation of it. Your Buy button is yours; asking a player to add currency or pay is
 the arcade's alone.
 
-### Tickets buy cosmetics; Gems buy anything
+### Coins buy cosmetics; Gems buy anything
 
-The arcade has two currencies a player spends: **Gems**, for progress, and **Tickets**
+The arcade has two currencies a player spends: **Gems**, for progress, and **Coins**
 (`ARCADE_TICKETS`), for cosmetics. The platform holds that line with two settings: each platform
 currency's **spend scope**, which the platform sets, and each of your items' **category**, which you
 set.
 
-- A currency whose spend scope is **`cosmetic_only`** may price cosmetics only. Tickets' is.
+- A currency whose spend scope is **`cosmetic_only`** may price cosmetics only. Coins' is.
 - A currency whose spend scope is **`any`** may price anything. Gems' is.
 
 The platform owns each currency's scope and can change it, so do not hard-code which is which: a
@@ -862,9 +862,9 @@ items:
   cosmetics: anything that changes how the player looks and never what they can do — or
   `progression`, anything that affects play. It defaults to `progression`, so an item is only ever a
   cosmetic because you said so.
-- **A price in a `cosmetic_only` currency, such as Tickets, is accepted only on a cosmetic.** On an
+- **A price in a `cosmetic_only` currency, such as Coins, is accepted only on a cosmetic.** On an
   item, that item must be `category: cosmetic` and a plain `item_type: item` — a `bundle` or
-  `loot_box` opens into things its own row does not describe, so it cannot be sold for Tickets.
+  `loot_box` opens into things its own row does not describe, so it cannot be sold for Coins.
 - **A recipe priced in a `cosmetic_only` currency must grant at least one cosmetic item and nothing
   else.** It is refused if it grants any currency, moves any progression, grants a non-cosmetic item,
   or rolls a loot table — a loot table is refused for now even when every entry is cosmetic. Taking
@@ -884,11 +884,11 @@ purchase catalog stops listing that currency's price on anything the scope does
 purchase naming such a price is refused `not_purchasable` before anything is charged.
 
 The category is a declaration the platform takes at your word, and the release review checks it.
-Labelling something that affects play `cosmetic` so it can be sold for Tickets breaks platform policy.
+Labelling something that affects play `cosmetic` so it can be sold for Coins breaks platform policy.
 
 **To sell a cosmetic that needs game progress first, sell it through a recipe.** An item's own
 `platform_prices` cannot carry prerequisites; a recipe's can. Grant the cosmetic from a recipe that
-declares the prerequisite and carries the Tickets price:
+declares the prerequisite and carries the Coins price:
 
 ```yaml
 catalogs:
@@ -909,7 +909,7 @@ catalogs:
             price: 120
 ```
 
-A player below level 10 is refused `recipe_locked` before any Tickets are taken, and
+A player below level 10 is refused `recipe_locked` before any Coins are taken, and
 `recipeAvailability` tells your shop the recipe is locked and what it needs (§9) — so show the lock
 ("Reach level 10 to unlock") instead of offering the purchase.
 
@@ -922,7 +922,7 @@ buyButton.disabled = !gems || gems.balance < price; // can the player afford it?
 ```
 
 **Read it to decide, never to display.** Platform-currency display belongs to the arcade: its
-wallet — the Gem menu, in the Gem Arcade — shows the player's Gems and Tickets totals while your
+wallet — the Gem menu, in the Gem Arcade — shows the player's Gems and Coins totals while your
 game runs, and your game keeps no
 counter, balance or wallet total of either of its own ([brand-art.md](brand-art.md) §5). Use the
 balance to enable a purchase or to say "not enough Gems" — not to draw a number.
@@ -952,7 +952,7 @@ if (gems && gems.remaining > 0) {
 }
 ```
 
-One entry per earned platform currency (Gems and Tickets today), for **this game and this player**:
+One entry per earned platform currency (Gems and Coins today), for **this game and this player**:
 how much more your game can still grant before the platform's ceilings trim the grant. It is the
 lower of what is left of your game's own cap and what is left of the player's daily maximum across
 all games, with the player's Boost applied — one figure, never a breakdown.
@@ -971,8 +971,8 @@ all games, with the player's Boost applied — one figure, never a breakdown.
 **Only `remaining` and `resetsAt` are stable to display.** Do not build an `earned / limit` progress
 bar: the bar switches referent when the binding ceiling changes.
 
-A player whose Tickets are spent for today reads `remaining: 0` with a `resetsAt`: say when more
-arrives (from `resetsAt`), not "no Tickets". When the platform has paused a currency's grants for
+A player whose Coins are spent for today reads `remaining: 0` with a `resetsAt`: say when more
+arrives (from `resetsAt`), not "no Coins". When the platform has paused a currency's grants for
 your game the entry reads `limit: 0, remaining: 0` with **no** `resetsAt`.
 
 **For a one-day allowance, `resetsAt` is the player's own next midnight — do not assume 00:00 UTC.**
@@ -1054,7 +1054,7 @@ grants itself.
 
 ## What to read next
 
-- [`arcade-economy.md`](arcade-economy.md) — Gems, Tickets and achievement points: which to use for
+- [`arcade-economy.md`](arcade-economy.md) — Gems, Coins and achievement points: which to use for
   what, and the rules each carries.
 - [`achievements.md`](achievements.md) — platform achievements on your progressions' thresholds.
 - [`game-economy-tutorial.md`](game-economy-tutorial.md) — build a shop, step by step, the safe way.

package/docs/manifest.json

@@ -8,8 +8,8 @@
   "documents": [
     {
       "file": "achievements.md",
-      "sha256": "adc8bfaa769fbb283a53de1190ed85cdf4c1c9753e8cf78335b4595e98f8fad4",
-      "updated": "2026-10-06T22:14:30Z"
+      "sha256": "c1ba25c834f5679dc5ce1c7c3b51d4219b5ac77fc898bf5d6fbf23e35614e35c",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "analytics.md",
@@ -18,13 +18,13 @@
     },
     {
       "file": "arcade-avatars.md",
-      "sha256": "7269a0dbd515e2c52e63f9fad2b3028e136396522aa68aa177c44f7eceb2c0e0",
-      "updated": "2026-10-14T19:48:50Z"
+      "sha256": "e02e435d91e389f9cc2025945ebc0ac11882bac85a4e6d5d74278f11e38fee91",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "arcade-economy.md",
-      "sha256": "338dcdfe4aaa90241f7132677a0135d0ec8e32336f4302413dc0f11391b37623",
-      "updated": "2026-10-15T23:20:43Z"
+      "sha256": "2a73e2cb4e82de78a9d57c614da67bfd6a79537163deca551c5beeb8e9693c56",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "async-opponents.md",
@@ -33,18 +33,18 @@
     },
     {
       "file": "brand-art.md",
-      "sha256": "44ba566da97e499f80b6c4898a5546bf7fb3dfba2290da9aa3e8d4e6056a7cce",
-      "updated": "2026-10-14T21:18:16Z"
+      "sha256": "151ece62736136e0acd5c4e3e2dd7e33eb6936923c89340670844452d34acf02",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "changelog.md",
-      "sha256": "3ccaf70d80a6164736920b4df6f817d600b2a80287d4a14783f72fbb470863f6",
-      "updated": "2026-10-21T13:51:48Z"
+      "sha256": "22d1e4aba2cdd10d9ff33e1d5fded140194a96fabe24f95aa673e9af1f07e72c",
+      "updated": "2026-10-21T19:49:02Z"
     },
     {
       "file": "daily-challenges.md",
-      "sha256": "0423168355c22724e705def15ca19a5651b7f0da3598ec5aabcc69c32e0bb401",
-      "updated": "2026-10-11T18:48:12Z"
+      "sha256": "fd1c44a923b8f7b82a52b958481e82ba5d62dc27de6a196a0776b0d34563ec54",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "dedicated-server-flow.md",
@@ -63,18 +63,18 @@
     },
     {
       "file": "game-economy-tutorial.md",
-      "sha256": "08588571cd6529d81bd064f65bc3158997418aeb88ce00ae281735c8b44bff1f",
-      "updated": "2026-10-02T19:05:02Z"
+      "sha256": "5f921001150ea47a92d97e943282988826ea27506107c71846e5ff79f0d26f15",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "getting-started.md",
-      "sha256": "dbda9199712f4112bfe316b7af6e63a11fcce6842e778672459e1532947cf21f",
-      "updated": "2026-10-21T13:51:48Z"
+      "sha256": "f70765a705776bea4f11c8067669204db31e992515d15a76c465785e71bc6abe",
+      "updated": "2026-10-21T19:49:02Z"
     },
     {
       "file": "inventory-and-catalogs.md",
-      "sha256": "fc2dbf113d2602fff90d03fc24e03d468c7b4ab3633844ed9d0df6b985e69385",
-      "updated": "2026-10-18T00:39:23Z"
+      "sha256": "e3968af5f3af88122db84ac372afd82e39c04c98cf6661f83e429243837ee6ff",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "leaderboards.md",
@@ -98,8 +98,8 @@
     },
     {
       "file": "platform-rules.md",
-      "sha256": "b259bcebc6ae12b1db9c7279a6e2adb174af9d60090bf31001e23616f6423fbf",
-      "updated": "2026-10-10T00:12:33Z"
+      "sha256": "ab5b971555490956ef50f6141b0f58a6a34335a7e4cc1ef0e4d339a259c9a062",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "player-sign-in.md",
@@ -108,8 +108,8 @@
     },
     {
       "file": "rewarded-ads.md",
-      "sha256": "a111ae68fb0d443f8c183c7a963668078a6d155124cf19da45391218c0716e1f",
-      "updated": "2026-10-17T17:23:21Z"
+      "sha256": "b413abb899016c9a6d0c288c39d804bdabcebceec1081bdcfbb1f3feb0073406",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "room-shapes.md",
@@ -123,13 +123,13 @@
     },
     {
       "file": "saving-player-progress.md",
-      "sha256": "11ab0684247cfc43d6d8faba6dbb897192354af5f5622b16fd96abcb156ca0cd",
-      "updated": "2026-10-12T21:21:05Z"
+      "sha256": "2b51c68651b8973531fb1fda4afc4442e1450443871800ca71126605bf4b39db",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "server-bundles.md",
-      "sha256": "2312a25bb11ce29f50b97b0737c708b31f6e0290f99fe2520179a9dbac67fb8c",
-      "updated": "2026-10-21T13:51:48Z"
+      "sha256": "95d84093c49693576297f2a6917064a1efbb6824c82acfc9f210d64a3b437d2f",
+      "updated": "2026-10-21T19:49:02Z"
     },
     {
       "file": "serverless-functions-js.md",
@@ -138,13 +138,13 @@
     },
     {
       "file": "serverless-functions.md",
-      "sha256": "eef5fa14dced0bca39b4f4b9d6688d4f81d6c4d2441ec3497380c21b7482022a",
-      "updated": "2026-10-15T14:37:57Z"
+      "sha256": "9a33e93c90c963fd82e4848d403f27134ec15636428f6cf896488089fec3ede1",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "trading-and-gifting.md",
-      "sha256": "d7ee3c85540ab8aae29988c16a76bee3ba03cc66b10d2faaf5cd7210a80a0544",
-      "updated": "2026-08-26T03:27:49Z"
+      "sha256": "e5a77bcae4243fbf69a34fa6440114677401255b40ee9825c15b87c6570e5030",
+      "updated": "2026-10-21T19:36:16Z"
     },
     {
       "file": "vibration.md",
@@ -153,8 +153,8 @@
     },
     {
       "file": "what-a-game-must-do.md",
-      "sha256": "3a9c0e307b78cfb8b959c7b47a1ad0349699be944903a24834ee785c3823b402",
-      "updated": "2026-10-21T13:31:36Z"
+      "sha256": "a0f1fd58acd28c72cca3574032c087ffbe2cb34e311086c99eceec7e2f9b7f20",
+      "updated": "2026-10-21T19:36:16Z"
     }
   ]
 }

package/docs/platform-rules.md

@@ -329,13 +329,13 @@ longer one, are in [`server-bundles.md`](server-bundles.md#how-long-your-server-
 Decided by the platform on **2026-09-26**, and a contract rather than an implementation fact.
 
 The **Boost** is something the Arcade sells for real money, in its own store. While a player has
-one, they earn **Gems and Tickets** faster — every grant is multiplied — and their earning limits
+one, they earn **Gems and Coins** faster — every grant is multiplied — and their earning limits
 and holdings cap are raised by the same tier. It **never** touches achievement points. The platform applies all of
 it on its own side, when it pays: a game does nothing to make a boost work, and cannot make one
 work harder.
 
 A game **may show** it. `gem.player.boost` carries each boostable currency's multiplier and the
-whole days left, so a reward screen can say "2× Tickets"; see
+whole days left, so a reward screen can say "2× Coins"; see
 [what a game must do](what-a-game-must-do.md#the-signed-in-players-boost-show-it-never-gate-on-it).
 A dedicated server can read the same effective boost for a player in its match, and the same rule
 holds there.

package/docs/rewarded-ads.md

@@ -39,7 +39,7 @@ config where it is not:
 - **Soulbound.** Every item or currency it grants has `transfer_policy: none`. A reward cannot be
   traded, gifted or moved.
 - **An ordinary item or a currency.** Not a bundle, not a loot box, and not a progression.
-- **Never a platform currency.** The upload refuses a reward that names Gems, Tickets or any
+- **Never a platform currency.** The upload refuses a reward that names Gems, Coins or any
   other platform currency.
 - **Never convertible into one of those.** The upload follows every recipe and catalog entry that
   spends the reward, then everything that spends what those grant, and so on. If that chain reaches

package/docs/saving-player-progress.md

@@ -474,7 +474,7 @@ The order matters, and two of the steps are the ones people skip:
 The reset clears this player's state **in this game, on that one channel**: saves,
 `gem.me.settings`, inventory and progressions, and the rest of what the game keeps for them.
 It does not touch your other channels, your other games, achievements, or your Gems and
-Tickets. Your purchases and what you paid stay on record, but an item a purchase delivered on
+Coins. Your purchases and what you paid stay on record, but an item a purchase delivered on
 that channel is cleared with the rest, and the answer lists those purchases.
 `gemctl support reset --help` has the full list, and the answer names whatever it left alone.
 

package/docs/server-bundles.md

@@ -80,8 +80,8 @@ To check the download yourself: the package npm serves is, byte for byte, the fi
 also publishes on its download host, with the hash beside it:
 
 ```bash
-curl -fsSL -O https://downloads.gemarcade.com/sdk/v14.0.0/gem-web-sdk.tgz
-curl -fsSL https://downloads.gemarcade.com/sdk/v14.0.0/gem-web-sdk.tgz.sri
+curl -fsSL -O https://downloads.gemarcade.com/sdk/v14.0.2/gem-web-sdk.tgz
+curl -fsSL https://downloads.gemarcade.com/sdk/v14.0.2/gem-web-sdk.tgz.sri
 openssl dgst -sha384 -binary gem-web-sdk.tgz | openssl base64 -A
 ```
 

package/docs/serverless-functions.md

@@ -18,7 +18,7 @@ change: checking that a finished run was plausible, or granting a reward whose c
 state only your code can judge.
 
 It is also how a game **with no dedicated server** pays a platform currency — Gems (`GEMS`) or
-Tickets (`ARCADE_TICKETS`) — or unlocks an achievement. A browser write
+Coins (`ARCADE_TICKETS`) — or unlocks an achievement. A browser write
 never does either. A function a player calls may, for **that player only**, on a progression you
 opt in. Section 2's
 [Paying the player who called](#paying-the-player-who-called) is the whole of it. Opting in makes
@@ -160,7 +160,7 @@ fires them only when you opt in:
   request answers `200`, and the transfer stays `pending` for the recipient to accept or reject
   (the previous subsection).
 - **Any currency the platform lists.** A function may pay every currency `gemctl platform config`
-  lists under `platform_grants` — Gems (`GEMS`) and Tickets (`ARCADE_TICKETS`) alike — so a daily
+  lists under `platform_grants` — Gems (`GEMS`) and Coins (`ARCADE_TICKETS`) alike — so a daily
   that pays Gems needs no dedicated server. (`function_gems_not_enabled` on an older receipt is from
   before functions could pay Gems.)
 - **No guests.** A guest account's call grants and unlocks nothing (`function_invoker_is_guest`).

package/docs/trading-and-gifting.md

@@ -13,7 +13,7 @@ as `gem.transfers` rather than through `gem.me`.
 await gem.transfers.initiate({
   to: { type: 'players', id: recipientId },
   items: [{ itemDefinitionId: 'iron-sword', quantity: 1 }],
-  currencies: [{ currencyId: 'coins', amount: 50 }],
+  currencies: [{ currencyId: 'gold', amount: 50 }],
   message: 'for the boss fight',
 });
 ```