PlotSquared在玩家死亡复活后无法使用传送指令. - 联机问答

Zapic

本帖最后由 Zapic 于 2018-12-21 18:14 编辑

如题,在玩家死亡复活后,使用类似于/p home,/p auto之类带有传送操作的指令都不会进行传送,会有消息提示,使用/p auto会claim地皮但不会传送.
但是在玩家退出重新进入服务器后,所有的指令又能用了...
一开始我以为是自动重生插件的问题,结果卸载掉后仍然有问题...
服务端用的Forge-1.12.2-14.23.5.2796+SpongeForge-14.23.5.2796-API7.1.2.
我认为可能出现问题的一些配置文件:
PlotSquared:
settings.yml:

# These first 7 aren't configurable
issues: "https://github.com/IntellectualSites/PlotSquared/issues"
suggestion: "https://github.com/IntellectualSites/PlotSquaredSuggestions"
wiki: "https://github.com/IntellectualSites/PlotSquared/wiki"
date: "19 Jan 2019 16:00:00 GMT"
build: "https://ci.athion.net/job/PlotSquared/2057"
commit: "https://github.com/IntellectualSites/PlotSquared/commit/6c6a00b"
platform: "Sponge"
# Show additional information in console
debug: true
# The big annoying text that appears when you enter a plot
# For a single plot: `/plot flag set titles false`
# For just you: `/plot toggle titles`
titles: true
# Enable or disable part of the plugin
# Note: A cache will use some memory if enabled
enabled-components:
# The database stores all the plots
database: true
# Events are needed to track a lot of things
events: true
# Commands are used to interact with the plugin
commands: true
# The UUID cacher is used to resolve player names
uuid-cache: true
# The plugin auto updater
updater: false
# Stores user metadata in a database
persistent-meta: true
# Optimizes permission checks
permission-cache: true
# Optimizes block changing code
block-cache: true
# Getting a rating won't need the database
rating-cache: true
# The converter will attempt to convert the PlotMe database
plotme-converter: true
# Allow WorldEdit to be restricted to plots
worldedit-restrictions: true
# Allow economy to be used
economy: true
# Send anonymous usage statistics. Bukkit only setting.
metrics: true
# Expiry will clear old or simplistic plots
plot-expiry: false
# Processes chunks (trimming, or entity/tile limits)
chunk-processor: true
# Kill mobs on roads
kill-road-mobs: true
# Kill items on roads
kill-road-items: false
# Kill vehicles on roads
kill-road-vehicles: true
# Notify a player of any missed comments upon plot entry
comment-notifier: false
# Let player's claim entire worlds with PlotSquared
worlds: true
# Actively purge invalid database entries
database-purger: false
# Delete plots when a player is banned
ban-deleter: false
ratings:
categories: []
claim:
# The max plots claimed in a single `/plot auto <size>` command
max-auto-area: 4
redstone:
# Disable redstone in unoccupied plots
disable-unoccupied: false
# Disable redstone when all owners/trusted/members are offline
disable-offline: false
# Detect and cancel invalid pistons on the edge of plots (e.g. placed with WorldEdit)
detect-invalid-edge-pistons: false
teleport:
# Teleport to your plot on death
on-death: false
# Teleport to your plot on login
on-login: false
# Add a teleportation delay to all commands
delay: 0
# The visit command is ordered by world instead of globally
per-world-visit: false
confirmation:
# Teleport to your plot on death
confirmation-timeout-seconds: 20
# Switching from PlotMe?
plotme:
# Cache the uuids from the PlotMe database
cache-uuds: false
# Relating to how many plots someone can claim
limit:
# Should the limit be global (over multiple worlds)
global: false
# The range of permissions to check e.g. plots.plot.127
max-plots: 127
chat:
# Sometimes console color doesn't work, you can disable it here
console-color: true
# Should chat be interactive
interactive: true
done:
# Require a done plot to download
required-for-download: false
# Only done plots can be rated
required-for-ratings: false
# Restrict building when a plot is done
restrict-building: false
# The limit being how many plots a player can claim
counts-towards-limit: true
web:
# The web interface for schematics
# - All schematics are anonymous and private
# - Downloads can be deleted by the user
# - Supports plot uploads, downloads and saves
url: "https://empcraft.com/plots/"
# The web interface for assets
# - All schematics are organized and public
# - Assets can be searched, selected and downloaded
assets: "https://empcraft.com/assetpack/"
# Configure the paths that will be used
paths:
schematics: "schematics"
bo3: "bo3"
scripts: "scripts"
templates: "templates"
translations: "translations"
uuid:
# Force using offline UUIDs (it usually detects the right mode)
offline: false
# Force using lowercase UUIDs
force-lowercase: false
# Use a database to store UUID/name info
use-sqluuidhandler: false
chunk-processor:
# Auto trim will not save chunks which aren't claimed
auto-trim: false
# Max tile entities per chunk
max-tiles: 4096
# Max entities per chunk
max-entities: 512
# Disable block physics
disable-physics: false
# This is an auto clearing task called `task1`
auto-clear:
task1:
threshold: 1
required-plots: -1
confirmation: true
days: 7
skip-account-age-days: -1
worlds:
- "*"
# See: https://github.com/IntellectualSites/PlotSquared/wiki/Plot-analysis
calibration:
variety: 0
variety-sd: 0
changes: 0
changes-sd: 1
faces: 0
faces-sd: 0
data-sd: 0
air: 0
air-sd: 0
data: 0

复制代码

Nucleus:
main.conf:

