BountyBoard

Put a price on any player. The killer claims the pot.

BountyBoard lets your players put point bounties on each other, and the hunter who lands the kill takes the whole pot. A level floor keeps new players safe.

Somebody on your server has it coming. BountyBoard puts a price on their head. Players pile points onto a target, the whole server watches the pot climb, and the hunter who lands the kill takes the lot. I built it for PvP servers that want a reason to go hunting. The kill is checked against the real player list, so a wild dino or a long fall never cashes in on somebody else's work, and a level floor keeps your fresh spawns off the board until they can look after themselves. Run a cluster? All nine maps share one board, speak to Discord once, and the board says which map your target is on today, not the one they ran from.

Supported Features

• Place a bounty: any player drops points on a rival with one chat command, and the pot pays out the moment somebody kills them.
• Type the name they can see: the survivor name over their head, their account name, their EOS id, their player id, their tribe, even a name they have since dropped. Whichever one your player knows is the one that works.
• It reads through the silly names: accents, Cyrillic and Greek letters that only look like ours, the wide letters, the circled ones, the fancy curly ones and xX_tags_Xx all come back to the plain name, so nobody has to work out how to type it.
• It fixes their spelling: type Dob and I answer that the closest player I can see is Bob, then let you take it with one number instead of guessing with your points.
• Two players with one name: when more than one person could be the target I show a short numbered list and you pick, so nobody ever pays to hunt the wrong player.
• Bounty your killer with one word: type /bounty last 500 straight after you die and the price lands on whoever just did it, no name needed at all.
• Pots pool up: when two or more players target the same person their points stack into one fat pot, so a hated player gets very expensive.
• Only a real kill pays: the killer has to match a live player on the server, so a wild dino, a fall or the cold never takes the money, and a kill between tribe mates pays nothing.
• A level floor for fresh spawns: say nobody under level 25 may be hunted and I turn the bounty away and tell the player why, so a beginner can find their feet before the hunt finds them.
• No punching down: cap how far below you a target may be, so a level 100 cannot buy a hit on somebody who just walked out of the water.
• Warn them, or do not: tell the target a bounty just landed on them, or run it stealth so they never see it coming.
• Staff bounties from RCON: put a price on a griefer from your console, a web panel or a bot, let the server pay for it, and write the reason straight into the Discord post.
• One board for the whole cluster: nine maps read each other through the folder your cluster already shares, so /bounty lists every map and your players know where to go hunting.
• The hunt follows them across maps: every map writes down who it has seen, so when I call the Most Wanted out I say where that player is today. Transfer to another map and the board moves with them.
• I shut up when the trail goes cold: if nobody has laid eyes on your target for days I stop naming a map rather than send your hunters somewhere on old news. You pick how old is too old.
• One Discord post that stays right: the board goes up once and then edits itself, so you pin one message instead of scrolling past a new one every few minutes.
• Quiet on restart day: tell me which posts belong to one map and which belong to the cluster, so nine servers coming up in the morning give you one message and not nine.
• Most Wanted shout outs: I call out the biggest open bounty every so often, which keeps the hunt warm without you saying a word.
• Hunter leaderboard: one command shows your best hunters and the points they have claimed, which gets people competing.
• A cut for the house: keep a share of each paid pot as a point sink, or set it to zero and let the hunter take everything.
• Expiry with a refund: a pot nobody claims can expire after a set number of hours, and the points go back to the players who put them in.
• Points with or without a shop: I spend and pay ArkShop points when it is installed, and keep my own point count when it is not, so the hunt runs on any server.
• Every line in your language: choose a language in the config and the words players see come from a plain text file you can open and edit, so your hunters read the board in their own tongue.

Console & RCON Commands

Every one of these works in the in game console and over RCON, and both give you the same answer back. Add --json to any of them and I answer in one line a bot or a web panel can read.

Command	What It Does	Where
BountyBoard.Reload	Read config.json in again with the server still up.	Both
`BountyBoard.Place <player	eos> `	Put a bounty up yourself. The server pays for it unless you name a player to charge.
`BountyBoard.Remove <player	eos>`	Call a bounty off and hand the points back to everyone who paid in.
BountyBoard.List	Show the open bounties, biggest first, a page at a time.	Both
`BountyBoard.Info <player	eos>`	The full file on one player: the pot, who paid in, their level and whether they may be hunted.
`BountyBoard.Where <player	eos>`	Which map is this player on right now, or where did the cluster last see them.
`BountyBoard.Level <player	eos>`	Tell me a player and I tell you their level and whether your rules let anyone hunt them.
BountyBoard.Top	Show the hunters who have collected the most.	Both
`BountyBoard.Hold <on	off>`	Stop new bounties and payouts before a wipe or an event, then let it run again.
BountyBoard.Wanted	Call the biggest open bounty out to the server right now.	Both
BountyBoard.Cluster	Which map am I, which other maps can I see, and who is posting the shared board.	Both
BountyBoard.Board	Push the cluster board to Discord without waiting.	Both
BountyBoard.Export	Hand the whole board back as one line of JSON.	Both
BountyBoard.Clear <eos>	The old name for Remove. It still works, so your old scripts keep running.	Both
BountyBoard.TestDiscord	Fire a test post at your Discord webhook.	Both

