Ello MCF! As the title says, I'm having a bit of a problem with LuckPerms not applying permissions to users outside of the overworld. I have my server set up with several separate worlds, one of which is supposed to be just for my brother's kids. I created a group called "thegirls" and was able to give this group permission to access their own world (which I called The Matrix) using the '/mv tp' command. However, once there, we ran into a new problem: They can't seem to interact with anything, despite having the essentials.build and essentials.build.interact perms. Out of desperation, I tried to add modifyworld.* to the group as well, but nothing worked. Their Matrix world was imported into Multiverse using the standard '/mv import' command. I cloned it from the TARDIM by UnlimitedMind42, and everything was normal, save for the item frames not surviving the cloning process. There are no WorldGuard regions or GriefPrevention claims in the Matrix, yet they can't interact with any of the levers, chests, doors, pressure plates, nothing at all.
This has also extended to the TARDIS Plugin that runs on my server, with people not being able to open their Artron Condenser chests or interact with the console to actually power up their TARDIS. It's quite frustrating, and so far I can't find an explanation for it. The only solution I've found is to OP the girls and TARDIS users, which of course is not a viable option. Everything I've found on the internet points to EssentialsAntiBuild as the culprit, but unfortunately, I don't have EssentialsAntiBuild.jar in my plugins folder, so that makes deleting it and restarting the server very difficult.
Finally, when I did 'lp verbose on' and had a friend hit a lever in his TARDIS, the only permissions accessed were NCP's checks, which all returned false. Shouldn't there have been a check for interaction permissions at the very least?
Plugin list: AngryWolves, ChestShop, Citizens, EssentialsX with the Chat, GeoIP, and Spawn modules, GriefPrevention, HeadsPlugin and its API, LuckPerms, Multiverse Core, NCP, TARDIS and TARDISChunkGenerator, Vault, NuVotifier, VotingPlugin, WildTP, Worldguard, and Worldedit.
So yeah, I'm kind of at a loss as to what to do. It's quite perplexing to me. Anyone got any insight?
Edit: I resolved this on my own through trial and error experimentation. If you're having this problem and you're absolutely sure it's not EssentialsAntiBuild, GriefPrevention, or WorldGuard, go into your server.properties file and set spawn-protection to a nice solid 0. Let your antigriefing plugin do the work of actually protecting spawn.
First of all, make sure you are using " /lp editor " to edit your permissions. Next, make sure you have permissions on the default rank. From the default rank tab, or whichever rank you would like to give perms, there should be a column called "World". Click that and type in the name of the world you would like that permission to be set true on.
You might have to add the same permission more than once!
Ay Superblaze27, thanks for the suggestion! Actually ended up solving it on my own. For anyone else who has this problem: If you're absolutely positive you don't have EssentialsAntiBuild.jar in your plugins folder, go into your server.properties file and look for a line labled Spawn-protection. Set that to a nice solid 0 and let WorldGuard+GriefPrevention do the rest. I did this and now everyone can interact with spawn and other worlds as they should.
Rollback Post to RevisionRollBack
Ah, Kirk, my old friend... Do you know the Klingon proverb that tells us revenge is a dish that is best served cold? It is very cold in space...
Ello MCF! As the title says, I'm having a bit of a problem with LuckPerms not applying permissions to users outside of the overworld. I have my server set up with several separate worlds, one of which is supposed to be just for my brother's kids. I created a group called "thegirls" and was able to give this group permission to access their own world (which I called The Matrix) using the '/mv tp' command. However, once there, we ran into a new problem: They can't seem to interact with anything, despite having the essentials.build and essentials.build.interact perms. Out of desperation, I tried to add modifyworld.* to the group as well, but nothing worked. Their Matrix world was imported into Multiverse using the standard '/mv import' command. I cloned it from the TARDIM by UnlimitedMind42, and everything was normal, save for the item frames not surviving the cloning process. There are no WorldGuard regions or GriefPrevention claims in the Matrix, yet they can't interact with any of the levers, chests, doors, pressure plates, nothing at all.
This has also extended to the TARDIS Plugin that runs on my server, with people not being able to open their Artron Condenser chests or interact with the console to actually power up their TARDIS. It's quite frustrating, and so far I can't find an explanation for it. The only solution I've found is to OP the girls and TARDIS users, which of course is not a viable option. Everything I've found on the internet points to EssentialsAntiBuild as the culprit, but unfortunately, I don't have EssentialsAntiBuild.jar in my plugins folder, so that makes deleting it and restarting the server very difficult.
Finally, when I did 'lp verbose on' and had a friend hit a lever in his TARDIS, the only permissions accessed were NCP's checks, which all returned false. Shouldn't there have been a check for interaction permissions at the very least?
Plugin list: AngryWolves, ChestShop, Citizens, EssentialsX with the Chat, GeoIP, and Spawn modules, GriefPrevention, HeadsPlugin and its API, LuckPerms, Multiverse Core, NCP, TARDIS and TARDISChunkGenerator, Vault, NuVotifier, VotingPlugin, WildTP, Worldguard, and Worldedit.
So yeah, I'm kind of at a loss as to what to do. It's quite perplexing to me. Anyone got any insight?
Edit: I resolved this on my own through trial and error experimentation. If you're having this problem and you're absolutely sure it's not EssentialsAntiBuild, GriefPrevention, or WorldGuard, go into your server.properties file and set spawn-protection to a nice solid 0. Let your antigriefing plugin do the work of actually protecting spawn.
Ah, Kirk, my old friend... Do you know the Klingon proverb that tells us revenge is a dish that is best served cold? It is very cold in space...
First of all, make sure you are using " /lp editor " to edit your permissions. Next, make sure you have permissions on the default rank. From the default rank tab, or whichever rank you would like to give perms, there should be a column called "World". Click that and type in the name of the world you would like that permission to be set true on.
You might have to add the same permission more than once!
Leave a thanks if I helped you!
Ay Superblaze27, thanks for the suggestion! Actually ended up solving it on my own. For anyone else who has this problem: If you're absolutely positive you don't have EssentialsAntiBuild.jar in your plugins folder, go into your server.properties file and look for a line labled Spawn-protection. Set that to a nice solid 0 and let WorldGuard+GriefPrevention do the rest. I did this and now everyone can interact with spawn and other worlds as they should.
Ah, Kirk, my old friend... Do you know the Klingon proverb that tells us revenge is a dish that is best served cold? It is very cold in space...