# 欢迎使用Nucleus1.7.0-S7.1.现在您修改的是Nucleus的主要配置文件.
#
# 如果您在使用nucleus的过程中出现了问题,我们为您提供了多渠道的联系方式:
#
# *Ore:https://ore.spongepowered.org/Nucleus/Nucleus
# *Nucleus官方文档::https://nucleuspowered.org/docs
# *Discord上的在线联系方式:https://discord.gg/MC2mAuS
#
# 感谢您使用Nucleus!
# ==============================================================
# +------------------------------------------------------------+
# |Modules|
# ||
# |设置为:|
# |ENABLED:以启动|
# |DISABLED:以禁用|
# |FORCELOAD:以强制启用并防止其他插件禁用|
# ||
# ||
# |请勿修改"-modules"的名字|
# |加上"-"是为了保证这个环节出现在最前面!|
# +------------------------------------------------------------+
"-modules" {
# 此模块用于提供管理员常用的指令.
admin=ENABLED
# 此模块管理玩家是否能够切换到AFK(暂离)状态.
afk=ENABLED
# 此模块帮助玩家在传送过后返回传送前的记录坐标点.
back=ENABLED
# 此模块为Nucleus增强版的封禁(Ban)管理系统.
ban=ENABLED
# 此模块允许聊天格式化,例如玩家前缀、昵称和一些其他信息.
chat=ENABLED
# 此模块将聊天记录单独的存储,以便于搜索.
chat-logger=ENABLED
# 此模块将指令使用记录显示在控制台上并单独的存储,以便于搜索.
command-logger=ENABLED
# 此模块允许有权限的用户实时监听其他玩家使用指令的情况.
command-spy=ENABLED
# 精确连接控制模块.此模块管理玩家是否能够进入服务器,没在白名单内的玩家将会看到相应的消息.
connection=ENABLED
# 此模块将控制玩家加入/离开服务器时候其他玩家看到的消息.
connection-messages=ENABLED
# 是否允许通过指令打开虚拟合成界面.
crafting-gui=ENABLED
# 此模块用于管理玩家死亡通告.
death-message=ENABLED
# 此模块是控制世界环境的工具包.
environment=ENABLED
# 此模块允许玩家通过指令来获得飞行模式.
fly=ENABLED
# 允许冻结指令将玩家冻结在原地
freeze-subject=ENABLED
# 此模块可以加载一些有趣的(通常不会有副作用的)指令.
fun=ENABLED
# 此模块将会为玩家提供私人的传送点(/home)
home=ENABLED
# 允许玩家在聊天中忽略其他玩家的信息
ignore=ENABLED
# 允许玩家通过指令查看服务器信息,这些信息将由服主以Text文本的形式提供.
info=ENABLED
# 允许查看其他玩家的背包
inventory=ENABLED
# 允许开启上帝模式
invulnerability=ENABLED
# 是否启用物品编辑模块,包括物品名字、描述和附魔.
item=ENABLED
# 是否启用监狱来惩罚熊孩子.
jail=ENABLED
# 是否启用快捷传送以传送到附近地点.
jump=ENABLED
# 此模块提供增强版的踢出“/Kick”指令.
kick=ENABLED
# 此模块允许服务器为玩家提供物品和工具包,可以通过指令领取也可以自动领取.
kit=ENABLED
# 此模块允许玩家间相互使用邮件进行留言.
mail=ENABLED
# 此模块提供了强化的私聊系统.
message=ENABLED
# 其他功能模块(Miscellaneous模块)
misc=ENABLED
# 管理/控制生物生成的模块.
mob=ENABLED
# 禁言管理模块,禁止指定玩家发言和执行指令.
mute=ENABLED
# 通过玩家名字封禁用户(而不是UUID)
nameban=ENABLED
# 允许玩家使用(同玩家名相区别的)昵称.
nickname=ENABLED
# 允许管理员们为玩家添加Note标记词条.
note=ENABLED
# 通过指令来检查玩家的信息.
playerinfo=ENABLED
# 允许将指令绑定在物品上,右键使用物品的时候激活相关指令.
powertool=ENABLED
# 提供基础的田地防踩踏和怪物防爆功能.
protection=ENABLED
# 为玩家提供随机传送功能.
rtp=ENABLED
# 增加一个规则指令.
rules=ENABLED
# 允许对服务器的服务器列表项进行修改.
server-list=ENABLED
# 添加简单的基于指令的服务器商店来购买和出售物品.
server-shop=ENABLED
# 简单格式化木牌文字的模块
sign=ENABLED
# 控制玩家的出生点等相关事宜的模块.
spawn=ENABLED
# 为管理者开启一个专有聊天频道.
staff-chat=ENABLED
# 允许玩家使用传送指令传送到其他玩家的位置.
teleport=ENABLED
# 允许使用隐身指令.
vanish=ENABLED
# 增加一个警告管理系统,将自动惩罚被警告的熊孩子.
warn=ENABLED
# 增加公用地标传送系统.
warp=ENABLED
# 世界管理,包括世界边界.
world=ENABLED
}
# +------------------------------------------------------------+
# | Admin |
# +------------------------------------------------------------+
admin {
# 公告的前缀和后缀,您可以使用的占位符:{{displayname}},{{name}}等.
broadcast-message-template {
prefix="&7[&c紧急公告&7]&r "
suffix=""
}
}
# +------------------------------------------------------------+
# | AFK |
# +------------------------------------------------------------+
afk {
# 如果设置为true,服务器将会在隐身的玩家进入AFK状态的时候发布通告.如果设置为false,只有没有隐身的玩家能够进入AFK状态.
afk-when-vanished=false
# 以秒为单位的时间,玩家如果在指定的时间内不活跃,将会自动进入AFK状态.设置为0以禁止此项,或者为玩家分配"nucleus.afk.exempt.toggle"权限.
afktime=300
# 以秒为单位的时间,玩家如果在指定的时间内不活跃,将会自动被服务器踢出.设置为0以禁止此项,或者为玩家分配"nucleus.afk.exempt.kick"权限.
#
# 请注意,这里的时间不是自从进入AFK之后开始计算的,而是从最后一次活跃的时候开始计算的.如果将此值设置为同"afktime"相等的值,那么相关玩家在进入AFK的同时就被服务器踢出.
afktimetokick=0
# 如果设置为true,任何尝试同AFK状态玩家交互的请求都会被告知此玩家处于AFK状态.
alert-on-command-send=false
# 如果设置为true,服务器将会在踢出不活跃玩家的时候发布通告,否则只有"nucleus.afk.notify"权限的玩家在被踢出的时候回发布通告.
broadcast-to-all-on-kick=true
# Iftrue,aplayerinspectatormodewillnothavetheirstatusbroadcastedtoplayers,norwilltheybekickedforgoingAFK.ThosewiththenotifypermissionwillstillseetheAFKmessages.
disable-in-spectator-mode=false
# 如果以下任何一段文字设置为空的话,他们将不会被发送.
messages {
# 由于不活跃而被踢出的玩家将会收到这个信息.
kick-message-to-subject="You have been kicked for being AFK for too long."
on-afk="&7*&6{{displayname}}&7暂时离开了."
on-command="&f{{displayname}}&7is currently AFK and may not respond quickly."
# 如果设置为空,将不会发送任何信息.
on-kick="&f{{displayname}} &7has been kicked for being AFK too long."
on-return="&7*&6{{displayname}}&7回来了."
}
# 设置为真,以下行为将会让玩家退出AFK状态.
triggers {
# 聊天
on-chat=true
# 执行指令
on-command=true
# 同任何物体交互
on-interact=true
# 移动
on-movement=true
# 转身(四处看)
on-rotation=true
}
}
# +------------------------------------------------------------+
# | Back |
# +------------------------------------------------------------+
back {
# 记录玩家上一次的死亡位置.
on-death=true
# 记录玩家穿越传送门之前的位置.
on-portal=false
# 记录玩家传送地标前的位置.
on-teleport=true
}
# +------------------------------------------------------------+
# | Bans |
# +------------------------------------------------------------+
ban {
# 临时封禁允许持续的最长时间(以秒为单位),如果设置-1将不限制此项.
maximum-tempban-length=-1
}
# +------------------------------------------------------------+
# | Chat |
# +------------------------------------------------------------+
chat {
# 一些模组或者插件会把玩家的前缀错误的移动到玩家消息中,如果出现这种情况,请将此项设置为true.
# 此时,Nucleus将会尝试修正它.
check-body-for-minecraft-prefix=false
# 当玩家执行"/me"时,自动添加的前缀.
me-prefix="&7*{{displayName}}"
# 如果设置为true,Nucleus将会尝试修改玩家的聊天内容.
modify-chat=true
# 如果设置为trueNucleus核心将接收并尝试按照自己的方式处理它.这可能有更高的优先级来处理并覆盖其他插件的处理方式,所以如果遇到问题请关闭此插件.
modify-main-message=true
# 如果设置为false,Nucleus将会优先考虑自己的前缀,而不会用被其他插件修改的前缀.
overwrite-early-prefixes=false
# 如果设置为false,Nucleus将会优先考虑自己的后缀,而不会用被其他插件修改的后缀.
overwrite-early-suffixes=false
# 如果设置为true,将会删除所有带有指向某个网页链接的下划线的蓝色文字.
remove-link-underlines=false
templates {
# 如果设置为true,Nucleus将会为正在发送消息的玩家选择最合适的聊天文字格式化模板.如果玩家没有"nucleus.chat.group"权限,将检查此玩家拥有的所有权限组.如果设置为false,Nucleus将只检测"nucleus.chat.group"的权限,并匹配现有的权限组聊天模板,如果没有匹配,Nucleus将应用默认模板,而不检查实际的权限组.
#
# 如果您服务器的聊天导致卡顿并且您开启了权限组聊天模板,尝试将此项设置为false,然后将"nucleus.chat.group"权限给予对应的权限组.
check-permission-groups=true
# 聊天格式化的默认模板(在某个组别模板没有被定义的时候)
default {
# 默认的玩家聊天颜色,如果此玩家/组别没有被定义"chatcolour"权限.如果设置默认的样式,请确保"namecolour"权限被设置为""(不改变颜色).请不要包含“&”格式化字符.
default-chatcolour=""
# 默认的玩家聊天字体,如果此玩家/组别没有被定义"chatstyle"权限.如果设置默认的样式,请确保"chatstyle"权限被设置为""(不改变字体).请不要包含“&”格式化字符.多个字体样式请用","分割开.
default-chatstyle=""
# 玩家聊天的默认颜色,如果此玩家/组别没有被定义"chatcolour"权限.如果设置默认的样式,请确保"namecolour"权限被设置为""(不改变颜色).请不要包含“&”格式化字符.
default-namecolour=""
# 玩家名字的默认字体,如果此玩家/组别没有被定义"namestyle"权限.如果设置默认的样式,请确保"namestyle"被设置为""(不改变格式).请不要包含“&”格式化字符.多个字体样式请用","分割开.
default-namestyle=""
# 设置聊天信息的前缀.{{prefix}}-前缀(权限插件的可选元素),{{suffix}}-后缀(权限插件的可选元素),{{name}}-真实ID,{{displayname}}-显示ID
prefix="&7[&r{{prefix:s}}{{displayname}}{{suffix}}&7]>&r "
# 设置聊天信息的后缀.{{prefix}}-前缀(权限插件的可选元素),{{suffix}}-后缀(权限插件的可选元素),{{name}}-真实ID,{{displayname}}-显示ID
suffix=""
}
# 组模板基于发送消息玩家所属的用户组,覆盖默认的模板格式.注意:组名区别大小写.
# 受权重值所影响,玩家将会使用与其匹配的最高权重值的模板,包括继承而来的权限组.如果两个权重值最高且相等的模板都可用,那么继承数量最多的组模板将会被使用.
group-templates {
DefaultTemplate {
# 默认的玩家聊天颜色,如果此玩家/组别没有被定义"chatcolour"权限.如果设置默认的样式,请确保"namecolour"权限被设置为""(不改变颜色).请不要包含“&”格式化字符.
default-chatcolour=""
# 默认的玩家聊天字体,如果此玩家/组别没有被定义"chatstyle"权限.如果设置默认的样式,请确保"chatstyle"权限被设置为""(不改变字体).请不要包含“&”格式化字符.多个字体样式请用","分割开.
default-chatstyle=""
# 玩家聊天的默认颜色,如果此玩家/组别没有被定义"chatcolour"权限.如果设置默认的样式,请确保"namecolour"权限被设置为""(不改变颜色).请不要包含“&”格式化字符.
default-namecolour=""
# 玩家名字的默认字体,如果此玩家/组别没有被定义"namestyle"权限.如果设置默认的样式,请确保"namestyle"被设置为""(不改变格式).请不要包含“&”格式化字符.多个字体样式请用","分割开.
default-namestyle=""
# 设置聊天信息的前缀.{{prefix}}-前缀(权限插件的可选元素),{{suffix}}-后缀(权限插件的可选元素),{{name}}-真实ID,{{displayname}}-显示ID
prefix="{{prefix:s}}{{displayname}}{{suffix}}&f: "
# 设置聊天信息的后缀.{{prefix}}-前缀(权限插件的可选元素),{{suffix}}-后缀(权限插件的可选元素),{{name}}-真实ID,{{displayname}}-显示ID
suffix=""
# 此模板的权重值,当多个模板都符合作用条件的时候,高数值的模板将会最终作用在聊天信息.
weight=1
}
}
# 如果设置为true,Nucleus将会在玩家发送消息的时候选择最合适的模板.如果设置为假
# 将会永远使用默认的聊天模板,但是将有一个性能增益,因为不需要从权限插件中检索玩家的权限组.
# 如果服务器有严重的性能问题时,请关闭此项.(这通常是由于权限插件功能不够完善)
use-group-templates=true
}
}
# +------------------------------------------------------------+
# | Chat Logger |
# +------------------------------------------------------------+
chat-logger {
# 是否开启日志记录.
enable-logging=false
# 是否记录聊天信息.
log-chat=true
# 是否记录邮件信息.
log-mail=false
# 是否记录私聊信息.
log-messages=true
}
# +------------------------------------------------------------+
# | Command Logger |
# +------------------------------------------------------------+
command-logger {
# 用来作为白/黑名单的指令集(参见whitelistoption).每个指令只需要记录一个简称即可.
command-filter=[]
# 如果任何选项设置为true,记录指令发起者.
log-command-source {
command-block=false
console=true
other-source=false
subject=true
}
# 如果设置为true,将会记录指令——/logs/nucleus/commands
log-to-file=false
# 如果设置为true,"command-filter"内包含的指令集将会作为白名单免于记录.
whitelist=false
}
# +------------------------------------------------------------+
# | Command Spy |
# +------------------------------------------------------------+
command-spy {
# 黑名单("filter-is-whitelist"为true的时候作为白名单)用于检测那些指令需要监听.
command-filter=[]
# 如果设置为true,"command-filter"将会作为一个监听的白名单使用,否则,它将会作为黑名单检测.
filter-is-whitelist=true
# 用于显示玩家指令的前缀.
prefix="&7[CS: {{name}}]: "
}
# +------------------------------------------------------------+
# | Connection |
# +------------------------------------------------------------+
connection {
# 可用预留槽的最大数目.如果设置-1将不限制此项.
reserved-slots=-1
# 如果此项非空,玩家在尝试加入满人的服务器的时候将会收到相关文字消息.
server-full-message=""
# 如果此项非空,白名单外的玩家在尝试加入白名单模式下的服务器的时候将会收到相关文字消息.
whitelist-message=""
}
# +------------------------------------------------------------+
# | Connection Messages |
# +------------------------------------------------------------+
connection-messages {
# 当检测到玩家更换ID的时候显示的提示信息.'使用{{previousname}}作为占位符来显示玩家之前的名字.'
changed-name-message="&f{{name}} &ewas previously known by a different name - they were known as &f{{previousname}}"
# 如果设置为true,拥有"nucleus.connectionmessages.disable"权限的玩家将不会在登录和退出的时候发布提示.
disable-with-permission=false
# 如果设置为true,当一个玩家被检测到以一个新ID登录的时候将会发布服务器提示.
display-name-change-if-changed=true
# 此消息可以使用所有的Minecraft文字格式化字符码.您可以使用'"{{name}}"'作为新玩家ID的占位符.
first-login-message="&f欢迎&6{{name}}&f来到&6Zapic&f的工业服!"
# 如果设置为true,Nucleus将会尝试确保每一名玩家都能看到登录/退出的相关提示信息,某些插件可以潜在的覆盖此项.
force-show-all-connection-messages=true
# 当玩家登录的时候显示的文本.此消息可以使用所有的Minecraft文字格式化字符码.您可以使用'"{{name}}"'作为新玩家ID的占位符.
login-message="&8[&a+&8] &f{{name}}"
# 当玩家退出的时候显示的文本.此消息可以使用所有的Minecraft文字格式化字符码.您可以使用'"{{name}}"'作为新玩家ID的占位符.
logout-message="&8[&c-&8] &f{{name}}"
# 允许修改登录信息.
modify-login-message=true
# 允许修改退出信息.
modify-logout-message=true
# 显示第一次加入服务器的提示信息.
show-first-login-message=true
}
# +------------------------------------------------------------+
# | Core |
# +------------------------------------------------------------+
core {
# 如果设置为true,如果您携带通配符权限(例如"*"或者"nucleus")登录,您将会收到由于使用通配符带来的相关问题的提醒如果您乐意使用通配符权限,请将此设置为false.
check-for-wildcard=false
# 如果设置此项,玩家在聊天位置点击其他玩家ID到时候,将会把相关的指令自动输入到执行点击动作的玩家聊天栏.使用{{player}}作为被点击玩家的ID.
command-on-name-click="/msg {{subject}}"
# 如果设置为true,控制台执行的命令会影响那些对命令有豁免权限的玩家.
console-overrides-exemptions=true
# 指定Nucleus数据文件的存储目录.默认情况下,数据文件将会存储在根目录.您可以使用绝对路径或者相对路径进行指定.
#
# |注意|修改此路径您应当注意到:
# *此修改仅会在重启后生效.
# *旧文件将不会自动移动到您设置的新的位置,您应当自己手动将文件拷贝过去
# *文件将会存储在指定位置的"nucleus"子文件夹内.
# *如果Nucleus无法找到指定路径,那么您设置过的路径将会被忽略,所以请确保您预先创建了对应的路径.
# *MC原版数据(不同于Nucleus自己存储的插件数据)是不受影响的.
#
# 通常情况下,您可能希望将数据存储在(使用UNIX路径):
# *"config/nucleus"这将会把数据存储在Nucleus配置文件夹下
# *"world"这将会把数据存储在主世界地图文件夹下.
#
# 如果不是必要(或者你清楚的知道这个应该如何配置),请——不——要——修改这一参数!大多数的管理员都不需要移动数据存储路径,所以您只需将此保留默认即可!
data-file-location=default
# 如果设置为true,将会把指令的堆栈追踪打印在控制台上.
debug-mode=false
# 如果为true,则权限"核.所有者","核.管理","原子核.mod"和"原子核.用户"可以用作permissionsto授予这些级别的所有建议的权限.请注意:**核setupperms将存在,但对于那些使用此权限结构的人是不必要的*任何特定权限将覆盖这些权限(因此,将"nucleus.home.base"设置为"false"应覆盖"核心".用户的真实该特定权限.
#
# 这些权限旨在避免使用通配符.一些权限没有给这些承滴盘,这是设计-登录时消失的权限(例如)必须始终单独给出.
enable-parent-perms=true
kick-on-stop {
# 如果设置为true,Nucleus将会在服务器停止的时候把所有玩家提前踢出.
enabled=true
# 当服务器关闭/重启的时候,以下信息将会呈现给玩家.你也可以使用/stop[reason]指令来覆盖下面的显示文本.
message="服务器正在重启,请等待3分钟..."
}
# 在尝试统计玩家人数的时候,启用此项将会把在Nucleus插件安装之前的玩家加入统计,但是可能导致同未注册过数据键的插件不兼容.如果您希望获得更好的兼容性,请讲此项设置为false,如果为了统计的准确性,此项可为true.
more-accurate-visitor-count=false
# 确定离线玩家的最大数量,并使其成为Nucleus指令的执行对象.
offline-user-tab-limit=20
# 如果将此值设置为"default",将会根据您的系统设置使用语言偏好(如果Nucleus预设库中存在此语言文件的话).如果设置为语言代号,Nucleus将会尝试使用指定语言预设作为默认语言.Nucleus优先会使用"en-GB"(英语)预设.
#
# 翻译的相关社区支持工作已经开展了.如果您有兴趣协助我们将您的母语翻译给Nucleus作为语言预设,请在Discord上面联系我们.
override-language=zh-CN
# 当Nucleus进行保存的时候,记录在控制台.
print-on-autosave=false
# 这一段参数用来定义玩家传送时,指定传送点周围的检测范围,.较大的数值意味着Nucleus将会检测更广泛的区域,过大的数值将会导致服务器延迟,默认情况下,一下的参数最为实用.
safe-teleport-check {
height=3
width=9
}
# 如果设置为真,当没有检测到权限插件或经济插件的时候,Nucleus将会在服务器启动的时候在控制台输出一条警告,如果你认为无关紧要,或者不想看到这些警告的话,将此项设置为false.
show-warning-on-startup=true
# 如果设置为true,一个"messages.conf"文件将会生成在Nucleus文件夹下,您可以通过这个文件自定义指令提示信息.
use-custom-message-file=true
# 如果设置为true,将会根据事件取消玩家的传送等待.
warmup-canceling {
# 执行一个指令
cancel-on-command=false
# 移动
cancel-on-move=true
}
# 如果在世界的UUID发生改变的时候,您发现了无法修正的问题,这将允许您将旧世界的UUID重定向为新的(或者世界名).这是一个用于指定新世界同旧世界的UUID和名字的映射集合(Map),以下部分的写法都是有效的:
#
# "123e4567-e89b-12d3-a456-426655440000"="world"
#
# "123e4567-e89b-12d3-a456-426655440000"="1b671a64-40d5-491e-99b0-da01ff1f3341"
#
# 其他插件将会检测这个映射集的内容来实现他们自己的迁移,而是否支持这个功能取决于调用此方法的插件.
world-uuid-migration {}
}
# +------------------------------------------------------------+
# | Death Messages |
# +------------------------------------------------------------+
death-message {
# 如果设置为"false",Nucleus将不会在玩家死亡时发送死亡通告.
enable-death-messages=true
# 如果设置为true,Nucleus将会尝试确保每一位玩家都收到了死亡通告.
force-show-all-death-messages=true
}
# +------------------------------------------------------------+
# | Environment |
# +------------------------------------------------------------+
environment {
# 允许天气设定的最大持续时间,以秒为单位.设置为-1不受限制.
maximum-weather-timespan=-1
}
# +------------------------------------------------------------+
# | Fly |
# +------------------------------------------------------------+
fly {
# 如果设置为true,当玩家不处于飞行模式但其登录地点处于空中的时候,Nucleus将会尝试为指定玩家寻找一个安全着陆点.
find-safe-location-on-login=true
# 如果设置为true,只有拥有飞行权限(nucleus.fly.base)的玩家可以在登录时允许飞行.如果设置为false,没有飞行权限的玩家如果在登录时处于空中,他们会被放置在地面.
require-fly-permission-on-login=false
# 如果设置为true,玩家处于飞行模式下线,他们的飞行状态将会被记录.如果设置为false,此信息仅会在玩家使用/fly指令的时候记录.
save-all-flystate-on-quit=true
}
# +------------------------------------------------------------+
# | Home |
# +------------------------------------------------------------+
home {
# 如果设置为true,如果一个玩家有超过其权限允许的家上限("home-count")的话,他将不能使用任何回家指令直到他删除了多余的家.
prevent-home-count-overhang=true
# 如果设置为true,玩家重生将会回到他们默认名为home的家.
respawn-at-home=false
# 如果设置为true,Nucleus将会尝试确保玩家的回家指令会传送到附近的安全区域(例如:其他玩家将传送地点的方块打碎).
use-safe-warp=true
}
# +------------------------------------------------------------+
# | Info |
# +------------------------------------------------------------+
info {
info {
# 如果"use-default-info-section"为true,指定的文件目录将会在玩家使用"/info"指令时显示.
default-info-section=info
# 如果设置为true,当一个玩家执行"/info"指令的时候,"default-info-section"部分的文件将会被呈现给他,/info指令将会默认的使用同/info<default-section>相同的功能.
# 如果设置为真,只有拥有"nucleus.info.list"权限的玩家可以执行"/info-l"指令并显示相关信息,如果设置为false,或者检索的信息不存在,将不会检测玩家的权限.
use-default-info-section=false
}
motd {
# 以秒为单位的延迟,在玩家登录游戏之后将MOTD发送给玩家.
motd-login-delay=0.5
# 用于展示每一页MOTD的标题,允许使用Minecraft文字格式化字符码.如果此处留空,将会完全隐藏MOTD的标题.
motd-title="&6MOTD"
# 如果设置为true,将在默认情况下为登录到服务器的玩家展示定义在"motd.txt"中的MOTD.
show-motd-on-join=true
# 如果设置为false,将会禁用页面管理系统展示MOTD.如果您只有一页MOTD,或者你不希望看到类似<<>>的标记出现,请将此项设置为false,否则我们建议您打开此项.
use-pagination=true
}
}
# +------------------------------------------------------------+
# | Invulnerability |
# +------------------------------------------------------------+
invulnerability {
# 如果设置为true,上帝模式的玩家将无法对其他玩家和生物造成伤害,除非其拥有nucleus.god.pvp.override权限.
disable-pvp-on-god=false
# 如果设置为true,只有拥有nucleus.god.base权限的玩家可以在登陆时保持上帝模式.如果设置为false,将不会在登录时检测玩家的上帝权限.
require-god-permission-on-login=false
}
# +------------------------------------------------------------+
# | Item |
# +------------------------------------------------------------+
item {
repair {
# 禁止使用/repair维修的物品黑名单(当下面use-whitelist为true时为白名单模式).
restrictions=[]
# 如果设置为true,上方的restriction项将会作为白名单的形式,仅在白名单内的物品能够维修.
use-whitelist=false
}
skull {
# 如果设置为true,Nucleus将会启用/skull指令作为"/give[player]skull[number]3{SkullOwner:[skullplayer]}"指令的简写(译者注:实际是用来获取指定玩家头颅的指令,eg./skullTollainear)
use-minecraft-command=false
}
}
# +------------------------------------------------------------+
# | Jail |
# +------------------------------------------------------------+
jail {
# 监狱内玩家允许执行的指令集.请不要添加“/”.
allowed-commands=[
m,
msg,
r,
mail,
rules,
info
]
# 如果设置为true,监狱内的玩家仅在在线情况下计时.
jail-time-counts-online-only=false
# 如果设置为true,监狱内的玩家将会被禁言.
mute-when-jailed=true
# 如果设置为true,/unjail指令将会检测执行者的"nucleus.jail.unjail"权限进行分监狱检验.
require-separate-unjail-permission=false
}
# +------------------------------------------------------------+
# | Jump |
# +------------------------------------------------------------+
jump {
# 使用/jump指令时所传送的最大距离.负数的值代表无限制-谨慎使用.
max-jump-distance=350
# 使用/thru指令时所传送的最大距离.负数的值代表无限制-谨慎使用.
max-thru-distance=25
unstuck-distances {
# /unstuck竖直方向上传送的最大距离.
height=1
# /unstuck水平方向上传送的最大距离.
horizontal-radius=1
}
}
# +------------------------------------------------------------+
# | Kit |
# +------------------------------------------------------------+
kit {
# 如果设置为true,玩家背包无法承载的物品将会掉落在玩家周围的地面上.
drop-items-if-inventory-full=true
# 如果设置为true,将会忽视"drop-items-if-inventory-full",同时,kit工具包只有在背包有足够空间的时候才继续给予.
must-get-all-items=false
# 如果设置为true,出现在道具名字或者描述中的所有类似{{name}}或者{{displayname}}的占位符将会替换为对应的文字.
process-tokens-in-lore=false
}
# +------------------------------------------------------------+
# | Message |
# +------------------------------------------------------------+
message {
# /helpop指令的前缀.
helpop-prefix="&7HelpOp: {{name}} &7> &r"
# 私聊接收者的显示前缀.使用{{from}}和{{to}}来区分发送者/接收者,{{fromDisplay}}或者{{toDisplay}}来显示名字.
msg-receiver-prefix="&7[&6{{fromDisplay}}&7 -> 我]:&r"
# 私聊发送者的显示前缀.使用{{from}}和{{to}}来区分发送者/接收者,{{fromDisplay}}或者{{toDisplay}}来显示名字.
msg-sender-prefix="&7[我 -> &6{{toDisplay}}&7]:&r"
socialspy {
# 如果设置为true,Nucleus将会检测"nucleus.socialspy.force"权限来开启私聊监听.
allow-forced=false
# 当玩玩家被禁言时(或者由其他原因导致的消息/指令发送失败),社交监听的前缀标签.
cancelled-messages-tag="&c[cancelled] "
# 设置社交监听的级别和任意自定义消息目标.
levels {
# 通过API注册过的自定义目标的监听等级.
custom-targets=2147483647
# 服务器的社交监听等级.
server=2147483647
}
# 社交监听者所受到监听信息的前缀和信息的格式化.使用{{from}}和{{to}}来定义消息的发送者/接收者,{{fromDisplay}}或{{toDisplay}}显示玩家名字.位于前缀结尾处的颜色和字体格式化符号将会影响后面携带信息的颜色和字体.
msg-prefix="&7[SocialSpy] [{{fromDisplay}}&7 -> {{toDisplay}}&7]: &r"
# 社交监听的消息前缀,作用于一名玩家不能发送一个消息给一个使用了/msgtoggle(屏蔽所有玩家信息)的玩家.
msgtoggle-blocked-messages-tag="&7[&c失败&7] "
# 如果设置为true,并且"use-levels"为真true,玩家也能够监听同级别玩家的信息.
same-levels-can-see-each-other=true
# 控制监听器所监听的*发送者*类型.
senders-to-spy-on {
custom-target=true
player=true
server=true
}
# 如果设置为true,显示玩家发送失败的信息(通常因为被禁言).
show-cancelled-messages=false
# 如果设置为true,Nucleus将会检测"nucleus.socialspy.level"项中的一个整数等级.一个玩家可以查看其查看等级以下的消息,
# 除非"same-levels-can-see-each-other"项被设置为true,这种情况下,他们能够监听同等级的信息.玩家的默认等级为0.
use-levels=false
}
}
# +------------------------------------------------------------+
# | Miscellaneous |
# +------------------------------------------------------------+
misc {
# 设置玩家通过/speed指令所获取的最大速度增益.
max-speed=5
}
# +------------------------------------------------------------+
# | Mob |
# +------------------------------------------------------------+
mob {
# /spawnmob所能生成实体的最大数量.
max-mobs-to-spawn=20
# 如果设置为true,Nucleus将会检测执行/spawnmob玩家的权限(译者注:只有拥有相关权限的玩家才能通过/spawnmob指令生成相关的实体).
# 相关权限为"nucleus.spawnmob.mobs.<mobid>",此处任何实体的id中的":"(半角冒号)替换为"."(半角点)即可.例如,生成一个爬行者的权限节点应该为
# "nucleus.spawnmob.mobs.minecraft.creeper".如果允许生成所有Minecraft原版实体,可以给予玩家"nucleus.spawnmob.mobs.minecraft"权限.
separate-mob-spawning-permissions=false
# 限制禁止生成的生物.每一个部分都于一个世界相对应,此处的世界名大小写敏感.
spawning-blocks {
DIM-1 {
# 实体或者方块的完整ID,Minecraft实体应该以"minecraft:"开头.
block-mobs-with-ids=[]
# 如果设置为true,所有的原版实体将会禁止在此世界生成.
block-vanilla-mobs=false
}
DIM1 {
# 实体或者方块的完整ID,Minecraft实体应该以"minecraft:"开头.
block-mobs-with-ids=[]
# 如果设置为true,所有的原版实体将会禁止在此世界生成.
block-vanilla-mobs=false
}
world {
# 实体或者方块的完整ID,Minecraft实体应该以"minecraft:"开头.
block-mobs-with-ids=[]
# 如果设置为true,所有的原版实体将会禁止在此世界生成.
block-vanilla-mobs=false
}
}
}
# +------------------------------------------------------------+
# | Mute |
# +------------------------------------------------------------+
mute {
# 被禁言的玩家将禁止执行以下指令.这是聊天模组相关的附加内容,/m已经被添加进禁止发言的阻止指令列表.
blocked-commands=[
"minecraft:me",
say
]
# 最大持续时间(以秒为单位)除非相关玩家有bypass权限.如果设置-1将不限制此项.
maximum-mute-length=-1
# 如果设置为true,禁言的时间将会以其在线的服务器tick数为准进行计时.
mute-time-counts-online-only=false
# 被禁止发言的标签(译者注:显示在相关无法发送/执行的指令后面).
muted-chat-tag="&7[&c禁言中&7] "
# 如果设置为true,解除禁言的指令将需要"nucleus.mute.unmute"权限才能执行.
require-separate-unmute-permission=true
# 如果设置为true,拥有"nucleus.mute.seemutedchat"权限节点的玩家将能看到被禁言用户未发送成功的消息.
see-muted-chat=false
}
# +------------------------------------------------------------+
# | Name Banning |
# +------------------------------------------------------------+
nameban {
default-reason="Your Minecraft username is not appropriate for this server. Please change it before attempting to access this server."
}
# +------------------------------------------------------------+
# | Nickname |
# +------------------------------------------------------------+
nickname {
# 昵称的最大长度.
max-nickname-length=20
# 昵称的最小长度.
min-nickname-length=3
# 昵称能够包含的字符,使用正则表达式来描述可支持的文字,如果Nucleus无法在此读取正则表达式的话,将会使用默认的"[a-zA-Z0-9_]+".如果想允许使用所有的字母,请使用".+".
pattern="[a-zA-Z0-9_]+"
# 聊天信息中的昵称前缀.
prefix="&7-"
}
# +------------------------------------------------------------+
# | Note |
# +------------------------------------------------------------+
note {
# 如果设置为true,拥有nucleus.note.showonlogin权限的玩家将会在拥有note条目的玩家登录的时候显示相关的提示.如果设置为false,则不会收到提醒.
show-login=true
}
# +------------------------------------------------------------+
# | Player Info |
# +------------------------------------------------------------+
playerinfo {
list {
list-grouping-by-permission {
# 如果启用按用户组显示list列表,不在任何用户组中的玩家将会默认的被放置在此用户组内.
default-group-name=Default
# 如果启用,list指令将会按用户组显示玩家列表.
enabled=true
# 如果启用按用户组显示list列表,那么任何在此处列出的用户组将会按与组名相对应的文字显示.
# 多个用户组可以使用相同的简称,此时将会被绑定在同一个组内.
group-aliases {
Admin=管理员
Default=玩家
}
# 此列表中的任何用户组将按此顺序列出,作为高于所有其他的用户组的组,它们将按字母顺序显示在下面.
group-order=[]
# 如果设置为true,如果一个未被定义简写的用户组没有被添加进上方的”group-aliases“部分,相关用户组将会被理解为`default`组.
use-aliases-only=false
}
# 如果你使用Multicraft维护服务器的话,请开启此项,此时控制台的/list指令将会被/minecraft:list指令代替.
server-panel-compatibility=false
# 此模板用于显示玩家的名字,它使用和聊天模板相同的占位符,默认为"{{displayname}}".
template="{{displayname}}"
}
seen {
# 如果设置为true,此指令只会给拥有"nucleus.seen.extended"权限节点的玩家展示完整的玩家数据信息.如果设置为false,信息将会根据执行者权限而现实(如果一个玩家拥有/ban相对应的权限那么他就能查看与ban相关的信息).
require-extended-permission-for-module-info=false
}
}
# +------------------------------------------------------------+
# | Protection |
# +------------------------------------------------------------+
protection {
# 禁止踩踏农田.
disable-crop-trample {
mobs=true
players=true
}
mob-griefing {
# 如果设置为true,将禁止生物破坏地形,白名单内的生物让然可以破坏地形.
enable-protection=true
whitelist=[]
}
}
# +------------------------------------------------------------+
# | rtp |
# +------------------------------------------------------------+
rtp {
# 在随机传送时寻找安全着陆点的最大尝试次数,将此值设置的过低将会由高几率传送失败.(译者注,将此值设置的过高可能导致过高的服务器性能消耗)
attempts=5
# 使用/rtp指令的时候默认的传送类型.可用的选项为:
#
# *"nucleus:default":标准的随机传送方式,将会以出生点为原点,最小/最大半径范围内的随机传送;
# *"nucleus:surface_only":随机传送将会尝试仅搜索可落脚的地表(即头顶不会有任何方块)的位置,以出生点为原点,最小/最大半径范围内进行随机传送;
# *"nucleus:around_player":同默认传送方式相似的随机传送,但是随机传送的范围将会以玩家所在坐标为原点,而不是世界出生点;
# *"nucleus:around_player_surface":同仅传送至表面的传送方式相似的随机传送,但是随机传送的范围将会以玩家所在坐标为原点,而不是世界出生点;
#
# 其他插件可能会添加他们独有的传送模式,这种情况下,他们将会在这里给您以ID形式的额外的可选的传送方式.
default-method="nucleus:around_player_surface"
# 如果此项不为空,并且有一个同此项值相匹配的世界名(大小写敏感的),那么当玩家执行`/rtp`的时候,将默认的在指定世界进行随机传送.否则会把玩家随机传送到其所在世界的随机位置.
default-world=""
# 传送位置的最大高度.
maximum-y=255
# 随机传送所检测的,以世界中心(或者世界边界的中心)为原点到随机传送范围的最小半径.
min-radius=0
# 传送位置的最小高度.
minimum-y=0
# 如果设置为true,Nucleus将会在执行随机传送前检测执行此命令的玩家是否拥有"nucleus.rtp.worlds.<worldname>"权限(此处的worldname可以为小写).
per-world-permissions=true
# 玩家将不会被传送到下面列表中的生物群系内.
prohibited-biomes=[
"minecraft:frozen_ocean",
"minecraft:ocean",
"minecraft:deep_ocean"
]
# 以世界中心(或者世界边界的中心)为原点,随机传送的最大检测半径,此项的值不会覆盖世界边界的值.
radius=300000
# 如果一个世界被添加进下方的列表,这个世界的相关传送参数将会覆盖全局设定世界名需要小写(所以地狱的世界名应该为dim-1").
#
# 复制示例部分并粘贴在块内,将“example”修改为世界名字来为不同的世界指定相关参数.
world-overrides {
example {
# 使用/rtp指令的时候默认的传送类型.可用的选项为:
#
# *"nucleus:default":标准的随机传送方式,将会以出生点为原点,最小/最大半径范围内的随机传送;
# *"nucleus:surface_only":随机传送将会尝试仅搜索可落脚的地表(即头顶不会有任何方块)的位置,以出生点为原点,最小/最大半径范围内进行随机传送;
# *"nucleus:around_player":同默认传送方式相似的随机传送,但是随机传送的范围将会以玩家所在坐标为原点,而不是世界出生点;
# *"nucleus:around_player_surface":同仅传送至表面的传送方式相似的随机传送,但是随机传送的范围将会以玩家所在坐标为原点,而不是世界出生点;
#
# 其他插件可能会添加他们独有的传送模式,这种情况下,他们将会在这里给您以ID形式的额外的可选的传送方式.
default-method="nucleus:default"
maximum-y=255
min-radius=30000
minimum-y=0
radius=30000
}
}
}
# +------------------------------------------------------------+
# | Rules |
# +------------------------------------------------------------+
rules {
# 规则界面的标题.
rules-title="&6规则"
}
# +------------------------------------------------------------+
# | Server List |
# +------------------------------------------------------------+
server-list {
# 如果设置为true,服务器在线玩家数将会被隐藏起来.
hide-player-count=false
# 如果设置为true,任何隐身状态下的玩家都不会出现在在线玩家数的计数范围内.
hide-vanished-players=false
# 如果设置为true,当一个玩家尝试在服务器列表里ping服务器的时候,以下的其中之一条信息将会被发送给这个玩家.如果在"whitelist"模式下,这一模块将仅在白名单模式下有效.
modify-server-list-messages=FALSE
# 发送给玩家的文字消息.若要拆分成两行,请在希望换行符的地方使用\n.(译者注:作用于服务器列表中的服务器描述)
server-list-messages=[
"&bWelcome to the server!\n&cCome join us!"
]
# 当服务器处于白名单模式下的为玩家显示的文字信息若要拆分成两行,请在希望换行符的地方使用\n.
#
# 如果此项留空,将会默认使用`server-list-messages`项内设置的文字.
whitelist-server-list-messages=[]
}
# +------------------------------------------------------------+
# | Server Shop |
# +------------------------------------------------------------+
server-shop {
# 玩家单次交易最多流通的物品数量上限.
max-purchasable-at-once=64
}
# +------------------------------------------------------------+
# | Spawn |
# +------------------------------------------------------------+
spawn {
# 如果设置为true,如果玩家尝试重生在自己的床上,Nucleus将会覆盖此行为,如果设置为false,Nucleus将会忽视在床上重生.
affect-bed-spawn=true
# 如果设置为true,Nucleus将会尝试强制将第一次加入服务器的玩家传送到指定地点.
# 只有在你需要使用Nucleus无视其他插件处理重生和出生规则的时候将此项启用.
force-first-spawn=true
# 这个部分将在单独世界或者全世界控制重生和/spawn的工作特性.
global-spawn {
# 如果此项和"spawn-on-login"项都被设置为true,玩家将会在登录的时候被传送到"target-spawn-world"项所对应世界的出生点.
on-login=true
# 如果设置为true,重生(例如死亡之后的重生)将会把玩家送往"target-spawn-world"项对应的世界的出生点,如果设置为false,他们将会被送往当前世界的出生点.
on-respawn=true
# 如果设置为true,玩家执行/spawn时会将其传送到默认世界的出生点(即"target-spawn-world"项对应的位置),如果设置为false,他们将会被送往当前世界的出生点.
on-spawn-command=true
# 默认的用来做服务器出生点的世界.如果此项无效(译者注:即Nucleus找不到这个世界或者未加载)默认的世界(译者注:world)将会被默认设置为服务器出生点.
target-spawn-world=spawn
}
# 如果设置为true,玩家在/spawn指定世界时将会检测其是否拥有"nucleus.spawn.worlds.<worldname>"权限节点,此处的“worldname”是世界名的小写形式.
per-world-permissions=false
# 如果设置为true,玩家将会在登录时被传送到默认世界的出生点.除非他们是初次登录或者拥有权限节点"nucleus.spawn.exempt.login".
spawn-on-login=true
# 如果"spawn-on-login"的值设置为“true”,当一个玩家登录在下列中任意一个世界的时候,他们将不会被重新传送到出生点.
#
# 这个列表既支持世界名,也支持世界的UUID.
spawn-on-login-exempt-worlds=[]
# 如果设置为true,使用/spawn指令的时候,将会为传送的玩家寻找一个安全着陆点.如果设置为false,将会直接将玩家传送到指定位置而不进行安全着陆检测.(译者注:关闭此项可能会将玩家传送到岩浆或者虚空中,如果目标点是岩浆或者虚空的话).
use-safe-spawn=true
}
# +------------------------------------------------------------+
# | Staff Chat |
# +------------------------------------------------------------+
staff-chat {
# 如果设置为true,Nucleus将会包括全部常用的聊天标签在聊天界面,包括前缀.
"include-standard-chat-formatting"=false
# 一个Minecraft文字格式化字符码(译者注:详见Minecraft颜色代码),用来将管理员聊天文字格式化.
message-colour=b
# '管理员聊天信息的前缀,你可以选择性使用以下占位符:{{prefix}}-前缀(由权限插件提供),{{suffix}}-后缀(由权限插件提供),{{name}}-实际名字,{{displayname}}-显示名字(译者注可能是nickname).'
# 如果"include-standard-chat-formatting"设置为"true",此格式将附加到对应前缀.
message-template="&7[&r{{displayname}}&7]>&r "
}
# +------------------------------------------------------------+
# | Teleport |
# +------------------------------------------------------------+
teleport {
# 如果设置为true,默认情况下,目标玩家将不会收到(/teleport)传送相关的通知.你有可以使用"-qfalse"来覆盖整个选项.
default-quiet=true
# 如果设置为true,传送指令(译者注:仅限Nucleus插件的Teleport指令)将会为传送的玩家寻找一个安全着陆点(译者注:关闭此项可能会将玩家传送到岩浆或者虚空中,如果目标点是岩浆或者虚空的话).
use-safe-teleportation=true
}
# +------------------------------------------------------------+
# | Vanish |
# +------------------------------------------------------------+
vanish {
# 如果设置为true,当玩家隐身时,Nucleus将会尝试警告tab列表.
alter-tab-list=false
# 如果设置为true,隐身的玩家在登录或退出时将不会在聊天界面显示登录提醒.
hide-connection-messages-on-vanish=false
}
# +------------------------------------------------------------+
# | Warn |
# +------------------------------------------------------------+
warn {
# 当玩家身上的警告标记超过指定条目的时候(译者注:由warnings-before-action项决定),将会自动执行的指令.
action-command="tempban {{name}} 1d Exceeding the active warning threshold"
# 如果没有为一个警告条目设置持续时间,在此设定默认的保存时长(以秒为单位).如果设置-1将不限制此项.
default-length=-1
# 如果设置为true,在警告条目过时后,将会以“过期警告”的形式保存.如果设置为false,则相反.
expire-warnings=true
# 一条警告条目最多保留时长(以秒为单位).如果设置-1将不限制此项.
maximum-warn-length=-1
# 一条警告条目至少保留时长(以秒为单位)(译者注:在此时长之后,这条警告才能过期).如果设置-1将不限制此项.
minimum-warn-length=-1
# 如果设置为true,玩家将在登录的时候提醒其身上携带的警告条目.如果设置为false,则不会.
show-login=true
# 玩家在收到指定数量的警告条目后,将会受到惩罚.如果设置-1将不做限制.
warnings-before-action=-1
}
# +------------------------------------------------------------+
# | Warp |
# +------------------------------------------------------------+
warp {
default-category-name=Uncategorised
# 地标传送的默认花费,能够通过使用/warpsetcost<warp><cost>指令覆盖单独的地标.
default-warp-cost=0.0
# 如果设置为true,/warplist指令将会把地标分类显示.
list-warps-by-category=false
# 如果设置为true,每一个地标都会检测玩家单独的地标传送权限-nucleus.warps.<name>.
separate-permissions=false
# 如果设置为true,地标的描述信息将会显示在/warplist清单中,鼠标悬停在地标名上可以查看其详细坐标信息.
show-warp-description-in-list=false
# 如果设置为true,使用/warp传送将会尝试在地标附近寻找安全着陆点.如果设置为false,将会直接将玩家传送到指定位置而不进行安全着陆检测(译者注:有时候可能会传送到岩浆或者虚空中,如果目标点是岩浆的话).
use-safe-warp=true
}
# +------------------------------------------------------------+
# | World |
# +------------------------------------------------------------+
world {
# 如果设置为正数,任何通过"/worldcreate"(或者"/nworldcreate")指令生成的世界将会自动的生成一个边界,设置为0或者负数可以禁用此项.
default-world-border-diameter=0
# 如果设置为true,加入或者改变一个世界将会切换游戏模式,除非对应的玩家拥有"nucleus.world.force-gamemode.override"权限.
enforce-gamemode-on-world-change=false
pre-generation {
# 如果设置为true,拥有"nucleus.world.border.gen.notify"权限节点的玩家将会在世界区块生成之后收到提示.建议关闭,因为他可能会刷屏.
display-after-each-gen=false
# 如果设置为true,在世界生成之前将会提示在线的玩家一个新的世界正在预生成.
display-generation-warning=true
# 以秒为单位,每一段时间之后都会警告在线的玩家世界的预生成正在进行.
notification-interval=20
}
# 如果设置为true,将会根据独立的权限节点限制玩家进入的世界-"nucleus.worlds.<worldname>"
separate-permissions=false
}