Player Commands

The command words live in config.json, so rename them or blank one out to switch it off.

Command	What It Does
/bounty <player> <points>	Put a bounty on a player, or add to a pot that is already open.
/bounty	Show the open bounties on the board right now.
/bountytop	Show the top hunters and the points they have claimed.
/mybounty	Show what is on your own head, and the bounties you have placed.
/bountywho <name>	Look a player up before you spend a thing. It shows who matches, who is on right now and when I last saw the rest.
/bounty last <points>	Put a price on whoever just killed you, without typing their name.
/bounty #1 <points>	Take the first player off the list I just showed you.

Permissions

Node	What It Unlocks
BountyBoard.Use	Lets a player place a bounty. Give it to your default group.
BountyBoard.Admin	Lets an admin run the staff commands from the in game console. Off until you ask for it in the config.

With no Permissions plugin installed, or the check switched off in the config, I fail open and any player may put up a bounty. RCON never asks for a node, because your RCON password is already the whole server.

Config

To see every configuration option, visit our docs. To edit your config files the easy way, open our configuration editor.

Requirements

• AsaApi v2.01 or newer
• A Windows server running ArkAscendedServer through the AsaApi loader
• ArkShop or WShop (optional, works without it, and I keep my own point count instead)
• Permissions (optional, works without it, only needed to say who may place a bounty)
• A Discord webhook (optional, works without it)

Installation

1. Unzip the download and put the BountyBoard folder inside ArkApi/Plugins/. Keep the folder name as it is, because AsaApi matches it against the DLL.
2. Open BountyBoard/config.json and set your point limits, the house cut and your expiry hours.
3. Want new players left alone? Put your lowest huntable level in Levels.MinTargetLevel.
4. Want Discord posts? Open discord.json, set Enabled to true and paste your webhook URL.
5. Start the server through AsaApiLoader.exe and watch ArkApi.log for the loaded line.
6. In game, type /bounty <player> <points> and let your server do the rest.

Support & Help

Stuck on the setup, or a pot that will not pay? Come and find me on Discord and we will work it out: https://discord.gg/8GGaEzWk9p

Frequently Asked Questions

What does BountyBoard do?

BountyBoard lets your players spend points to put a bounty on another player, and pays the whole pot to whoever kills them. Bounties on the same target pool together, the board is public, and a hunter leaderboard keeps score of who collects the most.

How do I install BountyBoard?

Unzip the download and drop the whole BountyBoard folder into ArkApi/Plugins/, keeping the folder name so it matches the DLL. Set your limits in config.json, then restart the server through the AsaApi loader and look for the loaded line in ArkApi.log.

Can I stop new players being hunted?

Yes, and it takes one number. Put 25 in Levels.MinTargetLevel and nobody at level 25 or under can have a bounty put on them. BountyBoard turns the bounty away and tells the player who tried exactly why. You can cap the other end too, and stop a high level buying a hit on somebody far below them.

I run a cluster. Will it post to Discord nine times?

Not any more. BountyBoard works out which map it is from your server launch line, so one config file can go to all your maps. You then say which posts belong to one map and which belong to the cluster, so nine servers restarting give you one message. All your maps also share one bounty board, and one Discord post keeps itself up to date instead of piling up.

My target moved to another map. Does the board keep up?

It does. Every map in your cluster writes down who it has seen and when, so BountyBoard looks your target up across the whole cluster before it shouts. The call out says which map they are on right now, or where they were last seen if they logged off. When the trail gets too old I stop naming a map, because sending ten hunters to the wrong island is worse than saying nothing.

Can several players put points on the same head?

Yes, and it is the best part. Bounties on one target pool into a single pot. Three players drop five thousand each and the hunter who lands the kill collects fifteen thousand, less whatever house cut you decided to keep.

Can a wild dino or a fall pay out a bounty?

No. The killer has to match a real player on the live player list, so the world itself never collects. Tribe mates are blocked as well, and nobody may place a price on their own head, so there is no way to farm your own pot.

Can my staff put a bounty up without logging in?

Yes. Run BountyBoard.Place from your console or over RCON and name the player or their EOS id, so it works even when they logged off. The server can pay for it, you can write the reason into the Discord post, and every one of my staff commands answers in JSON as well, so a Discord bot or a web panel can drive BountyBoard for you.

Does it need ArkShop?

No, and it is not fussy about which shop you run. With ArkShop or WShop installed, bounties spend and pay real shop points, and the Provider setting says which one holds them. Without either, BountyBoard keeps its own point count for each player, so the hunt still works. Add a shop later and I switch over on the next restart.

Was any AI content used in the making of this?

The source code itself was fully created by myself. I do use ChatGPT occasionally to generate product images, and I do use ChatGPT to generate the website descriptions. I do this because I don't speak native English perfectly. I am natively from Sweden, so I use GPT to help translate and write product descriptions. I also will sometimes use GPT to write better English logs. Majority of my Free plugins are open source, so you can review the code yourself and freely fork and edit it to your liking.