RustyWorks RCE Guides

Killfeed & Bountys

Announce every kill on your server with your own custom messages, track PvP/PvE stats automatically, and let staff — or players themselves — put a price on someone's head.

Time: 5 mins to turn on
Difficulty: Beginner
Requirements: Head Admin+ to configure

This is really two connected systems built on the same thing — your server's kill log. Killfeed watches every kill and death (PvP, PvE against NPCs, suicides, environmental deaths) and turns each into a fun message posted to Discord and/or announced in-game, while quietly tracking every player's stats. Bountys sits on top of it: staff can place a reward on a clan's base or a specific player, players can pay to put a bounty on someone else themselves, and the bot automatically puts bounties on players who go on a kill streak or a rampage.

⚠️

Killfeed is off by default

Turn on Killfeed System in settings first — until then, nothing in this module runs: no messages, no stats, no economy payouts, no bounty triggers.

Dashboard Settings

Open Killfeed & Bountys on your dashboard, pick a server, and use the Settings tab:

SettingWhat it controlsDefault
Killfeed SystemMaster switch for the entire module.Off
Discord AnnouncementsPosts each kill to your Killfeed log channel (set on the Server Setup page, not here).On once saved
V2 EmbedsUses Discord's newer container-style layout for kill posts instead of a classic embed.Off
In-Game BroadcastsAnnounces kills in Rust chat via RCON, batched up to 15 kills per message.Off
Combat BlockApplies a short teleport cooldown to both players after a PvP kill.On
Block DurationLength of that teleport cooldown, in seconds.300 (5 min), 5–3600 range
📝

Save your settings once, even if the defaults look right

Until you save Killfeed settings for the first time, the dashboard shows every toggle off except Combat Block — even though some of them default to "on" once a row actually exists. Open the Settings tab and hit Save at least once to be sure your server is running what you expect.

Custom Kill Messages

On the Kill Messages tab you can write your own pool of up to 15 messages per kill type (512 characters each) for PvP Kills, PvE Kills and PvE Deaths — one is picked at random each time. Use these placeholders:

  • {killer} / {victim} — player names
  • {kd} — the killer's PvP kill/death ratio. PvP messages only — in a PvE message it always shows as 0.00, so the editor won't let you save a PvE message that contains it.
  • Rust's <sprite index=0-15> emoji codes and <color=#hex>text</color> — both are in-game only and are automatically stripped before the message reaches Discord.

A "Preset Messages" panel gives you about 23 example lines per type to load in as a starting point and edit to taste.

💬

Presets aren't the bot's real fallback

If you leave a message pool empty, the bot doesn't quietly use those dashboard presets — it falls back to its own separate, smaller built-in set (10 messages per type, different wording). If you want the preset lines in play, load them into the editor and save.

How Kills Are Classified

The bot reads your server's live kill log and sorts every death into one of four categories, each behaving differently:

PvP KillPvE KillPvE DeathSuicide / Environmental
Stats updatedKiller's kills, victim's deathsKiller's PvE killsVictim's PvE deathsNone
Combat Block appliedYes, both playersNoNoNo
Economy rewardPvP Kill Reward to killerPvE Kill Reward to killerNoneNone
Bounty / killstreak engineStreak advances; any bounty on the victim auto-pays to the killerNot triggeredNot triggered — doesn't reset the victim's PvP streakNot triggered
Message pool usedPvP KillsPvE KillsPvE DeathsFixed generic line, not editable

NPC kills (Scientists and similar) are shown as "Scientist" regardless of the exact entity. Deaths to things like falling, drowning, radiation or the cold are treated as environmental — they get a simple fixed message and never touch stats, economy or bounties.

💰

Kill rewards come from the Economy module

The actual PvP/PvE Kill Reward amounts are set on the Economy & Shop page, not here — Killfeed just reads and pays them out. Leave them at 0 there and kills will still be tracked, just without a payout. A kill only pays out if the killer has a linked Discord account.

How Bounties Work

Enable Bountys from /bounty config in Discord — Clan Bounties and User Bounties are switched on independently, each with its own channel for a live, self-updating bounty board.

Clan Bounties

Staff place a bounty on a clan with /bounty clan_add — a grid reference, and a reward that's either a wallet amount, a Discord role, or a kit. Marking a clan bounty Claimed with a winning clan pays every linked member of that clan the full reward (not split between them). Up to 15 active clan bounties per server.

User Bounties

These pay out automatically the moment the bountied player is killed in PvP — all active bounties on that player are summed and paid to the killer in one go. As a safeguard, a bounty won't pay out if the killer and victim are in the same clan.

  • /bounty user_add — staff place a bounty on a player for free.
  • /bounty place_hit — any linked player can pay to put a bounty on someone else themselves (can't target yourself, and the amount comes out of your own wallet).
RustyWorks RCE BOT Today at 9:41 PM
💀 DeadEye_Dan put a bounty on ScrapKing99 for 2,500 eScrap! First one to take them out claims the reward.

Auto-Bounties: Killstreaks & Rampages

With User Bounties enabled, the bot automatically puts a bounty on a player's own head when they get too dangerous:

  • Killstreak trigger — every time a player's live kill streak reaches a multiple of your configured threshold (default every 5 kills), a bounty is placed on them worth your base reward times how many multiples they've hit (default 500 at streak 5, 1000 at streak 10, 1500 at streak 15, and so on). Configure both numbers in /bounty config → User Settings → Edit Kill Limits.
  • Rampage trigger — get 4 kills within 60 seconds and a bonus bounty worth 3× your base reward is added on top. This can stack with a killstreak bounty triggered by the same kill. These numbers are currently fixed and not configurable.

A player's streak only resets when they're killed by another player in PvP — dying to an NPC doesn't reset it.

Discord Commands

CommandWhoWhat it does
/killfeedconfigStaffFull settings panel mirroring the dashboard — toggles, message pools, and player-stats management.
/bounty configStaffClan Settings, User Settings (including Kill Limits) and Rules Settings for the bounty board.
/bounty clan_add / clan_remove / clan_updateStaffAdd, delete or resolve a clan bounty.
/bounty user_add / user_remove / user_updateStaffAdd, delete or mark a user bounty status. Note: marking a user bounty Claimed by hand does not pay it out — only an in-game kill does.
/bounty place_hitEveryone (linked)Pay to put a bounty on another player yourself.

Player Stats

The Player Stats tab on the dashboard (and the matching menu in /killfeedconfig) lets you look up any gamertag's PvP/PvE kills and deaths broken down by Today, This Week, This Month and All-Time, reset one player's stats, or wipe every player's stats for the server — handy right after a wipe.

Prerequisites & Good to Know

  • A Killfeed log channel must be set on the Server Setup page before Discord Announcements will post anywhere.
  • Kill rewards are configured on the Economy & Shop page, not here — set them to 0 to track kills without paying currency.
  • Players need a linked account for kills to earn them currency or bounty payouts; unlinked players are still tracked by gamertag.
  • Clan bounty reward strings only understand a wallet amount, a role, or a kit — anything else silently pays nothing, so always use the reward option the command gives you rather than typing your own.
  • If a victim is currently part of an active mini-event (like Nuketown or Gun Game), that kill is skipped entirely by Killfeed — no stats, no economy, no bounty effect — only a bare "eliminated" line is posted.
  • The live bounty board automatically shows resolved bounties (struck through) for 7 days before they drop off, and edits the same message in place rather than reposting.

Ready to turn on Killfeed?

Head to your dashboard to write your kill messages, or configure it directly with /killfeedconfig.