incanto 0.23.0 → 0.25.0

package/editor/index.html

@@ -5,7 +5,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <title>Incanto Scene Editor</title>
     <link rel="icon" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'><rect width='16' height='16' rx='3' fill='%236ee7dc'/><text x='8' y='12' text-anchor='middle' font-size='11' font-family='monospace' fill='%230e1018'>i</text></svg>" />
-    <script type="module" crossorigin src="./assets/index-D-bWhSDj.js"></script>
+    <script type="module" crossorigin src="./assets/index-Did0QjRa.js"></script>
     <link rel="modulepreload" crossorigin href="./assets/GameServer-C56iOUgF.js">
     <link rel="stylesheet" crossorigin href="./assets/index-D8QvwvOm.css">
   </head>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "incanto",
-  "version": "0.23.0",
+  "version": "0.25.0",
   "description": "Vibe-coding-first web game engine SDK — JSON-driven scenes on three.js",
   "keywords": [
     "game-engine",

package/skills/incanto-building-3d-games.md

@@ -50,7 +50,9 @@ One call does register → load → physics → input → renderer → start. Ph
 `'auto'`: Rapier is enabled iff the tree has physics bodies (force with
 `physics: true|false`). Keyboard attaches to `window` (`keyboard: false`
 disables); `pointer: { lockOnClick: false }` for look without lock. `seed` /
-`fixedHz` / `pixelRatio` pass through. The manual `Engine` + `loadScene` +
+`fixedHz` / `pixelRatio` / `adaptiveResolution` pass through (adaptive
+resolution is ON by default: slow frames render fewer pixels and recover
+automatically — pass `false` for screenshots and pixel-diff tests). The manual `Engine` + `loadScene` +
 `Renderer3D` boot still exists for full control.
 
 Imperative per-frame logic can hang off `game.engine.updated.connect((dt) => { ... })`; for

package/skills/incanto-environment.md

@@ -789,6 +789,21 @@ Swimming down is a different optical world, and the engine renders it as one:
                     "caustics": { "intensity": 0.6 } } } }
 ```
 
+### Where water meets ground
+
+The waterline is the thing that gives game water away. Incanto fades it in
+SCREEN SPACE, not in metres: a beach's water column climbs from nothing to
+knee-deep in centimetres of ground on a steep shore and in metres on a flat
+one, so any fixed depth ramp is invisible on the first and swallows the second.
+The shader divides the column by its own screen-space gradient, which turns the
+fade into a constant band of pixels — no slope and no camera angle can cut it
+back into a line. The band is then broken with world noise, breathed in and out
+with the swash (`shoreWaves`), and its last stretch froths.
+
+That means a shoreline needs nothing wired: no foam prop, no decal, no second
+mesh. If you want MORE of it, `shoreWaves` drives the breathing and the
+breakers, and `Terrain3D.wetline` darkens the sand the water just left.
+
 ### What water COSTS, and every dial that lowers it
 
 Fancy water is not one draw — it is extra SCENE RENDERS, and each one
@@ -802,6 +817,11 @@ with grass, trees and a mirror):
 | cube reflection | `reflection: true` | 256² × 6 faces | 6, every `reflectionInterval` ms (≥2 s while `mirror` is on — it is only the off-screen fallback then) |
 | the surface itself | always | — | a ~1.5 quads/m grid, capped 160² |
 
+The fragment shader also LODs itself: every ripple octave, the caustic loops
+and the whitecap noise are SKIPPED once distance has faded their contribution,
+rather than being computed and multiplied by zero. A pixel of horizon water
+used to pay for four noise octaves to throw three away.
+
 Grass, flowers, particles and trails are dropped from the side passes: they are
 most of a meadow's triangles and none of what anyone reads in a reflection or a
 depth mask.
@@ -820,10 +840,22 @@ for frames per water body:
 | `foam: false` | drops the shoreline foam work |
 | `interaction: false` | stops the per-frame body scan |
 
-Two more, outside water: `createGame3D({ pixelRatio: 1.5 })` — a retina display
-renders **4× the pixels**, and water is fragment-heavy, so capping the ratio is
-usually the single biggest win on a Mac; and `environment.bloom`, which adds a
-full-resolution HDR pass of its own.
+Two more, outside water. **`environment.bloom`** adds a full-resolution HDR
+pass of its own. And PIXELS: a retina display renders **4× the pixels** of a
+1× one, which is why a scene that profiles at 690k triangles and 270 draw calls
+can still miss frames — it is fill-bound, not geometry-bound.
+
+The engine handles that itself: **adaptive resolution is ON by default**. It
+watches the median frame time over a window and, when frames run slow, renders
+the same world at fewer pixels (down to 60% of the requested ratio, in 15%
+steps), handing them straight back when the frames recover. One hitch never
+moves it; a backgrounded tab never counts. Turn it off for screenshots, video
+capture or pixel-diff tests — and pin the ratio yourself if you would rather
+choose:
+
+```ts
+createGame3D({ canvas, scene, adaptiveResolution: false, pixelRatio: 1.5 });
+```
 
 If a scene feels heavy, measure before guessing — the browser console has the
 whole story:

package/templates-app/beacon-isle-3d/package.json

@@ -14,7 +14,7 @@
     "@dimforge/rapier2d-compat": "0.19.3",
     "@dimforge/rapier3d-compat": "0.19.3",
     "@pixiv/three-vrm": "^3.5.3",
-    "incanto": "^0.23.0",
+    "incanto": "^0.25.0",
     "three": "^0.184.0"
   },
   "devDependencies": {

package/templates-app/tps-3d/package.json

@@ -13,7 +13,7 @@
     "@dimforge/rapier2d-compat": "0.19.3",
     "@dimforge/rapier3d-compat": "0.19.3",
     "@pixiv/three-vrm": "^3.5.3",
-    "incanto": "^0.23.0",
+    "incanto": "^0.25.0",
     "three": "^0.184.0"
   },
   "devDependencies": {

package/templates-app/village-quest-3d/package.json

@@ -13,7 +13,7 @@
     "@dimforge/rapier2d-compat": "0.19.3",
     "@dimforge/rapier3d-compat": "0.19.3",
     "@pixiv/three-vrm": "^3.5.3",
-    "incanto": "^0.23.0",
+    "incanto": "^0.25.0",
     "three": "^0.184.0"
   },
   "devDependencies": {