Search the Community

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. 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): 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":{ "Player Auto Turrets without interference limit":12, "Radius within which the system checks for other turrets (lower = more turrets)":40 }, "vip1":{ "Player Auto Turrets without interference limit":20, "Radius within which the system checks for other turrets (lower = more turrets)":40 }, "vip2":{ "Player Auto Turrets without interference limit":30, "Radius within which the system checks for other turrets (lower = more turrets)":40 }, "vip3":{ "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) PlayerShowTurretCountInfoMessage EXAMPLE: EnableMessageInfo EXAMPLE: 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

FEATURES Turret Fury is a configurable plugin that allows total customization of Auto Turrets, Flame Turrets, Landmines, SAM Sites, Shotgun Traps & Tesla Coils through allowing configuration of; • Damage • Range • Accuracy • Bullet Speed • Trigger Duration • Arc • Explosion Radius • Scan/Sensing Radius • Amount of Pellets (Shotgun Traps) & More!* *See the config below for full list of configurables INSTALL To install, simply copy & paste the plugin (TurretFury.cs) as-is into your server plugins folder: ..\oxide\plugins\ CONFIG To configure; 1. Ensure you have loaded the plugin successfully in your server (this will automatically create a respective config file) 2. Open the plugin config file (TurretFury.json) in your config folder: ..\oxide\config\ 3. Adjust to the desired values 4. Save the config file & reload the plugin (“oxide.reload TurretFury”) (config preview below) { "Auto Turret": { "Enabled": true, "Infinite Ammo": false, "Health (Default 1000)": 1000.0, "Range (Default 30)": 30.0, "Bullet Speed (Default 200)": 200.0, "Aim Cone (Default 4)": 4.0, "Damage Scale (Default 1.0)": 1.0, "Ignored Shortnames": [ "sentry.scientist.static", "sentry.bandit.static" ] }, "Flame Turret": { "Enabled": true, "Fuel Per Sec (Default 0.5)": 0.5, "Health (Default 300)": 300.0, "Range (Default 4)": 4.0, "Arc (Default 45)": 45.0, "Trigger Duration (Default 4)": 4.0, "Damage Scale (Default 1.0)": 1.0, "Ignored Shortnames": [] }, "Landmine": { "Enabled": true, "Health (Default 100)": 100.0, "Min Explosion Radius (Default 2)": 2.0, "Max Explosion Radius (Default 3)": 3.0, "Damage Scale (Default 1.0)": 1.0, "Ignored Shortnames": [] }, "SAM Site": { "Enabled": true, "Requires Power": true, "Health (Default 1000)": 1000.0, "Damage Scale (Default 1.0)": 1.0, "Missile Scan Radius (Default 225)": 225.0, "Vehicle Scan Radius (Default 150)": 150.0, "Ignored Shortnames": [] }, "Shotgun Trap": { "Enabled": true, "Infinite Ammo": false, "Health (Default 300)": 300.0, "Sensor Radius (Default 1.25)": 1.25, "Aim Cone (Default 40)": 40.0, "Pellets (Default 20)": 20.0, "Damage Scale (Default 1.0)": 1.0, "Ignored Shortnames": [] }, "Tesla Coil": { "Enabled": true, "Requires Power": true, "Health (Default 250)": 250.0, "Range (Default 3)": 3.0, "Max Damage Output (Default 35)": 35.0, "Max Discharge Self Damage Seconds (Default 120)": 120.0, "Damage Scale (Default 1.0)": 1.0, "Ignored Shortnames": [] } } PERMISSIONS turretfury.use -- Required for TurretFury configuration to apply to player’s auto turrets FAQ Q: Does the Turret Fury plugin work with any Turret weapon? A: Yes, this plugin works with all Turret deployable weapons, from the revolver to the AK and everything in between. Q: How do I know what range to configure? A: This is completely up to you. A typical range configuration that our community of server admins have been using is 70.0, with some PVE servers increasing to around 100.0 Q: Will increasing Turret range and damage affect the static turrets at monuments? A: By default, this plugin does not affect/apply to any monument turrets (Bandit Camp / Compound / Fishing Village) to avoid nuisance deaths. Note the "Ignore Turret Shortnames" section of the config file addresses this. It is strongly recommended not to adjust this. Q: Does/can the plugin use permissions? A: Yes, we have implemented a number of additional features on the back of community feedback, one of these is a basic permissions system wherein users require the below permission in order to have their autoturrets use TurretFury's configuration; turretfury.use For more information, see https://umod.org/documentation/plugins/permissions/ or (https://codefling.com/plugins/permissions-manager/) Q: Will there be more features added in future? A: Yes, we have more functional improvements and additions coming soon, as well as a roadmap of ideas for future updates. If you have ideas or anything you would like to see included: please share them in the Discussion tab - they will be considered and, with enough upvotes, added to the dev roadmap. Happy turreting, and stay frosty. Discord: Dooogs#2145