Join the Game4Freak Discord Get exclusive plugin sneak peeks, talk directly with VisEntities, never miss important updates, and unlock special discount codes!
Build Refund

Build Refund 1.2.0

Sign in to download
Demolishing structures returns some of the original cost
Documentation License Changelog (2) Version History Discussion
Works With
Better No Escape
In vanilla Rust, when a player demolishes a structure, all materials used for construction and upgrades are permanently lost. This can be frustrating when players want to relocate their base, redesign rooms, or fix building mistakes. Build Refund addresses this by returning a configurable percentage of materials used for upgrades when structures are demolished, making the building economy more forgiving while maintaining server balance through the refund percentage setting.



Potential Conflicts

If you're using the No Gibs plugin, this plugin won't work correctly unless Disable Debris Spawn For Demolished Structures is set to false in No Gibs' settings.

Recommended Plugins

  • Extended Demolish -- Lets you change how long players can demolish their own structures.

Permissions

  • buildrefund.use -- Allows players to receive refunds when demolishing structures.

Configuration

JSON: 
{
  "Version": "1.2.0",
  "Refund Percentage": 100,
  "Use Game Tip Notifications": false,
  "Block Refund During Raid Block (Better No Escape)": false
}
  • Refund Percentage-- Controls what percentage of upgrade costs are returned to the player when demolishing a structure.
    • 100 = full refund of upgrade costs
    • 50 = half of upgrade costs returned
    • 0 = no refund (vanilla Rust behavior)
  • Use Game Tip Notifications -- When true, refund information displays as a blue in-game toast notification (small popup). When false, refund information is sent as a regular chat message.
  • Block Refund During Raid Block -- Requires the Better No Escape plugin to be installed and loaded. When true, players cannot receive refunds while raid-blocked, preventing exploitation during active raids.

Localization

JSON: 
{
  "Refund.Summary": "Demolished {0} ({1}). Refunded:\n{2}",
  "Refund.Blocked": "No refund while raid-blocked."
}
  • Like
Reactions: xiaoniu and (Manky)sieve
Author
VisEntities
Downloads
69
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

  • Currency Sync
    Currency Sync
    Syncs player money and reward points across all your servers
  • Durable Attachments
    Durable Attachments
    Prevents durability loss on all weapon attachments
  • Reforestation
    Reforestation
    Keeps forests dense by replanting trees after they are cut down

Latest updates

  1. 1.2.0

    Added config option to display messages as GameTip toasts instead of chat. Improved localization...

  2. 1.1.0

    Added optional support for Better No Escape that prevents refunding resources from demolished...
Read more…
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -