VoxelPort not following admns.txt
Beaupedia opened this issue · comments
For whatever reason even when a player is in admns.txt they cannot manage voxel ports until they are /op. We use a permissions plugin and do not give vanilla op to our Ops, and it's not really an option to start purely for VoxelPort.
When someone who is not /op'd but is in the admins txt tries, they get this error "need to write the help vp".
Please advise.
cricket cricket Hello? Anyone?
That is because we switched it to a permission node, the node is "voxelport.admin"
The wiki mentions absolutely nothing about it. It seems incredibly outdated.
Thanks though, this is much, much more preferable.
So, I've put the permission in and they are still getting "Example: /vp - need to write the help." anytime they try anything.
I'm using 2.049 from http://ci.thevoxelbox.com/job/VoxelPort/6/.
What am I missing?
Hate to be a pain here, but we rely heavily on this plugin. Any suggestions?
Sorry don't know much about voxelport, Ill get cryo back to help
I searched the entire codebase for "Example: /vp - need to write the help", it's not in there.
By any chance do you have multiple Voxelport jars that could be conflicting?
No, just the one.