Supply Signal Commands

Supply Signal Commands 1.4.0

Sign in to download
Run commands when a supply signal is thrown
Documentation License Changelog (7) Reviews (2) Version History Discussion

1.4.0

  • Each configured supply signal can now have its own cooldown, preventing repeated command triggers if thrown too frequently.
  • Added optional global and personal messages for each supply signal config.

1.3.2

  • Patched for December 6th Rust update.

1.3.1

  • Fixed placeholder formatting.

1.3.0

  • Added Run Random Command config option, allowing one random command from the list to be executed when a supply signal is thrown, instead of all commands.

1.2.0

  • Added a new config option to send a personalized message to the player when they throw a supply signal.

1.1.1

  • Corrected default config for vanilla supply signal to use an empty string for the item name.
  • Updated logic to prioritize skin id when the item name is empty.

1.1.0

  • Added Display Name config option to filter supply signals by item name, ensuring commands run only for those with the specified name.
Back
Top
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.
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.
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 -