incanto 0.68.0 → 0.69.0

package/templates-app/platformer-2d/src/main.ts

@@ -58,18 +58,30 @@ const game = await createGame2D({
   throw e;
 });
 
-document.querySelector('#loading')?.remove();
+// The console handle FIRST, before any wiring of your own can throw.
+// `game.stats()`, `game.assetErrors()`, `game.frame()` and `game.engine.log`
+// are the entire in-page diagnostic surface, and a static build has no other.
+// Assigned after the wiring, one mistake below took all of them with it.
+(window as unknown as { game: typeof game }).game = game;
 
-if (MUSIC_URL) {
-  game.engine.music.play(MUSIC_URL, { loop: true, fadeIn: 1.5 });
-  game.engine.audio.music = 0.3;
-}
+// And the loading overlay comes down LAST. Everything between here and there is
+// your code; a throw in it used to leave a level that renders perfectly with no
+// player, no error UI, and no way to ask the page what happened.
+try {
+  if (MUSIC_URL) {
+    game.engine.music.play(MUSIC_URL, { loop: true, fadeIn: 1.5 });
+    game.engine.audio.music = 0.3;
+  }
 
-// On-screen JUMP button (mobile + desktop parity); the joystick is auto-shown by
-// createGame2D on coarse pointers for the 'move' action.
-const jumpBtn = document.querySelector('#btn-jump');
-jumpBtn?.addEventListener('pointerdown', () => game.engine.input.handleKey('Space', true));
-jumpBtn?.addEventListener('pointerup', () => game.engine.input.handleKey('Space', false));
+  // No hand-rolled touch button here: the scene declares `"touch": "button"` on
+  // `jump` and `"touch": "joystick"` on `move`, so the ENGINE draws both on a
+  // coarse pointer — safe-area aware, off the home-indicator band, and sized to
+  // its own rules. This template used to draw an 88 px disc of its own at a flat
+  // `bottom: 2rem`, which covered 78% of the engine's jump button and put its
+  // lower edge inside the band iOS reserves for the leave-the-app swipe.
+} catch (e) {
+  showBootFailure(e);
+  throw e;
+}
 
-// Console playground: game.scene.root.getNode('Player').position = [x, y]
-Object.assign(window, { game });
+document.querySelector('#loading')?.remove();

package/templates-app/star-survivor/package.json

@@ -11,7 +11,7 @@
   },
   "dependencies": {
     "@dimforge/rapier2d-compat": "0.19.3",
-    "incanto": "^0.68.0",
+    "incanto": "^0.69.0",
     "three": "^0.184.0"
   },
   "devDependencies": {

package/templates-app/star-survivor/src/main.ts

@@ -45,12 +45,23 @@ const game = await createGame2D({
   throw e;
 });
 
-document.querySelector('#loading')?.remove();
+// The console handle FIRST, before any wiring of your own can throw.
+// `game.stats()`, `game.assetErrors()`, `game.frame()` and `game.engine.log`
+// are the entire in-page diagnostic surface, and a static build has no other.
+// Assigned after the wiring, one mistake below took all of them with it.
+(window as unknown as { game: typeof game }).game = game;
 
-if (MUSIC_URL) {
-  game.engine.music.play(MUSIC_URL, { loop: true, fadeIn: 1.5 });
-  game.engine.audio.music = 0.3;
+// And the loading overlay comes down LAST. Everything between here and there is
+// your code; a throw in it used to leave a level that renders perfectly with no
+// player, no error UI, and no way to ask the page what happened.
+try {
+  if (MUSIC_URL) {
+    game.engine.music.play(MUSIC_URL, { loop: true, fadeIn: 1.5 });
+    game.engine.audio.music = 0.3;
+  }
+} catch (e) {
+  showBootFailure(e);
+  throw e;
 }
 
-// Console playground: game.scene.root.getNode('Player').position = [x, y]
-Object.assign(window, { game });
+document.querySelector('#loading')?.remove();

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.68.0",
+    "incanto": "^0.69.0",
     "three": "^0.184.0"
   },
   "devDependencies": {

package/templates-app/tps-3d/src/main.ts

@@ -50,22 +50,33 @@ const game = await createGame3D({
   throw e;
 });
 
-document.querySelector('#loading')?.remove();
+// The console handle FIRST, before any wiring of your own can throw.
+// `game.stats()`, `game.assetErrors()`, `game.frame()` and `game.engine.log`
+// are the entire in-page diagnostic surface, and a static build has no other.
+// Assigned after the wiring, one mistake below took all of them with it.
+(window as unknown as { game: typeof game }).game = game;
 
-// Looping background music on the music bus (a calm tense pad). The engine
-// auto-resumes a gesture-blocked track on the first click/keypress.
-game.engine.music.play(musicUrl, { loop: true, fadeIn: 1.5 });
-game.engine.audio.music = 0.3;
+// And the loading overlay comes down LAST. Everything between here and there is
+// your code; a throw in it used to leave a level that renders perfectly with no
+// player, no error UI, and no way to ask the page what happened.
+try {
+  // Looping background music on the music bus (a calm tense pad). The engine
+  // auto-resumes a gesture-blocked track on the first click/keypress.
+  game.engine.music.play(musicUrl, { loop: true, fadeIn: 1.5 });
+  game.engine.audio.music = 0.3;
 
-// On-screen FIRE / JUMP buttons (mobile + desktop parity).
-for (const [id, code] of [
-  ['btn-fire', 'KeyF'],
-  ['btn-jump', 'Space'],
-] as const) {
-  const el = document.querySelector(`#${id}`);
-  el?.addEventListener('pointerdown', () => game.engine.input.handleKey(code, true));
-  el?.addEventListener('pointerup', () => game.engine.input.handleKey(code, false));
+  // On-screen FIRE / JUMP buttons (mobile + desktop parity).
+  for (const [id, code] of [
+    ['btn-fire', 'KeyF'],
+    ['btn-jump', 'Space'],
+  ] as const) {
+    const el = document.querySelector(`#${id}`);
+    el?.addEventListener('pointerdown', () => game.engine.input.handleKey(code, true));
+    el?.addEventListener('pointerup', () => game.engine.input.handleKey(code, false));
+  }
+} catch (e) {
+  showBootFailure(e);
+  throw e;
 }
 
-// Console playground for vibe-coding: game.scene.root.getNode('Player') …
-Object.assign(window, { game });
+document.querySelector('#loading')?.remove();

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.68.0",
+    "incanto": "^0.69.0",
     "three": "^0.184.0"
   },
   "devDependencies": {

package/templates-app/village-quest-3d/src/main.ts

@@ -36,7 +36,17 @@ const game = await createGame3D({
   throw e;
 });
 
-document.querySelector('#loading')?.remove();
-
-// Console-poking handle for playtesting ("teleport me to the elder").
+// The console handle FIRST, before any wiring of your own can throw.
+// `game.stats()`, `game.assetErrors()`, `game.frame()` and `game.engine.log`
+// are the entire in-page diagnostic surface, and a static build has no other.
+// Assigned after the wiring, one mistake below took all of them with it.
 (window as unknown as { game: typeof game }).game = game;
+
+// The overlay comes down LAST, after any wiring of your own. There is none in
+// this template — when you add some, put it above this line and wrap it:
+//
+//   try { …your wiring… } catch (e) { showBootFailure(e); throw e; }
+//
+// A throw between the overlay coming down and the handle going up used to leave
+// a level that renders perfectly with no player and no error of any kind.
+document.querySelector('#loading')?.remove();