Phil Deakins commented at 2023-08-19T14:07:17Z

I've just done a test with 16 avatars, none of which are registered as scripted agents, but 4 of them were returned as scripted agents. That's 25% of false positives.

Peter Stindberg commented at 2023-08-20T07:12:55Z

I am running scripted-agent detection at a scale and distributed, and had not a single false positive so far. In fact, very very few agents who show up with the flag, were not previously known already to be scripted agents. The perecentage of those who were previously known to be scripted agents but do NOT have that flag set is about 0,05 %.

A 25 % false positive rate on your end sounds like an odd cumulation. We can run some tests with my detector, if you like.

Peter Stindberg commented at 2023-08-20T07:14:53Z

As an afterthought: Your two testing agents - what does the SL backend show when you go to https://secondlife.com/my/account/sisa.php ? What do the detectors show when you use that page to toggle the status?

Peter Stindberg commented at 2023-08-20T07:53:51Z

We just tested it with 4 agents Phil has control over, and - to my huge surprise - all 4 showed up as scripted agents in my detector.  So there is defintiely something wrong with THEM - I still don't see this to be a systemic error on a grand scale, because by now I would have noticed (according to what I wrote in https://jira.secondlife.com/browse/BUG-234283?focusedCommentId=712595&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-712595 )

Phil Deakins commented at 2023-08-20T08:49:36Z, updated at 2023-08-20T08:50:26Z

My 4 avatars are available for checking and testing any time. I won't submit a support ticket about them because (I think) that may just get things fixed for them, but the bug would still apply to others. It needs to be dealt with because it is bug that makes the AGENT_AUTOMATED option unreliable.

Phil Deakins commented at 2023-08-21T12:36:06Z

All 4 (now 5) accounts' 'Scripted Agent Status' pages are set as "{}being controlled by a human{}", so that page gets that data from somewhere, probably the accounts' flags. When AGENT_AUTOMATED is requested for each of them, the data is got from somewhere. I suspect it's from the same place - a 2 or 4 byte integer of flags for the agent, so they should return the same  'human operated' result, but they don't. Even changing one of the accounts as a scripted agent, and then changing it back to 'human' doesn't fix the problem.

I am now thinking that perhaps there's another bit in the  agent's flags that has been set for another reason, and when AGENT_AUTOMATED is requested for any agent, a logical AND is performed on the agent's flags and returned accordingly. But the flags are not ANDed with 0x400 (the AGENT_AUTOMATED flag), but with a number that inspects 2 flags - the AGENT_AUTOMATED one and another that is set for another reason. The result would be a non-zero number and a 1 would be returned to the script, wrongly indicating that it's a scripted agent.

If there is another flag that also gets inspected, what is it?, and how can it be changed so that AGENT_AUTOMATED stops returning false positives?

Maestro Linden commented at 2023-08-21T18:13:55Z

Can the agents in question (with a positive AGENT_AUTOMATED flag) visit estates that block scripted agents? This location on the "Linden Homes 2" estate is a good test case:
http://maps.secondlife.com/secondlife/Flummox/133/48/1

Phil Deakins commented at 2023-08-21T19:14:21Z, updated at 2023-08-21T19:16:15Z

4 of the 5 can't get there. Instead they receive the message "{}Sorry, you don't have access to that teleport destination{}".

The other one can get there, but that was caused by me submitting a support ticket for it yesterday. Not to get that account fixed because it genuinely doesn't matter, but in an attempt to find out what's causing the false positives. Somebody clearly misunderstood and fixed it for that account. I'm trying to report a false positives bug that affects the whole of SL, or to at least find out what causes them.

Maestro Linden commented at 2023-08-23T15:55:06Z

To be clear, does any agent currently have AGENT_AUTOMATED enabled who can currently visit
http://maps.secondlife.com/secondlife/Flummox/133/48/1 ? If so, what's the agent name? The support fix to allow the agent to visit bot-banning regions should also cause the agent to no longer have the AGENT_AUTOMATED flag.

Phil Deakins commented at 2023-08-23T16:18:43Z

I'm not sure that I understand the question, Maestro, but...

All of the agents that can't TP to Bellisseria have their scripted agent status set as being "controlled by a human".

When AGENT_AUTOMATED is requested for them, using llGetAgentInfo(), they are all returned as scripted agents.

If it helps, Sparrow Woodland is one of them. She's set as being controlled by a human, but she's returned as a scripted agent by AGENT_AUTOMATED. By all means use that account to check what I mean.

I did a test with one of them by setting it as a scripted agent, and then resetting it as being controlled by a human, but it made no difference to it being returned as a scripted agent.

Maestro Linden commented at 2023-08-23T21:39:44Z

I can confirm that those agents are flagged as scripted agents internally, so the script is returning the correct result (as is the sim refusing entry). If you have an account in this state, I recommend filing a support ticket requesting a fix for the agent.