Disable delayed chunk unloads by default
While the option remains a powerful tool we recommend everyone use, 30s is proving to be a bit much for certain gametypes and many admins are confused that after updating they are now facing extreme loaded chunk counts. We do recommend experienced users configure this value as needed, but we cannot keep it as a default option given the variety of gametypes, the potential inexperience of new users, and previous users upgrading and now facing extreme chunk counts that offer little benefit.
Dieser Commit ist enthalten in:
Ursprung
2e2842032f
Commit
97d0490c4a
@ -1,4 +1,4 @@
|
||||
From 4386477ab987b1a8eb91d3efcac70e53ca77833f Mon Sep 17 00:00:00 2001
|
||||
From 54b4193c57fd00f93d585132e60ae22d9f0310de Mon Sep 17 00:00:00 2001
|
||||
From: Aikar <aikar@aikar.co>
|
||||
Date: Sat, 18 Jun 2016 23:22:12 -0400
|
||||
Subject: [PATCH] Delay Chunk Unloads based on Player Movement
|
||||
@ -17,7 +17,7 @@ This allows servers with smaller worlds who do less long distance exploring to s
|
||||
wasting cpu cycles on saving/unloading/reloading chunks repeatedly.
|
||||
|
||||
diff --git a/src/main/java/com/destroystokyo/paper/PaperWorldConfig.java b/src/main/java/com/destroystokyo/paper/PaperWorldConfig.java
|
||||
index 0d2af96..bc41b7e 100644
|
||||
index 0d2af96..327a784 100644
|
||||
--- a/src/main/java/com/destroystokyo/paper/PaperWorldConfig.java
|
||||
+++ b/src/main/java/com/destroystokyo/paper/PaperWorldConfig.java
|
||||
@@ -364,6 +364,15 @@ public class PaperWorldConfig {
|
||||
@ -26,7 +26,7 @@ index 0d2af96..bc41b7e 100644
|
||||
|
||||
+ public long delayChunkUnloadsBy;
|
||||
+ private void delayChunkUnloadsBy() {
|
||||
+ delayChunkUnloadsBy = PaperConfig.getSeconds(getString("delay-chunk-unloads-by", "30s"));
|
||||
+ delayChunkUnloadsBy = PaperConfig.getSeconds(getString("delay-chunk-unloads-by", "0s"));
|
||||
+ if (delayChunkUnloadsBy > 0) {
|
||||
+ log("Delaying chunk unloads by " + delayChunkUnloadsBy + " seconds");
|
||||
+ delayChunkUnloadsBy *= 1000;
|
||||
|
In neuem Issue referenzieren
Einen Benutzer sperren