PvPBounty

PvPBounty

Notice: If you are upgrading from V3 to V4, please delete your config so it can generate a new one!! Ever wanted to assign a bounty on your enemy and pay someone to take him on instead of you, while you sit peacefully in your base and do stuff? Now you can! PvPBounty allows you to do so. For another example, say you got raided on a pvp server, and want revenge on the person who raided you... Assign a bounty to them and then you may entice other users to come murder them for you! :D

Most recent version: Here!

All that aside

PvPBounty is meant to be a PvP oriented bounty system. It runs off both -MySQL- and flatfile, depending on what your preference is.It's main purpose is so that users can post bounties over other user's heads in order to get more people active in pvp and finding others. The bounty system works in this way: A user (whom has permission to post bounties) may post a bounty over another users head. Now at this point, there is an option based on your configuration. You can make it so that users either have to accept bounties to get the reward, or make it so that anyone who kills the person can get the bounty. There are also configurable messages for bounty Assigning and when a bounty is payed out. You can also set the min and max bounties.

Configuration

There is a main configuration file in the plugin's data folder, config.yml.
There are many configuration options, such as the following:

acceptbounty

This says whether or not users will have to accept bounties in order for them to be payed when the bounty's target is killed.

canstackbounties

This is whether or not bounties can stack after a first one over a person is assigned. If they can't, then if a user tries to set a bounty over someone who already has a bounty over their head, they will get a message telling them to wait till the current bounty is payed off.

bam (Bounty assign message) & bountypaymessage

These both have to do with the type of message that gets put out to the server when a bounty is assigned, and when a bounty is payed.
Read the configuration file for more information on this.

canmultikillbounty

This allows users to set diff amounts of people to be killed per bounty.
- This is going to be added in a later release, as it will take some decent recoding of the way this works.

Min/max bounty

These allow you to set a minimum bounty and a max bounty. if you set the maxbounty to -1, it will be considered the highest number possible in java.

DeathPayoutEnabled & DeathPayoutPercent

Death payout has to do with a bit of a user's money being taken upon their death. EG The DeathPayoutPercent is set to 7. That means whenever someone is killed, the person killing them gets 7% of the dieing person's money.

BountyAcceptanceFeeEnabled/Increment

These are in now, they allow for making it so that users can't accept too many bounties and have to pay portions of the bounty to accept them after having so many.

DeathPayoutMessageEnabled

This says whether or not users will be told that they lost/get money upon the death of themselves or someone else.

TrackingEnabled & TrackingFee & Tracking-radius

Assuming you give the users permission to track people they have a bounty on, this is the stuff related to it. The first is self-explanatory, the second is the fee required to track a person, and the tracking-radius is the radius at which tracking stops working if the tracker is within the radius of the target.

Broadcasting-enabled & broadcast-interval

This allows the plugin to broadcast messages about a random bounty every x amount of time. The default is set to 5 minutes. The interval is the # of seconds between each broadcast.

The rest of the configurations are doing with -sql- & factions if it is had. You can read more about them in the yml file.


NOTICE: Do not enable sql support at this point. It is still extremely buggy and chances are it won't work. I will work on getting this working in the coming days. For now, just keep all of the sql stuff as it is by default.

Perimissions

There are currently 3 permissions:
pvpbounty.bountyassign - Gives users the ability to assign a bounty
pvpbounty.bountylist - Gives users the ability to look into the bounty list
pvpbounty.bountyaccept - Gives users the ability to accept bounties
pvpbounty.remove - allows the user with the permission to remove bounties
pvpbounty.track - allows users to track someone that they have a bounty on
pvpbounty.bountynotice - For admins to see when a user is spamming bounties

Commands

/bountyassign [playername] [amount] - this allows you to assign bounties to a person
Aliases: assign, assignbounty

/acceptbounty [person] - allows you to accept a person's bounty
Aliases: accept, bountyaccept

/bountylist [page] - allows you to see the bounties
Aliases: blist

/remove /bounty - shows all the bounty commands.

Dependencies

This plugin only has 1 dependency which may be done away with soon: Vault

That's all

Leave any comments and suggestions in the comments please =).. if you have a issue, please put a ticket about it: http://dev.bukkit.org/server-mods/pvpbounty/tickets/ !