sponge {

    #G:处理（由于Sponge）损坏Mod的权宜之计

    broken-mods {...}

    #G:BungeeCord

    bungeecord {...}

    #G:TODO:CauseTracker

    cause-tracker {...}

    #G:命令相关

    commands {...}

    #Debug 除虫

    debug {...}

    #Entity 实体

    entity {...}

    #实体激活距离

    entity-activation-range {...}

    #实体碰撞

    entity-collisions {...}

    #G:exploits 漏洞修复

    exploits {...}

    #G:general 大体的配置 emmmm

    general {...}

    #G:ip-sets TODO

    ip-sets {}

    #记录

    logging {...}

    #G:MetricsCategory Bstats

    metrics {...}

    #G:modules 选择是否开启模块

    modules {...}

    #G:movement-checks 是否检查玩家移动

    movement-checks {...}

    #G:优化

    optimizations {...}

    #G:权限

    permission {...}

    #player-block-tracker

    #玩家方块追踪

    player-block-tracker {...}

    #spawner

    #世界生物生成

    spawner {...}

    #G:sql

    sql {...}

    #G:传送助手

    teleport-helper {...}

    #方块实体激活

    tileentity-activation {...}

    #timings

    timings {...}

    #world

    world {...}

    #世界生成修改器

    world-generation-modifiers=[...]

}

broken-mods {

    # 在网络线程编辑游戏对象的mod的Id列表, 在这里列出的mod的网络处理会被强行安排在主线程运行

    # 注意这里的设置应该被当做最后的方案， 而且只应当被当做等待Mod修复这个问题时的临时措施

    broken-network-handler-mods=[]

}

bungeecord {

    # 设置为'true'将会允许BungeeCord传递玩家的IP地址，uuid，以及账号数据。

    ip-forwarding=false

}

