Inactive [MISC] HeroBounty v1.9.0 - Bounty Board / Hit List [953]

HeroBounty Bounty Board / Hitlist Plugin (v 1.9.0)
Download HeroBounty
Source Code on GitHub This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

Show your thanks! Maintaining plugins like this one is very nearly a full time job. If you enjoy my plugins and appreciate the support I provide, then please consider providing some support of your own. Donating even a tiny amount keeps me motivated and makes me feel loved so go ahead and donate!

HeroBounty adds a whole new dimension to Minecraft PvP. For anyone who has ever been killed by another player and wanted them to pay, but just didn't want to spend the time hunting them down, here is your answer! HeroBounty adds a public hit list to your server, allowing players to anonymously post hits against their enemies for a reward paid out of their pocket. Other players can take on the role of bounty hunter, competing to fulfill bounties and earn the reward.

HeroBounty is a plugin originally developed for the HeroCraft server and is now officially being released to the public.

Enjoy!

Features:

• Anonymously issue hits against your enemies!
• Become a bounty hunter and kill for pay!
• Economy support! Earn in-game money for completing hits! Supports any economy that Register supports.
• And more!

Usage:


The available commands are summarized in the screenshot below. Any parameters in <angled brackets> are required. Any <id#> parameters require the position of the item in the relevant bounty list.



1. Creating a bounty
The /bounty new command posts a new bounty against the player and for the amount provided. A percentage based cut is taken out of the supplied amount; the remaining money is posted as the reward for the hit.



2. Viewing available bounties
The /bounty list command lists all available bounties and their associated rewards. Bounties are sorted from highest to lowest reward. This list keeps both the bounty issuer and the target anonymous. You will not discover the target of the bounty until you accept it.



3. Accepting a bounty
To accept a bounty, use the /bounty accept command and give it the id# of the bounty you'd like. Accepting a bounty incurs a small fee - usually 5% of the award value. Once accepted, you will be given the target's name and the duration of your issued bounty will start to count down. If you fail to kill the target in the given duration, the bounty will be retracted and you will have to purchase it again to continue.



4. Finding a target
To help in finding targets, use the /bounty locate command. This command displays a list of your targets and their approximate. Target locations are rounded to the nearest 100 blocks by default, but this value can be changed in the configuration. These locations are only meant to give you a rough idea of where your target is. It is up to you as the bounty hunter to actually track down the player and complete the hit.



5. Completing a bounty
If you manage to kill a player for whom you have purchased a bounty for, you will be given the reward associated with the hit. The server will be publicly alerted of your success. The target (now dead) will receive a small monetary penalty - usually 5% of the award value.



Installation:

1. Download the latest version of the plugin from the link at the top of this page.
2. Extract the contents of the archive to your /plugins folder.
3. Open /plugins/HeroBounty/config.yml and configure to your liking.
4. Save the modified file and start your server.

Configuration:


All of the settings related to HeroBounty are stored in your /plugins/HeroBounty/data.yml file in YAML format. If you are unfamiliar with YAML, simply follow the pattern found in the config.yml file in the archive you downloaded. The comments in this default file, prefaced with a #, describe what each of the configuration options do.

Permissions:
If found, HeroBounty will make use of TheYeti's Permissions plugin. The three available permission nodes are described below:

• herobounty.new - allows use of /bounty new
• herobounty.accept - allows use of /bounty accept
• herobounty.locate - allows use of /bounty locate
• herobounty.list - allows use of /bounty list
• herobounty.untargettable - makes a player unable to be targetted by bounties

A Message to Users


Thanks for all your support! I will do my best to keep this plugin updated and bug free. If you have any issues or feature requests, feel free to either leave a message here or find me on IRC.

Thanks to Nijikokun for help with making the plugin display nicely formatted messages!

Extra special thanks to my donors: wildshoetwt

Change Log:
Version 1.9.0

• Added Register support. Removed the negative balances option.

Version 1.8.0

• Updated for iConomy 5.0 - thanks to Matterz167

Version 1.7.7

• Added additional NPE checks in Economy
• Added the herobounty.list permission to regulate use of /bounty list

Version 1.7.6

• Updated for CB 612

Version 1.7.4

• Commands now load even if iConomy isn't found (woops)

Version 1.7.3

• Fixed a silly mistake regarding parameterized messages

Version 1.7.2

• Finished majority of internal rewrite
• Made iConomy optional (although it might be buggy without it - please test!)

Version 1.7.1

• Added the bounty.locate permission

Version 1.7.0

• Added Permissions support, including the herobounty.new, herobounty.accept and herobounty.untargettable nodes

Version 1.6.0

• Added compass-based locations with /bounty locate <id#>
• Revamped help menu
• Added command specific help. Type /<command> ? to use it (ie. /bounty new ?)

Version 1.5.0

• Updated to work with iConomy 4.3

Version 1.46

• Removed a debug message I accidentally left in - no more console spam

Version 1.45

• Fixed bounty kills not registering.

Version 1.44

• Revamped the /bounty locate command
• Added new configuration option to adjust location rounding

