Vanish No Packet

Vanish No Packet

855k Downloads

No announces when visible player quits.

Enitoni opened this issue · 8 comments

commented

So, I'm having this problem. Where I can see them join vanished and quit vanished. However, No matter how much I fiddle with the permissions I can not make it so they announce quit when quitting visible. They simply just... Diseapear from the server. Anyway to solve this?

Here are the permissions for all staff ranks.

- -vanish.nointeract
- -vanish.nochat
- vanish.silentjoin
- vanish.standard
- -vanish.silentquit
commented

I'm going to take a guess and say you're using PEX or GM. If so, can you test this using another perms plugin real quick for me.

commented

Err, I don't really know any other permissions plugin than pex. May you list a few that would work?

commented

Privileges, PermissionsBukkit, YAPP, zPermissions...

commented

Well. I've tried for a while now to get any of those working. And I simply just can't get them working. I've tried out all of those, And I just don't like how they operate. So I'll stay with PEX. Thank you for your time nonetheless! If you can still try to solve this problem, That would be greatly appreciated.

commented

I cannot reproduce it on normal permissions plugins. So I'm asking you to try it out using a normal permission plugin (PEX is not normal, as it breaks into the Bukkit permissions system and throws things around) to see if you still get it.

commented

Well. Is there a workaround? I could give you all the plugins I use, And then you could see if you could reproduce the problem? I'd also like to inform you that my internet is shitty and our server is public, Which makes it hard for me to switch permissions plugins. I'm going to try one more time, If you tell me exactly the plugin you used to try and recreate the problem. We're also running 1.7.2 if that helps.

commented

Three "words" on PEX.

I'd been a PEX user for a long time and my server (almost) never had
issues. That was until the day when I saw this text and test plugin source
proving that PEX really behaved wrongly in some cases - ask mbaxter and he
may have a link for you.

Then I moved to bPermissions. It took me about a week to get familiar with
it and to set up the permission nodes following bPerms philosophy, but in
the end that time was not wasted.

Badly coded injections aside, PEX has this particular way to read and check
permission nodes. Always use negations before the grants. That means, move
the "-vanish.silentquit" nodes above the "vanish..." nodes, in the same way
you did to other negations. If "vanish.standard" grants you the
"vanish.silentquit" node, and it's set above the negation as your YML paste
shows, then it will override the negation.

Try that change, but consider too moving to a better perms plugin.
On 1 Jan 2014 22:47, "Enitoni" [email protected] wrote:

I'd also like to add that, Fiddling with different permissions plugins are
hard for me, As my internet is pretty shitty and our server is public.


Reply to this email directly or view it on GitHubhttps://github.com//issues/534#issuecomment-31433956
.

commented

I am having the same exact issue since updating to v1.7.2 CB builds. Although I have not tracked down the cause, I can say it's not this plugin that's the culprit. I have ran the server with VNP removed and it's still occurring.