click on the ground to move the player there

Cursor-to-world picking is an INPUT action plus a physics query. Declare an action whose valueType is world_target so the engine resolves the cursor ray to a world point or entity, or use a screen2d action and shapecast from the camera yourself. React in an action handler to move, select, place, or aim. There is no getInputRay helper; the world_target value IS the resolved pick.

click or tap to select and place an object

Cursor-to-world picking is an INPUT action plus a physics query. Declare an action whose valueType is world_target so the engine resolves the cursor ray to a world point or entity, or use a screen2d action and shapecast from the camera yourself. React in an action handler to move, select, place, or aim. There is no getInputRay helper; the world_target value IS the resolved pick.

point and click cursor interaction

Cursor-to-world picking is an INPUT action plus a physics query. Declare an action whose valueType is world_target so the engine resolves the cursor ray to a world point or entity, or use a screen2d action and shapecast from the camera yourself. React in an action handler to move, select, place, or aim. There is no getInputRay helper; the world_target value IS the resolved pick.

aim at whatever the mouse cursor points at

Cursor-to-world picking is an INPUT action plus a physics query. Declare an action whose valueType is world_target so the engine resolves the cursor ray to a world point or entity, or use a screen2d action and shapecast from the camera yourself. React in an action handler to move, select, place, or aim. There is no getInputRay helper; the world_target value IS the resolved pick.

Pointer click and tap to world cursor interaction

The recipe

Author with project_apply_script_semantic_patch using the ai_safe op pack.

Declare the pick action on the InputProfileComponent (see input-mapping-actions-bindings). Use valueType:"world_target" so the engine resolves the cursor ray to a world point or entity and delivers it in the action payload; bind it to a mouse click or a touch tap.
React: addActionHandler { "actionKey":"pick" }. In the body (whole-body GessaScript via replaceScriptFromGessaScript) read the target world position or entity id from the action value.
Click to move: ctx.entity.patchComponent the player TransformComponent position toward the pick, or set a NavAgentComponent destination (see npc-enemy-navigation) so it paths there.
Click to select: from the pick, resolve the entity and mark it selected with writeTypedStateValue (a selectedId field), and toggle a HighlightComponent on it.
Click to place: spawnEntityFromTemplate { "prefabKey": <building> } at the pick, snapping to ctx.terrain.heightAt for ground alignment.
Manual ray (no world_target): use a valueType:"screen2d" action for raw cursor coordinates and ctx.physics.shapecast from the camera along the view ray, or ctx.physics.overlapTest a small shape at the hit, to find what was clicked.

Pitfalls

world_target already does the raycast; do not also shapecast for the same click. Use screen2d plus ctx.physics.shapecast only when you need a custom ray or filter.
The pick resolves on the authority; act on it server-side so all players agree on what was clicked or placed.
Touch and mouse feed the SAME action; add both a mouse and a touch binding so the pick works on desktop and mobile.
A click that must hit only certain things needs a physics filter or a tag check in the handler; the raw pick returns whatever is under the cursor.

Verify

simulation_run (qa.run.start) to prove a click moves, selects, or places at the intended world point.
project_get_graph_snapshot to confirm the pick action handler landed.

The recipe

Pitfalls

Verify

On this page