Additional Bounty permissions

Question

Additional Bounty permissions

Zoneman1972 opened this issue 7 years ago · 10 comments

Zoneman1972 commented 7 years ago

Hi there. I would like to lodge a request for an extra permission node that can allow my admins to be bounty exempt.
Also, an option to disable the auto bounty login notification for admins or vanished players.
And finally, an admin command that allows us to remove the random bounties from players.
Thanks heaps for all your hard work on this plugin. Me and my players absolutely love it!

Rocologo · Answer 1 · 2017-08-20T14:46:32.000Z

Hi, thank you for creating a ticket.

I have added some new features for you:

V5.0.7

Added new features. Ticket 287 (#287)
Vanished players is exempt from Random Bounties
Players with permission "mobhunting.bounty.randombounty.exempt" is exempt from Random Bounties.
Players with permission "mobhunting.bounty.admin" can delete random bounties

please test the snapshot on my jenkins server, build 453 or newer
https://fractal.lindegaard.one:8181/job/MobHunting/

Zoneman1972 · Answer 2 · 2017-08-21T13:44:34.000Z

Hi, I have done a days worth of testing and there are still some small bugs that need adjusting.
This message appears when you put a bounty on http://prntscr.com/gb0zh4
It looks like its not picking up the correct setting for amount.

This message shows when I tried to remove a players random bounty- http://prntscr.com/gb1ex9
The bounty was not removed however.

And this one shows that a players bounty couldn't be removed as it was claiming there was no bounty when there was. http://prntscr.com/gb1x5g And again the same opposite player message when removing a bounty.

As for the player in vanish not getting a random bounty applied, from what I saw, this appears to be working. I will test again tomorrow and report to you afterwards.

Thanks again for all your hard work.

Rocologo · Answer 3 · 2017-08-21T21:36:37.000Z

So I spend two hours on fixing this... I did not have much time to test the stuff, but I hope I am almost there now.

Please test build 458
https://fractal.lindegaard.one:8181/job/MobHunting/

PS. 10000000 is the same as 1.0E7 - it is a scientific notification (1.0E7 = 1.0*10⁷). But now it is formatted (i hope)

Rocologo · Answer 4 · 2017-08-24T07:45:25.000Z

I have released V5.0.7, with the above fixes included. Let me know if you find any bugs.

Zoneman1972 · Answer 5 · 2017-08-24T14:20:57.000Z

Hey there, Thanks again for working so hard on this plugin. I hate to say it but I am getting an error in the console. This is the message that I am getting: 25.08 00:16:04 [Server] WARN [MobHunting] Plugin MobHunting v5.0.7 generated an exception while executing task 166 25.08 00:16:04 [Server] INFO java.lang.NoClassDefFoundError: Could not initialize class one.lindegaard.MobHunting.compatibility.HerobrineCompat 25.08 00:16:04 [Server] INFO at one.lindegaard.MobHunting.MetricsManager$39.getValue(MetricsManager.java:406) ~[?:?] 25.08 00:16:04 [Server] INFO at org.mcstats_mh.Metrics.postPlugin(Metrics.java:449) ~[?:?] 25.08 00:16:04 [Server] INFO at org.mcstats_mh.Metrics.access$400(Metrics.java:61) ~[?:?] 25.08 00:16:04 [Server] INFO at org.mcstats_mh.Metrics$1.run(Metrics.java:242) ~[?:?] 25.08 00:16:04 [Server] INFO at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftTask.run(CraftTask.java:71) ~[spigot-1.12.jar:git-Spigot-596221b-9a1fc1e] 25.08 00:16:04 [Server] INFO at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:52) [spigot-1.12.jar:git-Spigot-596221b-9a1fc1e] 25.08 00:16:04 [Server] INFO at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_131] 25.08 00:16:04 [Server] INFO at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_131] 25.08 00:16:04 [Server] INFO at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]

…

On 24 August 2017 at 17:15, Rocologo ***@***.***> wrote: I have released V5.0.7, with the above fixes included. Let me know if you find any bugs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#287 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AbEX14HbHFK30JL2492ofXaklHVJfVPlks5sbSoVgaJpZM4O8W4b> .

Rocologo · Answer 6 · 2017-08-24T20:13:51.000Z

Do you have the Herobrine plugin installed on your server?

Rocologo · Answer 7 · 2017-08-24T20:16:36.000Z

I think you can fix this by disable integration to the Herobrine plugin in config.yml.

I will fix this in v5.0.8

Zoneman1972 · Answer 8 · 2017-08-24T21:09:02.000Z

No I don't. I didn't even know there was a herobrine plugin

…

Sent from my iPhone

On 25 Aug 2017, at 5:43 am, Rocologo ***@***.***> wrote: Do you have the Herobrine plugin installed on your server? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Zoneman1972 · Answer 9 · 2017-08-24T21:09:44.000Z

Ahhhhh ok I see. Let me check and get back to you

…

Sent from my iPhone

On 25 Aug 2017, at 5:46 am, Rocologo ***@***.***> wrote: I think you can fix this by disable integration to the Herobrine plugin in config.yml. I will fix this in v5.0.8 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Rocologo · Answer 10 · 2017-08-25T04:30:36.000Z

V5.0.8 is released. Try this instead.

Share to