Raid Limit

插件介绍

限制袭击建筑物的次数

It works by storing the owners of the buildings and the owner of the objects connected to the building.

This plug-in has built-in playtime tracking. Therefore, it is optional to put in a playtime tracker.If a playtime tracker exists, this plug-in will use a playtime tracker.

The plugin player RaidData are stored in data/RaidLimitPlayerData.json. Deleting this file would wipe all the number of times players raided a house.The plugin player UIData are stored in data/RaidLimitPlayerUIData.json. Deleting this file would wipe all players UI toggle dataThe plugin player OldTeamData are stored in data/RaidLimitPlayerTeamData.json. Deleting this file will delete the teaming information a few minutes ago.

主要用途

主要用于limitation、建筑、protection、gui等服务端功能。 本插件由 发布，当前目录记录版本为 v2.2.4，uMod 累计下载 14,375 次。

适用场景

• 需要调整建造、物品、制作或采集体验的服务器
• 希望改善玩家交互与日常体验的社区服务器

功能分类

权限节点

授权示例：oxide.grant user 玩家名 权限节点；撤销使用 oxide.revoke。

指令说明

相关依赖

• Image Library
• Anti Noob Raid
• Playtime Tracker

配置说明

官方配置示例

{
  "1.RaidLimitOperationType": {
    //Determines the operating mechanism of the raid limit (0=ObjectOwnerIdentification, 1=ToolCupboardIdentification)
    "1.1.OperationType": 0, 
    //By default, this option saves the owner of the building to determine the reduction of the raid counter (records all the people who contributed to the building.)
    "1.2.ObjectOwnerIdentification": {
      //Depth of recursively searching for objects (Higher numbers result in higher computations and higher accuracy)(-1 is 100% accurate)(The lower this number, the more likely the raid limit counter is to malfunction)
      "1.2.1.ObjectSearchDepth": -1,
      //Scope of searching between linked objects
      "1.2.2.ObjectSearchRange": 5
    },
    //This option determines the reduction of the raid limit counter based on the cupboard that is connected to the building
    "1.3.ToolCupboardIdentification": {
      //Depth of recursively searching for objects (Higher numbers result in higher computations and higher accuracy)(-1 is 100% accurate)(The lower this number, the more likely the raid limit counter is to malfunction)
      "1.3.1.ObjectSearchDepth": -1,
      //Scope of searching between linked objects
      "1.3.2.ObjectSearchRange": 5,
      //Determines whether to check the instance ID of the toolcupboard (This option allows basic restrictions to work in the "ToolCupboardIdentification" mechanism)
      "1.3.3.CheckToolCupboardInstanceID": true,
      //Check the people who are authorized on the cupboard (If you turn this option on, you can also raid the homes of all the people who are authorized on the cupboard with one counter reduction.)
      "1.3.4.CheckAuthorizedPeoples": true
    }
  },
  "2.RaidLimitSettings": {
    //Maximum number of possible times that can raid
    "2.1.OneTimeMaximumRaidableHomeCount": 2,
    //a time when the first-time user cannot be raid.
    "2.2.NoobCantRaidSecond": 10800,
    //Whether to reset all raid counts at 0 o'clock
    "2.3.InitializeCounterOnMidnightTime": true,
    //Frequency of timer sensing zero hour (high values give high accuracy)
    "2.4.MidnightTimeDetectionTimerInterval": 10,
    //Time taken to charge the counter (If the value is -1, the counter will not be recharged)
    "2.5.CounterChargeDelay": 18000,
    //The standard for measuring the time it takes to recharge.(0 = realtime, 1 = playtime)
    "2.6.CounterChargeDelayType": 0,
    //Charging method (0 = Fill up all the times when consumed all, 1 == Charge one at a time when the value is not maximum)
    "2.7.CounterChargeType": 0
  },
  "3.UISettings": {
    //Whether to use UI
    "3.1.UIEnable": true,
    //Update frequency of UI timer
    "3.2.UIUpdateInterval": 3
    //Position of the GUI showing the number of possible raid
    "3.3.UIPosition": {
      "3.3.1.AnchorMin": "0.28 0.025",
      "3.3.2.AnchorMax": "0.3392 0.06"
    }
  },
  "4.TeamSyncSettings": {
    //Synchronize raid limit counter with team members (Per-team limit is possible)
    "4.1.TeamCounterSync": true,
    //Prevent team members from bypassing counter reduction ( even if the player briefly disbandes the team to bypass the counter synchronization between team members, the counter is synchronized even if the person who was a team minutes ago Raid because the plug-in remembers the team in the state a few minutes ago.)
    "4.2.PreventTempDisband": true,
    //Interval to remember previous state of teaming
    "4.3.OldTeamSaveInterval": 600
  }
}

