This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
[BUG-8044] [Experience Tools] Improvement - llAgentInExperience() needs to operate independent of parcel/region allowed/blocked experiences to reflect correct data. #15690
Labels
Information
llAgentInExperience() returns a false negative when targeting an agent that is participating in the experience, while they are over land that either does not have the experience allowed or has the experience blocked.
This is an improvement request in response to BUG-7159.
In that jira, Maestro stated, "Changing the spec of llAgentInExperience() is a possibility, but that would run a risk of breaking scripts which rely on existing behavior."
I don't see any way for an application to efficiently rely on this funcition when targeting agents on other parcels, with it's current behaviour.
This issue, along with the recently fixed problems in BUG-6757, BUG-7036 & BUG-7048 had forced me to require participants of my experience to physically be over the same experience allowed parcel as the script. With the latter problems fixed, we now have a means of distinguishing between whether an experience is allowed/blocked on the agent and whether its allowed at the script's location or at the location of the target.
This is why I feel llAgentInExperience() should be updated to explicitly & literally perform as it's namesake implies.
I feel that this is yet, another issue where an experience function was not initially setup to work in a non-estate environment(mainland).
Please consider improving the operation of the function.
Thanks in advance for any consideration.
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: