Accepted simulation time in seconds inside a system lifecycle callback.
Signature
time: Numbertime advances with accepted simulation ticks, not wall-clock time or browser rendering. The embedding host chooses the fixed cadence. Failed ticks do not publish new time; this immutable binding is unavailable at module scope.
Examples
Read simulation time
Step once: time is positive after the first accepted tick.
Press Step once to reach the checked result.
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⌘ / Ctrl + Enter
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
true
Rust definition
Machine supplies accepted simulation seconds as Value::Number.
View Rust documentation →Support: runtime