cause-tracker {

    # A mapping that is semi-auto-populating for TileEntities whose types

    # are found to be providing "null" Block sources as neighbor notifications

    # that end up causing crashes or spam reports. If the value is set to 

    # "true", then a "workaround" will be attempted. If not, the 

    # 

    # current BlockState at the target source will be queried from the world.

    # This map having a specific

    # entry of a TileEntity will prevent a log or warning come up to any logs

    # when that "null" arises, and Sponge will self-rectify the TileEntity

    # by calling the method "getBlockType()". It is advised that if the mod

    # id in question is coming up, that the mod author is notified about the

    # error-prone usage of the field "blockType". You can refer them to

    # the following links for the issue:

    # <a href="https://gist.github.com/gabizou/ad570dc09dfed259cac9d74284e78e8b" target="_blank">https://gist.github.com/gabizou/ad570dc09dfed259cac9d74284e78e8b</a>

    # <a href="https://github.com/SpongePowered/SpongeForge/issues/2787" target="_blank">https://github.com/SpongePowered/SpongeForge/issues/2787</a>

    # Also, please provide them with these links for the example PR to

    # fix the issue itself, as the fix is very simple:

    # <a href="https://github.com/TehNut/Soul-Shards-Respawn/pull/24" target="_blank">https://github.com/TehNut/Soul-Shards-Respawn/pull/24</a>

    # <a href="https://github.com/Epoxide-Software/Enchanting-Plus/pull/135" target="_blank">https://github.com/Epoxide-Software/Enchanting-Plus/pull/135</a>

    # 

    # 简单来说在这里配置可以让Sponge自动修复一种Mod作者可能会犯的错误，

    # 错误的输出日志会类似:

    # <a href="https://gist.github.com/gabizou/ad570dc09dfed259cac9d74284e78e8b" target="_blank">https://gist.github.com/gabizou/ad570dc09dfed259cac9d74284e78e8b</a>

    # <a href="https://github.com/SpongePowered/SpongeForge/issues/2787" target="_blank">https://github.com/SpongePowered/SpongeForge/issues/2787</a>

    # 遇到的时候会自动在这里生成配置

    #

    auto-fix-null-source-block-providing-tile-entities {}



    # 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.

    # 

    # 如果设置为'true'，当一个Mod或者插件试图在非主线程生成一个实体，

    # Sponge会自动捕获这个实体，并且在主线中正确的生成它。

    # 捕获这个是因为某些mod并不考虑异步生成实体的后果，

    # 而且并不知道这样可能导致的潜在风险。

    # 如果设置为'false' Sponge将会忽略生成的实体，但是仍会发出警告。

    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.

    # 

    # 如果设置为'true',将会为PhaseStates提供更详细的Debug信息，

    # 每次PhaseState切换的时候都会输出StackTrace，来帮助更好的解决case泄漏问题。

    # 注意这可能会造成性能损失，因为会不时的生成栈信息。

    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=1000



    # 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.

    #

    # 如果verbose没有开启，这里限制打印出的最多的泄漏PhaseState数量，通常发生在服务器的一个PhaseState没有完成。

    # 虽然很罕见，但是这不应该发生，但是当它发生的时候，它可能会不停的输出。这里的设置为了在研究解决方案时限制这种情况。

    # 如果Verbos开启，所有的信息都会打印出来。

    maximum-printed-runaway-counts=3



    # If true, when a mod attempts to perform a neighbor notification

    # on a block, some mods do not know to perform a 'null' check

    # on the source block of their TileEntity. This usually goes by

    # unnoticed by other mods, because they may perform '==' instance

    # equality checks instead of calling methods on the potentially

    # null Block, but Sponge uses the block to build information to

    # help tracking. This has caused issues in the past. Generally,

    # this can be useful for leaving "true" so a proper report is

    # generated once for your server, and can be reported to the

    # offending mod author.

    # This is 'false' by default in SpongeVanilla.

    # Review the following links for more info:

    # <a href="https://gist.github.com/gabizou/ad570dc09dfed259cac9d74284e78e8b" target="_blank">https://gist.github.com/gabizou/ad570dc09dfed259cac9d74284e78e8b</a>

    # <a href="https://github.com/SpongePowered/SpongeForge/issues/2787" target="_blank">https://github.com/SpongePowered/SpongeForge/issues/2787</a>

    # 

    # 是否报告`auto-fix-null-source-block-providing-tile-entities`中的那个bug

    report-null-source-blocks-on-neighbor-notifications=false



    # If set to 'true', when a mod or plugin attempts to submit a command

    # asynchronously, Sponge will automatically capture said command

    # and submit it for processing on the server thread. The catch to

    # this is that some mods are performing these commands in vanilla

    # without considering the possible consequences of such commands

    # affecting any thread-unsafe parts of Minecraft, such as worlds,

    # block edits, entity spawns, etc. If this is set to false, Sponge

    # will politely ignore the command being executed, and emit a warning

    # about said command anyways.

    #

    # 如果设置为'true', 当一个mod或者插件试图异步执行命令时，Sponge会自动捕获上述命令

    # 并且在主线程执行。这个捕获是因为很多模组在原版这样做，而不考虑可能导致这些命令会异步的操作游戏的后果

    # 如果设置为'false' Sponge将会忽略被执行的命令，但是仍会发出警告。

    resync-commands-from-async=true



    # 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.

    #

    # 如果设置为'true', phase tracker会输出过多phase being entered，

    # 通常会被认为是phase重进入，或者未完成的错误

    # 如果这个错误并没有被报告的话 请把它报告给Sponge，如果已经报告了，你可能会需要关闭这个

    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

    #

    # 如果设置为'true', 当和PhaseTracker无关的错误发生时，phase tracker 会输出当前phases的额外的信息，

    # 这通常是没有必要的， 因为通常Exception本身的信息就足够指出是什么导致了这个错误

    verbose-errors=false

}

