Max-entity-collisions (in Spigot.yml in some builds)Ĭrammed entities (grinders, farms, etc.) will collide less and consume less TPS in the process. This changes how often (in ticks) inventories are refreshed while open. While enabling this eliminates vanilla behavior (cats block chests), do you really need this mechanic? Only go higher if you have significant tick loss from ticking spawners.Ĭhests scan for a cat on top of it when opened by a player. Doubling the delay will not impact spawn rates. This is the delay (in ticks) before an active spawner attempts spawns. Paper has a very efficient algorithm for explosions with no impact to gameplay. Setting this too low might result in unsaved chunks, so avoid going lower. This is incredibly important for modern servers (world saving sucks). This slows down incremental chunk saving during the world save task. Leave this near default if you use Paper’s arrow options. Paper has settings to reduce the gameplay impact of arrow removal. Some servers may want to keep arrows on the ground longer, but most will have no complaints if removed faster.
Similar to item-despawn-rate, but for arrows. See Paper’s alt-item-despawn-rate so you can target trash items (cobblestone) without clearing valuable items. While the TPS savings can be significant if reduced, it also impacts gameplay on servers where returning to dropped items is critical. The time (in ticks) before a ground item is removed.
Paper has an option to force nerfed mobs to jump/swim. A farm limiter plugin might be a better solution. This is big TPS savings for massive mob farms, but also messes with behavior. When enabled, mobs from spawners will not have AI (will not swim/attack/move). Merging will lead to the illusion of items disappearing as they merge together. Higher values allow more items to be swept into piles. Merging items means less ground item ticking. Enable villagers-active-for-panic to save some iron farms from breaking. Vanilla behavior ticks all villagers in loaded chunks. Note: Villagers should be left alone (if possible) to protect mechanics.Įnabling this prevents the server from ticking villagers outside the activation range. Avoid setting this too low or you might break mob behavior (mob aggro, raids, etc). Opt: animals:16, monsters:24, raiders: 48, misc:8Įntities past this range will be ticked less often. If view-distance is 5, set mob-spawn-range to 4)ĭef: animals:32, monsters:32, raiders: 48, misc:16 Warning: If your view-distance is 6 or smaller, set a spawn range 1 below that value (ex. After limiting spawns in Bukkit, this will condense mobs to mimic the appearance of normal rates. This sets the max mob spawning distance (in chunks) from players. The small TPS savings is not worth the potential damage. Note: Take regular backups to avoid data loss in the rare event of a fatal crash.ġ000 disables this feature. Should the server constantly save user data (false) or delay that task until a stop/restart (true)? This is nice TPS savings on Spigot (less on Paper since it’s more efficient). Worldsave Lag: Lag spikes from Worldsave? You might want to consider Paper’s lag-free saving. If you use your server or a plugin to run saves, STOP! They just run the very obsolete /save-all command. It should be 6000 by default, just double check it is not 0 (disabled). This enables Bukkit’s world saving and how often it runs (in ticks). Only go higher if you have significant tick loss to the mobSpawn task. Offsetting the tick rates spreads them out more. Increasing the time between spawn attempts should not impact gameplay. This sets how often (in ticks) the server attempts to spawn entities. Opt: monster:5, water:11, water-ambient:21, ambient:31 Ticking fewer chunks means less TPS consumption.ĭef: monster:1, water:1, water-ambient:1, ambient:1 Subsequent values in the guide will make the reduction less noticeable. Avoid going too low or the mob shortages will be noticeable. While there is more to this than “mobs per player” (explained here), lower values mean less mobs. Optimized: monsters:50, animals:8, water-animals:7, water-ambient:10, ambient:1 Bukkit.ymlĭefault: monsters:70, animals:10, water-animals:15, water-ambient:20, ambient:15 This guide breaks down suggested values that get the most out of your server without compromising gameplay. Spigot and Paper offer settings that greatly improve performance. Optimizing your server can be hard, but we will try to make it as easy as possible. It’s also a very good way to prevent your server from lagging and will allow your server to run better with more players. Optimizing your Minecraft server is a great way to help it run better and to get the best performance from your server.
0 kommentar(er)
