Skyler Pancake: would you mind divulging said script functions? do you have any idea how any lsl function is referred to in the source code? if so, would any new code have to be written or could the task be simply making an xml skin button define what's already there?

EnCore Mayne: https://wiki.secondlife.com/wiki/LlGetAgentInfo

if( llGetAgentInfo(UUID)&AGENT_AUTOMATED ) // It's marked as a bot

Journey Bunny: found llGetAgentInfo in Firestorm's and SL's repositories for lllslconstants.h (i'm not a C programmer, just looking if it's referenced anywhere in code as of this moment). nothing for AGENT_AUTOMATED.

there does exist a scripted agent flag tho. AGENT_SCRIPTED shows up once in a lllslconstants.h file.

looks like there's some new code required to have a button/function show up. who knows, maybe a Linden will pick up on this and put it on the Roadmap.

EnCore Mayne: AGENT_AUTOMATED plausibly wouldn't be in a viewerside repo--I think on compile time, it's converted. It's integer 0x4000. The constant referenced would be the function number for llGetAgentInfo.

The other thing you spotted--now we swap places. I'm a scripter, I don't delve into the viewer repos much. I do think that I've seen FS display agents that are identified as bots in a different colored dot on the mini-map. Maybe purple? So it's entirely possible that the viewer alread knows without needing LSL bridge stuff. It simply doesn't tell us in the profile info.

Journey Bunny: news to me. this minimap function is not in 6617.

nonetheless, having an lsl function does not mean it's available within the code of the viewer to graphically show (button on profile, highlighted colour on minimap, glowing beacon hovering over the avatar's head).

let us know which version of the viewer is capable of what you thought you saw somewhere.

EnCore Mayne: Firestorm 6.6.14 (69596) Aug 1 2023 13:18:08 (64bit / SSE2)

Shown in this image, the red arrow is pointing to an account marked as a bot.

Journey Bunny: can you refer to any documentation for that designation? on closer inspection that icon seems to be Gray, indicating someone you have blocked/muted. i don't find anything about bots in their wiki, icon colour or otherwise: https://wiki.firestormviewer.org/minimap

in other words, how did you ever find one of these "registered" scripted agents since we have no way of knowing their status (hence the need for the New Feature)?

EnCore Mayne: Ooooo, It be blocked/muted...hmmm. That one, I knew was a bot. Alright, maybe there a way the viewer knows, and I've been imagining it via having blocked some known bots! I'm willing to say it could well be that. (So, at present, it'd probably only be doable through the LSL bridge script)

And, yess, this needs to be a little robot badge on the Profile, regardless.

Journey Bunny: quite easy to see scripted ones on profile info as bots usually don't have payment activated. It makes me think that maybe I'll add that feature to my hud as the scripting is easy.

Anyway real bots are based on bots servers managing real avatars and on that it is quite impossible to see them as there are tons of tricks to make them behave like real avatars. Those ones will anyway grow up with the development of AI as far as SL becomes big enough to justify such investments.

If you move remotely an avatar even LL can't see it as it is basically an avatar or the same as opening several viewers.

EnCore Mayne "there does exist a scripted agent flag tho. AGENT_SCRIPTED"

That flag actually means that the agent is wearing one or more scripted attachments.

It's unfortunate that LL chose to call bots "Scripted Agents" as it is all too easy to confuse with AGENT_SCRIPTED.

Journey Bunny "Alright, maybe there isn't a way the viewer knows"

FireStorm has an "lslbridge", which is a object with a script that FS automatically adds to an agent's inventory then attaches. FS is then able to send command and queries to it and get various information from it.

So, FS certainly could use the lslbridge to find out if any given agent is a bot.

However, a built in way to supply this information directly to the viewer would be much more efficient. Also, more likely that other viewers implement displaying agents' bot status.

VriSeriphim Resident you are indeed correct. https://wiki.secondlife.com/wiki/AGENT_SCRIPTED

we could try: Profile_Badge_Scripted_Agent to fit in with the other references in FS's textures.xml such as: _Beta, _Beta_Lifetime, Lifetime, _Linden, Pplus_Lifetime, , _Premium_Lifetime, and _Team used in the panel_profile_secondlife.xml

VriSeriphim Resident exactly... I was a bit confused when I read Journey Bunny's comment. I check the SL Wiki to see if anything was changed, but, as of today, it certainly continues to identify that flag as "[carrying scripted objects]"(https://wiki.secondlife.com/wiki/AGENT_SCRIPTED).

Why flag is even being used in 2024 is beyond my understanding — I mean, has scripted attachments these days (even if they don't know!) — so I thought that maybe they had re-assigned that flag to mean something else, namely, "scripted agents" (= bots).

If they did that, well, then the Wiki needs to be changed :)

The last time I checked, AGENT_AUTOMATED the flag that "Identifies an avatar as having been registered with Linden Lab as an automated/scripted agent, i.e. a 'bot." (copying & pasting from the SL Wiki)

Also note the caveat pointed out in the SL Wiki (added by yours truly) — allegedly, was used to flag certain "special" avatars from the Olden Days (e.g. lifetime members, residents joined during the Beta, etc.), so, a small number of false positives possible. It should be rare, though.

It's like the avatar UUIDs from the very first dozen LL employees or so — those are non-v4-compliant UUIDs which clearly have been changed to terminate in 0001, 0002, etc. This, by itself, and from the perspective of LSL, is not really a problem (UUIDs are strings for all purposes, just limited in size and characters), but it means that tools toying around with those UUIDs will fail to validate them properly.