{
  "No Permission": "You do not have permission to use the '{0}' command.",
  "Date Changed": "The day has changed. The raid limit has been initialized.",
  "You Can Raid": "You have enough play time to raid.",
  "Add RaidList": "The owner of this building has been added to the raid list. you can raid {0} more time.",
  "Raid Blocked": "You can't raid any more today.",
  "Raid Blocked Time": "You have to play the game for more than {0}seconds before you can raid it. Your play time is {1}seconds",
  "Raid List Reset": "The raid limit has been initialized.",
  "Left Raid Count": "You can raid {0} more time.",
  //The items below have been added since version 1.1.0
  "bypass GUI Msg": "<color=#FFE400>bypass</color>",
  //The items below have been added since version 1.3.0
  "Team Member Raiding": "Team member \"{0}\" is raiding. Raid limit counter reduced. The owner of the house where the team is raiding has been added to the raid list."
  //The items below have been added since version 2.0.0
  "Add RaidList TC": "The building has been added to the raid list. you can raid {0} more time.",
  //The items below have been added since version 2.1.0
  "Raid Blocked NoRefill": "You can't raid any more.",
  "Raid Blocked RNextTime": "You can't raid right now. After {0} seconds in realtime, Raid count will be recharged.",
  "Raid Blocked PNextTime": "You can't raid right now. After {0} seconds in playtime, Raid count will be recharged.",
  "Raid Reset Specific Slayer": "Your raid limit has been refilled."
  //The items below have been added since version 2.2.0
  "SteamID Not Found": "Could not find this SteamID: {0}.",
  "Player Not Found": "Could not find this player: {0}.",
  "Multiple Players Found": "Found multiple players!\n\n{0}",
  "NotEnoughArgument": "to run this command you need {0} arguments.",
  "Invalid Parameter": "'{0}' is an invalid parameter.",
  "Count IncreasedC": "{0}'s raidlimit has increased by '{1}'.",
  "Count DecreasedC": "{0}'s raidlimit has decreased by '{1}'.",
  "Count IncreasedP": "raidlimit has increased by '{0}'.",
  "Count DecreasedP": "raidlimit has decreased by '{0}'."
}

更新日志

本站记录 uMod 官方插件信息。完整的历史更新日志请参阅 uMod 官方页面。

安装方法

1. 确认服务器已安装 Oxide / uMod 或兼容的 Carbon 框架。
2. 登录本站后点击"下载"，由本站已校验的本地缓存提供作者发布的文件。
3. 将 .cs 文件放入服务器的 oxide/plugins 目录。
4. 观察服务端控制台，确认插件编译并成功加载。
5. 具体配置、权限、指令和依赖请查看原作者的 uMod 页面。

使用前注意

• Rust 更新后，请先确认插件是否仍兼容当前服务端版本。
• 修改配置前建议备份原配置文件，并在测试服验证后再部署到正式服。
• 若插件依赖其他扩展或库，以 uMod 原作者页面的最新说明为准。
• 本站中文内容用于辅助理解，遇到版本差异时以官方英文文档和源码为准。