From a4bbe926b20cffcf48ee802acb6e25a08752803c Mon Sep 17 00:00:00 2001
From: Jason Penilla <11360596+jpenilla@users.noreply.github.com>
Date: Tue, 15 Jun 2021 03:13:30 -0700
Subject: [PATCH] Remove sync loading of spawn chunks

Adding the tickets is sufficient
---
 .../Configurable-Keep-Spawn-Loaded-range-per-world.patch      | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/patches/server/Configurable-Keep-Spawn-Loaded-range-per-world.patch b/patches/server/Configurable-Keep-Spawn-Loaded-range-per-world.patch
index 6ee5c5f094..b2cacab732 100644
--- a/patches/server/Configurable-Keep-Spawn-Loaded-range-per-world.patch
+++ b/patches/server/Configurable-Keep-Spawn-Loaded-range-per-world.patch
@@ -132,10 +132,6 @@ index 0000000000000000000000000000000000000000..00000000000000000000000000000000
 +            // left
 +            chunkproviderserver.addRegionTicket(TicketType.START, new ChunkPos(spawn.add(-radiusInBlocks, 0, z)), 1, Unit.INSTANCE); // level 32
 +        }
-+
-+        MCUtil.getSpiralOutChunks(spawn, radiusInBlocks >> 4).forEach(pair -> {
-+            getChunkSource().getChunkAtMainThread(pair.x, pair.z);
-+        });
 +    }
 +    public void removeTicketsForSpawn(int radiusInBlocks, BlockPos spawn) {
 +        // In order to respect vanilla behavior, which is ensuring everything but the spawn border can tick, we added tickets