Version 1.41

• Updated to meet new Bukkit standards
• Fixed long constructor spam
• Now using new damage events

Version 1.40

• Added the option to allow a target's balance to go negative if they cannot afford the death penalty

Version 1.30

• Added the option to pay hunters an inconvenience fee for cancelled bounties

Version 1.20

• Introduced the /bounty locate command
• Added new configuration options regarding location updating

Version 1.10

• Bug fix: players can no longer accept bounties on themselves
• Redone message displays
• Death penalty is now configurable
• Plugin message prefix is now configurable
• Server admins can now decide whether they want target names to show on the bounty list
• Supports plugins that modify names such as iChat

Version 1.01

• A global message is now sent when a new bounty has been placed.

Version 1.00

• Initial public release!

 

Damn right!

 

does this work with essentials economy

 

Yes

 

not to take your thunder DThielke, but he supports register. This means it will support all ECON plugins for the time being! So long as the API for register stays up to date.

 

Hello, thank you for the great plugin!

I was just wondering, is it currently possible to disable the broadcast messages? For instance, we have a group of "Assassins" on our server, that are the exclusive users of this plugin. The guild master sets the bounties, and the Assassins can pick them up. However, the public messages that tell there is a new bounty, as well as telling that a bounty has been fulfilled on x by y, kind of breaks the mystery involved in the whole affair.

I was just curious if it was possible to disable those messages, or if this wasn't an option right now.

Thanks again!

 

NOTICE: I will be away on vacation until June 17th and therefore I will be unable to provide support until then. HeroBounty should continue to work as is with future CraftBukkit builds until that date as I doubt there will be any major API changes.

See you when I get back!

 

Got a pretty serious bug here with the latest version of HB on CB803.

The person that gets killed gets the bounty that was set upon them.

Example:

I set a bounty on "bob" for 5000.
Steve accepts that bounty. The bounty+%fee is not withdrawn.
Steve kills bob.
Bob is awarded the bounty minus the %fee.

It is creating ingame money out of nothing.

 

Dthielke will be back from vacation in about a week. so be ready to harass him

 

Yeah for me the money is working ok except the hunted is getting the reward and not the hunter.

 

awe man. was gonna update this tonight thinking there was a working update :/

 

shitty bug with hunted <-> hunter :-/

 

This plugin changes PVP and bounty plugins. Best one I've ever seen. I don't know if I'll have it on my server.

 

HeroBounty Broken on #860 ?!?!!

If Bounty acceptet, Assassin won't get the reward... just nothing happend after killed.
Still in list etc.

 

I also have an issue with the hunter not gettin the reward after killijg bounty.

 

Also reporting the same issue as the others on 860, hunter not receiving reward.

 

We have to wait until DThielke is back

 

Requesting a feature in the next update, if someone tries to place a bounty on someone who is already on the bounty list, it will tell them there's already a bounty on said person (if it's lower) or replace the old bounty (if it's higher).

It would be nice to have the option (toggled via config?) that instead of replacing/ignoring the old/new bounty, it would add that much to the current bounty.

Example:
John places a bounty on Cody of 100C.
Laura also wants to place a bounty on Cody.
If Laura tries to place one for 50C, it'll error out; if she does 110C, it'll replace the old one.


With the new feature, she could place the 50C and the new bounty on Cody would be 150C.

 

Just in case it matters, the plugin.yml inside the JAR still shows 1.8.0

 

Can you update to 860 ?

 

org.bukkit.command.CommandException: Unhandled exception executing command 'bounty' in plugin HeroBounty v1.8.0
at org.bukkit.command.PluginCommand.execute(PluginCommand.java:37)
at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:128)
at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:287)
at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:712)
at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:678)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:671)
at net.minecraft.server.Packet3Chat.a(Packet3Chat.java:32)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:399)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:309)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
Caused by: java.lang.NullPointerException
at com.herocraftonline.dthielke.herobounty.command.commands.ListCommand.execute(ListCommand.java:30)
at com.herocraftonline.dthielke.herobounty.command.CommandManager.dispatch(CommandManager.java:55)
at com.herocraftonline.dthielke.herobounty.HeroBounty.onCommand(HeroBounty.java:88)
at org.bukkit.command.PluginCommand.execute(PluginCommand.java:35)

 

@DThielke Inactive?

 

Please update dude, that's rly a good plugin.

 

Id love to see this get an update

 

this is probably a stupid question, but does this require an economy plugin?

 

Abandoning us ?

 

Great plugin - hope you come backand support it!

It seems to mostly working with the newer versions of Bukkit, but we are noticing that it will sometimes go wrong and pay the bounty to the person who is killed rather than the person who killed them. Cannot work out what causes this at all

 

Please update this, for the love of god

 

Great plugin had an idea dont know if it will work ... how about being able to designate an area with item or however and then that area of wall will fill with the bountys that have been set by other players so a player can come up and right-click a sign to accept the bounty

i would do this myself but java is not my strong point

hope it helped

 

Would love to see this updated or forked.

 

Like this to show @DThielke that we want this to be updated !