Touches a prim in-world by using its coordinates.
This command tries to locate the object with specific coordinates, and touches it. The approximate coordinates may be given, with a specified precision.
The following table shows input values (you send them with the API call) and returned output values.
|Input basic parameters:|
|apikey||yes||Your personal developer's API key.|
|botname||yes||Your bot's SL login.|
|secret||yes||Bot access code of your bot.|
|dataType||no||Set to "json" to get JSON reply instead of URL-encoded string|
|custom||no||The custom data (string) to be passed back to caller script. This value will be returned back to the caller in HTTP response.|
|x||yes||the X coordinate (integer or float)|
|y||yes||the Y coordinate (integer or float)|
|z||yes||the Z coordinate (integer or float)|
|precision||no||the precision. Default 0.5 meters|
|result|| OK - command completed successfully|
FAIL - command failed
|resulttext||Detailed reason for the failure.|
|custom||The value from input "custom" parameter. See above.|
This command tries to find a prim somewhere close to the given coordinates. The precision can be set manually.
The default precision 0.5 meters. This means that object closer than 0.5 meters will be touched (only one object will be chosen though).
This command implies the same limitations as touch_prim:
- The distance. Bot view range is around 32 meters, so it may not see the object on the other side of the sim.
- The load time. Bot loads its surroundings within a minute after teleporting. Thus, give it 1-2 minutes to load all nearby prims. However, after loading, all new nearby prims are being detected immediately.
Bot tries to touch the prim at <214.5,127,32> with a precision of 1 meter:
InstAPI: See this query in API Test Suite: click here
(Miss an API call or parameter? Submit your request in forum)