Discussion in 'Archived: Plugin Releases' started by mbaxter, Aug 16, 2011.
You should look into documentation for permissions plugins.
can you make an unvanish command? That way I can run it for everyone on login. Sometimes this glitches and people logged in already vanished or something. It does not happen all the time. And I have the permissions setup correctly I think?
edit: btw I think its because they log out vanished with vanish.vanish permission, then when they log back in they no longer have that permission, due to the fact that on my server i limit the use of this plugin so people can use it as a spell. It only grants them the perm for a split second.
logging in vanished is only possible if you have the vanish.silentjoin permission. Make sure you're not giving that to people.
hi excuse me but i've found a bug with mchat: if a player join vanished with a prefix in mchat and he unvanish him cause a bug like this:
VNP assumes you don't have any other plugins messing with the tab window. I will add code for a mChat hook you can utilize that will solve this.
I didn't, I even have it set to false for everyone
Permissions seem to be working weird for me, sometimes they work sometimes they don't. Vanish.vanish always works fine though.
I'm using permissionsBukkit
Well, I can assure you that there is no issue with permissions handling in VNP. We've done enough testing to be sure of that. If a player joins vanished they joined with vanish.silentjoin set to true.
tnks a lot ç.ç
When is it gonna work whitout spout =) ?
fake join and quit wont work for me
What permissions relevant to these features have you given yourself?
all of them is there one that makes it so you dont see those messages?
Please list your permissions
And what permissions plugin are you using? And are you opped.
im opped and im using permissionsEX
That is your problem. Deop yourself, log out and back in, and things should work. Or update to the latest dev build (not 1.17) of pex.
ok ill try that do you know if pex has a exclude permissions node? i tried -- node.here
but it didnt work
i deopped me and installed the last dev build still doesnt work for me.
EDIT by Moderator: merged posts, please use the edit button instead of double posting.
Read the documentation
1.8.7 released. Contains what I'm almost positive will make that very rare crash go away.
Sadly the Spout team refuse to support the spout plugin anymore.
Got a nice error from Spout some say it's your plugin. Wondering if you could take a look at the ticket.
I'm upset for the following reasons;
#1. Permissions won't work. I tried giving negative permissions so my admins don't spawn vanished when they login to the server. This worked until recently with the 1.8.7 update. I'm using the latest PEX dev version. CB 1611, Spout 650.
#2. When players vanish, they create clones of themselves and "tab" makes a clone of them as well. Requires client restart for the fix.
#3. No way to /msg or /tp to anyone who is vanished. You should have a safety mechanism so you can backdoor that feature if you need an admin to teleport to a vanished admin.
Yup, as I stated (just now) in the issue, it's a confirmed bug but the Spout team will not fix it.
#1 Sounds like you have a permissions problem. Best talk with them about it. Nothing has changed in permissions management from this end.
#2 Tab cloning is odd, but I'm looking into it more as I have one other report of it. Could use a screenshot. As for phantom players, that's stranger, sounds like a packet didn't get through to you that should have. Could be related to your permissions issue (I hope!)
#3 You're using Essentials, right? I believe essentials has overrides for the hidden property, I think for teleportation it is /tpo instead of /tp and I'm not sure about a /msg replacement.
Afforess != the Spout team, he's a single member of it. Pull requests are always considered as well.
Should clear potion effects on a vanish, incase an admin is slowed or something
My problem is, that vanish does not prevent item pickup after using the /vanish command.
If I use /np oder /nf it says "You cannot toggle that".
(I'm Admin + OP)
And you're using PEX 1.17 or older. Deop yourself or upgrade to a dev build of PEX
Or fix your permissions.
I'm not a fan boy, nor am I wanting to argue with anyone, so any debates over plugin/permission design philosophies I won't take part in.
I'm using 1.17, VNP 1.8.7 and bukkit 1572, and all the VNP commands I've tried have worked without fail. PEX is a complicated (sometimes overly complicated ) permissions manager, and it's pretty easy to misconfigure it. Either I'm not using it to it's full extent and missing something (quite possible), or something isn't set up right on the server side. Am I the only one who doesn't seem to have problems with VNP and PEX?
You're not op. That's the bug with 1.17 and earlier. Ops don't get permissions assigned, they instead only get what permissions ops get. For many plugins this isn't an issue. VNP sets many permissions to default to false even for ops, such as the toggle feature as described in the issue above. So, this now-solved-but-not-released PEX bug becomes apparent in VNP and a few other plugins
OK, I'm being serious here, please help me understand.
Not Op... as in my player name isn't in the ops.txt file? Ok, I'll add it, make sure allow-ops is on in the PEX config, and test...
Oh, I think I see... If I add myself to the ops.txt file and remove all nodes from the group I am in (which would normally prevent me from doing anything under PEX), I can vanish and unvanish, but the vanish.toggle node isn't included, which it is supposed to be, correct?
Separate names with a comma.