dewdrop-sdk 0.5.1 → 0.5.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dewdrop-sdk",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Build a three.js game for Dewdrop: the Vite plugin, model calls, multiplayer, saves and voice.",
   "license": "MIT",
   "type": "module",

package/src/index.js

@@ -5,7 +5,8 @@
 // runs, `clients`, in that backend, over its port back, and `saves` into
 // the browser's own storage, which the plugin's script empties as each
 // page loads; `session` says when a session ends ahead of time, which here
-// none does; and `voice` reads the microphone through the browser's own
+// none does, and lets a game end its player's session, which here ends
+// nothing; and `voice` reads the microphone through the browser's own
 // audio worklet, into the chunks a game gets on Dewdrop.
 export { llm } from './llm.js';
 export { backend } from './backend.js';

package/src/session.js

@@ -1,17 +1,31 @@
 // `session` on a developer's machine. On Dewdrop a session can end ahead of
-// time — for maintenance, a newer version of its game published, or its
-// player idle for fifteen minutes — and hears of it first, up to fifteen
-// minutes before, a minute for an idle player: `session.ending` is
-// `{at, reason}`, `at` in milliseconds since the epoch as `Date.now()` counts
-// and `reason` `'restart'`, `'update'` or `'idle'`, and an `ending` event
-// fires each time it changes, its withdrawal to null included, so a game can
-// save and say so. `npm run dev` ends no session ahead of time, so here `ending`
-// stays null and the event never fires; a game tries its handler by calling
-// it.
-import { defineHandlers } from './net.js';
+// time — for maintenance, a newer version of its game published, its player
+// idle for fifteen minutes, its player away for ten — the page hidden, or
+// another game of theirs showing — or its player choosing to play in
+// another tab — and hears of it first, up to fifteen minutes before, a
+// minute for an idle or an away player, and as it ends for a player playing
+// elsewhere: `session.ending` is `{at, reason}`, `at` in milliseconds since
+// the epoch as `Date.now()` counts and `reason` `'restart'`, `'update'`,
+// `'idle'`, `'away'`, `'elsewhere'` or `'exit'`, and an `ending` event fires
+// each time it changes, its withdrawal to null included, so a game can save
+// and say so. A game ends its player's session itself with
+// `session.exit()`, which on Dewdrop takes the player back to Dewdrop's
+// home page while the room's other players play on, the game hearing
+// `'exit'` as it goes; a backend has no player to send anywhere, so there it
+// throws NotSupportedError. `npm run dev` ends no session, so here `ending`
+// stays null and the event never fires, a game trying its handler by
+// calling it, and `exit()` ends nothing: the console says so, once.
+import { defineHandlers, side } from './net.js';
 
+let told = false;
 class Session extends EventTarget {
   get ending() { return null; }
+  exit() {
+    if (side.backend) throw new DOMException('session.exit is unavailable in a backend', 'NotSupportedError');
+    if (told) return;
+    told = true;
+    console.info('[dewdrop] session.exit(): on Dewdrop this ends the session and takes the player back to Dewdrop’s home page; npm run dev keeps the game running');
+  }
 }
 defineHandlers(Session.prototype, ['ending']);