This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
[BUG-228091] llListenRemove() and llSensorRemove() no longer cull queued listen(), sensor() & no_sensor() events. Plus, concerns with other functions. #6245
Labels
Information
It's been a few years since I last tested, but to the best of my memory and from how I've structured my coding in my applications over the last decade, llListenRemove() & llSensorRemove() are supposed to cull any and all queued listen(), sensor() & no_sensor() events.
Today I was curious if this was still the case and I see that it no longer is.
So, even if I look like a fool for possibly forgetting expected behavior, its for the sake of all scripted content on the grid that I am filing this report in hopes that it can be verified on a region running server code prior to the version that changed listen and sensor queue priority.
Here is a test I made for llListenControl() and llListenRemove() testing, the former I do not have any memory over queued event culling behaviour as I mostly use the latter instead:
Here is a test I made llSensorRemove(), use with at least one other object within sensor range:
Here is a test I made for llCollisionFilter(), walk into the test object during the sleep to test:
Other Information
I included llCollisionFilter() because its another function I believe is affected, but I am not as sure as I am with listens and sensors.
My memory on llPassTouches() and llPassCollisions() suggests they should also cull their related events but I'm not as sure as with listens and sensors.
llSetTimerEvent(0.0) isn't affected.
llReleaseControls() isn't affected.
Original Jira Fields
The text was updated successfully, but these errors were encountered: