From d6e5499a0629f6b24776c706e934dcb7ad8726aa Mon Sep 17 00:00:00 2001 From: YouHaveTrouble Date: Sat, 21 Mar 2026 19:52:14 +0100 Subject: [PATCH] #138 removed mention of max-entity-collisions appearing in spigot.yml --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 626a6ab..fdac487 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ Note for users that are on vanilla, Fabric or Spigot (or anything below Paper) - go to your server.properties and change `sync-chunk-writes` to `false`. This option is forcibly set to false on Paper and its forks, but on other server implementations you need to switch this to false manually. This allows the server to save chunks off the main thread, lessening the load on the main tick loop. -Guide for version 1.21.5. Some things may still apply to 1.15 - 1.21.4. +Guide for version 1.21.11. Some things may still apply to 1.15 - 1.21.10. Based on [this guide](https://www.spigotmc.org/threads/guide-server-optimization%E2%9A%A1.283181/) and other sources (all of them are linked throughout the guide when relevant). @@ -262,7 +262,7 @@ This option decides if mob spawns should account for how many mobs are around ta `Good starting value: 2` -Overwrites option with the same name in [spigot.yml]. It lets you decide how many collisions one entity can process at once. Value of `0` will cause inability to push other entities, including players. Value of `2` should be enough in most cases. It's worth noting that this will render maxEntityCramming gamerule useless if its value is over the value of this config option. +Lets you decide how many collisions one entity can process at once. Value of `0` will cause inability to push other entities, including players. Value of `2` should be enough in most cases. It's worth noting that this will render maxEntityCramming gamerule useless if its value is over the value of this config option. #### update-pathfinding-on-block-update