Difference between revisions of "HTTP API/Bot Commands/set http callback/HTTP Bot Callback Events/nearby avatars"
From SmartBots Developers Docs
| Line 1: | Line 1: | ||
{{DISPLAYTITLE: nearby_avatars (HTTP Callback Event)}} | {{DISPLAYTITLE: nearby_avatars (HTTP Callback Event)}} | ||
| − | <onlyinclude>(DEPRECATED. Use [[HTTP_API/Bot_Commands/nearbyavatars_scan|nearbyavatars_scan] command instead | + | <onlyinclude>(DEPRECATED. Use [[HTTP_API/Bot_Commands/nearbyavatars_scan|nearbyavatars_scan]] command instead).</onlyinclude> |
Reports avatars nearby to the bot. | Reports avatars nearby to the bot. | ||
Latest revision as of 15:01, 26 November 2022
(DEPRECATED. Use nearbyavatars_scan command instead). Reports avatars nearby to the bot.
Incoming and outgoing parameters
The input parameters is being sent to your HTTP script along with this event. Output parameters (if any) should be generated by your script.
| Parameters | Required | Value | |
|---|---|---|---|
| Input parameters: | |||
| action | yes | = nearby_avatars | |
| bot_name | yes | the SL name of your bot | |
| channel | yes | the unique bot id | |
| cid | yes | internal HTTP connection identifier (you can ignore this value) | |
| Input parameters specific for nearby_avatars: | |||
| status | yes | teleport status:
| |
| avatars | yes | the nearby avatars (see below) | |
| heading | yes | Bot's heading (direction it looks), degrees | |
| location | yes | bot's current location, Region/X/Y/Z | |
Avatars list format
The avatars in a list are separated by a new line. Each avatar entry contains the following items:
- UUID
- full SL name
- X
- Y
- Z
The items are separated by ";".
Example:
417732f0-a100-4e2d-a9bf-e381cfd12c3a;CuteGuide Resident;128;12;20
<< return back to HTTP Callback events
