红石接近传感器(Redstone Proximity Sensor,简称 RPS)是一个插件,允许玩家制作并使用 RPS 火把。RPS 火把能够根据实体的接近程度来触发开启或关闭状态,并且支持大量自定义选项。你可能不想让玩家直接访问命令方块,这我理解,但如果只是限制为接近检测功能呢?这正是 RPS 的用武之地。
- 基于实体距离的接近传感器
- YML 存储
- 权限限制器(详见下文)
bStats 指标
更新检查器
原生支持众多保护类插件。
可为每个按钮设置权限,以便升级后的成员获得更多内容!
通过 API 自定义“触发器”,并原生支持 GriefPrevention,Towny, and LegacyFactions
默认触发器(GUI 中的那些)
Invert Power(反转电源):这类似于逻辑非(NOT)操作,它会反转应有的状态。如果玩家处于范围内且本应开启,反转电源后会在远离时关闭、靠近时开启。
Range(范围):你可以左键或右键点击来调整传感器的范围数值。配置文件中有一个选项可以修改允许的最大范围值,但我发现 20 已经足够合适。
Owner Only Edit(仅限所有者编辑):此选项应保持默认启用状态,以防止其他玩家编辑该火把。不过,如果没有服务器端的保护机制,其他玩家仍然可以破坏你的火把。
Owner Trigger(所有者触发器):启用此触发器后,它将检测火把的所有者,即放置该火把的玩家。
Player Entities Trigger(玩家实体触发器):此触发器用于除所有者之外的所有其他玩家。如果你想针对所有者进行触发,请使用上面的“所有者触发器”。
Hostile Entities Trigger(敌对实体触发器):指那些即使未被挑衅也会主动攻击的怪物。
Neutral Entities Trigger(中立实体触发器):指那些仅在受到挑衅时才会反击的怪物。
Peaceful Entities Trigger(和平实体触发器):指那些如果你攻击它们会逃跑,并且完全不会反击你的怪物。
Dropped Items Trigger(掉落物品触发器):此触发器会对地面上的物品产生反应,例如鸡的蛋等。
隐形实体触发:如果禁用此项,RPS 将不会检测隐形实体。所有隐形单位都将被忽略。
载具触发:根据 Minecraft 的定义,任何属于“载具”的实体,包括矿车和船只。
投射物触发器:当有人向你射击箭矢时,会出现一堵墙,使用此触发器非常简单。
使用方法
展示/评价
- rps.place (默认: true) :允许玩家放置该火把。
- rps.create (默认: true) :允许玩家合成该火把。
- rps.admin (默认: op) :允许用户使用 /rps 命令。
- rps.invisible(默认:op):使用 /ignorerps 时使其他 RPS 用户无法看到该玩家
- rps.list(默认:true):允许用户使用 /rpslist 命令
- rps.list.player(默认:op):允许用户使用 /rpslist [player] 命令
config 文件中的 rps.limiter 权限设置
在 config.yml 文件中,你会找到一个名为 "rps.limiter" 的节点部分,在该部分中你将看到类似如下内容:
limiter:
player:
amount: 40
默认值: true
管理员:
数量: -1
默认: op
这会根据你提供的名称创建新的权限。例如,“rps.limiter.player” 是第一个权限的键,而 “rps.limiter.admin” 是另一个权限的键。“default: true” 表示每个初始玩家的该权限默认设置为 TRUE(显而易见),任何未指定权限的限定等级将赋予 OP 的默认权限(允许的默认值为:true、false、op、not op)。数量可以是任意整数,-1 代表无限制。如果未指定数量,则自动设为 -1。服务器 OP 无论其权限级别如何,都将始终拥有无限制权限。
如果配置文件中没有设置限制器“组/等级”,玩家将能够放置无限数量的传感器,并且会在配置文件中生成一个 "rps.limiter.default" 等级。
注意:权限检查是按降序进行的,因此从技术上讲,在添加更高权限时,您不需要移除较低权限。(适用于拥有权限存储的用户)
按钮权限
将这些权限与任何权限商店插件或自定义设置搭配使用,以允许升级后的成员对 RPS 火把拥有更多控制权,或者禁用你不希望他们修改的按钮。在 2.5.0 版本中,按钮权限将会变更,请留意!
rps.button_invertpower (默认: true) : 使用该按钮的权限
rps.button_range (默认: true) : 使用该按钮的权限
rps.button_ownerownlyedit (默认: true) : 使用该按钮的权限
rps.button_owneronlytrigger (默认: true) : 使用该按钮的权限
rps.button_playerentitytrigger (默认: true) : 使用该按钮的权限
rps.button_hostileentitiestrigger (默认: true) : 使用该按钮的权限
rps.button_peacefulentitiestrigger (默认: true) : 使用该按钮的权限
rps.button_droppeditemtrigger (默认: true) : 使用该按钮的权限
rps.button_vehcileentitiestrigger (默认: true) : 使用该按钮的权限
rps.button_projectileentitiestrigger (默认: true) : 使用该按钮的权限
rps.button_invisibleentitiestrigger (默认: true) : 使用该按钮的权限
rps.button_townytrigger (默认: true) : 使用 Towny 附加组件的权限
rps.button_gptrigger (默认: true) : 使用 GP 附加组件的权限
rps.button_lfactiontrigger (默认: true) : 使用 LegacyFactions 附加组件的权限
- /ignorerps: 拥有 rps.invisible 权限时,你可以切换是否触发 RPS,不受其他设置影响。
- /rps reload: 重新加载配置文件和语言文件。
- /rps give <user> [amount]: 给予用户一个 RPS 火把
- /rps list <user>: 向发送者打印输出其(或指定用户的)RPS 位置。
- /rpslist [user]: 向发送者打印输出其(或指定用户的)RPS 位置。
所有配置文件都会自动生成,因此除非你损坏了原始文件,否则无需下载这些文件。
所有配置都非常直观。语言文件包含所有可见文本/聊天/lore/物品名称等内容,并支持颜色代码。
- 停止服务器
- 将 RedstoneProximitySensor jar 文件拖入你的 {server}/plugins/ 文件夹
- 启动服务器,让文件夹和文件在 {server}/plugins/RedstoneProximitySensor 中生成
- 如有需要,修改生成的文件。如果修改了配方,请重启服务器;否则请使用命令 /rps reload。
- Spigot v1.13 - 1.15.2
- Java 8
Redstone Proximity Sensor, or RPS, is a plugin that allows your players the ability to craft and than use the RPS Torch. The RPS Torch has the ability to trigger on/off via the power of entity proximity with a ton of customization possible. You wouldn't want to give players access to a command block, I understand that, but what about the limitations of just a proximity detection? That's where RPS comes in.
- Proximity Sensor based off entity distance
- YML Storage
- Permission Limiter (See below)
- bStats Metrics
- Update Checker
- Native support for many protection plugins.
- Set permissions per button so upgraded members can get more stuff!
- Custom "triggers" via API and native support for GriefPrevention,Towny, and LegacyFactions
Default Triggers (The ones in the GUI)
Invert Power: This is like a NOT operator, it inverts whatever the status should be. If a player is within range and it should be on, if you invert the power it will be off when away and on when near.
Range: You can left click or right click to change the Range amount for the sensor. There is a config option to change the max allowed amount but I found 20 to be decent enough.
Owner Only Edit: This should be left as Default enabled because it gives protection from editing the torch by other players, although without any server protection players could break other players torches.
Owner Trigger: This trigger enabled will be looking for the owner of the torch, the one who placed it down.
Player Entities Trigger: This trigger is for all other players BESIDES the owner. If you want to trigger for the owner use the one above.
Hostile Entities Trigger: These are mobs that would fight back even when not provoked
Neutral Entities Trigger: These are mobs that would fight back only when provoked
Peaceful Entities Trigger: These are mobs that would run away from you if you where to hit them and don't hit you at all.
Dropped Items Trigger: This would trigger for items that are on the ground. Chicken Eggs, exc.
Invisible Entities Trigger: If this is disabled the RPS will not detect invisible entities. Anything invisible will go undetected.
Vehicle Trigger: Anything according to Minecraft that is a Vehicle, including Minecarts and boats.
Projectile Trigger: Make a wall appear when someone is shooting arrows at you, its that easy with this trigger.
How To
Crafting
Gui Menu (Right click torch)
Showcase/Reviews
- rps.place (default: true) : Allows players to place the torch down.
- rps.create (default: true) : Allows players to craft the torch.
- rps.admin (default: op) : Allows user to use /rps command.
- rps.invisible(default: op) : Makes user invisible to the RPS when using /ignorerps
- rps.list(default: true) : Allows user to use /rpslist command
- rps.list.player(default: op) : Allows user to use /rpslist [player] command
rps.limiter Permissions in config file
In the config.yml file you will find a node section "rps.limiter", in this section you will see something like this:
[code] limiter:</div>
<div data-redactor="1"> player:</div>
<div data-redactor="1"> amount: 40</div>
<div data-redactor="1"> default: true</div>
<div data-redactor="1"> admin:</div>
<div data-redactor="1"> amount: -1</div>
<div data-redactor="1"> default: op[/code]
This will create new permissions based off the names you give it. "rps.limiter.player" for example is the permission key for the first one, "rps.limiter.admin" for the other one. "default: true" is so that every starting player has the permission set to TRUE by default (duh), any limiter rank added without one will be given the default permission of OP (allowed defaults are: true, false, op, not op). The amount can be any integer, and -1 represents unlimited. If an amount is not specified it is automatically set to -1. Server OP's will always have unlimited no matter their permission level.
If there are no limiter "groups/ranks" in the config file players will be able to place unlimited sensors and a "rps.limiter.default" rank will be generated in the config file.
Note: Permissions are checked in descending order so technically you do not need to remove a smaller amount permission when adding a greater amount permission. (for people who have permission stores)
Button Permissions
Use these permissions with any permission shop plugin, or your own setup to allow upgraded members more control over their RPS torches, or just disable buttons you don't want them to be able to modify. In 2.5.0 button permissions will change, keep a look out!
rps.button_invertpower (default: true) : Perm to use said button
rps.button_range (default: true) : Perm to use said button
rps.button_ownerownlyedit (default: true) : Perm to use said button
rps.button_owneronlytrigger (default: true) : Perm to use said button
rps.button_playerentitytrigger (default: true) : Perm to use said button
rps.button_hostileentitiestrigger (default: true) : Perm to use said button
rps.button_peacefulentitiestrigger (default: true) : Perm to use said button
rps.button_droppeditemtrigger (default: true) : Perm to use said button
rps.button_vehcileentitiestrigger (default: true) : Perm to use said button
rps.button_projectileentitiestrigger (default: true) : Perm to use said button
rps.button_invisibleentitiestrigger (default: true) : Perm to use said button
rps.button_townytrigger (default: true) : Perm to use Towny Addon
rps.button_gptrigger (default: true) : Perm to use GP Addon
rps.button_lfactiontrigger (default: true) : Perm to use LegacyFactions Addon
- /ignorerps: Having the rps.invisible permission you can toggle if you trigger the RPS or not no matter the settings.
- /rps reload: Reloads Config and Lang file.
- /rps give <user> [amount]: Gives user a RPS torch
- /rps list <user>: Gives sender a print out of their (or user's) RPS locations.
- /rpslist [user]: Gives sender a print out of their (or user's) RPS locations.
All configuration files will be generated automatically so there is no need to download these files unless you corrupted your originals.
All configuration is straight forward. The language file contains all visible text/chat/lore/item names/exc and includes support for colors.
- Stop server
- Drag the RedstoneProximitySensor jar file into your {server}/plugins/ folder
- Start server, let folder and files generate in {server}/plugins/RedstoneProximitySensor
- Modify generated files if needed. If modifying the recipe restart server, otherwise use command /rps reload.
- Spigot v1.13 - 1.15.2
- Java 8
评论 0
登录后参与评分
还没有评论,来抢沙发吧