-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
False Positive (ForceOP) #22
Comments
for this issue to be considered closed, NONE of these and ANY plugin using these methods should be logged as a false positive, while actual force ops are |
That might be the most difficult issue to fix |
@OpticFusion1 The false positive comes from p.setOp not if(p.isOp) |
I'm aware :P |
gonna try and spend a few hours on this issue, it's the biggest issue currently, besides dealing with obfuscated malware.. |
There's been quite a few updates since this, closing. A general issue will be made if a false-positive of this type is found again (however there's definitely going to be another issue opened up due to this definitely not getting fixed) |
None of these throw ForceOP triggers anymore which is nice. I just can't win can i XD |
General Troubleshooting
Issue
Issue Type
Description
Certain plugins cause a false positive due Player#setOp
this is usually used in the following way
setOp
dispatchCommand
setOp
The plugin below is an example of this, more plugins with this false positive can be provided as needed
ActionLibOpenSource(47507).zip
The text was updated successfully, but these errors were encountered: