but like @AdiT says ppl can destroy blocks… even if we make block-break false
Then your permissions are wrong. Paste your file so I can inspect it.
actually i dont wanna make another server and do everything to test…
Of course u know better than all of us…
Do your permissions contain those defaults? If not, then you probably loaded your server with PEX in database mode which breaks GP defaults.
yep Pex default is database mode and creates .db file…
Right, the database mode is what causes all the problems with GP permissions as it is buggy and does NOT work the same as file mode.
1 Like
I had a question about the plugin, I’ve downloaded it on my Pixelmon server but no one is able to build without first claiming? and I have it set to =1 which is for survival it says… I don’t know whats wrong? any suggestions or help! I want players to be able to mine its unrealistic to ask them to claim as they try to find ore.
Using greifprevention 47. Some claims can’t be abandoned or deleted, they return Error occured while executing command:null
Alright so i’m having some issues with flags in my adminclaim.
There’s two things i do not want happen, the flags both are set to false and yet they still do happen for some reason.
-
I want fire to not spread.
Example
However the lava still sets fire to the blocks and the wool still sets on fire and is gone after 5min.
Here you can see that fire-spread is set to false, Example. -
I want my water to look like this
Example
However it looks like this, eventhough as you can see the liquid-flow is false
Example
I have no clue why this keeps happening.
This is my PEX permissions file if it might help clarify.
permissions.json
Hope you or someone can help me out.
Thanks in advance
23.08 09:53:22 [Server] INFO Minecraft Forge: 11.15.1.1890
23.08 09:53:22 [Server] INFO SpongeForge: 1.8.9-1890-4.2.0-BETA-1653
23.08 09:53:22 [Server] INFO SpongeAPI: 4.2.0-SNAPSHOT-1f5dac2
23.08 09:53:22 [Server] INFO Minecraft: 1.8.9
griefprevention-1.8.9-2.0.0.59.jar
Not supported. Update to latest build to get help.
Tried updating to 66, everytime I update, players aren’t able to enter claims or break/place in wilderness. Here was my permissions after update http://pastebin.com/vTmW3vt4
You modified the wilderness defaults, follow the instructions in topic to generate a fresh permissions file then move your old perms back in. DO NOT mess with defaults unless you know what you are doing.
I just noticed you still have the lines I told you to remove last time…REMOVE LINES 7-33. There should be NO flag defaults in the DEFAULT USER.
You need to state the exact GP build and SF build you are using.
apologies i forgot.
Minecraft Forge: 11.15.1.1890
SpongeForge: 1.8.9-1890-4.2.0-BETA-1653
SpongeAPI: 4.2.0-SNAPSHOT-1f5dac2
Minecraft: 1.8.9
griefprevention-1.8.9-2.0.0.59.jar
GriefPrevention now has a Discord channel. If you need assistance please visit
2 Likes
How can I disable the spawning of monsters in claims?
And, how can I protect people from any damage in claims?
griefprevention.claim.flag.entity-spawn false
i guess…
u can close pvp but ppl will still get damage from monsters…
Hi! I has connected your skype several times, but you didn’t reply me. = - =
How can I disable pvp in claims? I didn’t find the option to turn on or turn off pvp in config file.