Folia block generation error #61

New issue

Open

opened 2023-04-26 14:21:42 +02:00 by xiaoyueyoqwq · 4 comments

xiaoyueyoqwq commented

2023-04-26 14:21:42 +02:00

(Migrated from github.com)

Expected behavior

It should have safely generated normal blocks following my server's packets, because blocks elsewhere on my server were normal

Observed/Actual behavior

But....Okay, look this then you can know the problems

Steps/models to reproduce

I think this is a completely random error, because most of my server is normal, including the error map I showed has been generated on the Paper server and copied to Folia, but Folia is still in the wrong state

But I observed a problem, at first Folia did load the maps normally, but as the loading maps got bigger and started to freeze from a certain edge, the maps started to get strange and made the normal loading maps wrong, which happened in the ocean, including the rivers along the oceans

Maybe it's an issue with my packets, but I can't 100% guarantee that this is the case, because the rest of the maps on my server are complete and error-free, so I chose to give you feedback

Plugin and Datapack List

plugins:

datapackets:

Folia version

[20:20:50 INFO]: Checking version, please wait...
[20:20:50 INFO]: This server is running Folia version git-Folia-"b97116b" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b97116b)
You are running the latest version

Other

This is a little bit wrong report, in that time server only output these things...

https://paste.ubuntu.com/p/XBJ8P9Ytwh/

### Expected behavior It should have safely generated normal blocks following my server's packets, because blocks elsewhere on my server were normal ### Observed/Actual behavior But....Okay, look this then you can know the problems ![image](https://user-images.githubusercontent.com/71379165/234566223-3376ab72-764e-4cae-b5a0-b08813023f81.png) ### Steps/models to reproduce I think this is a completely random error, because most of my server is normal, including the error map I showed has been generated on the Paper server and copied to Folia, but Folia is still in the wrong state But I observed a problem, at first Folia did load the maps normally, but as the loading maps got bigger and started to freeze from a certain edge, the maps started to get strange and made the normal loading maps wrong, which happened in the ocean, including the rivers along the oceans Maybe it's an issue with my packets, but I can't 100% guarantee that this is the case, because the rest of the maps on my server are complete and error-free, so I chose to give you feedback ### Plugin and Datapack List plugins: ![image](https://user-images.githubusercontent.com/71379165/234567433-3b2dfc01-5daa-4a97-ab37-183093128d6d.png) datapackets: ![image](https://user-images.githubusercontent.com/71379165/234568913-eeb0c061-481a-45f2-a4f9-18cd89e808af.png) ### Folia version [20:20:50 INFO]: Checking version, please wait... [20:20:50 INFO]: This server is running Folia version git-Folia-"b97116b" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b97116b) You are running the latest version ### Other This is a little bit wrong report, in that time server only output these things... ------------------------------------ https://paste.ubuntu.com/p/XBJ8P9Ytwh/ ------------------------------------

titandino commented

2023-05-03 00:09:28 +02:00

(Migrated from github.com)

No real reliable reproduction steps I can provide, unfortunately. I can get it to happen relatively reliably when just driving around in a boat. This was happening on an Intel Xeon Phi 7210 if that helps. It has an extremely high core count but the clock speed is pretty low so that could be why it is happening more often on this machine. I notice it doesn't happen nearly as often on my Intel i9-10600k.

I have had a few instances of terrain generation bugs as well. Nothing that looks like this, though. Mine consisted of just chunk borders similar to when you change the seed and try to generate new terrain. No real reliable reproduction steps I can provide, unfortunately. I can get it to happen relatively reliably when just driving around in a boat. This was happening on an Intel Xeon Phi 7210 if that helps. It has an extremely high core count but the clock speed is pretty low so that could be why it is happening more often on this machine. I notice it doesn't happen nearly as often on my Intel i9-10600k.

👀 2

xiaoyueyoqwq commented

2023-05-03 07:00:36 +02:00

(Migrated from github.com)

I have had a few instances of terrain generation bugs as well. Nothing that looks like this, though. Mine consisted of just chunk borders similar to when you change the seed and try to generate new terrain.

No real reliable reproduction steps I can provide, unfortunately. I can get it to happen relatively reliably when just driving around in a boat. This was happening on an Intel Xeon Phi 7210 if that helps. It has an extremely high core count but the clock speed is pretty low so that could be why it is happening more often on this machine. I notice it doesn't happen nearly as often on my Intel i9-10600k.

maybe you are right? My server was running on intel Xeon E5 server, maybe this is problem...

> I have had a few instances of terrain generation bugs as well. Nothing that looks like this, though. Mine consisted of just chunk borders similar to when you change the seed and try to generate new terrain. > > No real reliable reproduction steps I can provide, unfortunately. I can get it to happen relatively reliably when just driving around in a boat. This was happening on an Intel Xeon Phi 7210 if that helps. It has an extremely high core count but the clock speed is pretty low so that could be why it is happening more often on this machine. I notice it doesn't happen nearly as often on my Intel i9-10600k. maybe you are right? My server was running on intel Xeon E5 server, maybe this is problem...

Spottedleaf commented

2023-05-14 03:09:17 +02:00

(Migrated from github.com)

Are you sure your datapacks don't cause this?

titandino commented

2023-05-15 03:04:56 +02:00

(Migrated from github.com)

I am not quite sure what causes it. I can't seem to reproduce it when setting the seed manually in the server.properties.