Rewrite chunk system (#8177)

Patch documentation to come

Issues with the old system that are fixed now:
- World generation does not scale with cpu cores effectively.
- Relies on the main thread for scheduling and maintaining chunk state, dropping chunk load/generate rates at lower tps.
- Unreliable prioritisation of chunk gen/load calls that block the main thread.
- Shutdown logic is utterly unreliable, as it has to wait for all chunks to unload - is it guaranteed that the chunk system is in a state on shutdown that it can reliably do this? Watchdog shutdown also typically failed due to thread checks, which is now resolved.
- Saving of data is not unified (i.e can save chunk data without saving entity data, poses problems for desync if shutdown is really abnormal.
- Entities are not loaded with chunks. This caused quite a bit of headache for Chunk#getEntities API, but now the new chunk system loads entities with chunks so that they are ready whenever the chunk loads in. Effectively brings the behavior back to 1.16 era, but still storing entities in their own separate regionfiles.

The above list is not complete. The patch documentation will complete it.

New chunk system hard relies on starlight and dataconverter, and most importantly the new concurrent utilities in ConcurrentUtil.

Some of the old async chunk i/o interface (i.e the old file io thread reroutes _some_ calls to the new file io thread) is kept for plugin compat reasons. It will be removed in the next major version of minecraft.

The old legacy chunk system patches have been moved to the removed folder in case we need them again.

1 files changed, 42 insertions, 0 deletions

diff --git a/patches/server/0837-Buffer-OOB-setBlock-calls.patch b/patches/server/0837-Buffer-OOB-setBlock-calls.patch
new file mode 100644
index 0000000000..62e5606e17
--- /dev/null
+++ b/patches/server/0837-Buffer-OOB-setBlock-calls.patch
@@ -0,0 +1,42 @@
+From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
+From: Shane Freeder <[email protected]>
+Date: Sat, 19 Mar 2022 12:12:22 +0000
+Subject: [PATCH] Buffer OOB setBlock calls
+
+lets debug mode throw a trace in order to potentially see where
+such calls are cascading from easier, but, generally, if you see one setBlock
+call, you're gonna see more, and this just potentially causes a flood of logs
+which can cause issues for slower terminals, etc.
+
+We can limit the flood by just allowing one for a single gen region,
+we'll also only gen a trace for the first one, I see no real pressing need
+to generate more, given that that would *massively* negate this patch otherwise
+
+diff --git a/src/main/java/net/minecraft/server/level/WorldGenRegion.java b/src/main/java/net/minecraft/server/level/WorldGenRegion.java
+index 51d3150e732f95be13f5f54d994dab1fa89ed3f2..80c1e0e47818486a68e0114b063395290365346b 100644
+--- a/src/main/java/net/minecraft/server/level/WorldGenRegion.java
++++ b/src/main/java/net/minecraft/server/level/WorldGenRegion.java
+@@ -274,6 +274,7 @@ public class WorldGenRegion implements WorldGenLevel {
+         }
+     }
+ 
++    private boolean hasSetFarWarned = false; // Paper
+     @Override
+     public boolean ensureCanWrite(BlockPos pos) {
+         int i = SectionPos.blockToSectionCoord(pos.getX());
+@@ -293,7 +294,15 @@ public class WorldGenRegion implements WorldGenLevel {
+ 
+             return true;
+         } else {
++            // Paper start
++            if (!hasSetFarWarned) {
+             Util.logAndPauseIfInIde("Detected setBlock in a far chunk [" + i + ", " + j + "], pos: " + pos + ", status: " + this.generatingStatus + (this.currentlyGenerating == null ? "" : ", currently generating: " + (String) this.currentlyGenerating.get()));
++            hasSetFarWarned = true;
++            if (this.getServer() != null && this.getServer().isDebugging()) {
++                io.papermc.paper.util.TraceUtil.dumpTraceForThread("far setBlock call");
++            }
++            }
++            // Paper end
+             return false;
+         }
+     }