spoint 0.1.688 → 0.1.689

package/apps/world/tps-game.js

@@ -18,14 +18,17 @@ 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.
-  // AAA-push cross-piece regression (found live, round 5 of the open-landscape piece): startFraction
+  // AAA-push cross-piece regression (found live, round 5-7 of the open-landscape piece): startFraction
   // was bumped 0.3->0.27 by the low-sun/golden-hour piece's own round 3 so the world would boot AT
   // that piece's target lighting for easy iteration -- but this is the WORLD'S shared default time,
   // so every OTHER piece (open-landscape-midday included) got tested against golden-hour lighting by
-  // accident, not midday. Reverted to the original near-midday default; per-piece lighting states
-  // belong in each piece's own test setup (e.g. a critic-driven time override), never in the shared
-  // world config that every piece's test inherits.
-  timeOfDay: { serverAuthoritative: true, dayLengthSec: 600, startFraction: 0.3 },
+  // accident. Reverting to 0.3 wasn't actually a fix either: client/core/TimeOfDay.js's own
+  // _elevationDeg(frac)=sin((frac-0.25)*2pi)*(90-tilt) peaks at frac=0.5 (true solar noon) -- 0.3 is
+  // only ~18deg elevation (its own comment even says "0.3 ~ mid-morning", never claimed to be
+  // midday). Using 0.5 for genuine midday/high-sun testing; per-piece lighting states still belong
+  // in each piece's own test setup for pieces that need a DIFFERENT angle (e.g. low-sun), never in
+  // this shared world config that every piece's test otherwise inherits.
+  timeOfDay: { serverAuthoritative: true, dayLengthSec: 600, startFraction: 0.5 },
   // 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/core/TimeOfDay.js

@@ -111,7 +111,21 @@ export function createTimeOfDay(sun, ambient, opts = {}) {
     }
     const elevDeg = _elevationDeg(t)
     const kf = _lerpKeyframes(elevDeg)
-    if (sun) { sun.color.setHex(kf.sunColor); sun.intensity = kf.sunIntensity }
+    // BUG FOUND LIVE (AAA-push, startFraction changes had zero visible effect on the rendered sky/
+    // sun despite window.__timeOfDay.elevationDeg correctly reporting the new angle): this function
+    // updated sun.color/sun.intensity from the day-cycle every frame but never sun.position -- the
+    // DirectionalLight's direction stayed frozen at whatever the static world-config set once at
+    // boot, forever, regardless of the day cycle. onDirectionChange(dir) only fed the shadow-camera
+    // offset and the terrain sky-shader's local sun dir, neither of which is the visible THREE.js
+    // sun light object itself. A DirectionalLight's direction is FROM position TOWARD target (both
+    // default at the origin unless target is parented into the scene), so position the light along
+    // `dir` at a fixed distance to preserve the same effective direction the rest of the pipeline
+    // already computes from `dir`.
+    if (sun) {
+      sun.color.setHex(kf.sunColor); sun.intensity = kf.sunIntensity
+      const SUN_DIST = 200
+      sun.position.set(dir[0] * SUN_DIST, dir[1] * SUN_DIST, dir[2] * SUN_DIST)
+    }
     if (ambient) { ambient.color.setHex(kf.ambientColor); ambient.intensity = kf.ambientIntensity }
     if (typeof window !== 'undefined') {
       window.__timeOfDay = window.__timeOfDay || {}

package/package.json

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