Jump to content

Scalbox

Creator
  • Posts

    910
  • Joined

  • Last visited

Everything posted by Scalbox

  1. I was already thinking about creating a new plugin for SAMs. The plugin will have the same functionality as this one but will only be for SAMs. Furthermore, perhaps it is better to keep the limit of SAM turrets based on the radius, this way even bases that have many TCs can still set a limit of turrets limited by the radius. Otherwise based on TCs, they would still be able to put a lot of them. Alternatively I can apply both methods and you can choose in the configurations whether to use the limit based on the TC or the radius
  2. Changed Status from Pending to Closed Changed Fixed In to 1.0.2
  3. Is everything else working or are you having problems?
  4. Yes you can choose as you want, and enable the BuildingBlocked you told me and leave only cooldown. You set the rest of the limits to -1
  5. to add multiple command: { "Enabled":true, "Command":"cmd", "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)":false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)":false, "CooldownSeconds (-1 infinite)":5, "MaxUsagePerMinute (-1 infinite)":5, "MaxUsagePerHour (-1 infinite)":10, "MaxUsagePerDay (-1 infinite)":20, "MaxUsagePerWipe (-1 infinite)":100 }, { "Enabled":true, "Command":"cmd", "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)":false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)":false, "CooldownSeconds (-1 infinite)":5, "MaxUsagePerMinute (-1 infinite)":5, "MaxUsagePerHour (-1 infinite)":10, "MaxUsagePerDay (-1 infinite)":20, "MaxUsagePerWipe (-1 infinite)":100 }, { "Enabled":true, "Command":"cmd", "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)":false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)":false, "CooldownSeconds (-1 infinite)":5, "MaxUsagePerMinute (-1 infinite)":5, "MaxUsagePerHour (-1 infinite)":10, "MaxUsagePerDay (-1 infinite)":20, "MaxUsagePerWipe (-1 infinite)":100 }, { "Enabled":true, "Command":"cmd", "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)":false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)":false, "CooldownSeconds (-1 infinite)":5, "MaxUsagePerMinute (-1 infinite)":5, "MaxUsagePerHour (-1 infinite)":10, "MaxUsagePerDay (-1 infinite)":20, "MaxUsagePerWipe (-1 infinite)":100 }
  6. { "Enabled":true, "Command":"cmd", "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)":false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)":"Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)":false, "CooldownSeconds (-1 infinite)":5, "MaxUsagePerMinute (-1 infinite)":5, "MaxUsagePerHour (-1 infinite)":10, "MaxUsagePerDay (-1 infinite)":20, "MaxUsagePerWipe (-1 infinite)":100 } This is the basic example. Replace Command: cmd with your command, and then apply the limits you want. If you tell me what limit you need, I'll send you a conf for the command
  7. Released plugin 1.0.2
  8. Your container is missing this package: tzdata It should add your provider. But if it doesn't work, I can put a fix for it
  9. Hi, where is your server located? In which country? This is a problem of the provider not having that timezone
  10. Let me know if that's OK or if you run into any problems
  11. Update released
  12. I'm adding it to the plugin, I should release it between now and tomorrow along with other new changes
  13. HI so would you like me to add an option to block the command in case of building blocked? Yes, it is possible, let me know if this is what you need and I will add it to the plugin
  14. Version 1.0.7

    30 downloads

    Command Limiter Info Command Limiter allows you to limit the use of commands that players can use. For each command you can set the cooldown, minute, hourly, daily and wipe usage limits. It also allows you to apply limits in case of Building Blocks, Safe Zones, block the command permanently, etc... Command Limiter is useful for limiting the use of commands from plugins that do not implement a blocking system or implement an inflexible blocking system. Commands Commands can be typed in chat (by putting the / character in front of the command), or from console. /cl reset <steamID> -- This command allows you to reset usage limits for a specific player. To use this command you must have permission: commandlimiter.admin /cl wipe -- This command allows reset all usage limits for all players. To use this command you must have permission: commandlimiter.admin Commands can be added or modified in the configuration file: /oxide/config/CommandLimiter.json Permissions commandlimiter.admin -- Allows the use of commands reserved for administrators commandlimiter.bypass -- Allows you to bypass the command usage limit, but only for commands that have the CanBeBypassed field set to TRUE commandlimiter.bypass.force -- Allows you to easily bypass the command usage limit, regardless of the CanBeBypassed field Default Configuration { "TimeZone": "Europe/London", "Clear data on map wipe": true, "Print usage limits when command is blocked": true, "Chat Command": [ "cl", "commandlimiter" ], "Command Setting": [ { "Enabled": true, "Command": "cmd", "Commands alias": [], "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)": false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)": false, "CooldownSeconds (-1 infinite)": 30, "MaxUsagePerMinute (-1 infinite)": -1, "MaxUsagePerHour (-1 infinite)": -1, "MaxUsagePerDay (-1 infinite)": -1, "MaxUsagePerWipe (-1 infinite)": -1, "BypassPermission (Permissions to bypass the block even if [CanBeBypassed] is set to false)": [] }, { "Enabled": true, "Command": "cmd_2", "Commands alias": [ "alias 1", "alias 2" ], "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)": false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)": false, "CooldownSeconds (-1 infinite)": 30, "MaxUsagePerMinute (-1 infinite)": -1, "MaxUsagePerHour (-1 infinite)": -1, "MaxUsagePerDay (-1 infinite)": -1, "MaxUsagePerWipe (-1 infinite)": -1, "BypassPermission (Permissions to bypass the block even if [CanBeBypassed] is set to false)": [] } ], "VersionNumber": { "Major": 1, "Minor": 0, "Patch": 7 } } TimeZone -- Set the time zone with which the dates will be saved: Default: Europe/London. Clear data on map wipe -- Clear command usage data after a wipe. Default TRUE. Print usage limits when command is blocked -- Prints the command usage limits when a player uses one of the configured commands. 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. Command Setting -- The list of commands on which to apply the usage and cooldown limits must be inserted here. Enabled -- If set to TRUE, limits and cooldowns for this command will be enabled. Command -- The command on which to apply limits and cooldowns. Commands alias -- Here you can specify other commands to block with the same configurations. Useful to block a command, which has several similar or differently named commands, to do the same thing. Or alternatively to block multiple commands without creating different configurations. BlockCommand -- If set to TRUE, the command cannot be used by any player, except for players with the permissions: commandlimiter.admin or commandlimiter.bypass.force. SafeZone. Value [AllowOnly | Allow | Block] (Default Allow) -- Sets whether the command can be used in safe zones: AllowOnly: The command can only be used in safe zones. Block: The command cannot be used in safe zones. Allow: No restrictions for safe zones. BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow) -- Sets whether the command can be used in areas where you have building permissions: AllowOnly: The command can only be used where you do not have building permissions. Block: The command can only be used where you have building permissions. Allow: No restrictions for building zones. CanBeBypassed -- If set to TRUE the command can be bypassed by players with permission: commandlimiter.bypass. CooldownSeconds -- Cooldown for command reuse. MaxUsagePerMinute -- Limit the use of the command for each minute. MaxUsagePerHour -- Limit the use of the command for each hour. MaxUsagePerDay -- Limit the use of the command for each day. MaxUsagePerWipe -- Limit the use of the command for wipe. BypassPermission (Permissions to bypass the block even if [CanBeBypassed] is set to false) -- Here you can specify one or more names, to create permissions to bypass the limit. If the player has at least 1 of these permissions, he can bypass the limit even if the CanBeBypassed property is set to false. Example: if you enter "vip1” as permission, a command called commandlimiter.bypass.vip1 will be created that you can assign to players. Order Application Limits The usage and cooldown limits of the various commands are applied in the following order: Wipe limits -- If the wipe limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. Daily limits -- If the daily limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. Hourly limits -- If the time limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. Limits per minute -- If the minute limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. CooldownSeconds -- The command will be executed if the cooldown has expired, otherwise you will have to wait for the cooldown to reset. LOCALIZATION The plugin are translated into the following languages: English Italian Translation files are located in the /oxide/lang folder, here is an example of a /oxide/lang/en/CommandLimiter.json translation file. You can add translations for other languages by adding them to the folder: /oxide/lang
    $4.99
  15. Version 1.0.3

    11 downloads

    Better Legacy Wood Shelter Limiter and Decay Better Legacy Wood Shelter Limiter and Decay, allows you to change the limit and decay of legacy wood shelters you can place based on group/permission. You can create a group and change the limit and decay for all players, or based on the VIP group. Additionally, if the configured limits are not exceeded, it prevents Rust from destroying the old shelter when a player places a new shelter. Permissions betterlegacywoodshelter.default -- Assign the limits configured in the group: default. betterlegacywoodshelter.vip1 -- Assign the limits configured in the group: vip1. betterlegacywoodshelter.vip2 -- Assign the limits configured in the group: vip2. betterlegacywoodshelter.vip2 -- Assign the limits configured in the group: vip3. Default Configuration { "GroupSettings": { "default": { "Player Max Legacy Wood Shelter limit": 1, "Decay setting": { "Enable decay or not": false, "Decay begins after the last use, after the last time the door was opened": true, "Decay starts after X seconds after the last door opening": 64800, "Inflicting HP damage every X seconds": 3600, "Amount of HP damage to inflict": 20 } }, "vip1": { "Player Max Legacy Wood Shelter limit": 3, "Decay setting": { "Enable decay or not": false, "Decay begins after the last use, after the last time the door was opened": true, "Decay starts after X seconds after the last door opening": 64800, "Inflicting HP damage every X seconds": 3600, "Amount of HP damage to inflict": 20 } }, "vip2": { "Player Max Legacy Wood Shelter limit": 5, "Decay setting": { "Enable decay or not": false, "Decay begins after the last use, after the last time the door was opened": true, "Decay starts after X seconds after the last door opening": 64800, "Inflicting HP damage every X seconds": 3600, "Amount of HP damage to inflict": 20 } }, "vip3": { "Player Max Legacy Wood Shelter limit": 10, "Decay setting": { "Enable decay or not": false, "Decay begins after the last use, after the last time the door was opened": true, "Decay starts after X seconds after the last door opening": 64800, "Inflicting HP damage every X seconds": 3600, "Amount of HP damage to inflict": 20 } } } } 4 groups are created and each group has a base limit set that you can change: default -- Can place up to 1 legacy wood shelter vip1 -- Can place up to 3 legacy wood shelter vip2 -- Can place up to 5 legacy wood shelter vip3 -- Can place up to 10 legacy wood shelter Player Max Legacy Wood Shelter limit -- In this field you can specify the limit of how many legacy wood shelters you can place DECAY SETTINGS You can also define decay settings for various groups Enable decay or not -- Enable decay or not. Decay begins after the last use, after the last time the door was opened -- Defines whether to initiate decay for shelters that are no longer in use. A shelter is defined as "unused" after a certain period of time in which the door is no longer opened or closed. It is advisable to leave it at TRUE, useful for invalidating only the shelters that are no longer used. Decay starts after X seconds after the last door opening -- Determines after how many seconds, a shelter is considered no longer used/decaying. Inflicting HP damage every X seconds -- Once the shelter is considered unused/decaying, set how many seconds to inflict damage on the shelter. Amount of HP damage to inflict -- Defines how much HP to inflict on the unused/decaying shelter.
    $6.99
  16. Version 1.1.4

    261 downloads

    Ultimate Beds, allows you to change the number of sleeping bags and beds you can place compared to the basic limit imposed by rust. You can also decide the time within which a sleeping bag/bed becomes available for spawning and adjust the time for successful spawns, all through various permissions, including VIP permissions. It also allows you to define the distance between the various beds, preventing them from going into cooldown between them. You can set a custom decay for sleeping bags or beach towels, so that sleeping bags or beach towels without maintenance have a longer or shorter decay, based on the configuration for each individual group. Oxide/Carbon compatibility Permissions ultimatebeds.admin -- Permission to execute commands reserved for admins. ultimatebeds.default -- Assign the limits configured in the group: default. ultimatebeds.vip1 -- Assign the limits configured in the group: vip1. ultimatebeds.vip2 -- Assign the limits configured in the group: vip2. ultimatebeds.vip3 -- Assign the limits configured in the group: vip3. These are the groups that are created by default, but you can add and/or edit groups as you wish. For example, if you change the group vip1 to vip_elite, the permission ultimatebeds.vip_elite will be created If you create a new group, for example vipvanilla, the permission ultimatebeds.vipvanilla will be created. COMMANDS FOR ADMIN Commands can be typed in chat (by putting the / character in front of the command), or from console. To use these commands you must have the role: ultimatebeds.admin /ub info -- Shows some information about the state of decay of the sleeping bag or beach towel you are looking at. Default Configuration The configurationcan be found in the file: /oxide/config/UltimateBeds.json { "Chat Command": [ "ub", "ultimatebeds" ], "Chat Prefix": "UltimateBeds", "Disable Bag Gifting. Default false": false, "RolePermission": { "default": { "Priority. (lower = higher priority)": 100, "Player Max Sleeping Bag/Bed limit": 15, "Exclude camper beds from the limit. Default false": false, "Sleeping bag unlock time after placed": 300, "Bed unlock time after placed": 120, "Sleeping bag respawn cooldown": 300, "Bed respawn cooldown": 120, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50, "Sleeping Bag Decay Settings": { "Enable Custom Decay. Default: false": false, "Disable Decay. Default: false": false, "Delay before decay starts. Default: 24 hours": 24, "Duration of decay. Default: 12 hours": 12 } }, "vip1": { "Priority. (lower = higher priority)": 1, "Player Max Sleeping Bag/Bed limit": 60, "Exclude camper beds from the limit. Default false": false, "Sleeping bag unlock time after placed": 60, "Bed unlock time after placed": 30, "Sleeping bag respawn cooldown": 40, "Bed respawn cooldown": 20, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50, "Sleeping Bag Decay Settings": { "Enable Custom Decay. Default: false": false, "Disable Decay. Default: false": false, "Delay before decay starts. Default: 24 hours": 24, "Duration of decay. Default: 12 hours": 12 } }, "vip2": { "Priority. (lower = higher priority)": 2, "Player Max Sleeping Bag/Bed limit": 40, "Exclude camper beds from the limit. Default false": false, "Sleeping bag unlock time after placed": 100, "Bed unlock time after placed": 50, "Sleeping bag respawn cooldown": 80, "Bed respawn cooldown": 40, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50, "Sleeping Bag Decay Settings": { "Enable Custom Decay. Default: false": false, "Disable Decay. Default: false": false, "Delay before decay starts. Default: 24 hours": 24, "Duration of decay. Default: 12 hours": 12 } }, "vip3": { "Priority. (lower = higher priority)": 3, "Player Max Sleeping Bag/Bed limit": 20, "Exclude camper beds from the limit. Default false": false, "Sleeping bag unlock time after placed": 200, "Bed unlock time after placed": 100, "Sleeping bag respawn cooldown": 180, "Bed respawn cooldown": 80, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50, "Sleeping Bag Decay Settings": { "Enable Custom Decay. Default: false": false, "Disable Decay. Default: false": false, "Delay before decay starts. Default: 24 hours": 24, "Duration of decay. Default: 12 hours": 12 } } }, "VersionNumber": { "Major": 1, "Minor": 1, "Patch": 2 } } Basically 4 groups are created, and you can change the settings for each of these groups default vip1 vip2 vip3 These are the groups that are created by default, but you can add and/or edit groups as you wish. For example, if you change the group vip1 to vip_elite, the permission ultimatebeds.vip_elite will be created If you create a new group, for example vipvanilla, the permission ultimatebeds.vipvanilla will be created. FIELDS 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. Chat Prefix -- Chat message prefix. Disable Bag Gifting -- Disables bed assignment by other players. Default false. Priority. (lower = higher priority) -- Each group has its own property, the lower this number is, the more important the group is. This is useful in the case where a player has more roles assigned. In this case, the group with the lowest priority will be assigned, the most important group. Negative numbers are also allowed. PlayerMaxSleepingBagBed -- Defines the maximum number of sleeping bags/beds a player can place. Exclude camper beds from the limit -- You can choose to exclude beds that are located in campers from the bed limit count. Default FALSE SleepingBagUnlockTime -- Defines after how many seconds the sleeping bag is ready for use when placed for the first time. BedUnlockTime -- Defines after how many seconds the bed is ready for use when positioned for the first time. SleepingBagRespawnCooldown -- Defines after how many seconds the sleeping bag can be used to spawn after the sleeping bag has already been used. BedRespawnCooldown -- Defines after how many seconds the bed can be used for spawning after the bed has already been used. Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other) : 50, Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other) : 50 Sleeping Bag Decay Settings Enable Custom Decay -- Enable or disable custom decay. Default: false Disable Decay -- Disables sleeping bags or beach towels decay. Default: false Delay before decay starts -- Delay before the start of the decay for sleeping bags or beach towels without maintenance. Default: 24 hours NB: Applies only to newly placed sleeping bags or beach towels, after this group has been assigned to the player. Duration of decay Time taken for decay and then removal of sleeping bags or beach after decay has started. Default: 12 hours Applies to all sleeping bags or beach towels, both old and new, after this group has been assigned to the player. LOCALIZATION The plugin, therefore the automatic messages and statistics, are translated into the following languages: English Italian Translation files are located in the /oxide/lang folder, here is an example of a /oxide/lang/en/UltimateLocker.json translation file. You can add translations for other languages by adding them to the folder: /oxide/lang
    $7.99
1.8m

Downloads

Total number of downloads.

8.2k

Customers

Total customers served.

123.6k

Files Sold

Total number of files sold.

2.5m

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.