Jump to content
Enjoy amazing deals on over a thousand files during our Christmas in July sales event from now until July 15th! ×

1 Screenshot

  • 19.6k
  • 677
  • 73 kB

About Auto Turret Interference

Auto Turret Interference

Auto Turret Interference allows you or your CLAN/TEAM to change the limit of turrets allowed for different players, based on your configurations and assigned roles. You can also make sure that the server or event turrets do not have interference, for example Raidable Base.

In addition, it offers commands to see the statistics on the auto turrets, the possibility of turning the turrets ON and OFF via command, automatic switching ON and OFF of the auto turrets and much more.

It also allows you to change some configurations of the Auto turrets.

Oxide/Carbon compatibility

 

Basically, 4 groups are configured: Default, VIP1, VIP2, VIP3, in this way you can decide the limit of turrets in a given radius based on the group assigned to the user or the group they belong to

Permissions:

  • autoturretinterference.admin – Allows you to execute some commands reserved for administrators
     
  • autoturretinterference.default – Assign configurations: Default
  • autoturretinterference.vip1 – Assign configurations: VIP1
  • autoturretinterference.vip2 – Assign configurations: VIP2
  • autoturretinterference.vip3 — Assign configurations: VIP3

 

COMMANDS

Commands can be typed in chat (by putting the / character in front of the command), or from console.

  • /ati status or /ati st — This command allows the player to see his auto turret statistics and limits
  • /ati status <steamID> or /ati st <steamID> — This command allows the administrator to see another player’s auto turret and limit statistics. To use this command you must have permission: autoturretinterference.admin
  • /ati start or /ati stop — This command allows the player to turn all of your auto turrets ON or OFF. To use this command, you must enable the AllowCommandsToStartAndStop = true property in your configuration or have permission: autoturretinterference.admin
  • /ati start <steamID> or /ati stop <steamID> — This command allows you to turn ON or OFF all turrets of a player based on its SteamID. To use this command you must have permission: autoturretinterference.admin
    • NB: The commands start or stop turns all player auto turrets ON or OFF. If the player is part of a clan/team, all turrets of all members of the clan/team will be turned ON or OFF.

Commands can be added or modified in the configuration file: /oxide/config/AutoTurretInterference.json

Command output example (/ati status or /ati st):

AutoTurretInterference_Image_3-2.png.0197fb977a1b151fcf7eaf9eefecb69a.png


CLAN/TEAM

If you are part of a clan/team and there are 1 more members who have the VIP/ROLE, then all members of the clan/team will benefit.

Example: a clan/team member has the VIP/ROLE to be able to place 40 turrets, in this case all clan/team members will be able to place 40 turrets, but this does not mean that the total number of turrets you can place are added, the limit in in this case there are still 40 turrets, but they can be positioned by all members of the clan/team, rather than just the player who has the VIP/ROLE (in this case we assumed that the VIP/ROLE limited to 40 turrets).

If there are multiple clan/team members who have different VIPs/ROLEs, the best VIP/ROLE will be taken, usually VIP3

Configuration

The settings and options can be configured in the AutoTurretInterference under the config directory. 
The use of an editor and validator is recommended to avoid formatting issues and syntax errors.

 

{
   "Remove interference for server auto turrets: default true (Useful for Raidable Bases or events)":true,
   "PlayerShowTurretCountInfoMessage (Show the player, when he places a turret, a message with the number of turrets that are placed in the radius he is in. Default true.)": true,
   "AllowCommandsToStartAndStop (If set to TRUE, enables commands to allow the player or clan/team to turn their all auto turrets ON or OFF. Default FALSE)": false,
   "EnableAutomaticsStartAndStop (If set to TRUE, the player's turrets will be turned OFF when they go offline and ON when they come back online. For the clan/team, the entire clan must be offline to turn OFF the turrets automatically, but if at least one member of the clan comes back online, all the auto turrets will turn ON. Default FALSE)": false,
   "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)": true,
   "Chat Command": [
     "ati",
     "autoturretinterference"
   ],
   "RolePermission":{
      "default":{
         "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1,
         "Auto Turret target radius 360° instead 180°. Default false": false,
         "Player Auto Turrets without interference limit":12,
         "Radius within which the system checks for other turrets (lower = more turrets)":40
      },
      "vip1":{
         "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1,
         "Auto Turret target radius 360° instead 180°. Default false": false,
         "Player Auto Turrets without interference limit":20,
         "Radius within which the system checks for other turrets (lower = more turrets)":40
      },
      "vip2":{
         "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1,
         "Auto Turret target radius 360° instead 180°. Default false": false,
         "Player Auto Turrets without interference limit":30,
         "Radius within which the system checks for other turrets (lower = more turrets)":40
      },
      "vip3":{
         "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1,
         "Auto Turret target radius 360° instead 180°. Default false": false,
         "Player Auto Turrets without interference limit":40,
         "Radius within which the system checks for other turrets (lower = more turrets)":40
      }
   }
}

 

  • Remove interference for server auto turrets: default true (Useful for Raidable Bases or events): Whether or not to enable interference for server auto turrets. By default it is true, in this way the server's automatic turrets will not have interference, useful for events for example: Raidable Base.
  • PlayerShowTurretCountInfoMessage: Show the player, when he places a turret, a message with the number of turrets that are placed in the radius he is in. Default: TRUE.
  • AllowCommandsToStartAndStop: If set to TRUE, enables commands to allow the player or clan/team to turn their all auto turrets ON or OFF. Default FALSE.
  • EnableAutomaticsStartAndStop: If set to TRUE, the player's turrets will be turned OFF when they go offline and ON when they come back online. For the clan/team, the entire clan must be offline to turn OFF the turrets automatically, but if at least one member of the clan comes back online, all the auto turrets will turn ON. Default FALSE.
  • 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. Default: TRUE.
  • Chat Command: Here you can add, edit or delete Commands can be typed in chat (by putting the / character in front of the command), or from console.
  • Player Auto Turrets without interference limit: How many automatic turrets can a player place within the radius within which the system controls the other turrets, without them interfering. For example, basic rust allows 12 turrets in a radius of 40 meters, you can set for example 30 turrets instead of 12.
  • Radius within which the system checks for other turrets (lower = more turrets)
  • Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit).
    Maximum total number of auto turrets that can be active for player or entire clan/team.
    When Auto Turrets are placed, only a certain number in a certain radius, configured in the configuration file, can be active at a given time.
    However, this does not prevent you from being able to place unlimited Auto Turrets.
    For example, you have set a limit of 20 Auto Turrets in a 40 meter radius, this means that in a 40 meter radius there can be a maximum of 20 Auto Turrets. But if you place another 20 Auto Turrets more than 40 meters away from the first ones, then you can place another 20 active Auto Turrets, and so on.
    With this option you can establish the maximum number of Auto Turrets that can be active regardless of the radius, in order to avoid unlimited Auto Turrets.
    It is always recommended to use this configuration together with the others.
    For example you can decide that the forced maximum Auto Turrets limit is 5 times the number of active Auto Turrets in a given radius, it's up to you to decide. Default -1.
  • Auto Turret target radius 360° instead 180°: If set to TRUE, allows Auto Turrets to scan targets in 360° instead of 180°. Default FALSE


PlayerShowTurretCountInfoMessage EXAMPLE:

AutoTurretInterference_Image_2.png.79b66263c7174d24e7aa3bd87074f865.png


EnableMessageInfo EXAMPLE:

AutoTurretInterference_Image_4.png

Localization

The plugin, therefore the automatic messages and statistics, are translated into the following languages:

  • English
  • Italian
  • Spanish
  • French
  • German
  • Dutch
  • Turkish
  • Russian
  • Ukrainian

Translation files are located in the /oxide/lang folder, here is an example of a /oxide/lang/en/AutoTurretInterference.json translation file.

You can add translations for other languages by adding them to the folder: /oxide/lang


User Feedback

1.2m

Downloads

Total number of downloads.

6k

Customers

Total customers served.

89.2k

Files Sold

Total number of files sold.

1.7m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.