@daneren2005/shared-memory-physics 1.9.0 → 1.9.1

package/README.md

@@ -839,6 +839,11 @@ const clicked = world.findNearestSpatial(mouseX, mouseY, 0);
 const nearby = world.searchSpatialAround(x, y, 100, 100);
 ```
 
+The map defaults to `type: Float64Array`. Entity ids are never reused, so a `Float32` map, which only holds ids
+below 2^24 (~16.7M), runs out after that many entities have *ever* been created. `Float64` covers the whole
+uint32 eid range for about 1.4x the memory per entity. Pass `spatial: { type: Float32Array }` only if a world
+will create fewer entities than that over its lifetime.
+
 `searchSpatial`, `searchSpatialAround`, `findNearestSpatial`, and `findNearbySpatial` return live entities and
 accept entity filters. Shape-aware axis-aligned bounds are stored: rotated rectangles and capsules occupy the
 box around their actual outline. A direct transform/body edit outside the physics update must be followed by

package/dist/index.js

@@ -718,7 +718,10 @@ var $t = class extends e {
 	spatialIds = /* @__PURE__ */ new Set();
 	constructor(e, t = {}) {
 		let { spatial: n, ...r } = t;
-		super(e, r), this.spatialMap = new o(this.heap, n), this.on("entity-added", (e) => {
+		super(e, r), this.spatialMap = new o(this.heap, {
+			type: Float64Array,
+			...n
+		}), this.on("entity-added", (e) => {
 			this.updateSpatialEntity(e), e.on("component-added", (t) => {
 				(t === "transform" || t === "body") && this.updateSpatialEntity(e);
 			}), e.on("component-removed", (t) => {