From acf0b2d2f1546f70cf95114141b1623bc4702242 Mon Sep 17 00:00:00 2001 From: Newwind <support@newwindserver.com> Date: Sun, 25 Aug 2024 18:42:15 +0100 Subject: [PATCH] Fix incorrect timestamp in region file header recalculation (#11318) --- .../Attempt-to-recalculate-regionfile-header-if-it-is-co.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patches/server/Attempt-to-recalculate-regionfile-header-if-it-is-co.patch b/patches/server/Attempt-to-recalculate-regionfile-header-if-it-is-co.patch index 557f8c35ca..e41ac6f156 100644 --- a/patches/server/Attempt-to-recalculate-regionfile-header-if-it-is-co.patch +++ b/patches/server/Attempt-to-recalculate-regionfile-header-if-it-is-co.patch @@ -411,7 +411,7 @@ index 0000000000000000000000000000000000000000..00000000000000000000000000000000 + // simply destroy the timestamp header, it's not used + + for (int i = 0; i < 32 * 32; ++i) { -+ this.timestamps.put(i, calculatedOffsets[i] != 0 ? (int)System.currentTimeMillis() : 0); // write a valid timestamp for valid chunks, I do not want to find out whatever dumb program actually checks this ++ this.timestamps.put(i, calculatedOffsets[i] != 0 ? RegionFile.getTimestamp() : 0); // write a valid timestamp for valid chunks, I do not want to find out whatever dumb program actually checks this + } + + // write new header