@vibemancer/core 1.0.6 → 1.0.8

package/src/index-browser.ts

@@ -9,6 +9,7 @@
 export * from './types.js';
 export * from './rules.js';
 export * from './engine-version.js';
+export * from './replay-compat.js';
 export * from './engine/simulation.js';
 export * from './engine/hooks-runtime.js';
 export * from './engine/physics.js';

package/src/index.ts

@@ -1,6 +1,7 @@
 export * from './types.js';
 export * from './rules.js';
 export * from './engine-version.js';
+export * from './replay-compat.js';
 export * from './engine/simulation.js';
 export {DEFAULT_BUDGET, DEFAULT_FIGHT_BACKSTOP_MS, createBudgetState, createFightBudget, recordSpend, mayAct} from './engine/bot-compute-budget.js';
 export type {BudgetLimits, BotBudgetState, FightBudget} from './engine/bot-compute-budget.js';

package/src/replay-compat.ts

@@ -0,0 +1,35 @@
+/**
+ * Whether a stored match can still be replayed by the running engine.
+ *
+ * Spectate re-simulates a recorded match from its seed, so it may only do that when the
+ * engine is the one that produced it. The check used to be `match.engineVersion ===
+ * ENGINE_VERSION`, which is right in spirit and slightly too strict in fact.
+ *
+ * ENGINE_VERSION is a CONTENT HASH, so it answers "is this the same source?" rather than
+ * "is this the same behaviour?". Those come apart when the hashing itself is corrected. On
+ * 2026-09-09 the comment stripper was fixed — it had been hashing most comments as if they
+ * were code — and the value moved from 1688330189011034 to 3884810833238487 without
+ * packages/core/src changing by a byte. Under an exact comparison that would have stranded
+ * 26,948 of the 42,896 stored matches, 63% of them, for no reason a player could act on.
+ *
+ * So the gate consults a short list of historical values known to describe the same engine.
+ * See scripts/engine-version-equivalents.json for what may go in it, and for why a wrong
+ * entry is the dangerous kind of wrong: it fails OPEN.
+ */
+
+import {ENGINE_VERSION, EQUIVALENT_ENGINE_VERSIONS} from './engine-version.js';
+
+/**
+ * @param matchEngineVersion the `engineVersion` field as read from a stored match.
+ *   Deliberately typed to admit the junk a database can hand back: a document written
+ *   before the field existed returns undefined, and a missing version is never a match.
+ */
+export function canReplayMatch(matchEngineVersion: number | null | undefined): boolean
+{
+	if (typeof matchEngineVersion !== 'number') return false;
+	// NaN would fail `===` against everything, so an exact gate happened to reject it. Being
+	// explicit keeps that true now that the comparison is a lookup.
+	if (!Number.isSafeInteger(matchEngineVersion)) return false;
+	if (matchEngineVersion === ENGINE_VERSION) return true;
+	return EQUIVALENT_ENGINE_VERSIONS.includes(matchEngineVersion);
+}

package/src/rules.ts

@@ -61,6 +61,11 @@ export const RULES = {
 	MISSILE_MIN_CAST_TIME: 0.1, // seconds
 	MISSILE_BASE_RADIUS: 2, // base hitbox radius in units
 	MISSILE_DAMAGE_RADIUS_SCALE: 0.1, // additional radius per damage point
+	// The real hitbox is THREE TIMES the base+scale figure. This lived as a bare `* 3` inside
+	// calculateMissileRadius, outside RULES, so no document could interpolate it — and five
+	// of them consequently stated the unmultiplied formula, understating the hit window by
+	// 43-57%. It is a rule, so it lives with the rules.
+	MISSILE_RADIUS_MULTIPLIER: 3,
 	MISSILE_BASE_CAST: 0.1,
 	MISSILE_DAMAGE_SCALE: 0.226,
 	MISSILE_DAMAGE_POWER: 2 / 3, // sublinear: DPS always increases with damage
@@ -133,7 +138,7 @@ export const MISSILE_DAMAGE_RADIUS_SCALE = RULES.MISSILE_DAMAGE_RADIUS_SCALE;
  */
 export function calculateMissileRadius(damage: number): number
 {
-	return (RULES.MISSILE_BASE_RADIUS + damage * RULES.MISSILE_DAMAGE_RADIUS_SCALE) * 3;
+	return (RULES.MISSILE_BASE_RADIUS + damage * RULES.MISSILE_DAMAGE_RADIUS_SCALE) * RULES.MISSILE_RADIUS_MULTIPLIER;
 }
 
 // === MISSILE CAST TIME FORMULA ===