Auto Turret Interference & Settings 1.3.3

Hey mate, can you help me out please.

NullReferenceException: Object reference not set to an instance of an object

NullReferenceException: Object reference not set to an instance of an object

NullReferenceException: Object reference not set to an instance of an object,

When i  unload AutoTurretInterference it stops.

Unloaded plugin AutoTurretInterference v1.1.84 by Scalbox

v had an problem with the console flooding

33 minutes ago, Vwsurfer said:

Hey mate, can you help me out please.

NullReferenceException: Object reference not set to an instance of an object

NullReferenceException: Object reference not set to an instance of an object

NullReferenceException: Object reference not set to an instance of an object,

When i  unload AutoTurretInterference it stops.

Unloaded plugin AutoTurretInterference v1.1.84 by Scalbox

v had an problem with the console flooding

 

I replied to you in the support ticket

 Error while compiling AutoTurretInterference: Argument 3: cannot convert from 'bool' to 'string' | Line: 742, Pos: 101

Read update description....

Update for the next Rust update for Forced Wipe. Don't update before!!!

dsl ok

Hey, I play on a 1mx server and I'm having an issue with your plugin. It checks how many turrets are in a certain area but doesn't consider which team the turrets belong to. On a 1mx or even a 10x server, it's possible for raiders to spam turrets (without even turning them on), causing the defender's turrets to get electrified and disabled. Is there a way to add a team check to identify which team the turrets belong to? And if this is possible, will it affect performance?

6 hours ago, Pitu said:

Hey, I play on a 1mx server and I'm having an issue with your plugin. It checks how many turrets are in a certain area but doesn't consider which team the turrets belong to. On a 1mx or even a 10x server, it's possible for raiders to spam turrets (without even turning them on), causing the defender's turrets to get electrified and disabled. Is there a way to add a team check to identify which team the turrets belong to? And if this is possible, will it affect performance?

Hi
it's not like that, the plugin controls the turrets based on player and/or team. So if you have a limit of 40 turrets, there can be 40 turrets from one team and 40 from another team in one spot.
You probably have something wrong in your configurations or permissions

Furthermore, if the turret is not connected to the power, it is not counted

EnableMessageInfo (If set to TRUE, it shows a message info to the player, when he takes hold of an electricity cable or auto turret, of the commands that the plugin makes available to him)

Can you set it so that it only appears on the turret and not on the cable?

On 10/14/2024 at 3:59 PM, RR_Tappi said:

EnableMessageInfo (If set to TRUE, it shows a message info to the player, when he takes hold of an electricity cable or auto turret, of the commands that the plugin makes available to him)

Can you set it so that it only appears on the turret and not on the cable?

 

Hi
can you make an update to the plugin to allow this.
I will release an update as soon as possible.

I also take this opportunity to inform you and other people, that soon the plugin will also support automatic sharing of turret autorization with clan/team members.
You can enable or disable this configuration in the plugin configuration

On 10/14/2024 at 3:59 PM, RR_Tappi said:

EnableMessageInfo (If set to TRUE, it shows a message info to the player, when he takes hold of an electricity cable or auto turret, of the commands that the plugin makes available to him)

Can you set it so that it only appears on the turret and not on the cable?

 

plugin updated, now only shows the message if you have an auto turret in your hand

Hi all
I am not adding any new features to the plugin at the moment, but if you need any features that you would like to see in the plugin, please write them here in the comments.
Thanks

