HeliControl

Well, by default, the cooldown is 24 hours. The default limit is 5, and that resets as soon as the server's time goes to the next day. If you want them to be able to call 10 per day with no cooldown, don't give them a cooldown permission, just the limit.

For example:

Code:

oxide.grant user Shady helicontrol.limit.1

This would grant me the first limit, which by default, is 5. Without granting the cooldown permission, I can now call it 5 times today with no cooldown.

 

OK thanks. And permission must be on each player, or there is a permission for all the players of a sudden?

 

You can grant it to the default group which will give it to all players, if that's what you want, an example is:

Code:

oxide.grant group default helicontrol.limit.1

 

Hey, little issue.

When you have a cooldown for /callheli and the server restarts this happens:

 

I think I have a fix for this, but I can't test it right now. I'll let you know later, thanks for the report.

 

Code:

(18:50:03) | [Oxide] 10:50 [Error] Failed to call hook 'OnServerInitialized' on plugin 'HeliControl v1.0.40' (JsonReaderException: After parsing a value an unexpected character was encountered: ". Path 'WeaponList.M249', line 6, position 2.)
(18:50:03) | [Oxide] 10:50 [Debug]   at Newtonsoft.Json.JsonTextReader.ParsePostValue () [0x00000] in <filename unknown>:0
  at Newtonsoft.Json.JsonTextReader.ReadInternal () [0x00000] in <filename unknown>:0
  at Newtonsoft.Json.JsonTextReader.Read () [0x00000] in <filename unknown>:0
  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateDictionary (IDictionary dictionary, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonDictionaryContract contract, Newtonsoft.Json.Serialization.JsonProperty containerProperty, System.String id) [0x00000] in <filename unknown>:0
  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x00000] in <filename unknown>:0
  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x00000] in <filename unknown>:0
  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue (Newtonsoft.Json.Serialization.JsonProperty property, Newtonsoft.Json.JsonConverter propertyConverter, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerProperty, Newtonsoft.Json.JsonReader reader, System.Object target) [0x00000] in <filename unknown>:0
  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00000] in <filename unknown>:0

 

Put your HeliControlWeapons.json file (located in Oxide\data) into jsonlint.com and validate it. The error is almost certainly caused by an invalid config, not the plugin itself.

 

Shady757 updated HeliControl with a new update entry:

1.0.41

 

Hey Shady, so after running the new calltoself permission on a few servers, it seems that /callheli still calls at Random :/

I revoked the old permission from everyone and readded the new one (with the cooldown and limit permissions operating as well) but it still seems to have the same behaviour as the old one. They come onto the map but it's still at a random place. Any ideas on what I could do to fix it?

 

You're right, this appears to be a small code misplacement that I overlooked. Shouldn't be too hard to fix. I haven't tested this, but it might be enough to fix the issue. If they have "helicontrol.callheli" (not self or target) they'll still be able to call it randomly, but if they have just self with limit or cooldown, they should only be able to call it on themselves.

Try the attached one and let me know if it works how you want or how I described. Thanks

 

how to make that always drop m249?

 

Use a custom loot table that has the M249s repeated multiple times in it. If you need an example, I think I can make you one.

 

I did not find the loot table, please show an example

 

You need to enable it by config:

Code:

  "UseCustomLoot": true,

Afterwards at plugin reload it will create an example file in your data folder

 

Thank you all , it worked !

 

Any idea what mod is used to announce who killed the chopper or that it was killed? I see the message after I chop the pieces to bits but not when it crashes. Thanks for your help

 

It's Death Notes, I believe.

 

If I download this plugin, is there a way I can set a minimum amount of players needed online before a Chopper can begin to spawn?

Another question, is there a way to set the spawn timer for the Heli? For example, I could set the time for the Heli to make it only spawn every 2 hours normally?

 

You can set it to spawn however often you want, yes. You can also disable Rust's default spawns, which means it will only spawn whenever the timer goes off, based on the time you have set in the config.

Currently, there's no way to set it so there has to be a certain amount of players online before it spawns.

 

Which part of the config is it that I change to set how often the heli spawns?

Just so I know exactly.