quark 393, 1.19.2

by 80% of chance, Minecraft will be stuck at loading screen (white unresponsive screen) and at this step.
Dispatching Module Step CONSTRUCT_CLIENT

send log

Encountering same issue.

Apple M1 Pro
MacOS 13.1 (22C65)

Quark-3.4-389
Modpack: Create Flavored
Log: Here

Launch arguments

-Xmx4096m -Xms256m -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true -Duser.language=en -Duser.country=US

Can you confirm it works without quark? Maybe try with more ram

update: it'll happen much less (or even none) after a few success startups.

update:

found the cause: it was due to mr. crayfish's framework mod and gun mod. after removing these 2 mods no start-up issue persist.

Sorry for reopening this, but this still happens and it's very annoying. It seems to happen with a high number of mods, only with Quark. In my tests, it starts to crash somwhere at 105 mods enabled (including necessary libraries). Symptoms are the same, if you're lucky, the game starts. No error logs related to this can be found. I hope this gets fixed.

I seem to have encountered the same hanging issue for Quark 3.4-405 on MC 1.19.2 and I have been trying for hours to track down the issue. I got it to work once with 180 mods, then I could not load more than 133 for a long time, and now I have suddenly been able to load all of my 188 functioning mods at once.

Backpacked, Catalogue, and Configured by Mr. Crayfish did not seem to be the issue.

I have also been fluctuating my allocated RAM between 8GB and 4GB without noticeable effect, I even at the end kicked it up to 12 GB with no change.

It is said that Forge loaded mods in the order of file names, so I added a "." before Quark's name. Tested to be effective.