- 欢迎来到Minecraft插件百科！
- 对百科编辑一脸懵逼？帮助:快速入门带您快速熟悉百科编辑！
- 因近日遭受攻击，百科现已限制编辑，有意编辑请加入插件百科企鹅群：223812289
Regionerator：修订间差异
跳转到导航
跳转到搜索
Qsefthuopq（留言 | 贡献） 无编辑摘要 |
Qsefthuopq（留言 | 贡献） 无编辑摘要 |
||
| （未显示同一用户的7个中间版本） | |||
| 第2行： | 第2行： | ||
|icon= | |icon= | ||
|plugin=Regionerator | |plugin=Regionerator | ||
|version=1. | |version=1.5.6 | ||
|pre= | |pre= | ||
|ver= | |ver= | ||
|author=Jikoo | |author=Jikoo | ||
|URL=https://www.spigotmc.org/resources/ | |URL=https://www.spigotmc.org/resources/regionerator.12219 | ||
}} | }} | ||
[[Category:管理]][[Category:创世]] | |||
=免责声明= | =免责声明= | ||
这个插件通过直接修改或删除region文件来删除区块. | 这个插件通过直接修改或删除region文件来删除区块.这无法被还原，建议有定期备份服务器地图的服务器使用。<br /> | ||
插件作者不会对该插件任何对服务器地图的损坏负责。 | |||
=作用= | =作用= | ||
regionerator删除不使用的区块和区域，让您的服务器释放硬盘空间，摆脱破旧不堪的建筑或荒芜的土地。<br /> | |||
在观察者模式玩家不会造成土地被标记。 | 在观察者模式玩家不会造成土地被标记。 | ||
| 第44行： | 第45行： | ||
**需要worldedit | **需要worldedit | ||
**编辑所选区域内的标记 | **编辑所选区域内的标记 | ||
=作者的话= | |||
每次插件尝试删除区块时，RegioneratorChunkDeleteEvent将会被激活.这个事件每周期每次会运行最多1024次,插件本身比旧版本更加有效,但对服务器负荷也许仍然很重,建议任何使用本插件的人都要谨慎.<br /> | |||
Regionerator 也不能保证区块能被完全删除- 有可能当加载区块时会被储存 卸载和等待被写入. | |||
Each time Regionerator attempts to delete a chunk, the RegioneratorChunkDeleteEvent is fired. The event can be called up to 1024 times per tick per cycle running, and Regionerator itself, while much more efficient than it used to be, is still quite heavy. Caution is advised for anyone using it. | |||
Regionerator also makes no guarantee that chunks are fully deleted - it's possible that chunks could be stored unloaded and waiting to be written when Regionerator visits them. | |||
=配置= | |||
# 进行标志的区块范围 | |||
chunk-flag-radius: 4 | |||
# 每10秒标志在线玩家附近的区块 | |||
seconds-per-flag: 10 | |||
# 每5秒保存标志 | |||
minutes-per-flag-autosave: 5 | |||
# Flags older than x days can be ignored and the region deleted. | |||
# To disable flagging, set this to 0. | |||
# days-till-flag-expires must be greater than 0 to be used with delete-new-unvisited-chunks | |||
days-till-flag-expires: 7 | |||
# Chunks generated after the plugin is installed are automatically flagged. | |||
# If false, these chunks will be permanently flagged until visited. | |||
# Setting this value to false will allow you to pre-generate your maps for reduced load from exploration. | |||
# It will also reduce the amount of time wasted deleting untouched areas. | |||
delete-new-unvisited-chunks: false | |||
# Time in between deleting regions in ticks (20 ticks = 1 second) | |||
ticks-per-deletion: 5 | |||
# Chunks checked for deletion per interval. Default (128) handles an entire region every 9 intervals. | |||
# If this value is 1024 or lower (1 or fewer regions per cycle) an entire run cycle is dedicated to deletion to prevent lag. | |||
chunks-per-deletion: 128 | |||
# Hours between deletion cycles (cycles all reset on plugin reload/server restart) | |||
hours-between-cycles: 12 | |||
# Allow deletion cycles for separate worlds to run simultaneously. | |||
# Only enable this option if your server hardware is quite good. | |||
allow-concurrent-cycles: false | |||
# Worlds the plugin is able to delete regions in | |||
# If you change this list, be sure to delete the field "delete-this-to-reset-plugin" so that areas in use are not deleted by accident. | |||
worlds: [] | |||
# Hooks to attempt to check for protections from. | |||
# If your protection plugin of choice isn't here, ask! | |||
hooks: | |||
ASkyBlock: true | |||
Factions: true | |||
Feudal: true | |||
GriefPrevention: true | |||
Kingdoms: true | |||
Landlord: true | |||
RedProtect: true | |||
Residence: true | |||
Towny: true | |||
WorldGuard: true | |||
VanillaSpawnProtection: true | |||
# Debug-level enables more and more verbose logging of actions as increased. | |||
# OFF - no debug messages | |||
# LOW - Minimal debug messages, periodic deletion reports | |||
# MEDIUM - More debug messages. Spammy, not recommended. | |||
# HIGH - Lots of debug messages. Don't enable this unless you have a serious issue. | |||
debug-level: LOW | |||
=常见问题= | |||
我的服务器很卡! 我该什么办? | |||
尝试减少chunks-per-deletion的数值. 删除必须在主线程上进行，以防止潜在的错误. 在初始运行之后，在需要删除大量区域的情况下，它会运行得更加顺畅。. | |||
为什么这个插件删除区块要这么长时间? | |||
Well, Regionerator 不会知道哪些是已加载或未加载去看. 它需要收集数据 for as long as it takes chunks to become unvisited before it can tell what's safe to delete. | |||
为什么重载区块这么慢? | |||
如果这对你来说很慢的话, 尝试增大 chunks-per-deletion 或减少 ticks-per-deletion 的数值. | |||
支持自定义世界生成吗? | |||
Regionerator 实际上并不会重新生成区域,只是删除了区域. 无论您使用的是什么世界生成器，当它再次生成时，都会提供区块. | |||
可以添加某个保护插件的插件支持吗? | |||
当然. 只要这个插件有我能检测出区块的办法, 我就可以添加这个插件的支持. 我无法保证很快完成, 但这个插件是开源的, 你可以自由地在GitHub上pull request. 我无法有效地测试插件因为我不用这插件, 所以我不保证插件会正常地运行. | |||
=支持的保护插件= | |||
*ASkyBlock (未测试) | |||
*Factions / FactionsUUID (未测试) | |||
*Feudal (支持) | |||
*GriefPrevention | |||
*Kingdoms (未测试) | |||
*Landlord (未测试) | |||
*RedProtect (未测试) | |||
*Residence (支持) | |||
*Towny (未测试) | |||
*WorldGuard (可能有问题) | |||
*原版出生点保护 | |||
=开源= | |||
[https://github.com/Jikoo/Regionerator github] | |||
---- | |||
<big>本插件采用CC BY-SA 4.0协议</big> | |||
2019年9月3日 (二) 10:19的最新版本
Regionerator
| 外文名 | Regionerator |
| 作者 | Jikoo |
| 最新版本 | 1.5.6 |
| 源地址 | https://www.spigotmc.org/resources/regionerator.12219 |
免责声明
这个插件通过直接修改或删除region文件来删除区块.这无法被还原，建议有定期备份服务器地图的服务器使用。
插件作者不会对该插件任何对服务器地图的损坏负责。
作用
regionerator删除不使用的区块和区域，让您的服务器释放硬盘空间，摆脱破旧不堪的建筑或荒芜的土地。
在观察者模式玩家不会造成土地被标记。
权限
输入指令需要regionerator.command 权限.
指令
/regionerator - 获取所有世界的当前状态.
/regionerator reload - 重新加载配置并重启所有删除任务.
/regionerator pause - 暂停删除任务。为了防止一些问题发生，插件将在暂停之前完成当前检测的区域。
/regionerator resume - 恢复删除任务.
/regionerator check - 检测你所在的区块状态.
/regionerator flag - 永久标记相关区域为已加载.
/regionerator unflag - 取消标记相关区域为已加载.
- 无参数 (例如 /regionerator flag)
- 只限玩家
- 编辑所在区块上的标记
- 区块 x 和区块 z (例如 /regionerator unflag 0 0)
- 只限玩家
- 编辑特定区块上的标记
- 世界名,区块 x 和区块 z (例如 /regionerator flag world 0 0)
- 玩家和控制台可使用
- 编辑特定世界特点区块上的标记
- 选择 (例如 /regionerator unflag selection)
- 只限玩家
- 需要worldedit
- 编辑所选区域内的标记
作者的话
每次插件尝试删除区块时，RegioneratorChunkDeleteEvent将会被激活.这个事件每周期每次会运行最多1024次,插件本身比旧版本更加有效,但对服务器负荷也许仍然很重,建议任何使用本插件的人都要谨慎.
Regionerator 也不能保证区块能被完全删除- 有可能当加载区块时会被储存 卸载和等待被写入.
Each time Regionerator attempts to delete a chunk, the RegioneratorChunkDeleteEvent is fired. The event can be called up to 1024 times per tick per cycle running, and Regionerator itself, while much more efficient than it used to be, is still quite heavy. Caution is advised for anyone using it. Regionerator also makes no guarantee that chunks are fully deleted - it's possible that chunks could be stored unloaded and waiting to be written when Regionerator visits them.
配置
# 进行标志的区块范围 chunk-flag-radius: 4 # 每10秒标志在线玩家附近的区块 seconds-per-flag: 10 # 每5秒保存标志 minutes-per-flag-autosave: 5 # Flags older than x days can be ignored and the region deleted. # To disable flagging, set this to 0. # days-till-flag-expires must be greater than 0 to be used with delete-new-unvisited-chunks days-till-flag-expires: 7 # Chunks generated after the plugin is installed are automatically flagged. # If false, these chunks will be permanently flagged until visited. # Setting this value to false will allow you to pre-generate your maps for reduced load from exploration. # It will also reduce the amount of time wasted deleting untouched areas. delete-new-unvisited-chunks: false # Time in between deleting regions in ticks (20 ticks = 1 second) ticks-per-deletion: 5 # Chunks checked for deletion per interval. Default (128) handles an entire region every 9 intervals. # If this value is 1024 or lower (1 or fewer regions per cycle) an entire run cycle is dedicated to deletion to prevent lag. chunks-per-deletion: 128 # Hours between deletion cycles (cycles all reset on plugin reload/server restart) hours-between-cycles: 12 # Allow deletion cycles for separate worlds to run simultaneously. # Only enable this option if your server hardware is quite good. allow-concurrent-cycles: false # Worlds the plugin is able to delete regions in # If you change this list, be sure to delete the field "delete-this-to-reset-plugin" so that areas in use are not deleted by accident. worlds: [] # Hooks to attempt to check for protections from. # If your protection plugin of choice isn't here, ask! hooks: ASkyBlock: true Factions: true Feudal: true GriefPrevention: true Kingdoms: true Landlord: true RedProtect: true Residence: true Towny: true WorldGuard: true VanillaSpawnProtection: true # Debug-level enables more and more verbose logging of actions as increased. # OFF - no debug messages # LOW - Minimal debug messages, periodic deletion reports # MEDIUM - More debug messages. Spammy, not recommended. # HIGH - Lots of debug messages. Don't enable this unless you have a serious issue. debug-level: LOW
常见问题
我的服务器很卡! 我该什么办?
尝试减少chunks-per-deletion的数值. 删除必须在主线程上进行，以防止潜在的错误. 在初始运行之后，在需要删除大量区域的情况下，它会运行得更加顺畅。.
为什么这个插件删除区块要这么长时间?
Well, Regionerator 不会知道哪些是已加载或未加载去看. 它需要收集数据 for as long as it takes chunks to become unvisited before it can tell what's safe to delete.
为什么重载区块这么慢?
如果这对你来说很慢的话, 尝试增大 chunks-per-deletion 或减少 ticks-per-deletion 的数值.
支持自定义世界生成吗?
Regionerator 实际上并不会重新生成区域,只是删除了区域. 无论您使用的是什么世界生成器，当它再次生成时，都会提供区块.
可以添加某个保护插件的插件支持吗?
当然. 只要这个插件有我能检测出区块的办法, 我就可以添加这个插件的支持. 我无法保证很快完成, 但这个插件是开源的, 你可以自由地在GitHub上pull request. 我无法有效地测试插件因为我不用这插件, 所以我不保证插件会正常地运行.
支持的保护插件
- ASkyBlock (未测试)
- Factions / FactionsUUID (未测试)
- Feudal (支持)
- GriefPrevention
- Kingdoms (未测试)
- Landlord (未测试)
- RedProtect (未测试)
- Residence (支持)
- Towny (未测试)
- WorldGuard (可能有问题)
- 原版出生点保护
开源
本插件采用CC BY-SA 4.0协议