Cascading World Generation Caused by Quark
nveXyounes opened this issue · 1 comments
In my modded Minecraft 1.12.2 world, I’m experiencing cascading world generation lag, and Quark appears to be one of the causes. While populating chunks, Quark is loading adjacent chunks, which results in cascading worldgen lag and negatively affects performance.
[14:28:57] [Server thread/WARN] [FML]: Quark loaded a new chunk [-118, -79] in dimension 0 (overworld) while populating chunk [-119, -79], causing cascading worldgen lag.
[14:33:29] [Server thread/WARN] [FML]: Quark loaded a new chunk [-118, 125] in dimension 0 (overworld) while populating chunk [-118, 124], causing cascading worldgen lag.
[14:44:39] [Server thread/WARN] [FML]: Quark loaded a new chunk [-131, 149] in dimension 0 (overworld) while populating chunk [-130, 149], causing cascading worldgen lag.
This issue arises during terrain generation when new chunks are being loaded by Quark while adjacent chunks are still being populated.
Mods Involved:
Quark (contributing to cascading worldgen)
Other mods: LLibrary, Mowzie's Mobs, Open Terrain Generator, Biomes O' Plenty, etc., are also contributing to similar issues.
Steps to Reproduce:
Load a modded Minecraft 1.12.2 world with Quark enabled.
Explore new chunks and monitor the logs for cascading worldgen warnings.
Observe that Quark triggers new chunk generation while adjacent chunks are being populated.
quark version : Quark-r1.6-179.jar
Custom World generation mods : OpenTerrainGenerator-1.12.2-v9.5-R1.jar + Biome_Bundle_O_Plenty-1.12.2_v1.0.jar
Forge : forge:1.12.2-14.23.5.2860
Sorry, old issue, clearing out the tracker. I believe this is caused by Quark's large underground features (like the big stone blobs). Rewriting these to work chunk-by-chunk would be quite difficult and 1.12 is far out of support. 😔
Unfortunately this paste seems to be cut off, so I can't tell if this is big time runaway cascading worldgen lag or if it's just a few blocks spilling across a chunk border here and there. A few blocks here and there is annoying, but should be fine.