由于防火墙和互联网问题,插件开发暂时中断
这是我的第一个服务器模组。该插件对新手极其友好。本质上,它是一个全自动的防破坏插件,会自动认领玩家建造的区块(16x16),而玩家无需进行任何操作即可保护区域。此外,如果因某些原因无法保护该区域(例如玩家已用完分配的区块配额,或与其他已认领区块不相邻),玩家在放置方块时会收到通知。插件包含好友列表功能,并且通过可配置的消息支持将插件本地化为服务器的本地语言。
该插件还会自动忽略不属于玩家创作的常见方块,因此不会因为放置火把等操作导致整个洞穴被认领。
v1.1 修复了与 WorldEdit 的兼容性问题
致所有从 V1.2 或更早版本升级到 V1.3 或更高版本的玩家:
在更新之前,请务必删除 /plugins 目录下的 ChunkAutoClaimer 文件夹!
非常重要!
V1.2 与 V1.3 之间的配置文件格式已更改,导致两者不兼容!
由于方块 ID 拼写错误,配置生成中存在一个 bug。请在配置的 ignoreblocks: 下方添加 - 50,以排除火把。
该插件的功能是什么?
本质上,这是一个完整的防破坏插件,用于对抗游戏中所有基于方块的破坏行为。所谓“基于方块的破坏”,是指本插件不会防止其他形式的破坏,如 PvP 破坏、聊天破坏/刷屏等。这些有其他插件负责处理。
本插件基于“可合成方块”的概念运作。所谓“可合成方块”,我指的是所有必须通过合成才能获得的方块。
我将火把排除在此列表之外 (从 1.4 版本开始,抱歉之前拼错了方块 ID),因为火把是一种玩家在没有实际建造有用结构时广泛散布的方块,例如用于洞穴照明。我还允许将“昂贵”的非合成方块计入——例如矿石等,因为这些方块也是玩家不会随意散布的。
排除非合成廉价方块(例如沙子、圆石、原木)的原因是,人们经常通过堆砌大量非合成的廉价材料来摆脱被困空间。当然,玩家不希望在地狱逃生时认领他们逃离的所有洞穴。
被忽略(不计入)的方块列表可以进行配置,只需在配置中添加或删除您希望忽略的方块 ID 即可。
它是如何工作的?
现在进入正题。通过至少放置 7 个(可配置,默认为 7)方块,玩家即可认领该区域。除非其他玩家将当前玩家添加为好友列表,否则任何人都无法在此处建造。如果玩家想要移除/取消认领该区域,只需破坏 7 个(同样可配置,默认为 7)方块即可。
通过这种机制,反破坏(antigrief)功能完全自动化。玩家无需知道有保护存在,他们只需不断地建造即可。这就像原版 Minecraft 的体验,但不会有被破坏的风险。当他们将房屋夷为平地以搬迁到新的地点时,地块会自动取消认领,所有人都可以在那里建造。
为了防止通过认领不必要的土地来进行破坏行为,有两个有用的配置选项:
maxclaims:玩家最多可以拥有的认领数量上限。可以通过 /set 命令覆盖。
requiretouch:(true/false)- 要求特定玩家拥有的认领区域必须彼此相邻。
为了防止在野外发生破坏行为,有许多有用的配置选项:
allowfirespread:(true/false):允许火焰在认领区域外蔓延和燃烧。允许在认领区域外 51 格范围内点燃或放置火块。
无论所有权或授权情况如何,火焰永远不会在认领区域内蔓延或燃烧。只要您拥有对该区域的权限(例如可以在此建造),就始终允许在认领区域内点燃或放置火块。
allowugfirespread - 与 firespread 相同,但适用于地下层以下。
allowlava/allowwater - 允许在野外倾倒水桶/熔岩桶。
allowuglava/allowugwater - 同上,但适用于地下。
allowtnt - 指定爆炸是否对地面以上产生影响。
allowugtnt - 同上,但适用于地下。
belowground - 整数,表示地面高度。低于此值被视为地下,高于此值被视为地上。
为了防止因频繁操作好友列表而导致 config.yml 文件变得巨大,有一个很好的配置选项:
maxfriends:玩家在好友列表中最多可以拥有的好友数量。
新增功能:
当有读取或写入区块保护状态的操作发生时(例如尝试在没有授权的情况下在区块内建造、认领区块、取消认领区块,或对区块执行 /chk 或 /set 命令),该区块会被标记。
配置选项:
markblock - 用于标记的方块 ID。
markdata - 用于标记的方块数据值。
markclaims - true/false - 启用/禁用标记功能。
config 文件中默认的 un/claimblocks=7 设置好吗?我需要更改它吗?
你应该更改它。大多数服务器有不同的风格。这些数值是针对生存服务器优化的,因此如果你运行的是创造模式服务器,建议将数值更改为非常高的值,比如最高到 10-16。切勿超过 16,因为区块宽度为 16 格,而大多数玩家建造的单格厚墙壁会导致玩家永远无法认领土地。超过 16 将要求玩家建造双格厚的墙壁。
如果你运行的是创造模式服务器,我还建议更改 config 中的 ignoreblocks 列表,以包含更多方块,并将 belowground 选项设置为较低的值,或者将 allowugtnt 设置为 false。否则,你可能会看到你的沙漠地区遭到严重破坏。你也可以自由尝试这些数值。有时使用比 claimblocks 更高的 unclaimblocks 也是有好处的,例如 claimblocks=4 且 unclaimblocks=5。你只需要找到最适合你服务器的配置,同时也要考虑其他插件的影响。如果你的服务器建筑风格是玩家建造巨大的城堡,那么也应该更改 maxclaims。此外,如果你的服务器有大量不同的玩家,请考虑更改 maxfriends 选项。默认的 7/7/9/5 配置适合大多数服务器。
为什么箱子/门不受保护?
因为我鼓励创造性建造。方块保护已经足够了。对于非常简单(丑陋)的箱子保护,你只需在箱子上方放置一个方块。由于该方块无法被破坏,箱子也就无法被打开。
但我鼓励的是创造性的保护措施,如高级红石电路、代码锁、隐藏门、水下入口等。
为什么这个插件比 <pluginname> 更好?
- LogBlock, BigBrother, HawkEye:
这些插件更侧重于在破坏行为发生后进行检测,以便随后踢出或封禁搞事者。而我的插件旨在
(结合其他插件)实现服务器的完全自动化和无管理员模式。使用我的插件和其他一些插件,你应该可以把 /kick 和 /ban 命令扔进垃圾桶了!
您还推荐哪些其他插件?
- NoCheatPlus - 在配置文件中将所有选项设置为“cancel”,即可在不踢人或封禁的情况下获得反作弊保护。
- nolagg - 防止破坏者通过在相同位置丢弃大量物品(如 9999999 个)来对服务器发起 DDoS 攻击。
- orebfuscator - 防止透视。
- spamguard - 优秀的反垃圾信息插件,可防止玩家在聊天中刷屏。记得在配置文件中将 warnstokick 和 kickstoban 设置为 2000000000,以防止插件踢人或封禁玩家。
如果你安装了所有这些插件,包括我的插件,你将拥有一个完全自管理的服务器,没有任何踢人/封禁。
为什么基于区块的保护比任意保护更好?
现在让我们明确一点。基于区块的保护,如本插件和 MyChunk,是基于 Minecraft 的“区块”,其大小为 16x16,从基岩延伸到天空。
任意保护是指你可以自由选择地块大小,例如 Grief prevention 和 Residence。
区块保护的优势:
- 数据量更小。一个区块由两个坐标标识。任意地块必须存储四个坐标(起始和结束),留下双倍大小的数据文件。如果你还存储底部和顶部以启用声明堆叠,那就是六个坐标。想想看,文件大小是原来的三倍!此外,由于给定世界中区块坐标的数量是方块坐标的 1/16,因此方块坐标比区块坐标更大。基本上,方块坐标也大 256 倍,导致数据文件变得巨大无比。
- 代码不需要检查声明的重叠情况。要么区块被声明,要么未被声明。中间没有过渡状态。在任意地块中,可能存在一半的声明属于其他人的情况,因此插件必须检查所有内容,这会增加处理时间。
- 没有土地浪费。使用任意保护时,可能会出现大面积的土地上有太多租户的情况,导致房屋之间只有 2-3 个方块宽的 unprotected 小径,这些区域毫无用处。
- 区块周围总是有一些“自由呼吸的空间”,因为玩家不会恰好建在区块边界上。一个普通的新手玩家可能会声明总共 32x32 个方块的 2x2 区域(从基岩到天空),并在中间建造一座房子,留出四周各 4 个方块的空间。而任意保护可能导致房屋几乎相互接触,显得杂乱无章。
关于新手和协作建造者呢?
为了支持协作建造,内置了一个好友列表功能。你只需通过 /add 或 /del 添加或删除好友即可,好友在你的声明中具有完全权限,除了取消你的声明或信任其他人之外。如果你不小心把某个你不记得名字的黑客加入了好友列表,只需输入 /del 不带任何参数,即可彻底清除好友列表。
好友列表的最大值可配置,以防止玩家使 config.yml 变得过大。
如果作为玩家的你彻底搞砸了,例如在你不记得位置的区域用完了所有声明,并且把一切都弄得一团糟,你可以通过输入 /reset 来重置自己。
这将取消你对所有领地(claims)的所有权,并清空你的好友列表。之后,你只需从你的房子中移除 7 个方块并重新放置,即可轻松重新认领你的房子。
如果你想移除区域内的 7 个方块,但仍希望该区域保持受保护状态该怎么办?
很简单。只需先移除 6 个方块,然后放置一个方块,接着再次移除更多方块即可。
或者每第 6 个方块破坏一个非贵重方块。
如何像 GriefPrevention 那样实现“管理员领地(adminclaims)”?
只需将领地的所有者设置为某个不存在的名称即可。你可以在未受保护的陆地和已受保护的陆地上执行此操作。计数器和列表会自动相应更新。例如:/set SOMETHING。请注意,/set 会覆盖 maxclaims 限制,因此无需担心“管理员领地用尽”的问题。
请注意,有人可能会注册并占用某个管理员领地的名称来进行破坏行为,因此请谨慎选择管理员领地的“所有者”。
建议使用 /set notch 来设置管理员领地,因为 Notch(Minecraft 的创造者)绝不会去破坏服务器,他可能根本不会访问你的服务器,而且由于没有人可以注册 notch 这个名字,你的管理员领地将保持安全。
如果你有大量的领地需要设为管理员领地,比如你要建造的大型城市,请确保你拥有 OP(管理员)权限,且你自己没有任何领地。务必执行 /reset。然后像往常一样创建领地。完成后,运行以下命令:
/reset YOURNAME notch
这将(再次)重置你自己的配置,并将你所有的领地转移给“notch”。由于 notch 永远不会破坏你的服务器,你的城市现在受到了保护,而你仍然可以自由地对自己的角色和/或领地进行操作(例如重置等),而不会影响城市。但请记住,只要你拥有 OP 权限,你就可以在管理员领地中破坏/放置方块。不过,你不会取消任何管理员领地的归属。
如果你希望确保不触碰其他领地,可以使用 /chk 检查你所处的领地,或使用 /walktest 查找已被占用的领地。
可以使用哪些命令?
/chk - 检查你当前站立的区块。用于确认你是否确实受到保护。
/add <朋友> - 将 <朋友> 添加到你的好友列表中
/del <朋友> - 从你的好友列表中移除 <朋友>
/del - 清空你的好友列表
/set - 仅限 OP - 无论所有者是谁,取消你当前站立区块的领地归属。
/set <名称> - 仅限 OP - 将你当前站立区块的领地归属更改为 <名称>
/reset - 重置你的个人资料。
/reset <名称> - 仅限 OP - 重置 <名称> 的个人资料。如果 <名称> 长期不活跃或不再游玩,此命令非常有用。
/reset <名称1> <名称2> - 仅限 OP - 重置 <名称1> 的个人资料,然后将其所有领地转移给 <名称2>。例如,当 <名称1> 更换了 Minecraft 账号时,或用于设置管理员领地。
/walktest - 开启行走测试模式,在此模式下你只能在未受保护的区域建造。再次输入该命令可关闭。- 不适用于荒野保护。
为什么配置文件中有这么多项目?
main/messages/* - 字符串 - 本地化系统。允许你配置插件的语言。
main/config/requiretouch - 布尔值 - 要求玩家的领地彼此相邻。
main/config/allowfirespread - 布尔值 - 控制领地外的火灾蔓延与引燃。
main/config/allowugfirespread - 布尔值 - 控制地下领地外的火灾蔓延与引燃。
main/config/allowlava - 布尔值 - 控制领地外的岩浆放置。
main/config/allowuglava - 布尔值 - 控制地下领地外的岩浆放置。
main/config/allowtnt - 布尔值 - 控制爆炸。
main/config/allowugtnt - 布尔值 - 控制地下爆炸。
main/config/allowwater - 布尔值 - 控制领地外的水流放置。
main/config/allowugwater - 布尔值 - 控制地下领地外的水流放置。
main/config/belowground - 整数 - 设置地面层级。
main/config/markblock - 整数 - 设置标记区块时使用的方块 ID。
main/config/markdata - 整数 - 设置标记区块时使用的方块数据(例如羊毛颜色)。
main/config/markclaims - 布尔值 - 启用/禁用标记功能
main/config/claimblocks - 整数 - 声明一块区域所需放置的可接受方块数量。
main/config/unclaimblocks - 整数 - 取消声明一块区域所需移除的可接受方块数量。
main/config/maxclaims - 整数 - 玩家最多可拥有的领地数量 - 可通过 /set 覆盖。
main/config/maxfriends - 整数 - 玩家在好友列表中最多可添加的好友数量。
main/config/configversion - 整数 - 为你维护配置文件,以防配置文件更新。设置为 99999 可绕过此功能。
main/config/ignoreblocks - 整数列表 - 被视为不可接受的方块 ID。这些方块不计入 claimblocks/unclaimblocks。
main/players/*/blockcounter - 存储玩家 * 在上次声称(lastclaim)区块中连续放置的方块数量
main/players/*/lastclaim - 存储玩家最近放置或移除方块的区块。如果此值发生变化,blockcounter 将被重置。
main/players/*/gotwarning - 防止插件向用户发送垃圾信息。当玩家收到“无法声明的土地”警告时设置此项,当玩家在可接受的区域内放置/移除方块时重置此项。
main/players/*/walktest - 存储玩家当前的 walktest 状态。每次玩家加入游戏时重置。
main/players/*/claims - 领地列表。获取 * 拥有的所有领地,/reset 命令正常工作所必需。
main/players/*/friends - 存储玩家的好友列表
main/claims/* - 存储区块 * 的所有者。
插件是否支持权限系统?
是的,从版本 1.7 开始
权限节点如下:
chunkautoclaimer.op - 提供所有 OP(管理员)命令的访问权限,并允许玩家在通常不允许建造的区域内进行建造。
chunkautoclaimer.unlimited - 无限声明区块,好友和声明区块无需相邻,无论 requiretouch 设置如何。
为什么 CAC 会忽略 OP?(仅限 V1.1)
OP(管理员)可以随意建造/破坏方块以执行其管理任务。如果 OP 希望仅接触未受保护的表面,可以通过输入 /walktest 启用
walktest。
requiretouch、maxclaims 和 maxfriends 不适用于 OP。
/walktest 有什么用?我不明白这个命令的意义在哪里?
一些示例:
- 你是 OP,想要在未受保护的土地上执行一些职责。你开启 /walktest 以确保不会触碰受保护的土地。
- 你刚刚建造了一座大房子,想要确保它完全受到保护。你开启 /walktest,然后尝试破坏房子周围的随机方块,最终找出任何未受保护的角落。
- 你想要寻找一些未受保护的土地,但不想误入那些你在所有者好友列表中的土地。
- 你打算进行 PvP,但不想意外破坏自己建筑中的方块。
- 你想要对你建造的机械装置进行真实测试,这可能会导致你意外破坏方块,并且你想确保这一点。
- 你建造了一个大型复杂结构,想要像“破坏者”一样探索它。
源代码:
PayPal 捐赠:
我的 Minecraft 用户名: sebnie
待办事项:
- 防止取消声明区块,如果取消声明会导致两个玩家的区块不再相邻——当 requiretouch 设置为 true 时。
(我目前没有解决方案,欢迎为此提供想法)
- 反垃圾信息
- DynMap 集成
- 修复翻译以便可以移除消息
- 一些错误修复
- 可能提供一种让用户向系统表明他们是有经验的方法,这将使模组更安静,当然如果他们后悔决定,可以随时切换回来。
- 为没有经验的用户在放置箱子时添加信息提示,告诉他们可以在箱子上方放置方块来保护它。
- Listfriends/listchunks 命令,允许玩家列出他们的好友/区块
- /home 命令将他们带回到最后声明的区块。
不做/不修复:
- 按区块/声明的好友列表。这对终端用户来说过于复杂。我希望保持插件对终端用户的简单性。要么你信任一个用户,要么你不信任。中间没有别的选项。为什么你会信任用户在 A 区域建造却不信任他们在 B 区域建造?
- 子声明。这也是一个过于高级的功能。
- 数据库。不需要这个。在小规模服务器上使用该插件,或者如果使用该插件会影响性能,请使用 SSD。
PLUGIN DEVELOPMENT TEMPORARLY DOWN DUE TO SOME FIREWALL & INTERNET PROBLEMS
This is my first server mod. This plugin is extremely newbie-friendly. Basically, its a completely automatic block antigrief plugin, which automatically claims chunks (16x16) people build on, without the player need to do ANYTHING to protect the area. Also, if the area cannot be protected for a reason, for example if player have used up all his allotted chunks, or are not adjacent to his other's chunks, the player will be notifyed on placement of block. Contains a friendslist, and the plugin can also be localized to the server's local language, thanks to configurable messages.
The plugin also automatically ignores common blocks which does not belong to players creations, so not people claim whole caves due to putting up torches and such.
WORLEDIT compatibility fixed in v1.1
NOTE TO ALL WHO UPGRADE FROM VERSION V1.2 or older, TO V1.3 or newer:
DELETE YOUR ChunkAutoClaimer FOLDER IN /plugins PRIOR TO UPDATING!
VERY IMPORTANT!
Config format was changed between V1.2 and V1.3 making configs incompatible between them!
There was a bug in config generation, due to a misspelled blockID. Add - 50 below ignoreblocks: in your config, thats to exclude torch.
What does the plugin do?
Basically, this is a complete Anti-Grief plugin, that combats all in-game block-based grief. With block-based grief, I mean that the plugin will not prevent other forms of grief like PvP griefs, chat grief/spamming and such. Theres other plugins for that.
This plugins works of a concept called "craftable blocks". With craftable blocks, I count all blocks that must be crafted to be able to obtain.
I excepted Torch from this list (From version 1.4, sorry did misspell a blockID), because Torch is a block that you spread around you without actually building anything useful, for example as lighting in caves. I also allow "expensive" non-craftable blocks to be counted - for example ore and such, because these blocks is also blocks players wont spread around with.
The reason of excepting non-craftable cheap blocks (for example sand, cobblestone, raw tree logs) is because often, people get out of stuck spaces by bulding a high pile of a cheap material that is noncraftable. And of course, the players does not want to claim all caves they get out from in a emergency.
The list of ignored (non-counted) blocks can be configured, just add/remove the block IDs you want to ignore in config.
How does it work?
So now to the point. By building atleast 7 (configurable, 7 is the default) blocks, the player claims the area. Nobody else can build here except for when players add them to friends list. If the player want to remove/unclaim the area, the player simply removes(breaks) 7 (this is also configurable, 7 is default) blocks.
By this system, the antigrief is completely automatic. Player does not need to know there is protection, they just build and build and build. Like vanilla minecraft experience but without griefing. And when they flat the house with the ground to move to a new place, the plot is automatically unclaimed and everyone can build there.
To prevent griefing by claiming unneccessary land, theres 2 configuration options that is useful:
maxclaims: Maximum claims a player can own. Can be overriden by /set command.
requiretouch: (true/false) - Require that claims a specific player own touch each other.
To prevent griefing in the wilderness, there is much configuration options that is useful:
allowfirespread: (true/false): Allow fire to spread and/or burn outside claims. Allow igniting/placing of fire block 51 outside of claims.
Fire will never spread or burn inside claims regardless of owner/authorization. Igniting/placing fire inside claim is always allowed provided you have authorization to the claim - eg can build there.
allowugfirespread - Same as firespread but applies below the belowground value.
allowlava/allowwater - allows unbucketing of water/lava in the wilderness.
allowuglava/allowugwater - same as above but applies underground.
allowtnt - Specifies if explosions does have any effect above ground.
allowugtnt - same as above but applies underground.
belowground - integer for ground level. Below this are considered underground, above this are considered overground.
To prevent spamming the friendslist so config.yml gets huuge, theres one configuration option that is good to go:
maxfriends: Maximum number of friends a player may have on friendslist.
NEW!:
Chunks are marked when something reads or writes to a chunk protection status, for example when you try to build in a chunk without authorization, claim a chunk, unclaim a chunk, or does /chk or /set on a chunk.
Configuration options:
markblock - Block ID to use when marking.
markdata - Block Data to use when marking.
markclaims - true/false - enable/disable the marking function.
Is the default un/claimblocks=7 in config file good to do? Should I change it?
You should change it. Most servers have different styles. The values are optimized for a survival server, so if you run a creative, its recommended to change the values to very high values, like up to 10-16. Do never exceed 16, then players will never claim land since chunks are 16 blocks wide and most players build singe-block thick walls. Exceeding 16 would require players to build double-block thick walls.
If you run a creative server, I also recommend to change the ignoreblocks list in config, to include more blocks, and also either change belowground option to a lower value, or setting allowugtnt to false. Else you might see your deserts to be very griefed. You are also free to experiment with the values. Sometimes it can be good with a higher unclaimblocks than claimblocks, for example claimblocks=4 and unclaimblocks=5. You just need to find a good config that fits your server best, based on other plugins aswell. Also the maxclaims should be changed if your building style on server is that players build huuuuge castles. Also consider changing the maxfriends option if your server have a large number of different players. The default 7/7/9/5 config does fit most servers.
Why aren't chest and/or doors protected?
Its because I encourage creative building. Block protection is all you need. For a very simple (ugly) chest protection, you simply put a block above the chest. Since the block cannot be destroyed, the chest cannot be opened either.
But what I encourage is creative protections like advanced redstone circuits, codelocks, hidden doors, underwater entrys and such.
Why are this plugin better than compared to <pluginname>?
- LogBlock, BigBrother, HawkEye:
These plugins are more aimed to detecting grief after it has been done, for the purpose of kicking/banning the griefer then. My plugin aims of
(in combination of other plugins) to make a server completely automatic and adminless. With my plugin and some other plugins, you should be able to put /kick and /ban into the dustbin!
- PreciousStones, Residence, GriefPrevention, MyChunk:
Those require players to manually protect the area. Many newbies don't understand how to protect, or forgets to protect, despite of the plugin educating the players. Before I did this plugin, I ran GriefPrevention on my server. It was a huge disaster, since none player did extend their claims.
When Griefers come along to the server, they griefed the houses so they looked very funny with non-griefed floors floating in the air, with a chest in the middle. That was because GriefPrevention's initial claim. I tried everything, giving a player a golden shovel at spawn (and GriefPrevention had a info message shown when selecting golden shovel), and much more. But players didn't listen.
What I needed was something FULLY automatic, where players do not need to think about the protection. That was why I created this.
Which other plugins do you recommend?
- NoCheatPlus - just set everything to "cancel" in config to get anticheat protection without kicks and bans.
- nolagg - Prevents griefers from DDoSing the server by dropping 9999999 items in the same place.
- orebfuscator - Prevent Xrayers.
- spamguard - Great antispam plugin to prevent people from spamming the chat. Remember to set warnstokick and kickstoban to 2000000000 in config to prevent the plugin from kicking/banning someone.
If you install all these plugins including my plugin, you have a completely self-adminning server without any kick/bans.
Why are chunk-based protection, better than arbitary protection?
Now lets get this straight. Chunk-based protection, like this plugin and MyChunk, is based on minecraft "chunks", which are 16x16 in size and extend from bedrock to sky.
Arbirtary protection, is when you are free to select the plot size for yourself, like Grief prevention and Residence.
Advantages of Chunk protection:
- Smaller data sizes. A chunk is identified by 2 coordinates. Arbitary plots must store 4 coordinates (start & end), leaving double sized datafiles behind. If you also store bottom and top to enable stacking of claims, its 6 coordinates. Talk about 3 times as large files! Also, block coordinates are larger in size than chunk coordinates, since theres 1/16 less chunk coordinates for a given world than block coordinates. So basically, block coordinates are also 256 times larger, making data files huuuuuge.
- Code does not need to check for overlapping of claims. Either a chunk is claimed, or a chunk is unclaimed. Theres nothing between. In arbitary plots, there is a possible that half the claim is owned by someone else, so the plugin must check everything, which increases processing time.
- Theres no waste of land. With arbitary protection, you can end up in a situation when a large plot of land has so many tenants so theres just small walkways of 2-3 block wide unprotected land between the houses, which are useless.
- Theres always some "breathing freeroom" around the chunks, since players will not build exactly where a chunk is. A normal newbie player would propably claim a 2x2 area of a total of 32x32 blocks from bedrock to sky, and build a house in the middle, leaving say 4 blocks on all sides. Arbitary protection can leave houses nearly touching everyone, making it ugly.
What about newbies and collaborative builders?
To enable collaborative building, theres a friendslist builtin. You simply /add or /del friends from this list, and friends have full permissions in your claims EXCEPT for unclaiming your claims or trusting others. If you mess up and add a griefer to your friends list that you don't remember the name of, just type /del without any arguments, and your friendslist are completely cleared.
The friendslist maximum is configurable to prevent a player from making config.yml huge.
If you as a player completely mess up, for example using up your claims at a area you dont remember the location of, and just mess everything up, you can reset yourself by writing /reset .
This unclaims ALL your claims and CLEARS your friendlist. You can then easly claim your house again by removing 7 blocks from your house and placing them again.
What if you want to remove 7 blocks from your area, but still have the area claimed?
Easy. Just remove 6 blocks, then add a block, and then remove more blocks again.
Or break a nonexpensive block each 6th block.
How I do "adminclaims" like in GriefPrevention?
Just /set the claims to some nonexistent name. You can do this both on unprotected land and protected land. Counters and lists will be updated accordingly automatically. For example: /set SOMETHING. Note that /set overrides maxclaims, so no worry "running out of adminclaims".
Please consider that someone may register and take a name of a adminclaim for the purpose of griefing, so select the "owner" of the adminclaim carefully.
I would suggest using /set notch for adminclaims, since Notch (the creator of Minecraft) would never go and grief some server, he would not probably visit your server, and since nobody can register notch's name, your adminclaims stay safe.
If you have LOTS of claims to make adminclaim, like a large city you are gonna build, make sure you are OP, and you don't own any claims. Do /reset for sure. Then you make claims as usual. When you are done, run this:
/reset YOURNAME notch
this will (again) reset yourself, and then transfer all your claims to "notch". Since notch never gonna grief your server, your city is now protected, while you still can do whatever you want with your own character and/or claims (eg resetting and such) without affecting the city. But remember, as long as you are OP, you can break/place blocks in adminclaims. However, you will not unclaim any adminclaims.
If you want to be sure of not touching claims, either /chk the claim you are building in, or use /walktest to find occupied claims.
Which commands can be used?
/chk - Checks the plot you are standing on. Useful to check that you really have protection.
/add <friend> - Adds <friend> to your friendslist
/del <friend> - Removes <friend> from your friendslist
/del - Clears your friendslist
/set - OPONLY - Unclaims the plot you are standing on regardless of owner.
/set <name> - OPONLY - Claims/changes owner of the plot you are standing on to <name>
/reset - Resets your profile.
/reset <name> - OPONLY - reset <name>'s profile. Useful if <name> got very inactive or is no longer playing.
/reset <name1> <name2> - OPONLY - reset <name1>'s profile, and then transfer all his claims to <name2>. Good for example if <name1> changed minecraft account, or for adminclaims.
/walktest - Toggles Walktest mode on, which means you can only build in unprotected areas. Type again to turn off. - Does NOT apply to wilderness protection.
Why are it so many items in the configuration file?
main/messages/* - strings - Localization system. Allows you to configure the language of plugin.
main/config/requiretouch - boolean - Require that players claims are adjacent to each other.
main/config/allowfirespread - boolean - Controls fire spread & igniting outside of claims.
main/config/allowugfirespread - boolean - Controls fire spread & igniting outside of claims under ground.
main/config/allowlava - boolean - Controls lava placement outside of claims.
main/config/allowuglava - boolean - Controls lava placement outside of claims below ground.
main/config/allowtnt - boolean - Controls explosions.
main/config/allowugtnt - boolean - Controls explosions under ground.
main/config/allowwater - boolean - Controls water placement outside of claims.
main/config/allowugwater - boolean - Controls water placement outside of claims below ground.
main/config/belowground - integer - Sets the ground level.
main/config/markblock - integer - sets the block ID to use when marking chunks.
main/config/markdata - integer - sets the block DATA (for example wool color) to use when marking chunks.
main/config/markclaims - boolean - enable/disable the mark function
main/config/claimblocks - integer - Number of acceptable blocks that need to be placed to claim a area.
main/config/unclaimblocks - integer - Number of acceptable blocks that need to be removed to unclaim a area.
main/config/maxclaims - integer - Number of plots a player max may own - can be overriden by /set.
main/config/maxfriends - integer - Max number of friends a player may have on friendslist.
main/config/configversion - integer - Maintains the config for you, incase config are updated. Set to 99999 to bypass the feature.
main/config/ignoreblocks - integer list - Block IDs that are deemed unacceptable. These blocks do not count toward claimblocks/unclaimblocks.
main/players/*/blockcounter - Stores the number of consequetive blocks placed in chunk lastclaim by *
main/players/*/lastclaim - Stores the last chunk the player placed or removed a block in. If this changes, blockcounter are reset.
main/players/*/gotwarning - Prevent the plugin from spamming people. This are set when players get "unclaimable land" warning, and are reset when player places/removes block in acceptable land.
main/players/*/walktest - Stores player's current walktest status. It is reset everytime player joins.
main/players/*/claims - List of claims. Gets all claims owned by *, required for /reset to work.
main/players/*/friends - Stores the player's friendslist
main/claims/* - Stores the owner of chunk *.
Does the plugin support permissions?
Yes, from version 1.7
The permissions nodes is as follows:
chunkautoclaimer.op - gives access to all OP commands AND possibility to build in areas the player normally isnt permitted to build in.
chunkautoclaimer.unlimited - unlimited claims, friends and claims does not need to be adjacent regardless of requiretouch setting.
Why does CAC ignore OPs? (ONLY in V1.1)
OP can build/destroy anywhere to be able to do its administrative tasks. If a OP want to only touch unprotected surfaces, he can enable
walktest by typing /walktest .
requiretouch, maxclaims and maxfriends does NOT apply to OPs.
What are /walktest good for? I dont see the point in the command?
Some examples:
- Your'e a OP and want to do some duties on unprotected land. You turn on /walktest to be sure to not touch protected land.
- You have just built a large house and want to be sure its protected in complete. You turn on /walktest and then try breaking random blocks around your house to eventually find any unprotected spots.
- You want to find some unprotected land, and don't want to wander into lands where you are on the owner's friendslist.
- You are gonna do some PvP, and dont want to unintentionally break blocks in your buildings.
- You want to do a real test of a contraption that you built, that might result in you unintentinally breaking blocks, and want to be sure.
- You have built a large complex and want to explore it "as a griefer".
Source Code:
PayPal Donate:
My Minecraft name: sebnie
TODO:
- Prevent unclaiming of chunks if the unclaim would cause 2 of the players chunk not to be adjacent anymore - if requiretouch are set to true.
(I do not have any solution for this, come with ideas for this)
- AntiSpam
- DynMap integration
- Translation fix so messages can be removed
- some bugfixes
- probably some way for users to indicate to the system that they are experienced, and this will make the mod more quiet, of course this can be toggled again if they regret their decision.
- Add information message to nonexperienced users when placing a chest, that they can protect it by placing block above it.
- Listfriends/listchunks commands which will allow player to list their friends/chunks
- /home command takes them to their last claimed chunk.
ToNotDo/WontFix:
- Per chunk/claim friendslist. This becomes too advanced to end users. I want to keep the plugin simple for end users. Either you trust a user, or you don't trust a user. Theres nothing between. Why would you trust the user to build in AREA A but not in AREA B?
- subclaims. A too advanced feature too.
- Database. Theres no need for this. Use this plugin on small servers and/or use a SSD if the plugin gets a performance impact.
评论 0
登录后参与评分
还没有评论,来抢沙发吧