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

cascading worldgen lag on world creation (server) (1.12.2) (rv5 stable 11) #3486

lAimBotl opened this issue May 9, 2018 · 2 comments


Copy link

@lAimBotl lAimBotl commented May 9, 2018


[21:47:55] [Server thread/WARN] [FML]: Applied Energistics 2 loaded a new chunk [-2, 16] in dimension 0 (overworld) while populating chunk [-2, 15], causing cascading worldgen lag.
[21:47:55] [Server thread/WARN] [FML]: Please report this to the mod's issue tracker. This log can be disabled in the Forge config.


-In forge server console.
*Edit: seems to happen when someone is loading new chunks.
[15:49:48] [Server thread/WARN] [FML]: Applied Energistics 2 loaded a new chunk [71, -34] in dimension 7 (twilight_forest) while populating chunk [70, -34], causing cascading worldgen lag.

  • Minecraft Version: "1.12.2"
  • AE2 Version: "appliedenergistics2-rv5-stable-11"
  • Forge Version: "forge-1.12.2-"
Copy link

@yueh yueh commented May 19, 2018

If it is just happens once, it is really not that much of an issue. Forge just being a bit too agressive with their reporting. I might look into it, once there is not much other things around or if someone could prove it is an actual issue. (Also twilight forest is notorious for a slow world gen, so maybe there is something strange happen on their side)

Copy link

@lAimBotl lAimBotl commented May 19, 2018

It happens now when people are loading new chunks normally in any dimension, (the server is not pre genned) cannot tell if forge is somehow mistaking players loading chunks vs ae2

fscan added a commit that referenced this issue Jun 20, 2018
…sabled and prevent cascading worldgen.
@yueh yueh closed this in #3542 Jun 26, 2018
yueh added a commit that referenced this issue Jun 26, 2018
* Fixes crash when either quartz types are disabled and prevent cascading worldgen.
* Also fixes  #3486
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants