From 91a851403334eeb0b7c0b4757bcca16a5a24ca79 Mon Sep 17 00:00:00 2001 From: YouHaveTrouble Date: Fri, 15 Jan 2021 20:07:05 +0100 Subject: [PATCH] update with new data --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c9d1f0e..a5f7105 100644 --- a/README.md +++ b/README.md @@ -58,11 +58,12 @@ localhost or the same datacenter (<2 ms ping), disabling this (-1) will be benef

bukkit.yml

spawn-limits

-default: monsters:70, animals:10, water-animals:15, ambient:15
-optimized: monsters:45, animals:8, water-animals:3, ambient:1
+default: monsters:70, animals:10, water-animals:15, water-ambient:20, ambient:15
+optimized: monsters:12, animals:5, water-animals:2, water-ambient:2, ambient:0
explanation:
Lower values mean less mobs. Less mobs is less lag in general, but you want to balance it with player quality of life, -finding mobs in the world is big part of gameplay. More detailed explanation of how limits are calculated can be found in this pdf. +finding mobs in the world is big part of gameplay. With per-player-mob-spawns +those numbers represent basically 1:1 limit of mobs in the given category per player, so mob cap math is `playercount*limit`.

chunk-gc.period-in-ticks

default: 600