@bountyboard/arcade-sdk 1.3.0 → 1.4.1

package/docs/relay-rooms.md

@@ -1,12 +1,12 @@
 # Relay rooms
 
-Relay rooms are the zero-server-code multiplayer tier. Every game with SDK
-multiplayer approved gets them automatically: hosted lobbies, shareable invite
-codes, public quick match, reconnect handling, and message fan-out — without
-registering a server module or running any backend. The same `joinRoom()` API
-drives all tiers, so a game can start on relay rooms and graduate to a
-refereed module or an external authoritative server later without client
-rewrites.
+Relay rooms are the multiplayer tier that needs no server code. Every game with
+SDK multiplayer approved gets them automatically: hosted lobbies, shareable
+invite codes, public quick match, reconnect handling, and message fan out,
+without registering a server module or running any backend. The same
+`joinRoom()` API drives all tiers, so a game can start on relay rooms and
+graduate to a refereed module or an external authoritative server later without
+client rewrites.
 
 ## What the server owns (and what it refuses to)
 
@@ -15,13 +15,13 @@ The relay server authoritatively owns everything it can own *generically*:
 - the roster and seat cap,
 - host designation and succession,
 - admission (signed tickets, room binding, per-seat connection caps),
-- message fan-out with rate and size guardrails.
+- message fan out with rate and size guardrails.
 
 It deliberately does not interpret game payloads, so it cannot referee them.
-Relay outcomes are client-trusted: relay rooms never emit `match_end`, never
+Relay outcomes are client trusted: relay rooms never emit `match_end`, never
 report results to Bounty Board, and never feed win/loss records or
-leaderboards. Games that need authoritative results — anything ranked,
-recorded, or reward-adjacent — must use a refereed Bounty-hosted module or a
+leaderboards. Games that need authoritative results (anything ranked,
+recorded, or reward adjacent) must use a refereed Bounty hosted module or a
 registered external authority instead.
 
 ## Joining
@@ -39,7 +39,7 @@ const room = await joinRoom({
 - `code` joins a friend's room.
 - `match: true` enters the game's open public room, or founds one.
 
-All three go through the standard signed-ticket flow; nothing about relay
+All three go through the standard signed ticket flow; nothing about relay
 rooms weakens admission.
 
 ### Room size
@@ -52,7 +52,7 @@ next arrival re-founds it. Ship the same `roomSize` from every client of
 your game so matchmade rooms are founded consistently.
 
 Quick match fills rooms to the founded size. Because matchmaking reserves
-seats conservatively, a burst of simultaneous quick-match joins can briefly
+seats conservatively, a burst of simultaneous quick match joins can briefly
 overshoot a small room; losers of that race receive `room_full` and the SDK
 automatically retries into the next room.
 
@@ -61,7 +61,7 @@ automatically retries into the next room.
 `room.send(payload)` relays `payload` to **every** player in the room,
 including the sender. There are no private messages: every client sees every
 payload, so never send secrets (hidden roles, private hands) through a relay
-room. Payload semantics are entirely yours — the server never reads them.
+room. Payload semantics are entirely yours. The server never reads them.
 
 Messages are batched per server tick and delivered through `room.on('event')`:
 
@@ -78,7 +78,7 @@ room.on('event', event => {
 });
 ```
 
-Guardrails (over-limit traffic is dropped silently; the state snapshot's
+Guardrails (traffic over the limit is dropped silently; the state snapshot's
 `dropped` counter is the debugging breadcrumb):
 
 | Limit | Value |
@@ -101,9 +101,9 @@ grace keeps both the seat and the host role, so a brief network blip does not
 thrash host succession.
 
 Use the host as your game's coordinator: it can own spawn timing, level
-seeds, or authoritative-enough game state for casual play. Remember the trust
-model — a modified client can lie, which is acceptable for casual co-op and
-couch-style games and not acceptable for anything with stakes.
+seeds, or authoritative enough game state for casual play. Remember the trust
+model. A modified client can lie, which is acceptable for casual co-op and
+couch style games and not acceptable for anything with stakes.
 
 ## State snapshots
 
@@ -123,12 +123,12 @@ current.
 Relay rooms never settle: there is no `end` event, and a room lives while it
 has players (seats survive a 15-second reconnect grace). Implement your own
 notion of rounds or matches in game messages, and call `room.leave()` when
-the player exits — leaving is immediate and never reconnects.
+the player exits. Leaving is immediate and never reconnects.
 
 ## Graduating to a refereed tier
 
-If your game outgrows client trust — ranked results, tournaments, anything
-paid — the ticket flow, room codes, and quick match all stay the same; the
+If your game outgrows client trust (ranked results, tournaments, anything
+paid), the ticket flow, room codes, and quick match all stay the same; the
 room's simulation moves server-side. Contact Bounty Board about a refereed
-Bounty-hosted module, or keep your own server and register it under the
+Bounty hosted module, or keep your own server and register it under the
 external authority contract (see `external-authoritative-servers.md`).

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@bountyboard/arcade-sdk",
-  "version": "1.3.0",
-  "description": "Bounty Board Arcade SDK — leaderboards, cloud saves, rewarded ads, A/B variants, and multiplayer rooms for games on bountyboard.gg",
+  "version": "1.4.1",
+  "description": "Bounty Board Arcade SDK: leaderboards, cloud saves, rewarded ads, A/B variants, and multiplayer rooms for games on bountyboard.gg",
   "keywords": [
     "bountyboard",
     "arcade",