@spawnite/engine 0.1.0-beta.15

package/dist/wiki/engine/errors/SP0391.md

@@ -0,0 +1,20 @@
+---
+title: SP0391
+description: "useEvent(%s) listens for a server-only event, which stays on the room and never reaches a view: read it in a system with readEvents, or declare it ..."
+---
+
+The engine makes this error in `useEvent`, from `@spawnite/engine`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+useEvent(%s) listens for a server-only event, which stays on the room and never reaches a view: read it in a system with readEvents, or declare it reliable.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0392.md

@@ -0,0 +1,20 @@
+---
+title: SP0392
+description: "%s was handed the step of a join that has ended: a join hook's step reaches the joining player and what her join spawns only while her join hooks run."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed the step of a join that has ended: a join hook's step reaches the joining player and what her join spawns only while her join hooks run. Keep no step past its hook; a system's own step reaches the world.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0393.md

@@ -0,0 +1,20 @@
+---
+title: SP0393
+description: "%s was handed a join step with no world."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed a join step with no world.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0394.md

@@ -0,0 +1,20 @@
+---
+title: SP0394
+description: "%s was handed an authority over the world while a join runs, whose hooks reach the joining player and what her join spawns alone, so a refused join..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed an authority over the world while a join runs, whose hooks reach the joining player and what her join spawns alone, so a refused join can take back all it did. Pass the hook's step, or change the rest of the world from a system once her join has run.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0395.md

@@ -0,0 +1,20 @@
+---
+title: SP0395
+description: "%s was handed no authority over its world: pass the room's step, inside if (step.authoritative) or in a system with no runsOn, or requireAuthority(..."
+---
+
+The engine makes this error in `readAuthorityWorld`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed no authority over its world: pass the room's step, inside if (step.authoritative) or in a system with no runsOn, or requireAuthority(world) outside a step.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0396.md

@@ -0,0 +1,20 @@
+---
+title: SP0396
+description: "%s was handed no authority: pass the room's step, inside if (step.authoritative) or in a system with no runsOn, requireAuthority(world) outside a s..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed no authority: pass the room's step, inside if (step.authoritative) or in a system with no runsOn, requireAuthority(world) outside a step, or findAuthority(world, entity) for an entity only a page holds.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0397.md

@@ -0,0 +1,20 @@
+---
+title: SP0397
+description: "%s was handed the authority of another world than its entity's: pass the authority of the world the entity lives in."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed the authority of another world than its entity's: pass the authority of the world the entity lives in.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0398.md

@@ -0,0 +1,20 @@
+---
+title: SP0398
+description: "%s was handed a join hook's step, which reaches the joining player and the entities her join spawned alone: a join adds to her and spawns, and leav..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed a join hook's step, which reaches the joining player and the entities her join spawned alone: a join adds to her and spawns, and leaves the rest of the world as it was, so a refused join undoes all of it. Change the rest of the world from a system, whose step reaches it.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0399.md

@@ -0,0 +1,20 @@
+---
+title: SP0399
+description: "%s was handed an authority over another entity: findAuthority(world, entity) gives one over the entity it names alone."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was handed an authority over another entity: findAuthority(world, entity) gives one over the entity it names alone.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0400.md

@@ -0,0 +1,20 @@
+---
+title: SP0400
+description: "attach would attach entity %s to entity %s, which is it or follows it: an attachment cannot form a loop."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+attach would attach entity %s to entity %s, which is it or follows it: an attachment cannot form a loop. Attach the child to an entity outside its own chain.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0401.md

@@ -0,0 +1,20 @@
+---
+title: SP0401
+description: "attach was handed entity %s and entity %s of two worlds: attach two entities of one world."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+attach was handed entity %s and entity %s of two worlds: attach two entities of one world.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0402.md

@@ -0,0 +1,20 @@
+---
+title: SP0402
+description: "attach was handed an entity that is gone, %s: attach two entities that are alive."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+attach was handed an entity that is gone, %s: attach two entities that are alive.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0403.md

