spoint 0.1.680 → 0.1.682

package/apps/world/tps-game.js

@@ -18,7 +18,7 @@ const TERRAIN = {
   // they stay a single source of truth. Singleplayer (WorkerEntry.js's in-Worker boot of this same world
   // def) also reads serverAuthoritative, but with no other client to sync to it's a no-op there in
   // practice -- the local clock behaves identically to before this feature.
-  timeOfDay: { serverAuthoritative: true, dayLengthSec: 600, startFraction: 0.3 },
+  timeOfDay: { serverAuthoritative: true, dayLengthSec: 600, startFraction: 0.27 },
   // weather-server-driven-state-and-multiplayer-sync: same real-multiplayer-test-world rationale as
   // timeOfDay.serverAuthoritative immediately above -- every connected client's weather state
   // (client/core/Weather.js) stays a server-pushed value (src/sdk/ServerWeather.js, MSG.WEATHER_SYNC)

package/client/app.js

@@ -2422,7 +2422,15 @@ function startInputLoop() {
     ams.dispatchInput(sendInput,engineCtx); client.sendInput(sendInput)
   }, 1000/60)
 }
-renderer.domElement.addEventListener('click', ()=>{ if (inputConfig.pointerLock&&!document.pointerLockElement) renderer.domElement.requestPointerLock() })
+renderer.domElement.addEventListener('click', ()=>{
+  if (!inputConfig.pointerLock || document.pointerLockElement) return
+  // requestPointerLock() can throw synchronously (not just reject) in some browser/automation
+  // contexts -- e.g. "The root document of this element is not valid for pointer lock" when the
+  // element's document isn't the active top-level document at click time. Left unguarded this was
+  // an uncaught exception that tripped the app's global error boundary, converting a benign
+  // lock-denial into a full page crash. The keydown fallback below still recovers gameplay either way.
+  try { renderer.domElement.requestPointerLock() } catch (e) { console.warn('[input] requestPointerLock failed:', e?.message || e) }
+})
 // requestPointerLock() is a trusted-gesture-gated browser API that can silently reject (denied
 // engagement heuristic, automation-driven click, embedded/iframe context) with no visible error --
 // the click-prompt overlay then never dismisses and gameplay looks permanently blocked even though

package/client/core/TimeOfDay.js

@@ -40,7 +40,7 @@ const KEYFRAMES = [
   { deg: -90, sunColor: 0x0a1030, sunIntensity: 0.0, ambientColor: 0x0d1428, ambientIntensity: 0.10 }, // deep night
   { deg: -6, sunColor: 0x1a2550, sunIntensity: 0.0, ambientColor: 0x1a2440, ambientIntensity: 0.14 }, // astronomical twilight, sun still below horizon (no direct light)
   { deg: 0, sunColor: 0xff7a3c, sunIntensity: 0.55, ambientColor: 0x4a4060, ambientIntensity: 0.22 }, // horizon: warm orange sunrise/sunset
-  { deg: 8, sunColor: 0xffb266, sunIntensity: 1.05, ambientColor: 0x8a8496, ambientIntensity: 0.28 }, // low sun: golden hour
+  { deg: 8, sunColor: 0xffa552, sunIntensity: 1.8, ambientColor: 0xffcf9e, ambientIntensity: 0.55 }, // low sun: golden hour (matches tps-game.js's intended fill-light-visible palette)
   { deg: 30, sunColor: 0xfff0dc, sunIntensity: 1.45, ambientColor: 0xc9d4e8, ambientIntensity: 0.32 }, // mid-morning/afternoon
   { deg: 70, sunColor: 0xffffff, sunIntensity: 1.6, ambientColor: 0xfff4d6, ambientIntensity: 0.3 }, // near-noon, matches SceneSetup's original static values
   { deg: 90, sunColor: 0xffffff, sunIntensity: 1.55, ambientColor: 0xfff4d6, ambientIntensity: 0.3 }, // straight overhead

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spoint",
-  "version": "0.1.680",
+  "version": "0.1.682",
   "description": "Physics and netcode SDK for multiplayer game servers",
   "type": "module",
   "workspaces": [