World stuck on loading screen at 100%

[AndreasHnida]

After installing the datapacks phi.core and phi.modifyinv for use with Builders-Wand-1.14 and activating it ingame every world I tested gets stuck at the loading screen at 100% after I save quit and reopen the game.

Removing the Phi datapacks from the datapacks folder solves the issue. The world get loaded fine. The datapacks can than be placed back into the datapacks folder and activated by /reload while the game is running.

I am playing MC 1.14.4

Installed Mods:
Forge 28.0.55
preview_OptiFine_1.14.4_HD_U_F4_pre2
VoxelMap-Mod-1.14.4
U-Team-Core-1.14.4
OpenBlocks-Elevator-Mod-1.14.4
reap-1.10.1

[vdvman1]

I just tested the latest version of Phi in Vanilla 1.14.4 and Vanilla 19w34a and it loads without problems on my machine. How long ago did you download Phi? It might be an issue with a previous version, however it is likely to be caused by the mods you have installed. Can you send me the game log when the problem occurs? I might be able to narrow down what is causing the problem and why.

[AndreasHnida]

I have to admit that the world loads after about 3-4 minutes being stuck at 100% if I run the game on a purely vanilla configuration. (normally an average world loads within 10-20 seconds). After waiting for over half an hour while trying to load the modded configuration I might have become impatient and concluded the issue would also exist with a pure vanilla configuration without waiting long enough for my system. Sorry for that.

Nethertheless I wanted to at least track down the mods causing this problem so that there is information available for you for future reference. Btw, the debug output of minecraft does not output anything unusual. Furthermore I have to clarify that I am running a pretty old hardware setup at the moment (Phenom II x6 1075T @3ghz / 12GB Ram with 6 GB allocated to minecraft due to some excessive mods I have running on 1.12.2). So these are my findings based on my old hardware. But like I said, maybe it helps you for future reference.

I created a new world, installed the two datapacks (phi.core and phi.modifyinv) I need for the builder wand datapack, set a time limit for loading the world of about 2-3 minutes and began adding and removing mods one at a time, restarting minecraft and trying to load the test world. Here are my findings of the mods I have currently installed on 1.14.4.

Not causing any problems in combination are:
Forge Modloader 28.0.55
preview_OptiFine_1.14.4_HD_U_F4_pre2
Compressed-Items-Mod-1.14.4
CraftingCraft-Mod-1.14.4
Extended-Lights-Mod-1.14.4
KleeSlabs-Mod-1.14.4
OpenBlocks-Elevator-Mod-1.14.4
The-Flying-Things-Mod-1.14.4
Useful-Backpacks-Mod-1.14.4
U-Team-Core-1.14.4
Hwyla-Mod-1.14.4
VoxelMap-Mod-1.14.4

Stuck at 100% are:
Flesh-2-Leather-Mod-1.14.4
MinecraftCapes Forge 1.14.4
reap-1.10.1-1.14.4

Take care and keep up your awesome work.

[vdvman1]

That is quite strange that it is those mods that are having issues, I would have expected it to be either forge itself or optifine.
Would you mind linking me to those mods so I can see if I can find why they might be causing problems? I might be able to make bug reports for those mods if I can narrow down the true cause

[Bloo-dev]

Some of our users are reporting a similar issue - let's sort this out together. I'll run some tests later.

[vdvman1]

New evidence for what is causing this bug has been found. It appears that changing the scheduled functions to uses 2t instead of 1t stops the freezing, so it is possible that forge is running functions scheduled for 1t in the current tick instead of the next tick and resetting the chain length, resulting in an infinite loop.
However I haven't tested this