Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with large_icicle_tilted generation #19

Closed
GisusCryst opened this issue Nov 27, 2024 · 3 comments
Closed

Error with large_icicle_tilted generation #19

GisusCryst opened this issue Nov 27, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@GisusCryst
Copy link

GisusCryst commented Nov 27, 2024

Im getting:

[13:25:08] [Worker-Main-10/ERROR]:
Detected setBlock in a far chunk [32, -45], pos: class_2338{x=514, y=-14, z=-705}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / yungscavebiomes:frosted_caves/large_icicle_tilted]

over and over again in my server logs.

These messages seem to occur for newly generated chunks only.

Im using the Fabric version v2.0.0 for 1.20.1

@yungnickyoung yungnickyoung added the bug Something isn't working label Feb 3, 2025
@yungnickyoung
Copy link
Member

Looks like the large icicles are able to tilt a little too much, resulting in them trying to exceed the chunk bounds of the feature. Shouldn't cause any real issues, although it will occassionaly spam the logs.

@Claas-Fan-92
Copy link

Hello, we have the same problem on our server. If a player is in the Frosted Caves area, the CPU shoots up. If the player leaves the area, everything goes back to normal. I currently have a chunkloader there as we have a mining device allocated to it. As soon as a player is on the server, the server tells me it is overloaded even though the CPU and RAM are within the normal range in terms of utilization. If the server is empty again, everything goes back to normal despite the fact that there is a chunkloader. I've watched these icicles, but they don't break off, they just grow downwards.

@yungnickyoung
Copy link
Member

Fixed in v2.0.2.

@Claas-Fan-92 your issue sounds entirely different. Please open a new issue report for it, and it would be useful if you included the latest.log as well as a Spark profile so I can see where the performance bottleneck is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants