lokiplay 0.4.3 → 0.4.5

package/dist/AGENTS.template.md

@@ -92,7 +92,10 @@
   what the update path does, then ask them to confirm server. Write
   `"authority": "server"` and `step`. Do not elect a player host. Server
   rooms are browser-only, run in Singapore, and end if the step fails; they
-  do not fall back to a player. That is fairness, not lower latency.
+  do not fall back to a player. That is fairness, not lower latency. The
+  viewer clock follows `tickRate`. Leave `simulationHz` as the local
+  prediction step. Do not set `simulationHz` equal to `tickRate` to unstick
+  presentation.
 - Before compiling `step`, change the state update so the next state depends
   only on the previous state and this tick's inputs. Drawing, sound, and
   asset loads stay in the browser. If the update reads the DOM, the clock,
@@ -136,7 +139,7 @@
   (call each at most once per rendered frame). Keep authoritative
   snapshots compact and self-contained (no references to transient
   local-only state).
-- `snapshotHz` (default/cap 30) is a ceiling, not a delivery guarantee. Do
+- `snapshotHz` (default 30, cap 100) is a ceiling, not a delivery guarantee. Do
   not default to the highest rate. Start conservative — pass
   `adaptiveRate: true` with `initialSnapshotHz` around 12-15 and
   `minSnapshotHz` around 8, or an explicit low fixed `snapshotHz` — and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lokiplay",
-  "version": "0.4.3",
+  "version": "0.4.5",
   "description": "Command-line tools for Loki game projects and deployments.",
   "license": "MIT",
   "repository": {
@@ -39,7 +39,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@lokiplay/protocol": "0.4.3",
+    "@lokiplay/protocol": "0.4.5",
     "fflate": "^0.8.3"
   }
 }