Advanced Backup

Advanced Backup 1.5.0

Creates scheduled backups of your server
Documentation License Changelog (8) Reviews (2) Version History Discussion

1.5.0

  • Discord notifications are now always sent after a backup is created, the ZIP file is only attached when it's under Discord's size limit.
  • Added Verbose Console Output config option that lets you suppress the per‑file backup spam and keep only summary messages.

1.4.0

  • You can now back up specific files or folders inside oxide/ and carbon/ without needing to include the whole folder, for example, plugins/Volcano or data/Gamemode/AimTrain.
  • No need to include file extensions like .cs or .json, just use the base name (e.g., Volcano will automatically match Volcano.cs).

1.3.0

  • Added two new settings to help reduce potential server lag during the backup process:
    • Number Of Files Copied Per Batch lets you pick how many files get copied in one go.
    • Pause Duration Between Batches Seconds lets you define the delay between each batch of file copies.
  • Added a new Backup Time setting, allowing you to set an exact time (in HH:mm format) for daily backups. If set (e.g. 15:09), the backup will run at that precise time instead of just following an interval.

1.2.0

  • Updated for Carbon compatibility.

1.1.3

  • Added a retry mechanism for files that are temporarily locked.

1.1.2

  • Fixed an issue where backups would sometimes fail due to files being inaccessible or are in use.

1.1.1

  • Fixed relative path calculation where nested files in whitelisted directories were not being backed up.
  • Added file size validation to skip Discord uploads for oversized backups.

1.1.0

  • You can now specify a custom message in the config that will be sent along with the backup file to Discord.
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. Make sure 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 -