When players join the team, I often encounter serious server lag Is it because my turret is set to a radius of 250 meters Is it related to the limit of 250 turrets?

 "Plugins Report": [

    "AutoTurretInterference (1.3.0) (253.836 MB), Total Hook Time = 42.367574",

    "AdvanceVehicle (1.5.1) (8.238 MB), Total Hook Time = 38.721996",

    "RaidableBases (3.0.5) (71.137 MB), Total Hook Time = 34.868144",

    "NpcSpawn (2.8.2) (5.262 MB), Total Hook Time = 24.41779",

    "BetterLoot (4.0.4) (259.809 MB), Total Hook Time = 21.129918",

    "Basements (1.0.4) (67.121 MB), Total Hook Time = 16.985361",

    "Clans (3.0.33) (496.535 MB), Total Hook Time = 13.414993",

    "InfoPanel (1.0.9) (286.977 MB), Total Hook Time = 12.82279",

    "StackSizeController (4.1.3) (60.195 MB), Total Hook Time = 8.14294",

    "YouShallNotSpawn (1.1.2) (305.246 MB), Total Hook Time = 7.985421",

    "AutoFarm (3.2.3) (173.352 MB), Total Hook Time = 7.121134",

    "PlayerRanks (2.3.2) (79.605 MB), Total Hook Time = 5.515355",

    "RustRewards (3.2.4) (132.867 MB), Total Hook Time = 4.983444",

    "NoGibs (1.2.0) (80.453 MB), Total Hook Time = 4.848005",

    "NTeleportation (1.8.9) (153.754 MB), Total Hook Time = 4.690478",

    "RaidBlock (1.3.5) (5.113 MB), Total Hook Time = 3.9522",

    "EntityOwner (3.4.1) (4.809 MB), Total Hook Time = 3.256975",

    "BGrade (1.1.6) (6.082 MB), Total Hook Time = 3.084284",

    "QuarryComputer (1.6.4) (6.762 MB), Total Hook Time = 2.976389",

    "BankSystem (1.3.15) (10.391 MB), Total Hook Time = 2.730392",

    "BetterTC (1.5.6) (24.48 MB), Total Hook Time = 2.579141",

    "Vanish (1.9.2) (2.281 MB), Total Hook Time = 2.325906",

    "InstantBarrel (1.3.2) (1.895 MB), Total Hook Time = 2.237118",

    "DeathNotes (6.4.6) (7.039 MB), Total Hook Time = 2.12719",

    "Shop (1.2.72) (42.711 MB), Total Hook Time = 2.077342",

    "Arkan (1.0.21) (7.48 MB), Total Hook Time = 2.020371",

    "NPCKits (1.2.6) (21.785 MB), Total Hook Time = 1.937675",

    "SpawnHeli (3.1.1) (5.875 MB), Total Hook Time = 1.706401",

250 meters is way too much, and could cause a small lag when joining a clan, as the player must be authenticated on all the turrets placed by the clan. However, in all my tests, with up to 500 turrets, I've never had any such problems; the turrets are assigned to the player in a background process.

On 2025/7/13 at PM7點09分, Scalbox said:

250公尺太遠了，加入部落時可能會造成輕微的延遲，因為玩家必須在部落放置的所有砲塔上進行身份驗證。不過，在我所有的測試中，最多有500個砲塔，我從未遇到過這樣的問題；砲塔是在後台進程中分配給玩家的。

After my test, it is true that placing many turrets will cause the server to freeze or even disconnect when new teammates join the team. I placed 500-1000 turrets but not all of them were turned on. And I used automatic authorization. If possible, I hope to add a setting for batch authorization of turrets.

14 minutes ago, 賴宜佑 said:

After my test, it is true that placing many turrets will cause the server to freeze or even disconnect when new teammates join the team. I placed 500-1000 turrets but not all of them were turned on. And I used automatic authorization. If possible, I hope to add a setting for batch authorization of turrets.

open support ticket,  but

this has never happened in my tests because turrets are shared one at a time.

And in any case, you're making an extreme case, since no team ever gets to have 500/1000 turrets.

33 minutes ago, 賴宜佑 said:

My server is 10X PVP The total number of turrets on my server is more than 1,000 Some turrets that exceed the team may have 200-500 When they are changing shifts It will cause my backend to reload all the automatically authorized turrets and the server will freeze

https://umod.org/plugins/automatic-authorization

38 minutes ago, 賴宜佑 said:

https://umod.org/plugins/automatic-authorization

This plugin doesn't perform any checks on the group, the number of turrets within a given radius, etc.
It has nothing to do with my plugin, which performs checks to manage interference.
In any case, if you have any problems, please open a ticket!

I just checked, and the plugin does not do anything when a player joins the clan, do the same test again by disabling the plugin  automatic-authorization

and also open ticket