Use these too…
pex group default perm griefprevention.claim.flag.block-break false
pex group default perm griefprevention.claim.flag.block-place false
pex group default perm griefprevention.claim.flag.enter-claim true
pex group default perm griefprevention.claim.flag.exit-claim true
pex group default perm griefprevention.claim.flag.interact-block-primary false
pex group default perm griefprevention.claim.flag.interact-block-secondary false
Making def false means griefprevention false
and if gp made false than default group will override gp
if u still need help after using these commands i can give my skype to help u
@blood I know you said on my 1.8.9 server it was the KEssentials plugins fault but thats not on my 1.10.2 and i get the same error. http://pastebin.com/i78KGsvj
So how do i prevent this from spamming the console?
1.8.9 console never was spammed till i swapped from Polis to GP. Same with 1.10.2
I HAVE A EASY SUGGESTION… to make this plugin easier for admins…
First of all as far as i tried, PermissionService adds permission strings to the permission list when ever it faces the script line…
It means if u have a script line that checks for a permission and that script line is not executed ever, there wont be this permission in the list…
For example:
If i add this plugin to my server,
then if i try to find griefprotection.claim.create permission,
I WONT BE ABLE TO FIND IT…
Cuz if no one tries to make a claim, the script line that checks for griefprotection.claim.create permission will never be executed and added to the permission list…
Many admins are getting confused in situations like this…
SOOO if plugin only checks every permission string in the script at initialition, all permission strings will be added to the list and it will be easier to manage permissions…
I have an AdminClaims, where I use Pressure Plate, but my players can’t use them.
I tried those solutions, and none are working :
Setting /accesstrust public
Setting those flag to true for any : collide-block // collide-entity // interact-block-primary // interact-block-secondary // interact-entity-primary // interact-entity-secondary // item-use
A player can walk on the plate, the sound of the pressure plate activating is “spammed”, but no redstone are activated
So, is def supposed to be set to true, and then use those commands? (Sorry for all the questions, I’m not used to the 1.10.2 config, I’ve been using 1.7.10 for years)
an admins def has to be true to use every command…
but at first join after installing Pex u should give def true from the console…
Pex is overriding op/deop command and making permission managing more detailed but more secure…
Actually these are not the all commands that i wrote above… Pex has autocorrection help and (i suggest u to use this from console) if u try to look for griefprotection permission u will see lots of them… After sending
/pex debug
command, then if u interact or try something that gives “You dont have permission to do this” event, in console there will be a warning that what permission disabling u…
Try" /pex debug " then make someone use that plate…
in console there will be a warning that shows which permission disables players to use pressure plates…
it will be like
griefprotection.claim.flag.interact-block-secondary.minecraft.stone_pressure_plate
wait u didnt set a default group then…
/pex default user parent add group default
/pex rank default add group default
use these first to make a default group that will include every default user…
than use
/pex group default info
if the permissions u gave are not there, then use those block-place,break etc. commands again above…
I already have a default group…the one I gave you the info (perms) to in a previous post. Or was that one done incorrectly and I need to make a new one?
