Core
Helpers for validating reusable authored values once and reusing them later.
Definition is intended for static or rarely changing authored data such as spawn points, collider sizes, arena bounds, or other constants that should cross the validation boundary once and then remain branded afterward.
In game code this is the "content setup" companion to runtime/world setup: validate authored constants early, keep them in carried form, and then reuse them from setup systems, reset systems, or content modules without revalidating on every frame.
// Validate authored constants once when defining the content bundle.
const player = Definition.all({
spawn: Definition.entry(Vector2, { x: 32, y: 48 }),
size: Definition.entry(Size2, { width: 16, height: 16 })
})Helpers that validate one or several authored values through existing constructors.
Validates one reusable authored value through an existing constructor.
Use this for one named authored constant that should cross a constructor boundary now and remain in carried form afterward.
// Validate a single authored position once during content setup.
const playerSpawn = Definition.entry(Vector2, { x: 32, y: 48 })Validates a named record of reusable authored values at once.
Successful entries are returned under the same keys. Failed entries remain keyed so authored-data setup can report exactly which constant was invalid.
Use this when one content bundle or level definition should either validate as a whole or report a structured set of authoring failures.
// Validate one authored content bundle and keep failures keyed by field.
const definitions = Definition.all({
spawn: Definition.entry(Vector2, { x: 32, y: 48 }),
collider: Definition.entry(Size2, { width: 16, height: 16 })
})