@@ -0,0 +1,20 @@
+---
+title: SP0403
+description: "\"%s\" cannot name an event: a name is letters and digits starting with a lower case letter, as \"damaged\" and \"roundEnded\" are."
+---
+
+The engine makes this error in `defineEvent`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+"%s" cannot name an event: a name is letters and digits starting with a lower case letter, as "damaged" and "roundEnded" are. The log, the dump and a room's stream know the event by it.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0404.md

@@ -0,0 +1,20 @@
+---
+title: SP0404
+description: "Two events are named \"%s\": the log, the dump and a room's stream know an event by its name, so each needs its own."
+---
+
+The engine makes this error in `defineEvent`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+Two events are named "%s": the log, the dump and a room's stream know an event by its name, so each needs its own. Rename one of them.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0405.md

@@ -0,0 +1,20 @@
+---
+title: SP0405
+description: "emitEvent was handed no event: make it with defineEvent(name, schema)."
+---
+
+The engine makes this error in `emitEvent`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+emitEvent was handed no event: make it with defineEvent(name, schema).
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0406.md

@@ -0,0 +1,20 @@
+---
+title: SP0406
+description: "emitEvent(%s) was handed no authority: pass the room's step, requireAuthority(world) outside a step, or findAuthority(world, entity) for an entity ..."
+---
+
+The engine makes this error in `emitEvent`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+emitEvent(%s) was handed no authority: pass the room's step, requireAuthority(world) outside a step, or findAuthority(world, entity) for an entity only this page holds.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0407.md

@@ -0,0 +1,20 @@
+---
+title: SP0407
+description: "emitEvent(%s) was handed a join hook's step, which reaches the joining player and what her join spawns alone: emit an event about the world from a ..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+emitEvent(%s) was handed a join hook's step, which reaches the joining player and what her join spawns alone: emit an event about the world from a system, once her join has run.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0408.md

@@ -0,0 +1,20 @@
+---
+title: SP0408
+description: "%s was emitted past the bound of %s events or %s bytes held (maximumHeldEvents, maximumHeldEventBytes)%s: a runaway emitter, such as an emit every ..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s was emitted past the bound of %s events or %s bytes held (maximumHeldEvents, maximumHeldEventBytes)%s: a runaway emitter, such as an emit every step for every entity. Emit on a change, or keep the value in a trait.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0409.md

@@ -0,0 +1,20 @@
+---
+title: SP0409
+description: "readEvents(step, %s) ran outside the system its step runs: a view hears an event with useEvent, and a system reads in the step it is handed, keepin..."
+---
+
+The engine makes this error in `readEvents`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+readEvents(step, %s) ran outside the system its step runs: a view hears an event with useEvent, and a system reads in the step it is handed, keeping no step for later.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0410.md

@@ -0,0 +1,20 @@
+---
+title: SP0410
+description: "readEvents(step, %s) read a local event, which no step emits: hear it in a view with useEvent."
+---
+
+The engine makes this error in `readEvents`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+readEvents(step, %s) read a local event, which no step emits: hear it in a view with useEvent.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0411.md

@@ -0,0 +1,20 @@
+---
+title: SP0411
+description: "\"%s\" cannot name a prefab: a name is letters and digits starting with a lower case letter, as \"wolf\" and \"kartBlue\" are."
+---
+
+The engine makes this error in `definePrefab`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+"%s" cannot name a prefab: a name is letters and digits starting with a lower case letter, as "wolf" and "kartBlue" are. It is the key the dump writes the prefab under.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0412.md

@@ -0,0 +1,20 @@
+---
+title: SP0412
+description: "Two prefabs are named \"%s\": the room and every page know a prefab by its name, so each needs its own."
+---
+
+The engine makes this error in `definePrefab`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+Two prefabs are named "%s": the room and every page know a prefab by its name, so each needs its own. Rename one of them.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0413.md

@@ -0,0 +1,20 @@
+---
+title: SP0413
+description: "%s lists %s among its traits, which the engine makes from %s: set that instead, so a scene and a system spawn it alike."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s lists %s among its traits, which the engine makes from %s: set that instead, so a scene and a system spawn it alike.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0414.md

@@ -0,0 +1,20 @@
+---
+title: SP0414
+description: "%s holds a %s, which a spawn cannot copy for each entity: hold plain records, lists, maps, numbers, text and three.js vectors in a prefab's traits,..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+%s holds a %s, which a spawn cannot copy for each entity: hold plain records, lists, maps, numbers, text and three.js vectors in a prefab's traits, and make anything else in a system after the spawn.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0415.md

@@ -0,0 +1,20 @@
+---
+title: SP0415
+description: "A spawn was given a prefab named %s, which no definePrefab declared: make a prefab with definePrefab, or leave the name out of a spawn's options."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+A spawn was given a prefab named %s, which no definePrefab declared: make a prefab with definePrefab, or leave the name out of a spawn's options.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0416.md

@@ -0,0 +1,20 @@
+---
+title: SP0416
+description: "An entity drawn as \"%s\" has a hull collider, and the hull corners registered under that name wrap no body, so it would have none, on the page or in..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+An entity drawn as "%s" has a hull collider, and the hull corners registered under that name wrap no body, so it would have none, on the page or in a room: no corners are registered, as for a model registered by a bare url, baked with hullPoints: false or baked before the corners existed, or the corners lie on one line. Bake the manifest with hullPoints on, and register the model with its entry, registerModel(name, models[id]), or give it a box or a capsule collider sized to what it draws.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0417.md

@@ -0,0 +1,20 @@
+---
+title: SP0417
+description: "A %s body was declared with no collider, so it would have no shape to collide with: give it a collider, such as collider: { shape: box({ size: [1, ..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+A %s body was declared with no collider, so it would have no shape to collide with: give it a collider, such as collider: { shape: box({ size: [1, 1, 1] }) }.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0418.md

@@ -0,0 +1,20 @@
+---
+title: SP0418
+description: "spawnLocal ran in a predicted system as it stepped her alone, as a correction's re-run does, which would make one more entity for every correction."
+---
+
+The engine makes this error in `spawnLocal`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+spawnLocal ran in a predicted system as it stepped her alone, as a correction's re-run does, which would make one more entity for every correction. Spawn a page's own entity from a system with runsOn: RunContext.Client, or from a view's effect.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0419.md

@@ -0,0 +1,20 @@
+---
+title: SP0419
+description: "Entity %s has a %s body and a %s collider at index %s, which a %s body cannot take: a triangle mesh goes on a fixed or a kinematic body, and a heig..."
+---
+
+The engine makes this error inside its own work, not in an engine call a game makes.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+Entity %s has a %s body and a %s collider at index %s, which a %s body cannot take: a triangle mesh goes on a fixed or a kinematic body, and a heightfield or voxels on a fixed one. Give it a box, a sphere, a capsule, a cylinder, a cone or a convex hull, or make the body fixed.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.

package/dist/wiki/engine/errors/SP0420.md

@@ -0,0 +1,20 @@
+---
+title: SP0420
+description: "setBody was handed entity %s, which has no body: declare one with body and collider on its Entity, its prefab or its spawn."
+---
+
+The engine makes this error in `setBody`, from `@spawnite/engine/core`. Its declaration's comment says what the call requires.
+
+## The message
+
+Each `%s` is a value the error names where it is thrown, such as an entity, a name or a number:
+
+```text
+setBody was handed entity %s, which has no body: declare one with body and collider on its Entity, its prefab or its spawn.
+```
+
+## What to do
+
+The message says what was asked, what was wrong and what to change. The line under it, which starts `Spawnite:`, names the system that ran, the engine call, the entity and the tick where the engine knew them.
+
+When the message and that line do not explain the failure, it may be a bug in the engine. [Errors and bug reports](/engine/testing/errors/) says how to reproduce it and write a bug bundle.