commands {

    # 处理多个插件要求同一个命令名时的冲突，正确的格式是 <command>=<plugin name> 例如 "sethome=homeplugin"

    aliases {}



    # 设定当一个用户尝试使用一个他没有所需权限的命令时，sponge的行为。

    command-hiding {

        # 如果设置为true, 当尝试用户Tab补全，或者使用"/sponge which"与"/sponge:help"命令时，会防止没有权限的命令被补全。

        # 

        # 注意一些命令可能始终不会在没有权限的用户Tab补全时出现，不论这里如何设置。

        hide-on-discovery-attempt=true



        # 如果设置为true，当用户尝试使用无权使用的命令时，Sponge会表现的与这个命令并不存在一样，而不是显示缺少权限的信息。

        hide-on-execution-attempt=false

    }

    # 某些mod可能不会进行在执行他们的命令时进行权限检查。设置这项为true将会强制检查Sponge提供的权限("<modid>.command.<commandname>")。

    # 注意这个那样设置会导致一些通常所有人都可以使用的命令现在需要权限。

    #

    # 设置这项为true也会对显示在Tab补全和sponge help命令中的命令有更强的控制

    # 如果你并没有使用一个权限插件，这里强烈建议设置为 false（就如它默认一样）

    enforce-permission-checks-on-non-sponge-commands=false



    //由于bug这里坏掉了



    # 设置是否修改某些命令使其只影响使用者所在的世界，而不是所有世界。

    multi-world-patches {

        ""=true

    }

}

debug {

    # 检测并防止异步调用部分PlayerChunkMap的操作，这会影响服务器性能，所以你只应在debug特定问题时使用。

    concurrent-chunk-map-checks=false



    # 检测并防止异步使用entities的尝试。这会影响服务器性能，所以你只应在debug一个已经存在的问题时使用。

    concurrent-entity-checks=false



    # 如果设置为'true', Java的thread contention monitoring for thread dumps将会启用。

    thread-contention-monitoring=false

}

entity {



    # 一个点的实体碰撞数量超过这里的数值会输出警告。

    collision-warn-size=200



    # 画在其艺术更变时在客户端重生的延迟（tick）

    entity-painting-respawn-delay=2



    # 假人从Tab列表移除的延迟（tick）

    human-player-list-remove-delay=10



    # 物品消失的时间（tick）

    item-despawn-rate=6000



    # 如果一个实体消失的距离与玩家的距离有关， 这个距离的上限。

    # 即超过这个的距离的实体如果计算其消失概率，则结果为必然消失。

    living-hard-despawn-range=128



    # 如果一个实体消失的距离与玩家的距离有关， 那么在多少秒之后会考虑移除这个实体

    living-soft-despawn-minimum-life=30



    # 如果一个实体消失的距离与玩家的距离有关， 这个距离的下限。

    # 即低于这个距离则不会消失

    living-soft-despawn-range=32



    # 如果一个实体的碰撞箱超过这个设置就会移除这个实体，设置为0来关闭

    max-bounding-box-size=1000



    # 如果一个实体的速度的平方超过这里的设置，其将会被移除

    max-speed=100

}

entity-activation-range {



    # 如果设置为'true', 新发现的实体会被将以默认值自动添加到这里的设置中。

    auto-populate=false



    # 默认的实体激活距离

    defaults {

        ambient=32

        aquatic=32

        creature=32

        misc=16

        monster=32

    }



    # 按照mod的设置。

    mods {}

}

