@spawnite/engine 0.1.0-beta.15

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

@@ -0,0 +1,20 @@
+---
+title: SP0077
+description: "startCooldown: the cooldown \"%s\" has %s seconds; pass seconds above 0, or start none"
+---
+
+The engine makes this error in `startCooldown`, 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
+startCooldown: the cooldown "%s" has %s seconds; pass seconds above 0, or start none
+```
+
+## 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/SP0078.md

@@ -0,0 +1,20 @@
+---
+title: SP0078
+description: "\"global\" is the abilities' shared cooldown: import globalCooldown to start or read it, or define your own under another name."
+---
+
+The engine makes this error in `defineCooldown`, 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
+"global" is the abilities' shared cooldown: import globalCooldown to start or read it, or define your own under another name.
+```
+
+## 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/SP0079.md

@@ -0,0 +1,20 @@
+---
+title: SP0079
+description: "\"%s\" cannot name a cooldown: a name is letters and digits starting with a lower case letter, as \"dash\" is."
+---
+
+The engine makes this error in `defineCooldown`, 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 cooldown: a name is letters and digits starting with a lower case letter, as "dash" is. The engine keeps names with a colon, such as "ability:dash".
+```
+
+## 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/SP0080.md

@@ -0,0 +1,20 @@
+---
+title: SP0080
+description: "A behaviour needs a name: defineBehaviour({ name: \"glow\", trait: GlowTrait })."
+---
+
+The engine makes this error in `defineBehaviour`, 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
+A behaviour needs a name: defineBehaviour({ name: "glow", trait: GlowTrait }).
+```
+
+## 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/SP0081.md

@@ -0,0 +1,20 @@
+---
+title: SP0081
+description: "\"%s\" cannot name a behaviour: a name is camel case, starting with a lower case letter, as \"healthBar\" is."
+---
+
+The engine makes this error in `defineBehaviour`, 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 behaviour: a name is camel case, starting with a lower case letter, as "healthBar" is.
+```
+
+## 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/SP0082.md

@@ -0,0 +1,20 @@
+---
+title: SP0082
+description: "Two behaviours are named \"%s\": one of a trait %s, and one of a trait %s."
+---
+
+The engine makes this error in `defineBehaviour`, 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 behaviours are named "%s": one of a trait %s, and one of a trait %s. The name is the behaviour's row in Add behaviour, its key in the dump and its page in the Wiki, 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/SP0083.md

@@ -0,0 +1,20 @@
+---
+title: SP0083
+description: "\"%s\" cannot name a trait: a name is letters and digits starting with a lower case letter, as \"damaged\" and \"heldWeapons\" are."
+---
+
+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" cannot name a trait: a name is letters and digits starting with a lower case letter, as "damaged" and "heldWeapons" are. It is the key the dump writes the trait 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/SP0084.md

@@ -0,0 +1,20 @@
+---
+title: SP0084
+description: "Two definitions are named \"%s\": %s, and %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
+Two definitions are named "%s": %s, and %s. The name is the key the dump, the devtools and a room's stream write a trait under, 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/SP0085.md

@@ -0,0 +1,20 @@
+---
+title: SP0085
+description: "%s sets %s: a trait streams to its owner, stays on the room, is kept by the room and each page, or is predicted on her page, so pick one."
+---
+
+The engine makes this error in `defineTrait`, 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 sets %s: a trait streams to its owner, stays on the room, is kept by the room and each page, or is predicted on her page, so pick one.
+```
+
+## 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/SP0086.md

@@ -0,0 +1,20 @@
+---
+title: SP0086
+description: "%s sets seenByAll without predicted: seenByAll streams a predicted trait to every page, so add predicted: true, or drop seenByAll for a trait every..."
+---
+
+The engine makes this error in `defineTrait`, 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 sets seenByAll without predicted: seenByAll streams a predicted trait to every page, so add predicted: true, or drop seenByAll for a trait every page sees already.
+```
+
+## 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/SP0087.md

@@ -0,0 +1,20 @@
+---
+title: SP0087
+description: "%s sets anyEntity without predicted: anyEntity lets any entity hold a predicted trait, so add predicted: true, or drop anyEntity for a trait any en..."
+---
+
+The engine makes this error in `defineTrait`, 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 sets anyEntity without predicted: anyEntity lets any entity hold a predicted trait, so add predicted: true, or drop anyEntity for a trait any entity holds already.
+```
+
+## 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/SP0089.md

@@ -0,0 +1,20 @@
+---
+title: SP0089
+description: "%s read \"%s\" on a page, where it never is: the trait is serverOnly, so only the room holds it."
+---
+
+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 read "%s" on a page, where it never is: the trait is serverOnly, so only the room holds it. Move the read to a system whose entry leaves runsOn out, which runs on the room alone. Where the page needs the value too, define the trait without serverOnly so the room streams it, with predicted: true where her page predicts it on her character, or with local: true so the room and the page each keep their own.
+```
+
+## 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/SP0090.md

@@ -0,0 +1,20 @@
+---
+title: SP0090
+description: "No character spawned."
+---
+
+The engine makes this error in `placeCharacter`, 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
+No character spawned.
+```
+
+## 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/SP0091.md

@@ -0,0 +1,20 @@
+---
+title: SP0091
+description: "sendPlayerInput() got an entity with no Input: pass the character that placeCharacter or spawnCharacter returns."
+---
+
+The engine makes this error in `sendPlayerInput`, 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
+sendPlayerInput() got an entity with no Input: pass the character that placeCharacter or spawnCharacter returns.
+```
+
+## 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/SP0092.md

@@ -0,0 +1,20 @@
+---
+title: SP0092
+description: "Cannot stack %s of \"%s\" in a slot: not a whole count"
+---
+
+The engine makes this error in `registerItem`, 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
+Cannot stack %s of "%s" in a slot: not a whole count
+```
+
+## 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/SP0093.md

@@ -0,0 +1,20 @@
+---
+title: SP0093
+description: "registerItem: \"%s\" heals by %s; a heal takes a finite number from 0."
+---
+
+The engine makes this error in `registerItem`, 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
+registerItem: "%s" heals by %s; a heal takes a finite number from 0.
+```
+
+## 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/SP0094.md

@@ -0,0 +1,20 @@
+---
+title: SP0094
+description: "registerItem: \"%s\" pays %s coins; a coin effect takes a finite number from 0."
+---
+
+The engine makes this error in `registerItem`, 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
+registerItem: "%s" pays %s coins; a coin effect takes a finite number from 0.
+```
+
+## 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/SP0095.md

@@ -0,0 +1,20 @@
+---
+title: SP0095
+description: "Cannot move %s of an item: the count must be a whole number above 0, such as 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
+Cannot move %s of an item: the count must be a whole number above 0, such as 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/SP0096.md

@@ -0,0 +1,20 @@
+---
+title: SP0096
+description: "Await loadRapier as well as loadRecast before baking a navmesh with a hull collider: Rapier decides which body a hull's points build."
+---
+
+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
+Await loadRapier as well as loadRecast before baking a navmesh with a hull collider: Rapier decides which body a hull's points build.
+```
+
+## 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/SP0097.md

@@ -0,0 +1,20 @@
+---
+title: SP0097
+description: "The collider parts do not merge"
+---
+
+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
+The collider parts do not merge
+```
+
+## 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/SP0098.md

@@ -0,0 +1,20 @@
+---
+title: SP0098
+description: "No map is mounted to name \"%s\" on; frame all or a point"
+---
+
+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
+No map is mounted to name "%s" on; frame all or a point
+```
+
+## 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/SP0099.md

@@ -0,0 +1,20 @@
+---
+title: SP0099
+description: "Cannot frame \"all\": the scene draws nothing yet."
+---
+
+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
+Cannot frame "all": the scene draws nothing yet. Frame a point, or wait for the scene to draw.
+```
+
+## 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/SP0100.md

@@ -0,0 +1,20 @@
+---
+title: SP0100
+description: "No prop, region, path or view named \"%s\"; the map has %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
+No prop, region, path or view named "%s"; the map has %s
+```
+
+## 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/SP0101.md

@@ -0,0 +1,20 @@
+---
+title: SP0101
+description: "The map resolves to more than %s materials, the most the ground draws: %s."
+---
+
+The engine makes this error in `resolveGroundMaterials`, from `@spawnite/engine/devtools`. 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
+The map resolves to more than %s materials, the most the ground draws: %s. Paint or rule fewer.
+```
+
+## 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/SP0102.md

@@ -0,0 +1,20 @@
+---
+title: SP0102
+description: "The map's terrain holds a %s m grid at %s m cells, but the map is %s m at %s m: run spawnite map terrain resample to rewrite it at the map's grid."
+---
+
+The engine makes this error in `createGroundSurface`, 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
+The map's terrain holds a %s m grid at %s m cells, but the map is %s m at %s m: run spawnite map terrain resample to rewrite it at the map's grid.
+```
+
+## 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/SP0103.md

@@ -0,0 +1,20 @@
+---
+title: SP0103
+description: "The navmesh bake failed: %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
+The navmesh bake failed: %s. Check that the ground has faces a walker can stand on, and that the walker's radius, height and step fit 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/SP0104.md

@@ -0,0 +1,20 @@
+---
+title: SP0104
+description: "No collision shape for the scatter kind %s: the model kit's manifest keeps no hull for it."
+---
+
+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
+No collision shape for the scatter kind %s: the model kit's manifest keeps no hull for it. Pass its shape in bakeObstacles' shapes, or bake the hulls again with pnpm nx models @spawnite/assets.
+```
+
+## 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/SP0105.md

@@ -0,0 +1,20 @@
+---
+title: SP0105
+description: "No trunk in the scatter kind %s: its shape has no faces between the walker's step and its height, where a trunk blocks."
+---
+
+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
+No trunk in the scatter kind %s: its shape has no faces between the walker's step and its height, where a trunk blocks. Give the kind a shape whose trunk spans that band, or let it collide by its whole mesh.
+```
+
+## 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/SP0106.md

@@ -0,0 +1,20 @@
+---
+title: SP0106
+description: "The collision parts do not merge"
+---
+
+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
+The collision parts do not merge
+```
+
+## 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/SP0107.md

@@ -0,0 +1,20 @@
+---
+title: SP0107
+description: "A %s m radius dabs a %s m stroke more than %s times: widen the radius or shorten the stroke."
+---
+
+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 m radius dabs a %s m stroke more than %s times: widen the radius or shorten the stroke.
+```
+
+## 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.