-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Capture release timer #858
Comments
Closed
Pingout
added a commit
that referenced
this issue
Jul 27, 2023
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
Merged
Pingout
added a commit
that referenced
this issue
Jul 27, 2023
Fixed the first half of the Issue #858
Merged
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
What version of OpenCollar are you using? 8.1
Two strange issues in capture.
This can be tested by following steps:
If the wearer opens and uses the capture menu, then the autorelease timer tick is restarted.
The cause is that llSetTimerEvent(1) is called from Commit(), but this does not happen when settings are restored on a captured collar, but it is called when accessing the menu
This is caused by the test for g-iEnabled on line 183, and a possible fix is the following:
The text was updated successfully, but these errors were encountered: