Supply Signal Commands (Legacy Thread)

Return to plugin
Status
Not open for further replies.
Recent First Highest Voted
Failed compiling 'SupplySignalCommands.cs':
1. 'PhoneController' does not contain a definition for 'PositionToGridCoord' [CS0117]
(SupplySignalCommands 52 line 229)
 
Upvote 0 Downvote
Hi VisEntities,

Could you give me some pointers on where I am going wrong with the following.

I can only get the supply signal to call a heli when person who threw it is an admin. My config file is as follows:

JSON: 
{
  "Version": "1.3.2",
  "Supply Signals": [
    {
      "Item Name": "Call Patrol Heli",
      "Item Skin Id": 2920176050,
      "Should Explode": true,
      "Run Random Command ": false,
      "Commands To Run": [
        {
          "Type": "Client",
          "Command": "heli.calltome"
        }
      ]
    }
  ]
}

The Skin ID of the supply drop is the same as the one I have in the kit, as is the kit display name in Kits and the Item Name in this plugins so I'm not sure what I am doing wrong/missing?

Also, should
JSON: 
"Should Explode": true,
stop the actual airdrop coming in?

Thanks in advance,
Rynki
 
Upvote 0 Downvote
Rynki said:
I can only get the supply signal to call a heli when person who threw it is an admin. My config file is as follows:
Click to expand...
The heli.calltome command requires admin privileges. That being said, to call a helicopter to a player, you'd need a patrol helicopter plugin that provides a command for this purpose. Unfortunately that's just how it works with certain native commands

Rynki said:
Also, should "Should Explode": true, stop the actual airdrop coming in?
Click to expand...
If set to false, no pink smoke will appear and the cargo plane that drops the airdrop won't spawn
 
Upvote 0 Downvote
Rynki said:
Ah excellent, got it now. I'll have a tinker.
Any suggestions for a patrol heli plugin that will work well alongside yours?
Click to expand...
There isn't a specific one that comes to mind, anything should work. This plugin works universally with any plugin as long as it provides commands and placeholders for player id, name, etc.

I might consider making a simple plugin to call helicopters if the existing ones are too complex or packed with unnecessary features
 
Upvote 0 Downvote
VisEntities said:
I might consider making a simple plugin to call helicopters if the existing ones are too complex or packed with unnecessary features
Click to expand...
That would be great as the one I use locks to player or team and I really just want one that calls in a heli, so a player lobs a flare and everyone has to be on their toes and avoid or help deal with it :)
 
Upvote 0 Downvote
Rynki said:
That would be great as the one I use locks to player or team and I really just want one that calls in a heli, so a player lobs a flare and everyone has to be on their toes and avoid or help deal with it :)
Click to expand...
Alright, I have added it to my todo list. In the meantime, you can use this simplified version. The command is heli.call2player <playerId> and set its type to Server in the config
JSON: 
      "Commands To Run": [
        {
          "Type": "Server",
          "Command": "heli.call2player {PlayerId}"
        }
      ]
 

Attachments

Upvote 0 Downvote
That is amazing, works perfectly for me will test that with my players later when some of them get online :)
Going back to this one,
JSON: 
"Should Explode": false,
We still get the smoke and the airdrop?
 
Upvote 0 Downvote
Rynki said:
That is amazing, works perfectly for me will test that with my players later when some of them get online :)
Going back to this one,
JSON: 
"Should Explode": false,
We still get the smoke and the airdrop?
Click to expand...
Then you likely have another plugin interfering and manually triggering the explosion
 
Upvote 0 Downvote
Status
Not open for further replies.
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 -