EssentialsX

EssentialsX

2M Downloads

essentials.feed/heal.cooldown.bypass permissions being ignored

mrcoffee1026 opened this issue ยท 13 comments

commented

Information

Full output of /ess version:
2.0.1-b601

Server log (upload logs/latest.log to Gist):

EssentialsX config (upload plugins/Essentials/config.yml to Gist):
feed: 14400 # 4 hour cooldown
heal: 21600 # 6 hour cooldown

Details

Permissions applied to user:

  • essentials.feed.cooldown.bypass
  • essentials.heal.cooldown.bypass

Describe your issue here.
User still required to sait the cooldown amounts between uses of /heal and /feed.

commented

Sounds like a problem with your permissions plugin

commented

Then it would be the only permission that is giving luckperms problems?? I don't think so.

commented

Run /ess debug, then paste the full console output when a player with the bypass permission runs a command with a cooldown while the cooldown is active.

commented

Well therein the problem lies, looks like its no longer checking for that permission it is instead checking for this one:

[15:23:21] [Server thread/INFO]: CoffeeTheMug issued server command: /heal
[15:23:21] [Server thread/INFO]: [Essentials] checking if CoffeeTheMug has essentials.commandcooldowns.bypass - false

Which is not good... since that permission allows bypass for other items which I wiould like the cooldown preserved for like... repair.

commented

Apologies, I did not have time to take a close look at this earlier.

It seems that using the command-cooldowns function will always check the player for that permission (see

&& !user.isAuthorized("essentials.commandcooldowns.bypass")) {
). I'm afraid it's not possible to do what you're trying to do currently.

commented

@AgentTroll Essentials has had a separate heal/feed cooldown for long before EssentialsX added command cooldowns - those cooldowns use the essentials.feed.cooldown.bypass and essentials.heal.cooldown.bypass permissions.

@mrcoffee1026 Please post your full config to Gist as instructed by the template.

.

commented

@AgentTroll That's why I asked for the config - I wasn't sure which cooldown the OP was using.

@mrcoffee1026 The permissions you've set apply to the Essentials heal-cooldown option in your config.yml, not EssentialsX's command-cooldowns system.

To use the bypass permissions for those two commands, comment out the commands from below command-cooldowns and set heal-cooldown in your config.


Side note: "OP" in uppercase in the context of an online discussion can mean either "original poster" or "original post" interchangably. "op" in lowercase in the context of Minecraft servers does indeed mean "operator".

commented

Sorry I misunderstood you. I'll try with the settings adjusted... I take it there is no "feed-cooldown" setting?

commented

https://gist.github.com/mrcoffee1026/05ad1a99b0ff218c8bae1600e8cdc0fc

So far as i know there's not an "ignore essentials.feed.cooldown.bypass and ignore essentials.heal.cooldown.bypass" option in the config file, but have fun.

commented

@md678685 yes I understand, but OP isn't using the heal-cooldown field, but rather the command-cooldowns

commented

I'm not giving everyone OP so they can achieve the old "essentials.feed/heal.cooldown.bypass" permissions, that would be insane. These two permissions simply need to be obeyed.

commented

@mrcoffee1026 They are controlled by the same heal-cooldown setting.

commented

too bad those can't be set independently. Thanks.