This is a brief overview that can be used to quickly optimize the server settings. You can find more optimizations in this post.
With the gamerule disableElytraMovementCheck (set to true) you can turn off the anti-cheat check while flying the Elytra.
Name | Description | Default value | Recommended value |
view-distance | Determines the amount of world data that the server sends to the client. | 10 | between 8 and 10 |
simulation-distance | Sets the maximum distance from players that entities can be in order to be updated by the server. ("Entity Tick") | 10 | between 6 and 8 |
A Paper/ Spigot server is required for these settings!
Name | Description | Default value | Recommended value |
|
Sets entity spawn limits. These limits are per player! |
|
|
A Paper Server is required for these settings!
Name | Description | Default value | Recommended value |
|
Sets the maximum number of chunks saved in a single tick when saving the world. | 24 | between 16 and 20 |
|
If true, hopper performance is greatly improved by preventing the "InventoryMoveItem" event from being called for each slot in a container. | false | true |
|
validatenearbypoi* acquirepoi* mob-spawner secondarypoisensor* * Values that are too high for these settings can affect some villager/raid farms! |
|
|
|
The rate in ticks (20 ticks = 1 second) at which arrows shot by creative players or non-player entities are despawned. | default | 40 or 60 |
|
If "false", no ticks for armor stands are executed. Only noticable if using many armor stands. |
true | false |
|
If "true", tells the server to cache entity searches during an explosion instead of recalculating throughout the process. |
false | true |
|
Specifies the Redstone implementation that the server uses. In rare cases, a non-vanilla mode can lead to unwanted side effects with redstone builds! Also, plugins that change Redstone behavior might not work. |
VANILLA | EIGENCRAFT or ALTERNATE-CURRENT |