Hands-on examples See the Script API cookbook for complete scripts showing where each API lives and how the pieces fit together.
Authoritative option metadataNavigation option names are defined once in runtime/scripting/NavAPI.js and consumed by both runtime behavior and editor IntelliSense. The machine-readable api-options.json mirrors the documented public option groups.
Vaelis uses options in a few different ways. An explicit option normally wins for that call; otherwise the method uses the component/default value. This matters most for navigation and raycasts.
Pattern
What it means
this.navMoveToward(x,y,160)
Explicit speed is used for this call; other behavior can come from the NavAgent2D component.
Only finalArriveDist changes for this call; unrelated options keep their defaults/component behavior.
nav.findPath(...,{ radius: 24 })
Manual query uses the supplied radius instead of assuming the caller's component radius.
physics.raycast(...,{ exclude:[this] })
The current entity is removed from the query results, preventing self-hits.
Do not invent option names. Vaelis is not drop-in Unity/Unreal/Godot API compatibility. Use the exact option names documented here and in the editor's IntelliSense.
areaCosts is an indexed 16-slot array on the component. Assign a new normalized array back to the property; mutating a previously-read temporary is not enough unless you reassign it.
When generating Vaelis code, prefer the documented option name and shape exactly as listed. Do not invent Unity/Unreal/Godot option names just because they sound familiar; Vaelis’s runtime and IntelliSense contract is the authority.