Kicked for flyhack while vanished
On my server I'm not set as owner, so I'm not able to use the noclip and such, but I am still added to the admin group to be allowed perms for vanish. However, every time I try and go up ladders while vanished, I'm getting kicked for flyhack. Is there a way to get this to stop? I remember there used to be a setting that allowed this to be bypassed, but it seems to have been removed from the config.
If you're in the admin group, then server owner can set the anticheat to only affect people that are not mods/admins.
I am the server owner, I just don't know how to set it to have the admin group not be effected by it. Is there a permission I can give that group? This used to be a setting in the plugin config I thought, but since then I cannot find it.

Basically what I want is to be logged into my server, be in the admin group, and not be kicked while vanished going up and down ladders like I used to not be, but not require being added as an owner to do so.
Drake63
I am the server owner, I just don't know how to set it to have the admin group not be effected by it. Is there a permission I can give that group? This used to be a setting in the plugin config I thought, but since then I cannot find it.

Basically what I want is to be logged into my server, be in the admin group, and not be kicked while vanished going up and down ladders like I used to not be, but not require being added as an owner to do so.

antihack.userlevel 0

0 == users, 1 == admins, 2 == developers, in the past it was by default at 0, but was later changed to be 2. You can change it to 0 so anticheat only checks normal users, not admins.

casualrussian

antihack.userlevel 0

0 == users, 1 == admins, 2 == developers, in the past it was by default at 0, but was later changed to be 2. You can change it to 0 so anticheat only checks normal users, not admins.

Tried this and still getting kicked. I ONLY get kicked while vanished, so I know its vanish that's causing it. Any other time I will not get kicked.

Ill add a line of code to stop anti hack on vanished players. Thanks for the heads up.
Thank you @Whispers88 I remember this being a minor issue before and being able to change a config setting or something to fix it, but can't remember exactly what. With the rework I think it probably was just an overlook because not many people had issues with it.
casualrussian

antihack.userlevel 0

0 == users, 1 == admins, 2 == developers, in the past it was by default at 0, but was later changed to be 2. You can change it to 0 so anticheat only checks normal users, not admins.

If you set it to 0, then it shouldn't affect admins at all. You can drop from the sky and nothing will happen.
casualrussian
If you set it to 0, then it shouldn't affect admins at all. You can drop from the sky and nothing will happen.
yes but while vanished it's changing my status on server somehow. I'm set in the admin group but i removed myself as owner in the server so my name isn't green and i cannot use noclip or anything. While vanish I'll quickly go up a ladder and it will trigger the flyhack eventhough I'm in admin group. I tried it multiple times while vanished and not to see if it was triggered otherwise and it wasn't unless I was in vanish.
Drake63
yes but while vanished it's changing my status on server somehow. I'm set in the admin group but i removed myself as owner in the server so my name isn't green and i cannot use noclip or anything. While vanish I'll quickly go up a ladder and it will trigger the flyhack eventhough I'm in admin group. I tried it multiple times while vanished and not to see if it was triggered otherwise and it wasn't unless I was in vanish.

If you do not have the adming flag (green name etc), then you're not in the admin group. Oxide group name "admin" doesn't mean that you're actually admin, it's just that admins are automatically added to that permission group.

In that case the antihack wouldn't do anything, wait for the developer to fix the issue.

This did this yesterday again while I was added as owner as well. So it is for sure a vanish issue. Has this been fixed in the latest version of vanish?