An opaque ECS identity created by spawn.
Signature
Entity stores a Rust u64 handle. IDs are allocated in creation order and cannot be constructed from a Number in the language. Copying a handle keeps the same identity; it does not duplicate the entity or its components.
Use get, set, has and bind with a concrete component type. A handle can outlive its entity, but subsequent access to a removed entity is rejected.
Examples
Share an entity identity
Both handles address the same entity, so the update through alias is visible through item.
Devices
Use this scene on another device
Show a QR code for your glasses, or send a link to another browser. You can keep working here.
Sharing starts a fresh run of the last compiled code. Your editor draft stays here.
Join a session
Open an invitation link, or paste a link or code from the other device.
Connect your other device
On RayNeo, open Menu → Connect live and scan this code. In another browser, open the invitation link below.
Or enter this code:
Waiting for another device. You can keep working while it connects.
Browsers can edit code; every device can use scene controls. The device that started the session controls playback.
Connection settings
A full invitation link includes its host. With a code alone, both devices need the same live host. Pairing setup
main.kj
Loading…Drag to orbit · select to inspect
0 entities
Scene controls
Loading the language runtime…
Output 0
No output.
State
Compile source to inspect its values.
TraceNo execution yet
- Executed source spans appear here.
Expected output
4
Rust definition
Value::Entity(u64); stable interpreter identity, not a pointer or a Rust SDK Entity struct.
View Rust documentation →Support: runtime