复制代码

Sponge:
global.conf:

# 1.0
#
# # If you need help with the configuration or have any questions related to Sponge,
# # join us at the IRC or drop by our forums and leave a post.
#
# # IRC: #sponge @ irc.esper.net ( https://webchat.esper.net/?channel=sponge )
# # Forums: https://forums.spongepowered.org/
#
sponge {
# Stopgap measures for dealing with broken mods
broken-mods {
# A list of mod ids that have broken network handlers (they interact with the game from a Netty handler thread).
# All network handlers from a forcibly scheduled to run on the main thread.
# Note that this setting should be considered a last resort, and should only be used as a stopgap measure while waiting for a mod to properly fix the issue.
broken-network-handler-mods=null
}
bungeecord {
# If 'true', allows BungeeCord to forward IP address, UUID, and Game Profile to this server.
ip-forwarding=false
}
cause-tracker {
# If set to 'true', when a mod or plugin attempts to spawn an entity
# off the main server thread, Sponge will automatically
# capture said entity to spawn it properly on the main
# server thread. The catch to this is that some mods are
# not considering the consequences of spawning an entity
# off the server thread, and are unaware of potential race
# conditions they may cause. If this is set to false,
# Sponge will politely ignore the entity being spawned,
# and emit a warning about said spawn anyways.
capture-async-spawning-entities=true
# If 'true', more thorough debugging for PhaseStates
# such that a StackTrace is created every time a PhaseState
# switches, allowing for more fine grained troubleshooting
# in the cases of runaway phase states. Note that this is
# not extremely performant and may have some associated costs
# with generating the stack traces constantly.
generate-stacktrace-per-phase=false
# The maximum number of times to recursively process transactions in a single phase.
# Some mods may interact badly with Sponge's block capturing system, causing Sponge to
# end up capturing block transactions every time it tries to process an existing batch.
# Due to the recursive nature of the depth-first processing that Sponge uses to handle block transactions,
# this can result in a stack overflow, which causes us to lose all infomration about the original cause of the issue.
# To prevent a stack overflow, Sponge tracks the current processing depth, and aborts processing when it exceeds
# this threshold.
# The default value should almost always work properly - it's unlikely you'll ever have to change it.
max-block-processing-depth=100
# If verbose is not enabled, this restricts the amount of
# runaway phase state printouts, usually happens on a server
# where a PhaseState is not completing. Although rare, it should
# never happen, but when it does, sometimes it can continuously print
# more and more. This attempts to placate that while a fix can be worked on
# to resolve the runaway. If verbose is enabled, they will always print.
maximum-printed-runaway-counts=3
# If 'true', the phase tracker will print out when there are too many phases
# being entered, usually considered as an issue of phase re-entrance and
# indicates an unexpected issue of tracking phases not to complete.
# If this is not reported yet, please report to Sponge. If it has been
# reported, you may disable this.
verbose=true
# If 'true', the phase tracker will dump extra information about the current phases
# when certain non-PhaseTracker related exceptions occur. This is usually not necessary, as the information
# in the exception itself can normally be used to determine the cause of the issue
verbose-errors=false
}
commands {
# Command aliases will resolve conflicts when multiple plugins request a specific command,
# Correct syntax is <unqualified command>=<plugin name> e.g. "sethome=homeplugin"
aliases {}
# Patches the specified commands to respect the world of the sender instead of applying the
# changes on the all worlds.
multi-world-patches {
defaultgamemode=true
difficulty=true
gamerule=true
seed=true
setdefaultspawnpoint=true
time=true
toggledownfall=true
weather=true
worldborder=true
}
}
debug {
# Detect and prevent parts of PlayerChunkMap being called off the main thread.
# This may decrease sever preformance, so you should only enable it when debugging a specific issue.
concurrent-chunk-map-checks=false
# Detect and prevent certain attempts to use entities concurrently.
# WARNING: May drastically decrease server performance. Only set this to 'true' to debug a pre-existing issue.
concurrent-entity-checks=false
# Dump chunks in the event of a deadlock
dump-chunks-on-deadlock=false
# Dump the heap in the event of a deadlock
dump-heap-on-deadlock=false
# Dump the server thread on deadlock warning
dump-threads-on-warn=false
# If 'true', Java's thread contention monitoring for thread dumps is enabled.
thread-contention-monitoring=false
}
entity {
# Number of colliding entities in one spot before logging a warning. Set to 0 to disable
collision-warn-size=200
# Number of entities in one dimension before logging a warning. Set to 0 to disable
count-warn-size=0
# Number of ticks before a painting is respawned on clients when their art is changed
entity-painting-respawn-delay=2
# Number of ticks before the fake player entry of a human is removed from the tab list (range of 0 to 100 ticks).
human-player-list-remove-delay=10
# Controls the time in ticks for when an item despawns.
item-despawn-rate=6000
# The upper bounded range where living entities farther from a player will likely despawn
living-hard-despawn-range=128
# The amount of seconds before a living entity between the soft and hard despawn ranges from a player to be considered for despawning
living-soft-despawn-minimum-life=30
# The lower bounded range where living entities near a player may potentially despawn
living-soft-despawn-range=32
# Maximum size of an entity's bounding box before removing it. Set to 0 to disable
max-bounding-box-size=1000
# Square of the maximum speed of an entity before removing it. Set to 0 to disable
max-speed=100
}
entity-activation-range {
# If 'true', newly discovered entities will be added to this config with a default value.
auto-populate=false
# Default activation ranges used for all entities unless overridden.
defaults {
ambient=32
aquatic=32
creature=32
misc=16
monster=32
}
# Per-mod overrides. Refer to the minecraft default mod for example.
mods {}
}
entity-collisions {
# If 'true', newly discovered entities/blocks will be added to this config with a default value.
auto-populate=false
# Default maximum collisions used for all entities/blocks unless overridden.
defaults {
blocks=8
entities=8
}
# Maximum amount of entities any given entity or block can collide with. This improves
# performance when there are more than 8 entities on top of each other such as a 1x1
# spawn pen. Set to 0 to disable.
max-entities-within-aabb=8
# Per-mod overrides. Refer to the minecraft default mod for example.
mods {
botania {
blocks {}
# Default maximum collisions used for all entities/blocks unless overridden.
defaults {}
# If 'false', entity collision rules for this mod will be ignored.
enabled=true
entities {
botaniacorporeaspark=-1
botaniaspark=-1
}
}
minecraft {
blocks {
"detector_rail"=1
"heavy_weighted_pressure_plate"=150
"light_weighted_pressure_plate"=15
"mob_spawner"=-1
"stone_pressure_plate"=1
"wooden_button"=1
"wooden_pressure_plate"=1
}
# Default maximum collisions used for all entities/blocks unless overridden.
defaults {}
# If 'false', entity collision rules for this mod will be ignored.
enabled=true
entities {
thrownpotion=-1
}
}
}
}
exploits {
# Enables filtering invalid entities when a chunk is being saved
# such that the entity that does not "belong" in the saving
# chunk will not be saved, and forced an update to the world's
# tracked entity lists for chunks.
# See https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0311-Prevent-Saving-Bad-entities-to-chunks.patch
filter-invalid-entities-on-chunk-save=true
# Enables focing a chunk load when an entity position
# is set. Usually due to teleportation, vehicle movement
# etc. can a position lead an entity to no longer exist
# within it's currently marked and tracked chunk. This will
# enable that chunk for the position is loaded. Part of several
# exploits.See https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0335-Ensure-chunks-are-always-loaded-on-hard-position-set.patch
load-chunk-on-position-set=true
# Enables forcing chunks to save when an entity is added
# or removed from said chunk. This is a partial fix for
# some exploits using vehicles.See https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0306-Mark-chunk-dirty-anytime-entities-change-to-guarante.patch
mark-chunks-as-dirty-on-entity-list-modification=true
# Prevents an exploit in which the client sends a packet with the
# itemstack name exceeding the string limit.
prevent-creative-itemstack-name-exploit=true
# Enables forcing updates to the player's location on vehicle movement.
# This is partially required to update the server's understanding of
# where the player exists, and allows chunk loading issues to be avoided
# with laggy connections and/or hack clients.See https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0378-Sync-Player-Position-to-Vehicles.patch
sync-player-positions-for-vehicle-movement=true
# Enables forcing a chunk-tracking refresh on entity movement.
# This enables a guarantee that the entity is tracked in the
# proper chunk when moving.https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0315-Always-process-chunk-registration-after-moving.patch
update-tracked-chunk-on-entity-move=true
}
general {
# The directory for Sponge plugin configurations, relative to the
# execution root or specified as an absolute path.
# Note that the default: "${CANONICAL_GAME_DIR}/config"
# is going to use the "plugins" directory in the root game directory.
# If you wish for plugin configs to reside within a child of the configuration
# directory, change the value to, for example, "${CANONICAL_CONFIG_DIR}/sponge/plugins".
# Note: It is not recommended to set this to "${CANONICAL_CONFIG_DIR}/sponge", as there is
# a possibility that plugin configurations can conflict the Sponge core configurations.
#
config-dir="${CANONICAL_GAME_DIR}/config"
# Disable warning messages to server admins
disable-warnings=true
# If 'true', sleeping between chunk saves will be enabled, beware of memory issues.
file-io-thread-sleep=false
# Additional directory to search for plugins, relative to the
# execution root or specified as an absolute path.
# Note that the default: "${CANONICAL_MODS_DIR}/plugins"
# is going to search for a plugins folder in the mods directory.
# If you wish for the plugins folder to reside in the root game
# directory, change the value to "${CANONICAL_GAME_DIR}/plugins".
plugins-dir="${CANONICAL_MODS_DIR}/plugins"
}
ip-sets {}
logging {
# Log when blocks are broken
block-break=false
# Log when blocks are modified
block-modify=false
# Log when blocks are placed
block-place=false
# Log when blocks are populated in a chunk
block-populate=false
# Log when blocks are placed by players and tracked
block-tracking=false
# Log when chunks are queued to be unloaded by the chunk garbage collector.
chunk-gc-queue-unload=false
# Log when chunks are loaded
chunk-load=false
# Log when chunks are unloaded
chunk-unload=false
# Whether to log entity collision/count checks
entity-collision-checks=false
# Log when living entities are destroyed
entity-death=false
# Log when living entities are despawned
entity-despawn=false
# Log when living entities are spawned
entity-spawn=false
# Whether to log entity removals due to speed
entity-speed-removal=false
# Log when server receives exploited packet with itemstack name exceeding string limit.
exploit-itemstack-name-overflow=false
# Log when player attempts to respawn invisible to surrounding players.
exploit-respawn-invisibility=false
# Log when server receives exploited packet to update a sign containing commands from player with no permission.
exploit-sign-command-updates=false
# Add stack traces to dev logging
log-stacktraces=false
# Log when a world auto-saves its chunk data. Note: This may be spammy depending on the auto-save-interval configured for world.
world-auto-save=false
}
metrics {
# Determines whether plugins that are newly added are allowed to perform
# data/metric collection by default. Plugins detected by Sponge will be added to the "plugin-permissions" section with this value.
#
# Set to true to enable metric gathering by default, false otherwise.
default-permission=false
# Provides (or revokes) permission for metric gathering on a per plugin basis.
# Entries should be in the format "plugin-id=<true|false>".
#
# Deleting an entry from this list will reset it to the default specified in
# "default-permission"
plugin-permissions {
aliases=false
autopickup=false
boop=false
carrotshop=false
catclearlag=false
coloranvil=false
commandblockingmanager=false
commandbooks=false
craftbook=false
"dosmike_lockette"=false
economylite=false
flexiblelogin=false
griefprevention=false
holograms=false
inspector=false
instantrespawn=false
inventorykeeper=false
karoglansigneditor=false
luckperms=false
mirage=false
myplugin=false
newhonor=false
nucleus=false
pixelautomessages=false
placeholderapi=false
plotsquared=false
plusone=false
redprotect=false
serial-key=false
serverlistplus=false
skinchanger=false
soulbound=false
statusprotocol=false
tabmodifier=false
totaleconomy=false
treedestroyage=false
virtualchest=false
virtualtool=false
worldedit=false
}
}
modules {
# Enables experimental fixes for broken mods
broken-mod=false
bungeecord=false
entity-activation-range=true
entity-collisions=true
# Controls whether any exploit patches are applied.
# If there are issues with any specific exploits, please
# test in the exploit category first, before disabling all
# exploits with this toggle.
exploits=true
# Allows configuring Vanilla movement and speed checks
movement-checks=false
optimizations=true
# Use real (wall) time instead of ticks as much as possible
realtime=false
# Controls block range and tick rate of tileentities.
# Use with caution as this can break intended functionality.
tileentity-activation=false
timings=true
tracking=true
}
movement-checks {
# Controls whether the 'player/entity moved wrongly!' check will be enforced
moved-wrongly=true
# Controls whether the 'player moved too quickly!' check will be enforced
player-moved-too-quickly=true
# Controls whether the 'vehicle of player moved too quickly!' check will be enforced
player-vehicle-moved-too-quickly=true
}
optimizations {
# Runs lighting updates asynchronously.
async-lighting {
# If 'true', lighting updates are run asynchronously.
enabled=true
# The amount of threads to dedicate for asynchronous lighting updates. (Default: 2)
num-threads=2
}
# Caches tameable entities owners to avoid constant lookups against data watchers. If mods
# cause issues, disable this.
cache-tameable-owners=true
# If 'true', block item drops are pre-processed to avoid
# having to spawn extra entities that will be merged post spawning.
# Usually, Sponge is smart enough to determine when to attempt an item pre-merge
# and when not to, however, in certain cases, some mods rely on items not being
# pre-merged and actually spawned, in which case, the items will flow right through
# without being merged.
drops-pre-merge=true
# If 'true', provides a fix for possible leaks through
# Minecraft's enchantment helper code that can leak
# entity and world references without much interaction
# Forge native (so when running SpongeForge implementation)
# has a similar patch, but Sponge's patch works a little harder
# at it, but Vanilla (SpongeVanilla implementation) does NOT
# have any of the patch, leading to the recommendation that this
# patch is enabled "for sure" when using SpongeVanilla implementation.
# See https://bugs.mojang.com/browse/MC-128547 for more information.
#
enchantment-helper-leak-fix=true
# If 'true', allows for Sponge to make better assumptinos on single threaded
# operations with relation to various checks for server threaded operations.
# This is default to true due to Sponge being able to precisely inject when
# the server thread is available. This should make an already fast operation
# much faster for better thread checks to ensure stability of sponge's systems.
faster-thread-checks=true
# If 'true', re-writes the incredibly inefficient Vanilla Map code.
# This yields enormous performance enhancements when using many maps, but has a tiny chance of breaking mods that invasively modify Vanilla.It is strongly reccomended to keep this on, unless explicitly advised otherwise by a Sponge developer
map-optimization=true
# If 'true', uses Panda4494's redstone implementation which improves performance.
# See https://bugs.mojang.com/browse/MC-11193 for more information.
# Note: This optimization has a few issues which are explained in the bug report.
panda-redstone=true
# Handles structures that are saved to disk. Certain structures can take up large amounts
# of disk space for very large maps and the data for these structures is only needed while the
# world around them is generating. Disabling saving of these structures can save disk space and
# time during saves if your world is already fully generated.
# Warning: disabling structure saving will break the vanilla locate command.
structure-saving {
# If 'true', newly discovered structures will be added to this config with a default value.
auto-populate=false
enabled=false
# Per-mod overrides. Refer to the minecraft default mod for example.
mods {
minecraft {
# If 'false', this mod will never save its structures.
enabled=true
structures {
mineshaft=false
}
}
}
}
}
player-block-tracker {
# Block IDs that will be blacklisted for player block placement tracking.
block-blacklist=null
# If 'true', adds player tracking support for block positions.
# Note: This should only be disabled if you do not care who caused a block to change.
enabled=true
}
# Used to control spawn limits around players.
# Note: The radius uses the lower value of mob spawn range and server's view distance.
spawner {
# The number of ambients the spawner can potentially spawn around a player.
spawn-limit-ambient=15
# The number of animals the spawner can potentially spawn around a player.
spawn-limit-animal=15
# The number of aquatics the spawner can potentially spawn around a player.
spawn-limit-aquatic=5
# The number of monsters the spawner can potentially spawn around a player.
spawn-limit-monster=15
# The ambient spawning tick rate. Default: 400
tick-rate-ambient=400
# The animal spawning tick rate. Default: 400
tick-rate-animal=400
# The aquatic spawning tick rate. Default: 400
tick-rate-aquatic=400
# The monster spawning tick rate. Default: 1
tick-rate-monster=1
}
# Configuration options related to the Sql service, including connection aliases etc
sql {
# Aliases for SQL connections, in the format jdbc:protocol://[username[:password]@]host/database
aliases {}
}
# Blocks to blacklist for safe teleportation.
teleport-helper {
# If 'true', this blacklist will always be respected, otherwise, plugins can choose whether
# or not to respect it.
force-blacklist=false
# Block IDs that are listed here will not be selected by Sponge's safe teleport routine as
# a safe block for players to warp into.
# You should only list blocks here that are incorrectly selected, solid blocks that prevent
# movement are automatically excluded.
unsafe-body-block-ids=null
# Block IDs that are listed here will not be selected by Sponge's safe
# teleport routine as a safe floor block.
unsafe-floor-block-ids=null
}
tileentity-activation {
# If 'true', newly discovered tileentities will be added to this config with default settings.
auto-populate=false
# Default activation block range used for all tileentities unless overridden.
default-block-range=64
# Default tick rate used for all tileentities unless overridden.
default-tick-rate=1
# Per-mod overrides. Refer to the minecraft default mod for example.
mods {}
}
timings {
enabled=true
hidden-config-entries=[
"sponge.sql"
]
history-interval=300
history-length=3600
server-name-privacy=false
verbose=false
}
world {
# The auto-save tick interval used when saving global player data. (Default: 900)
# Note: 20 ticks is equivalent to 1 second. Set to 0 to disable.
auto-player-save-interval=900
# The auto-save tick interval used to save all loaded chunks in a world.
# Set to 0 to disable. (Default: 900)
# Note: 20 ticks is equivalent to 1 second.
auto-save-interval=900
# The number of newly loaded chunks before triggering a forced cleanup.
# Note: When triggered, the loaded chunk threshold will reset and start incrementing.
# Disabled by default.
chunk-gc-load-threshold=0
# The tick interval used to cleanup all inactive chunks that have leaked in a world.
# Set to 0 to disable which restores vanilla handling. (Default: 600)
chunk-gc-tick-interval=600
# The number of seconds to delay a chunk unload once marked inactive. (Default: 15)
# Note: This gets reset if the chunk becomes active again.
chunk-unload-delay=15
# If 'true', any request for a chunk not currently loaded will be denied (exceptions apply
# for things like world gen and player movement).
# Warning: As this is an experimental setting for performance gain, if you encounter any issues
# then we recommend disabling it.
deny-chunk-requests=false
# Lava behaves like vanilla water when source block is removed
flowing-lava-decay=false
# The amount of GameProfile requests to make against Mojang's session server. (Default: 1)
# Note: Mojang accepts a maximum of 600 requests every 10 minutes from a single IP address.
# If you are running multiple servers behind the same IP, it is recommended to raise the 'gameprofile-task-interval' setting
# in order to compensate for the amount requests being sent.
# Finally, if set to 0 or less, the default batch size will be used.
# For more information visit http://wiki.vg/Mojang_API
gameprofile-lookup-batch-size=1
# The interval, in seconds, used by the GameProfileQueryTask to process queued GameProfile requests. (Default: 4)
# Note: This setting should be raised if you experience the following error:
# "The client has sent too many requests within a certain amount of time".
# Finally, if set to 0 or less, the default interval will be used.
gameprofile-lookup-task-interval=4
# If 'true', this world will generate its spawn the moment its loaded.
generate-spawn-on-load=false
# Vanilla water source behavior - is infinite
infinite-water-source=false
# The list of uuid's that should never perform a lookup against Mojang's session server.
# Note: If you are using SpongeForge, make sure to enter any mod fake player's UUID to this list.
invalid-lookup-uuids=[
"00000000-0000-0000-0000-000000000000",
"0d0c4ca0-4ff1-11e4-916c-0800200c9a66",
"41c82c87-7afb-4024-ba57-13d2c99cae77"
]
# The defined merge radius for Item entities such that when two items are
# within the defined radius of each other, they will attempt to merge. Usually,
# the default radius is set to 0.5 in Vanilla, however, for performance reasons
# 2.5 is generally acceptable.
# Note: Increasing the radius higher will likely cause performance degradation
# with larger amount of items as they attempt to merge and search nearby
# areas for more items. Setting to a negative value is not supported!
item-merge-radius=2.5
# If 'true', this worlds spawn will remain loaded with no players.
keep-spawn-loaded=true
# If 'true', natural leaf decay is allowed.
leaf-decay=true
# If 'true', this world will load on startup.
load-on-startup=true
# The maximum number of queued unloaded chunks that will be unloaded in a single tick.
# Note: With the chunk gc enabled, this setting only applies to the ticks
# where the gc runs (controlled by 'chunk-gc-tick-interval')
# Note: If the maximum unloads is too low, too many chunks may remain
# loaded on the world and increases the chance for a drop in tps. (Default: 100)
max-chunk-unloads-per-tick=100
# Specifies the radius (in chunks) of where creatures will spawn.
# This value is capped to the current view distance setting in server.properties
mob-spawn-range=4
# A list of all detected portal agents used in this world.
# In order to override, change the target world name to any other valid world.
# Note: If world is not found, it will fallback to default.
portal-agents {
"minecraft:default_the_end"=DIM1
"minecraft:default_the_nether"=DIM-1
}
# If 'true', this world will allow PVP combat.
pvp-enabled=true
# Override world distance per world/dimension
# The value must be greater than or equal to 3 and less than or equal to 32
# The server-wide view distance will be used when the value is -1.
view-distance=-1
# If 'true', natural formation of ice and snow in supported biomes will be allowed.
weather-ice-and-snow=true
# If 'true', thunderstorms will be initiated in supported biomes.
weather-thunder=true
# If 'true', this world will be registered.
world-enabled=true
}
}

复制代码

插件列表:

如果你还想检查什么就在回复里说一句.

ww龙mc

本帖最后由 ww龙mc 于 2018-12-21 18:49 编辑

PlotSquared并不完全兼容Sponge
所以并不建议使用，如果想要用的话可以尝试泼猴dalao改过的论坛附件似乎不能上传
所以帖百度盘的：https://pan.baidu.com/s/1hBmobyj-48mbUXe4NNeDbA

Zapic

ww龙mc 发表于 2018-12-21 18:48
PlotSquared并不完全兼容Sponge
所以并不建议使用，如果想要用的话可以尝试泼猴dalao改过的论坛附件似乎不 ...

排除插件确认是PlotSquared的问题.
即使只有ps和lperms死亡后仍然会出现这些问题.
你提供给我的问题也存在.
已向插件作者报告.