-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update oc_capture.lsl #969
Conversation
A number of problems are addressed in this Commit: 1) Owner will have the ability to end a capture 2) Owner and Captor are both notified of successful capture and end of capture 3) BLOCKED individuals are prevented from using Capture 4) Wearer can now end a capture using the Capture menu when in a non-Risky capture
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We successfully tested this. Edit: We tested with wearer being owned, but not an owner themselves. Subsequent tests have shown that release through the menu is possible in both "risky" and "non-risky" modes. I have been unable to duplicate the inability to release when capture is in "risky" mode.
In order to only allow unowned wearer to release capture in non risky mode cange line 144 to:
|
This does not compile inworld. The curly brace needs to be a ; |
It compiles for me and does what it should, of course needs more testing. The fragment in the merged file at line 144
This allows anyone with menu access to release the capture,
This allows release only by owners or wearer in non risky mode. |
> > This allows release only by owners or wearer in non risky mode. You are of course correct. I missed a close parenthesis when I copied your changes into the script. I will post the full script with all the changes here so we can do testing and comment. Thanks for your help. |
A revision to PR #969 This update has most of the features of 969 without the bugs, plus an important detail: 1) Owner can now end a Capture Issue #903 2) Owner and Captor are both notified of successful Capture and End of Capture 3) BLOCKED individuals can not Capture Issue #959 4) Wearer can end Capture when Risky is off 5) When Risky is active, the Captive's only escape is using Safeword 6) Fixes a bug in the timer when Captive relogs and Captor leaves the sim Issue #858
Moved to PR #970 |
A number of problems are addressed in this Commit: