@looop-games/cli 0.1.30 → 0.1.31

package/CHANGELOG.md

@@ -14,6 +14,15 @@ Versions: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.1.31] - 2026-08-21
+
+### Changed
+- `looop dev` no longer starts a multiplayer server for a **single-player** game.
+  A game with no `config({ multiplayer: true })` runs its whole simulation in the
+  browser, so the local PartyKit server was dead weight — dev now skips it and
+  says so. Structural hot-reload (adding an entity/trait) still works. A
+  multiplayer game is unaffected.
+
 ## [0.1.30] - 2026-08-21
 
 ### Fixed

package/lib/dev.mjs

@@ -17,7 +17,7 @@ import { createStaticServer } from './static-server.mjs';
 import { createLlmShim, DEFAULT_API_BASE } from './llm-shim.mjs';
 import { getToken, getApiBase } from './config.mjs';
 import { resolvePorts, portInUse, killPort, lanIp } from './ports.mjs';
-import { assertNoInertOverride, isFrameworkV2, scanPrimitives } from './primitives.mjs';
+import { assertNoInertOverride, isFrameworkV2, isSinglePlayerV2, scanPrimitives } from './primitives.mjs';
 import { buildDevRoomServer, DEV_OVERRIDES_DIR } from './room-server.mjs';
 import { createFileWatcher, createRoomReloader } from './room-reload.mjs';
 import { hasDeclaredAssets, assetsPageUrl } from './assets-page.mjs';
@@ -151,8 +151,40 @@ export async function dev({ cwd = process.cwd(), port, noMp = process.env.NO_MP
   log(`→ static      :${ports.static}  (serving ${project.dir}, engine ${engine.version}, auto-reload on)`);
 
   // ─── multiplayer (partykit on the bundle's room code) ───
-  if (noMp) {
-    log(`→ multiplayer :${ports.mp}  (skipped — NO_MP=1)`);
+  // A single-player framework-v2 game (no config({ multiplayer: true })) runs its
+  // authoritative sim in-process via LocalRoom — its client never opens a socket,
+  // so standing up partykit here just burns a port and a workerd process. Skip it,
+  // mirroring publish, which deploys no per-game room worker for the same game.
+  const singlePlayer = isSinglePlayerV2({ projectDir: project.dir, skeleton: roomSkeleton });
+  if (noMp || singlePlayer) {
+    log(
+      singlePlayer && !noMp
+        ? `→ multiplayer :${ports.mp}  (skipped — single-player; add config({ multiplayer: true }) to enable)`
+        : `→ multiplayer :${ports.mp}  (skipped — NO_MP=1)`,
+    );
+    // No room worker, but the client still assembles its graph against the injected
+    // skeleton — so a STRUCTURAL edit (new entity/trait) must rebuild the skeleton
+    // and push it to the static server, or the page reloads onto a stale skeleton
+    // and assembleGraph throws ("re-ran N ticks but the skeleton has M"). The full
+    // partykit reloader below does this as a side effect; single-player needs a
+    // stripped-down version with no child to respawn. (NO_MP on a real multiplayer
+    // game has no client to serve a skeleton to, so it needs none.)
+    if (singlePlayer) {
+      const skelWatcher = createFileWatcher({
+        files: roomInputs,
+        dirs: ['entities', 'components', 'overrides/shared/ui/room'].map((d) => join(project.dir, d)),
+        onChange: async () => {
+          try {
+            const built = await buildDevRoomServer({ projectDir: project.dir, engine });
+            staticServer.setSkeleton(built.skeleton ?? null);
+            skelWatcher.setFiles(built.inputs);
+          } catch (err) {
+            log(`[skeleton] rebuild failed — fix the error and save again: ${err.message}`);
+          }
+        },
+      });
+      servers.push({ close: () => skelWatcher.close() });
+    }
   } else {
     if (tookOver && (await portInUse(ports.mp))) {
       log(`→ multiplayer :${ports.mp}  (our stale server — reclaiming)`);

package/lib/primitives.mjs

@@ -166,6 +166,17 @@ export function isServerBacked(projectDir) {
   });
 }
 
+// VQ7M2K: a framework-v2 game is SINGLE-PLAYER unless it declares
+// config({ multiplayer: true }). A single-player game runs its authoritative sim
+// in-process (the LocalRoom transport) with no wire — so dev stands up no partykit
+// room and publish deploys no per-game room worker. The multiplayer flag lives in
+// the built skeleton's config (emitSkeleton → graph.config, default false); a game
+// with no skeleton (a v1 primitive/entity game) is never single-player in this
+// sense and keeps its room. Callers pass the skeleton they already built.
+export function isSinglePlayerV2({ projectDir, skeleton }) {
+  return isFrameworkV2(projectDir) && skeleton?.config?.multiplayer !== true;
+}
+
 // The one cycle shadowing makes possible, caught in the creator's own words.
 //
 // A NEW primitive may subclass an engine one — that is the RECOMMENDED way to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@looop-games/cli",
-  "version": "0.1.30",
+  "version": "0.1.31",
   "description": "Looop game development CLI — dev server, login, and publishing for standalone Looop games.",
   "type": "module",
   "license": "Apache-2.0",