entity-collisions {



    # 如果设置为'true', 新发现的实体/方块会被将以默认值自动添加到这里的设置中。

    auto-populate=false



    # 一个实体或者方块能够碰撞的最大数量，这个设置会提升例如8个实体站在一个方块上面时的性能。设置为0来关闭。

    max-entities-within-aabb=8



    # 分mod设置。

    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 {

                corporeaspark=-1

                spark=-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 {

    # If limit-book-size is enabled, controls the multiplier applied to each book page size

    # 如果limit-book-size开启，这里控制每页的大小

    book-size-total-multiplier=0.98

    # 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 <a href="https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0311-Prevent-Saving-Bad-entities-to-chunks.patch" target="_blank">https://github.com/PaperMC/Paper ... ies-to-chunks.patch</a>



    # 过滤不正确的实体保存

    filter-invalid-entities-on-chunk-save=true

    # Limits the size of a book that can be sent by the client.

    # See <a href="https://github.com/PaperMC/Paper/blob/f8058a8187da9f6185d95bb786783e12c79c8b18/Spigot-Server-Patches/0403-Book-Size-Limits.patch" target="_blank">https://github.com/PaperMC/Paper ... k-Size-Limits.patch</a>

    # (Only affects SpongeVanilla)



    # 限制书的大小，只影响SpongeVanilla

    limit-book-size=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 <a href="https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0335-Ensure-chunks-are-always-loaded-on-hard-position-set.patch" target="_blank">https://github.com/PaperMC/Paper ... -position-set.patch</a>

    # (Only affects SpongeVanilla)



    # SpongeVanilla

    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 <a href="https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0306-Mark-chunk-dirty-anytime-entities-change-to-guarante.patch" target="_blank">https://github.com/PaperMC/Paper ... e-to-guarante.patch</a>

    # (Only affects SpongeVanilla)



    # SpongeVanilla

    mark-chunks-as-dirty-on-entity-list-modification=true

    # If limit-book-size is enabled, controls the maximum size of a book page

    # 如果限制书大小开启， 这里设置书最多的页数

    max-book-page-size=2560

    # Prevents an exploit in which the client sends a packet with the 

    # itemstack name exceeding the string limit.



    # 防止客户端发送超过string限制的 物品名

    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 <a href="https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0378-Sync-Player-Position-to-Vehicles.patch" target="_blank">https://github.com/PaperMC/Paper ... n-to-Vehicles.patch</a>

    # (Only affects SpongeVanilla)



    # SpongeVanilla

    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.<a href="https://github.com/PaperMC/Paper/blob/fd1bd5223a461b6d98280bb8f2d67280a30dd24a/Spigot-Server-Patches/0315-Always-process-chunk-registration-after-moving.patch" target="_blank">https://github.com/PaperMC/Paper ... -after-moving.patch</a>

    # (Only affects SpongeVanilla)



    # SpongeVanilla

    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 "config" 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. 

    # 



    # Sponge的插件的配置文件的文件夹，可以绝对/相对路径

    # 注意默认的"${CANONICAL_GAME_DIR}/config" 会使用游戏根目录下的 config文件夹

    # 如果你你希望插件配置可以配置到 "${CANONICAL_CONFIG_DIR}/sponge/plugins"

    # 注意不建议设置为 "${CANONICAL_CONFIG_DIR}/sponge" 因为可能会和sponge的核心配置文件冲突

    config-dir="${CANONICAL_GAME_DIR}/config"



    # If 'true', sleeping between chunk saves will be enabled, beware of memory issues.



    # 如果设置为'true', chunk保存之间会sleeping， 要注意内存问题

    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".



    # 额外的搜索插件的文件夹，可以为绝对/相对路径

    # 注意默认的${CANONICAL_MODS_DIR}/plugins 将会搜索Mods文件夹中的Plugins文件夹

    # 如果你希望plugins目录位于游戏的根目录 可以改为"${CANONICAL_GAME_DIR}/plugins".

    plugins-dir="${CANONICAL_MODS_DIR}/plugins"

}

ip-sets {}

logging {

    # Log when blocks are broken

    # 当方块破坏时log

    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

    # 世界生成 emmm

    block-populate=false

    # Log when blocks are placed by players and tracked

    # log tracking

    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

    # 增加 stacktraces

    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.

    # log 世界自动保存

    world-auto-save=false

}

metrics {

    # 默认的统计的状态 UNDEFINED被当做关闭，TRUE 开启， FALSE 关闭

    global-state=UNDEFINED

    # 每个插件的配置

    # 格式为<pluginid> = <TRUE|FALSE|UNDEFINED> 

    plugin-states {}

}

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 {

    # 控制是否进行'player/entity moved wrongly!'(玩家/实体移动错误)检查

    moved-wrongly=true

    # 控制是否进行'player moved too quickly!'(玩家移动过快)检查

    player-moved-too-quickly=true

    # 控制是否进行'vehicle of player moved too quickly!'(玩家载具移动过快)检查

    player-vehicle-moved-too-quickly=true

}

optimizations {

    # Runs lighting updates asynchronously.

    # 异步更新光照

    async-lighting {

        # If 'true', lighting updates are run asynchronously.

        # true 开启

        enabled=true

        # The amount of threads to dedicate for asynchronous lighting updates. (Default: 2)

        # 异步光照更新线程 （默认2）

        num-threads=2

    }



    # Caches tameable entities owners to avoid constant lookups against data watchers. If mods 

    # cause issues, disable this.

    #

    # 缓存tameable entities的所有者来避免重复的数据查询。

    # 如果造成mod错误，请关闭这个

    cache-tameable-owners=true



    # Occasionally, some built in advancements, 

    # recipes, etc. can fail to deserialize properly

    # which ends up potentially spamming the server log

    # and the original provider of the failing content

    # is not able to fix. This provides an option to

    # suppress the exceptions printing out in the log.



    # 有时，一些内建的成就，合成之类会反序列化失败

    # 造成在服务器log中输出一大堆信息，这个提供了抑制这些信息的方法

    disable-failing-deserialization-log-spam=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.



    # 如果设置为'true', 方块的实体掉落会被提前合并，来避免生成额外的实体，然后生成之后再被合并。

    # 通常Sponge会足够聪明，能够分别什么时候需要预合并，

    drops-pre-merge=false



    # Uses theosib's redstone algorithms to completely overhaul the way redstone works.

    # 使用theosib的红石算法来改造红石的工作方式

    eigen-redstone {

        # If 'true', uses theosib's redstone implementation which improves performance. 

        # See <a href="https://bugs.mojang.com/browse/MC-11193" target="_blank">https://bugs.mojang.com/browse/MC-11193</a> and 

        #     <a href="https://bugs.mojang.com/browse/MC-81098" target="_blank">https://bugs.mojang.com/browse/MC-81098</a> for more information. 

        # Note: We cannot guarantee compatibility with mods. Use at your discretion.

        #

        # 如果设置为'true' 将使用theosib的红石实现，来提升性能

        # 详见 <a href="https://bugs.mojang.com/browse/MC-11193" target="_blank">https://bugs.mojang.com/browse/MC-11193</a> 与 <a href="https://bugs.mojang.com/browse/MC-81098" target="_blank">https://bugs.mojang.com/browse/MC-81098</a> 

        # 注意： 我们不能保证与mod兼容，出错了你自己负责

        enabled=false



        # If 'true', restores the vanilla algorithm for computing wire power levels when powering off.

        # 如果设置为'true', 将仍然使用原版的算法计算充能取消时的线缆能量。

        vanilla-decrement=false



        # If 'true', restores the vanilla algorithm for propagating redstone wire changes.

        # 如果设置为'true', 将仍然使用原版的算法计算线缆变更时的改变扩散。

        vanilla-search=false

    }



    # 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 <a href="https://bugs.mojang.com/browse/MC-128547" target="_blank">https://bugs.mojang.com/browse/MC-128547</a> for more information.

    # 

    # 如果设置为'true', 将会提供一个一个潜在的内存泄漏的修复，Forge已经做了

    # 所以只对SpongeVaniila比较有用

    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.

    #

    # 如果设置为'true', sponge会同一个更好线程检查

    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

    #

    # 如果设置为'true' 将会重写低效的原版Map代码

    # 这会在拥有大量地图时带来巨大的性能提升，但是有非常小的可能，会导致mod出错。

    # 强烈建议设置为true

    map-optimization=true



    # Based on Aikar's optimizationo of Hoppers, setting this to 'true'

    # will allow for hoppers to save performing server -> client updates

    # when transferring items. Because hoppers can transfer items multiple

    # times per tick, these updates can get costly on the server, with

    # little to no benefit to the client. Because of the nature of the

    # change, the default will be 'false' due to the inability to pre-emptively

    # foretell whether mod compatibility will fail with these changes or not.

    # Refer to: <a href="https://github.com/PaperMC/Paper/blob/8175ec916f31dcd130fe0884fe46bdc187d829aa/Spigot-Server-Patches/0269-Optimize-Hoppers.patch" target="_blank">https://github.com/PaperMC/Paper ... imize-Hoppers.patch</a>

    # for more details.

    #

    # 优化漏斗

    # 基于Aikar的漏斗优化，设置这个为'true'会减少当传递物品时服务器端向客户端的数据更新。

    # 由于漏洞可以在一个tick传递多个物品，这些更新会在服务器端消耗很多，但是对客户端并没有什么帮助。

    # 这个默认为'false'因为不知道这些改变会不会影响mod。

    # 详见： <a href="https://github.com/PaperMC/Paper/blob/8175ec916f31dcd130fe0884fe46bdc187d829aa/Spigot-Server-Patches/0269-Optimize-Hoppers.patch" target="_blank">https://github.com/PaperMC/Paper ... imize-Hoppers.patch</a>

    optimize-hoppers=false



    # If 'true', uses Panda4494's redstone implementation which improves performance. 

    # See <a href="https://bugs.mojang.com/browse/MC-11193" target="_blank">https://bugs.mojang.com/browse/MC-11193</a> for more information. 

    # Note: This optimization has a few issues which are explained in the bug report. 

    # We strongly recommend using eigen redstone over this implementation as this will

    # be removed in a future release.

    # 如果设置为'true' 将会使用Panda4494的红石算法

    # 详见 <a href="https://bugs.mojang.com/browse/MC-11193" target="_blank">https://bugs.mojang.com/browse/MC-11193</a>

    # 注意这个优化有一些错误报告，我们强烈建议使用上面的eigen redstone因为这个会在之后的版本移除

    panda-redstone=false



    # 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.

    #

    # 结构保存

    # 处理结构保存到硬盘，很大的地图中结构可能会占据很大的硬盘空间，但是只在它周围的时间被生成的时候需要

    # 取消保存这些结构可以节省硬盘以及保存中消耗的时间，如果你的世界已经生成完成

    # 警告： 关闭保存机构会导致原版locate命令失效

    structure-saving {

        # If 'true', newly discovered structures will be added to this config

        # with a default value of 'true'. This is useful for finding out

        # potentially what structures are being saved from various mods, and

        # allowing those structures to be selectively disabled.

        # 如果设置为'true', 新发现的结构会被以默认的配置'true'添加到配置文件中，

        # 可以帮助发现不同的mod保存的结构，以便于关闭。

        auto-populate=false

        # If 'false', disables the modification to prevent certain structures

        # from saving to the world's data folder. If you wish to prevent certain

        # structures from saving, leave this "enabled=true". When 'true', the

        # modification allows for specific 'named' structures to NOT be saved to

        # disk. Examples of some structures that are costly and somewhat irrelivent

        # is 'mineshaft's, as they build several structures and save, even after

        # finished generating.



        # 如果为'false'，关闭阻止特定结构保存到数据文件夹中的修改。如果你期望阻止特点结构保存

        # 需要设置这里为'true',

        enabled=false

        # Per-mod overrides. Refer to the minecraft default mod for example.

        mods {

            minecraft {

                # If 'false', this mod will never save its structures. This may

                # break some mod functionalities when requesting to locate their

                # structures in a World. If true, allows structures not overridden

                # in the section below to be saved by default. If you wish to find

                # a structure to prevent it being saved, enable 'auto-populate' and

                # restart the server/world instance.

                enabled=true

                # Per structure override. Having the value of 'false' will prevent

                # that specific named structure from saving.

                structures {

                    mineshaft=false

                }

            }

        }

    }

    # Vanilla performs a lot of is area loaded checks during

    # entity collision calculations with blocks, and because

    # these calculations require fetching the chunks to see

    # if they are loaded, before getting the block states

    # from those chunks, there can be some small performance

    # increase by checking the entity's owned active chunk

    # it may currently reside in. Essentially, instead of

    # asking the world if those chunks are loaded, the entity

    # would know whether it's chunks are loaded and that neighbor's

    # chunks are loaded.

    # 

    # 原版在检查实体与方块碰撞时会进行很多区域是否加载的检查，

    # 由于这些检查需要先判断区块是否加载，然后才能获取方块状态

    # 这里可以做一些小的优化，通过实体当前所在的区块检查，而不是通过

    # 询问世界区块是否已经加载，这些石头应当知道它的区块是否加载以及周边区块是否加载

    use-active-chunks-for-collisions=false

}

permission {

    # If 'true', Sponge plugins will be used to handle permissions rather than any Forge mod

    # 如果设置为'true', sponge插件会来处理权限，而不是forgemod

    # 即使用Sponge插件的权限系统替换forge权限Api

    forge-permissions-handler=false

}

player-block-tracker {

    # Block IDs that will be blacklisted for player block placement tracking.

    # 将不会进行玩家放置追踪的方块列表。

    block-blacklist=[]



    # 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.

    # 如果设置为'true', 将添加方块位置的玩家追踪

    # 注意： 只有当你完全不在意谁更改了方块的时候才可以关闭这里。

    enabled=true

}

spawn-limit 设置生物的上限(每个玩家)，和当前世界玩家数相乘得到最终结果

tick-rate 设置多久尝试刷新一次怪物， 比如400则是400tick尝试刷一次

二者之中任意一个设置为0则关闭对应种类生物的生成

spawner {

    # 一个玩家周围可以生成的环境生物(蝙蝠)数量.

    spawn-limit-ambient=15

    # 一个玩家周围可以生成动物数量.

    spawn-limit-animal=15

    # 一个玩家周围可以生成的水生生物的数量.

    spawn-limit-aquatic=5

    # 一个玩家周围可能生成的怪物数量.The number of monsters the spawner can potentially spawn around a player.

    spawn-limit-monster=70

    # 环境生物生成tick比率. 默认: 400

    tick-rate-ambient=400

    # 动物生成tick比率. 默认: 400

    tick-rate-animal=400

    # 水生生物生成tick比率. 默认: 400

    tick-rate-aquatic=400

    # 怪物生成tick比率. 默认: 1

    tick-rate-monster=1

}

sql {

    # Aliases for SQL connections, in the format jdbc:protocol://[username[:password]@]host/database

    aliases {}

}

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.

    # 

    # 不会被选座sponge的安全传送路径的方块id

    # 你应该只在这里添加被错误选中的方块， 阻止移动的固定方块会被自动包含

    unsafe-body-block-ids=[]



    # Block IDs that are listed here will not be selected by Sponge's safe 

    # teleport routine as a safe floor block.

    #

    # 不会被选择作为sponge的安全传送路径的地板的方块列表

    unsafe-floor-block-ids=[]

}

tileentity-activation {



    # If 'true', newly discovered tileentities will be added to this config with default settings.

    # 如果设置为'true', 新发现的方块实体会被以默认配置添加到这里的设置中

    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.

    # 默认的所有方块实体的 tick 比率，多少个 Mc tick 运行一次方块 tick，默认为1

    default-tick-rate=1



    # Per-mod overrides. Refer to the minecraft default mod for example.

    # 按照mod的具体设置.参考 Minecraft 默认为例子

    mods {}

}

只在global.conf中生效

Timings 分析，需要开启模块

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.

    # 全局设置：只在global.conf中生效

    # 保存全部玩家数据的时间间隔，单位 tick. (默认: 900)

    # 注意：20 tick 等于 1 秒。设置为 0 则会关闭。

    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.

    # 可以每个世界独立设置

    # 自动保存当前世界所有加载的区块的时间间隔，设置为 0 则关闭，单位为 tick。（默认： 900）

    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)

    # 可以每个世界独立设置

    # 当前世界两次区块清理直接的 tick 间隔，

    # 设置为 0 将会关闭并使用原版的逻辑。

    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.

    # 可以每个世界独立设置

    # 区块卸载延迟

    # 多少秒之后，被标记为不活跃的区块会被卸载。（默认：15）

    # 注意： 当区块重新活跃时，会重新计算

    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.

    # 可以每个世界独立设置

    # 如果设置为'true', 任何对当前尚未加载的区块的请求都会被拒绝（除了例如世界生成和玩家移动之类的情况）

    # 警告：这是一个实验性的提升性能的设置，如果你遇到了任何问题我们建议你关闭这个。

    deny-chunk-requests=false



    # 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.

    # 全局设置：只在global.conf中生效

    # GameProfileQueryTask 进行游戏账号数据查询的时间间隔，单位为秒。（默认： 4）

    # 注意：这个设置当你遇到 ："The client has sent too many requests within a certain amount of time"

    # 时应该提高。最后，如果设置为0或者更低，会使用默认的间隔。

    gameprofile-lookup-task-interval=4



    # If 'true', this world will generate its spawn the moment its loaded.

    # 可以每个世界独立设置

    # 如果设置为'true', 世界会在它加载的时候生成出生点周围的区块。

    generate-spawn-on-load=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.

    # 全局设置：只在global.conf中生效

    # 不会向 Mojang 的 session 服务器查询的的UUID列表

    # 注意：如果你使用SpongeForge，请确保把所有 mod 的 fake player 的 UUID 添加到这里。

    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!

    # 可以每个世界独立设置

    # 默认的物品实体合并半径，当两个物品在这个距离之内，他们会尝试合并。

    # 通常 2.5 是可以接受的

    # 注意： 提高这个半径很有可能会导致性能降低，因为大量物品会尝试与其周围的物品合并。

    # 并不支持设置为负！

    item-merge-radius=2.5



    # If 'true', this worlds spawn will remain loaded with no players.

    # 可以每个世界独立设置

    # 如果设置为'true', 这个世界的出生点会保持加载，就算没有一个玩家。

    keep-spawn-loaded=true



    # If 'true', natural leaf decay is allowed.

    # 全局设置：只在global.conf中生效

    # 如果设置为'true', 将会允许自然的树叶腐败消失。

    leaf-decay=true



    # If 'true', this world will load on startup.

    # 可以每个世界独立设置

    # 如果设置为'true', 这个世界将会在服务器开启的时候加载。

    load-on-startup=false



    # 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)

    # 可以每个世界独立设置

    # 每个tick等待卸载的区块中会被卸载的最大数量

    # 注意：当区块GC开启时， 这里的设置只会影响GC允许的tick，（由'chunk-gc-tick-interval'控制）

    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

    # 可以每个世界独立设置

    # 设置生物将会生成的半径（单位区块）

    # 这个值会不会超过当前视距（view-distance）设置

    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.

    # 可以每个世界独立设置

    # 如果设置为'true', 这个世界将会允许 PVP 战斗。

    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.

    # 可以每个世界独立设置

    # 每个世界独立的设置视距，这个值应当大于等于 3 并小于等于 32

    # 如果设置为-1 则会使用服务器的视距设置。 

    view-distance=-1



    # If 'true', natural formation of ice and snow in supported biomes will be allowed.

    # 可以每个世界独立设置

    # 如果设置为'ture", 在支持的生物群系中会自然形成冰与雪。

    weather-ice-and-snow=true



    # If 'true', thunderstorms will be initiated in supported biomes.

    # 可以每个世界独立设置

    # 如果设置为'ture", 在支持的生物群系中雷暴，看起来是雷暴的时候是否会在白天刷怪。

    weather-thunder=true



    # If 'true', this world will be registered.

    # 可以每个世界独立设置

    # 如果设置为'true', 这个世界会被注册，即是否启用这个世界。

    world-enabled=true

}

# 应用到当前世界的世界生成修改器

world-generation-modifiers=[]