castle-web-sdk 0.4.22 → 0.4.23

package/dist/multiplayer.js

@@ -64,16 +64,20 @@ class MultiplayerConnectionImpl {
             throw castleError;
         }
     }
+    // Unserializable data is a mistake in the deck and still throws. A missing
+    // socket is not: connections drop whenever a phone sleeps or changes network,
+    // and the session recovers on its own. A realtime deck sends every frame and
+    // has no useful branch to take meanwhile, so those messages are dropped.
+    // State arrives in whole snapshots, so the next send past recovery is current.
     send(data) {
         const text = serializeClientMessage(data);
-        if (this.currentState !== "connected") {
+        if (this.currentState === "closed") {
             throw multiplayerError("MULTIPLAYER_NOT_CONNECTED", "Multiplayer.send requires a connected session.", "Multiplayer.send");
         }
         if (this.solo)
             return;
-        if (!this.socket || this.socket.readyState !== WebSocket.OPEN) {
-            throw multiplayerError("MULTIPLAYER_NOT_CONNECTED", "The multiplayer connection is not available.", "Multiplayer.send");
-        }
+        if (!this.socket || this.socket.readyState !== WebSocket.OPEN)
+            return;
         this.socket.send(text);
     }
     onMessage(callback) {
@@ -177,6 +181,10 @@ class MultiplayerConnectionImpl {
         this.currentPlayerId = frame.playerId;
         this.currentSessionId = frame.sessionId;
         this.reconnectToken = frame.reconnectToken;
+        // Re-acquisition is limited to one per outage, not one per session. A phone
+        // is backgrounded many times in a play, and each of those is its own outage;
+        // without this the second one finds the budget spent and closes for good.
+        this.reAcquisitionUsed = false;
         this.transition("connected");
         this.startKeepalive();
     }

package/dist/storage.js

@@ -1,7 +1,7 @@
 import { CastleError } from "./errors";
 import { hostRequest } from "./transport";
-// The child coalesces writes -- a frame can set the same key many times -- and
-// hands them to the host on this interval. The host, not the deck, talks to the
+// Writes coalesce by key as they are made, so setting the same key repeatedly
+// costs one entry; this is how often the result is handed to the host. The host, not the deck, talks to the
 // server and owns retry: it lives in the page, so it is still alive to finish a
 // write while the deck's frame is being torn down.
 const FLUSH_INTERVAL_MS = 200;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "castle-web-sdk",
-  "version": "0.4.22",
+  "version": "0.4.23",
   "type": "module",
   "main": "dist/castle.js",
   "types": "dist/castle.d.ts",
@@ -14,7 +14,7 @@
       "default": "./dist/server/wrapper.js"
     }
   },
-  "//host": "host.{js,d.ts} is the host-side executor and leaderboardPanel.{js,d.ts} is the host-side leaderboard UI \u2014 both deliberately NOT exported and NOT packaged. They are vendored into host repos via scripts/copy-host-module.mjs; decks must never receive them.",
+  "//host": "host.{js,d.ts} is the host-side executor and leaderboardPanel.{js,d.ts} is the host-side leaderboard UI — both deliberately NOT exported and NOT packaged. They are vendored into host repos via scripts/copy-host-module.mjs; decks must never receive them.",
   "files": [
     "dist",
     "README.md",