Cascading worldgen lag error
IITFA opened this issue ยท 4 comments
Expected Behavior
Spotted error in server console, probably shouldn't be an error.
Actual Behavior
Steps to Reproduce
Was flying around in creative
Version of Minecraft, Bewitchment, Forge, Patchouli, and Baubles used
1.12.2
bewitchment-1.12.2-0.0.21.3.jar
Screenshots encouraged
Logs, in the event of a crash
[20:31:54] [Server thread/WARN] [FML]: Bewitchment loaded a new chunk [47, 230] in dimension 0 (overworld) while populating chunk [48, 230], causing cascading worldgen lag.
[20:31:54] [Server thread/WARN] [FML]: Please report this to the mod's issue tracker. This log can be disabled in the Forge config.
[20:32:04] [Server thread/WARN] [minecraft/MinecraftServer]: Can't keep up! Did the system time change, or is the server overloaded? Running 10330ms behind, skipping 206 tick(s)
If this is a question, developer commentary, or a suggestion, ignore this template
I'm not a developer nor do I understand Java code, but I can tell you that this happens with multiple mods such as Ruins, Thermal Expansion Mods, and any other mod that has something to generate in the world. This mainly just a minecraft limitation...
@EnvyingGolem47 Cascading worldgen lag is when a mod loads another chunk while generating. This is not, in it of itself a bad thing because some structures are multi-chunk. The problem is when the loading of this chunk loads yet another chunk and it continues. This is mostly caused by incorrect position offsets in generation of trees and flowers and such. You should not get "cascading worldgen lag" errors if a mod is doing things properly.
