Wow… i think i know what is this problem…
Redownload and try again. Using the latest SpongeAPI. I thinks no problens on latest Sponge server version.
1 Like
Working like a charm
Nvm, fixed the issue
Based on your issue, i have update to the latest claim system of 6.5.4 from my version for bukkit!
This new system you can (6.4.1):
- Players can place the sign in diferent y location and not only in the same y location;
- Can claim putting the sign under the fences;
- The claim loop will check only in max and min y locations of the signs, and not from 0 to 256. This will avoid the problem the server stop to respond on claim a regions, and improve a lot the server performance;
- Added delayed messages, to do not spam messages and not overload server when player cant build or use itens. Will be 1 message/second;
- Added item-use options on globalflags to deny specific usage of itens on worlds, in or out of regions;
Enjoy!
2 Likes
Had a question, how would I go about letting users use the claim wand to make their own regions instead of fences?
On description o added a second method:
With that perm, the user still couldn’t get the claim wand to do so. Hmm
I recommend to give the wand only with kits. With the perm redprotect.own.claim the player can set the two points and claim.
Correct. We use the wand instead and it works like a charm. Follow what @FabioZumbi12 said ^-^
Could anyone possibly give me an example of this: 
I dont want to screw it up.
items=[]
}Use like this:
items=[ "minecraft:item", "minecraft:item" ]
How exactly did you add it to a kit? and does the claim limit perms still work with this?
Claim limit still works just the same as it did before.
And you can simply give them whatever is written in the redprotect configuration. It doesnt need to be enchanted to work 
That being said, make sure to put it on an item that users don’t normally use.
For example I set it on a Pixelmon Aluminum Hoe. Something no one ever uses.
OH and I’d also suggest that you changed the /rp tutorial and remove the redprotect.create permission so they wont get confused.
@FabioZumbi12 Thank you so very much ^-^
1 Like
deny-item-usage {
allow-on-claimed-rps=true
allow-on-wilderness=false
items=[
"minecraft:obsidian",
"minecraft:bedrock"
]
}
If allow-on-claimed-rps is suppose to allow it on player claims, then it is not working.
However, it is successfully blocking placement as it should be.
"minecraft:fire",
"minecraft:lava",
"minecraft:flowing_lava",
Lava and fire also not working with this in or outside of claims
Try to use “minecraft:lava_bucket” or “minecraft:water_bucket”, since the usage of lava comes from lava bucket.
Remeber, this will deny the player usage and not the world to generate and spread lava/fire.
Correct I understand that 
It’s just whatever is on the blacklist players can’t user in their claims OR in the wilderness. Even if the config is set to usable on claims = true.
What about those who use dispensers to lava grief though? This is why I would need to disable it in the world 
Thank you so much for everything you do!
Oh, you is correct, its a error on code that dont allow on claimed rps in any way… On next update will be fixed.
1 Like
Fixing my error on code, i have detected an error on API.
If the player interact with Primary button of mouse, return the correct getInteractionPoint() but if interact with secondary return wrong location, returning numbers around 0 and 1;
I will see if theres something about this on API issues.
As a temporary fix, we will use the player location.
( with wrong locations, the plugin always get null regions, considering wilderness and not allowing the item usage)
On this update:
- Fix item use on claimed rps;
- Add per world changes like lava and water flow and damage, and leaves decay. See glogalflags.yml;
Enjoy!
Have command can’t let player into
other people region protections?