Solved Signals Dropping Crates Instead of Vehicles

Return to plugin
PistOffBastd

PistOffBastd

Donor
Customer
Im having a little trouble with this one.

F1
adv.givesignal Pist 1942900715
adv.givesignal Pist 1942896432
adv.givesignal Pist 1942906150
adv.givesignal Pist 1942898011

All of the signals are spawning correctly with the correct Skin ID's, Permissions are granted, however every drop is a regular supply crate ,with FancyDrop loaded. Unload FancyDrop and the results are the same. FancyDrop is only used to prohibit the daily vanilla Air Drop.

The plugin config is unmodified.
 
Recent First Highest Voted
By the way, the issue is that you're not including the display name in the command. The correct format is:
adv.givesignal <playerNameOrId|SteamID> <skinId> [displayName] [amount]

But you're running it like this:
Code: 
adv.givesignal Pist 1942900715
adv.givesignal Pist 1942896432
adv.givesignal Pist 1942906150
adv.givesignal Pist 1942898011

You need to include the display name too, which you can get from the config for each drop. For example:
JSON: 
"Supply Signal Skin Id": 1942906150,
"Supply Signal Display Name": "Rowboat"

So the correct command would be: adv.givesignal Pist 1942906150 Rowboat
 
Upvote 0 Downvote
You must log in or register to reply here.
  • About us
    Game4Freak is a Rust plugin marketplace and modding platform offering free and premium plugins for server owners looking to improve and take their servers to the next level.
  • Our
  • Your
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 -