LuckPerms

LuckPerms

41.4k Downloads

Command Blocks giving 2 items instead of 1

Bladesteel opened this issue ยท 34 comments

commented

We are making an amusement park style server, and we would love to use LuckPerms. However, when it is installed in the server, even without any permissions added, anyone who is not /op on the server receives 2 items instead of 1. Here is an example command for giving an item:

/minecraft:give @ a[level=1,x=-36,y=65,z=439,distance=..2] minecraft:nether_brick

(we use levels to make sure the ride is actually ridden, and the levels are removed at the same time as the item is recieved)

Any help would be great!

(edit: put a space between @ and a, because it looked like it was marking someone's profile)

commented

Except it does? Adding LP makes the command not work as intended. Thus it is a problem with LP.

And LP making a vanilla minecraft command function incorrectly is a big problem! You can say all you want that "having a perm plugin wouldn't affect a vanilla command", except it does!. This was the ONLY plugin on the SPIGOT SERVER, and it caused this issue. Thus is it a problem with this plugin.

I came here for help, and all I'm getting is "adding LP wouldn't change any vanilla commands" which is what I spent all day testing for. Removing plugins, adding them. I made the ONLY plugin on the server LP and it still gave that issue. So you can say "it's not LP's issue" all you want, the proof says otherwise.

commented

This is just nonsense. The vanilla give command works fine on our 1.15 paper server regardless if LP is installed or not.

commented

So instead of giving help, people just come to insult and say "this isn't an issue with LP". Nice community you got here. Almost makes me glad we are unable to use LP.

commented

You incorrectly said that LuckPerms is causing your issue. When others (who know far more about the plugin than you do) told you it wasn't, you still insisted that LuckPerms was the issue, instead of asking for other possible causes. I think it's quite unreasonable to be upset with the maintainers of this plugin.

Since the vanilla give command works perfectly on my paper 1.15.2 LuckPerms server, it's clearly not the fault of the plugin, rather than your specific server setup.

commented

We provide the information we have.
You use a vanilla command with a command block that can easly be triggered twice.
A perm plugin would not trigger a command twice. It would only deny access to it, when the player lacks permissions. If the player hss the perm, then the command is executable.
LP won't trigger twice.

From the 2,200+ issues is yours the first one reporting this, which is a clear indicator that it isn't LPs fault.

Also, we try to help and be nice here. You're the person calling others idiots for spending time answering questions and such. Your attitude is bad and you should work on it.

Additionally did you not try at all to provide any usable information like your Server type and version, version of LP and what steps you did to reproduce.

commented

The command block isn't being triggered twice. If you had actually read the OP, you would have seen that anyone who isn't opped on the server gets 2 items. Meanwhile anyone who is opped gets 1 item, as intended. And you neither requested, nor asked about steps of reproduction, server type, version or anything either. You just said "its not LP's responsibility".

commented

Now is a great time to "provide any usable information like your Server type and version, version of LP and what steps you did to reproduce."

commented

LP is not responsible for these commands

commented

So LP, a minecraft plugin, isn't responsible for LP not working with a minecraft command?
Sounds pretty stupid to me.

commented

The command you mentioned is not a LP command at all, so yes it is not in LP responsability to handle it.

Additionally is LP not a Minecraft plugin, but rather a Spigot, Sponge or Nukkit plugin depending on the server you run.

commented

Yes it is? If the plugin cannot work with normal minecraft commands, then it shouldn't be part of minecraft.

Additionally, Spigot, Sponge, and Nukkit are all how you run Minecraft servers!

ADDITIONALLY it is ONLY an issue when LP is installed. Not any other time. Thus, it is an issue with LP. Not minecraft.

commented

See my updated comment.
LP is not a minecraft plugin.
Vanilla Minecraft does not run plugins. You use a modded Server like Spigot for this.

And LP handles permissions. Period.
Everything outside of this (chat, handling commands, etc.) is not the job of LP.

Please learn the basics about plugins and modded servers before assuming that a Permission plugin would handle everything.

commented

See my updated comment. This is a LP issue, as it is only an issue when LP is installed.

commented

It doesn't matter if LP is installed or not. If a command worked before LP (and especially a vanilla command) then having a perm plugin wouldn't affect it in such a way.

commented

If you allow them all antibuild permissions (the * wildcard) does it work properly?

commented

One more thing to try is turning verbose on, and noting exactly which permissions are checked when an OP does the thing and exactly which permissions are checked when a non-OP does the thing. If the op is getting true for a node that comes back as false or undefined for the non-OP, try giving that node to the non-OP group

commented

We don't want them to have access to all antibuild permissions. Only wooden (oak) pressure plates, buttons, trapped chests, and ender chests. All permissions are turned off for non-opped people (except the 4 items set to true), and when someone is Opped they have all permissions true.

commented

I completely understand, but this is likely an issue with a missing permission or something like it, so testing with the user having a wildcard node would be valuable, as it will let us know if it's an op vs non op thing or a missing permission thing

commented

Its a missing permission. Having all the permissions permitted gives the single item as expected. I wouldn't know which permission it could be.

commented

One more thing to try is turning verbose on, and noting exactly which permissions are checked when an OP does the thing and exactly which permissions are checked when a non-OP does the thing. If the op is getting true for a node that comes back as false or undefined for the non-OP, try giving that node to the non-OP group

This is the next logical step. Compare the permissions checked for an op player to those of a non-OP player

commented

Glad it's resolved!

commented

Thank you. The issue was that essentials.build.drop.* had to be given. Otherwise the /give command from a command block gives 2 items instead of 1.

commented

That might be worth reporting to EssentialsX btw!

commented

Sooo? Did you manage to find the source of the problem?

I'm assuming that you've closed this issue because it wasn't being caused by LP, but please correct me if that's wrong.

commented

I closed it because I received no help. We moved onto another permissions plugin.

commented

Sorry, this isn't a 24/7 helpdesk. At least give me a chance to reply... it hadn't even been 24 hours.

The replies above, whether they're correct or not, don't constitute an official response.

I'd like to see the bug resolved so it doesn't affect other users, so would appreciate your cooperation. However if you've given up that's fine too I guess.

commented

Of course.
Doing some more research with the plugins on the server, the issue is caused by both EssentialsXAntibuild and LuckPerms (I thought essentialsX would be fine, as that is what is recommended on the webpage for LuckPerms, and worked with permissionsex).. Only when both plugins are on the server does this issue happen. Once I figured this out, I attempted to allow default rank to use command blocks, as well as to use powered rails (setting essentials.build.interact.command_blocks and .powered_rails to true), and that didn't work.