Server Crash

[xKumorio]

фцвфцвфцв

[xKumorio]

Now when I go to the account that is there the server instantly shuts down

[electronicboy]

Just to clarify, are you saying that you moved the chunks from one part of the world to another?

…

On Wed, 9 Aug 2023, 03:18 kumorio, ***@***.***> wrote: Now when I go to the account that is there the server instantly shuts down — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMAZHJHX3A6YP5IQGEFHTXULXONANCNFSM6AAAAAA3JJ2UWE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[xKumorio]

Just to clarify, are you saying that you moved the chunks from one part of the world to another?
…
On Wed, 9 Aug 2023, 03:18 kumorio, @.> wrote: Now when I go to the account that is there the server instantly shuts down — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMAZHJHX3A6YP5IQGEFHTXULXONANCNFSM6AAAAAA3JJ2UWE . You are receiving this because you are subscribed to this thread.Message ID: @.>

No, I moved an entire region to different coordinates

[electronicboy]

So, yes. I'd imagine that that is the very issue, the chunks are pointing to block locations out of the region and thus blowing up as it tries to schedule ticks for them as part of the upgrade logic.

…

On Wed, 9 Aug 2023, 03:37 kumorio, ***@***.***> wrote: No, I moved an entire region to different coordinates — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMAZEUQZAEF5XUCF5BN6LXULZU3ANCNFSM6AAAAAA3JJ2UWE> . You are receiving this because you commented.Message ID: ***@***.***>

[xKumorio]

So, yes. I'd imagine that that is the very issue, the chunks are pointing to block locations out of the region and thus blowing up as it tries to schedule ticks for them as part of the upgrade logic.
…
On Wed, 9 Aug 2023, 03:37 kumorio, @.> wrote: No, I moved an entire region to different coordinates — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMAZEUQZAEF5XUCF5BN6LXULZU3ANCNFSM6AAAAAA3JJ2UWE . You are receiving this because you commented.Message ID: @.>

For example:

I have a region that is located at the coordinates
50 50

I move it to coordinates 25000 25000

If this region was generated in 1.20.1 there is no problem, but if it was generated in 1.12.2 the folia crashes.

I've been getting errors like that:

[07:07:07] [RegionFile I/O Thread #2/ERROR]: Attempting to read chunk data at [coords, coords] but got chunk data for [coords, coords] instead! Attempting regionfile recalculation for regionfile
[07:07:07] [RegionFile I/O Thread #2/ERROR]: Can't recalculate regionfile header, regenerating chunk [coords, coords]

[electronicboy]

Yes, because the chunk contains data which is related to the location in the world, so when stuff falls out of bound, it blows up, 100% as expected Paper also saves the position of the chunk to prevent an old bug where chunks would end up being relocated and destroying the world, so that's going to create issues. This is basically 100% unsupported behaviour, and I'd be surprised if this wasn't closed as a won't fix as a result, if you want to relocate chunks safely, you'll actually need to do it properly, i.e. dealing with the data inside of them.

…

On Wed, 9 Aug 2023, 03:43 kumorio, ***@***.***> wrote: So, yes. I'd imagine that that is the very issue, the chunks are pointing to block locations out of the region and thus blowing up as it tries to schedule ticks for them as part of the upgrade logic. … <#m_-8354801420376215939_m_4863907484734151969_> On Wed, 9 Aug 2023, 03:37 kumorio, *@*.*> wrote: No, I moved an entire region to different coordinates — Reply to this email directly, view it on GitHub <#143 (comment) <#143 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMAZEUQZAEF5XUCF5BN6LXULZU3ANCNFSM6AAAAAA3JJ2UWE <https://github.com/notifications/unsubscribe-auth/AAJMAZEUQZAEF5XUCF5BN6LXULZU3ANCNFSM6AAAAAA3JJ2UWE> . You are receiving this because you commented.Message ID: @.*> For example: I have a region that is located at the coordinates 50 50 I move it to coordinates 25000 25000 If this region was generated in 1.20.1 there is no problem, but if it was generated in 1.12.2 the folia crashes. I've been getting errors like that: [07:07:07] [RegionFile I/O Thread #2 <#2>/ERROR]: Attempting to read chunk data at [coords, coords] but got chunk data for [coords, coords] instead! Attempting regionfile recalculation for regionfile [07:07:07] [RegionFile I/O Thread #2 <#2>/ERROR]: Can't recalculate regionfile header, regenerating chunk [coords, coords] — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMAZGDBM2EKNMIQ7BVCJTXUL2LNANCNFSM6AAAAAA3JJ2UWE> . You are receiving this because you commented.Message ID: ***@***.***>

[xKumorio]

Yes, because the chunk contains data which is related to the location in the world, so when stuff falls out of bound, it blows up, 100% as expected Paper also saves the position of the chunk to prevent an old bug where chunks would end up being relocated and destroying the world, so that's going to create issues. This is basically 100% unsupported behaviour, and I'd be surprised if this wasn't closed as a won't fix as a result, if you want to relocate chunks safely, you'll actually need to do it properly, i.e. dealing with the data inside of them.
…
On Wed, 9 Aug 2023, 03:43 kumorio, @.> wrote: So, yes. I'd imagine that that is the very issue, the chunks are pointing to block locations out of the region and thus blowing up as it tries to schedule ticks for them as part of the upgrade logic. … <#m_-8354801420376215939_m_4863907484734151969_> On Wed, 9 Aug 2023, 03:37 kumorio, @.> wrote: No, I moved an entire region to different coordinates — Reply to this email directly, view it on GitHub <#143 (comment) <#143 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMAZEUQZAEF5XUCF5BN6LXULZU3ANCNFSM6AAAAAA3JJ2UWE https://github.com/notifications/unsubscribe-auth/AAJMAZEUQZAEF5XUCF5BN6LXULZU3ANCNFSM6AAAAAA3JJ2UWE . You are receiving this because you commented.Message ID: @.> For example: I have a region that is located at the coordinates 50 50 I move it to coordinates 25000 25000 If this region was generated in 1.20.1 there is no problem, but if it was generated in 1.12.2 the folia crashes. I've been getting errors like that: [07:07:07] [RegionFile I/O Thread #2 <#2>/ERROR]: Attempting to read chunk data at [coords, coords] but got chunk data for [coords, coords] instead! Attempting regionfile recalculation for regionfile [07:07:07] [RegionFile I/O Thread #2 <#2>/ERROR]: Can't recalculate regionfile header, regenerating chunk [coords, coords] — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMAZGDBM2EKNMIQ7BVCJTXUL2LNANCNFSM6AAAAAA3JJ2UWE . You are receiving this because you commented.Message ID: @.**>

Today I transferred everything correctly no errors in the conosol, but still the server crashes

[xKumorio]

@Spottedleaf
I deleted absolutely all entities in all regions, as well as scanned the world with https://github.com/Fenixin/Minecraft-Region-Fixer.
No errors are shown, also I do not write anything in the console just an error that was the same and remains the same

[Spottedleaf]

Resolved by 4179b8f3fa86437aa1d9742930fd8ca6d23515a0 in f6e91e9

You should understand that Paper does other things when regionfiles are relocated like this:

1. Regionfile recalculation will delete every single chunk in the regionfile
2. Entities located outside of the deserialized chunk are deleted
3. Tile entities located outside of the deserialized chunk are deleted
4. Vanilla deletes scheduled ticks outside of the deserialized chunk
5. The fix to this issue is to delete neighbouring scheduled ticks

You'll notice that the common trend is to clean up after user or plugin error.

You need to properly relocate chunks using other tools.