@ai-rpg-engine/starter-template 3.8.1 → 3.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-rpg-engine/starter-template",
-  "version": "3.8.1",
+  "version": "3.9.0",
   "description": "Starter template for ai-rpg-engine — scaffold a standalone game project from it",
   "type": "module",
   "engines": {

package/src/setup.ts

@@ -150,7 +150,11 @@ export function createGame(seed?: number): Engine {
     });
 
     // Author data → runtime. JSON hosts: extractSessionContent(pack) →
-    // construct modules (buildWorldStack({ districts: session.districts })) →
+    // construct modules (traversalCore/statusCore/combatCore/inventoryCore/
+    // cognitionCore/environmentCore/districtCore/encounterSpawn +
+    // presence/length-gated quests/dialogues/abilities/equipment — NOT
+    // buildWorldStack; see content-schema's extractSessionContent JSDoc for
+    // the full recipe, F-c9309691) →
     // applyContentPack({ profiles, channels: createStandardChannels() }).
     // Import createStandardChannels from @ai-rpg-engine/modules — do not
     // auto-inject. This factory still wires named catalogs at construction;
@@ -163,9 +167,17 @@ export function createGame(seed?: number): Engine {
         throw new Error(`applyContentPack failed:\n${detail}`);
     }
 
-    // Set player context
-    engine.store.state.playerId = 'player';
-    engine.store.state.locationId = 'start';
+    // F-bc7b8ab1: no manual playerId/locationId stamp needed here —
+    // content.ts's placements[] places pack's single type:'player' entity at
+    // 'start', so applyContentPack's own identity stamp (F-67786a6c) already
+    // derived both onto the store above. Don't add one back for your own
+    // starting zone either: if your pack authors exactly one type:'player'
+    // entity with a placement, the stamp tracks it for free — a hand-written
+    // override here is the exact pattern that can silently diverge from
+    // content.ts once you move the starting zone. Only fall back manually
+    // for a pack that declares zero or several type:'player' entities (the
+    // stamp is deliberately ambiguous-safe: it never guesses):
+    // if (!engine.store.state.playerId) engine.store.state.playerId = 'player';
 
     return engine;
 }

package/src/starter.test.ts

@@ -305,3 +305,23 @@ describe('starter template — cross-instance state isolation', () => {
             .not.toBe(a.world.entities['grunt'].resources);
     });
 });
+
+// ═══════════════════════════════════════════════════════════════════
+// IDENTITY STAMP (F-bc7b8ab1)
+// Pin, not a bug fix: this must read identically before and after removing
+// setup.ts's post-applyContentPack `engine.store.state.playerId = 'player';
+// engine.store.state.locationId = 'start';` lines — content.ts's
+// placements[] places { entityId: 'player', zoneId: 'start' }, and pack
+// carries exactly one type:'player' entity, so applyContentPack's own
+// identity stamp (F-67786a6c) already derives the same values. The manual
+// lines were the pre-fix-style override the stamp was written to obsolete —
+// this is the scaffold every new game is copied from, so the leftover
+// pattern would otherwise keep propagating into new starters.
+// ═══════════════════════════════════════════════════════════════════
+describe('starter template — identity stamp owns playerId/locationId (F-bc7b8ab1)', () => {
+    it('boots with playerId "player" and locationId "start" from applyContentPack\'s own identity stamp, with no manual override line', () => {
+        const engine = createGame(1);
+        expect(engine.world.playerId).toBe('player');
+        expect(engine.world.locationId).toBe('start');
+    });
+});