Gaming32 / mod-loading-screen

An advanced loading screen with the loading progress of mods
https://modrinth.com/mod/mod-loading-screen
MIT License
5 stars 3 forks source link

Crashing on Fabric 0.14.24 (GDLauncher) #23

Open C4uTi0N opened 10 months ago

C4uTi0N commented 10 months ago

[11:58:21] [main/INFO]: Loading Minecraft 1.20.1 with Fabric Loader 0.14.24 [11:58:21] [main/INFO]: Loading 6 mods:

Gaming32 commented 10 months ago

Please send your entire log.

C4uTi0N commented 10 months ago

Without Fabric API latest.log

With Fabric API latest.log

Gaming32 commented 10 months ago

So it just exits?

C4uTi0N commented 10 months ago

yes MC

And it has worked fine in the past

Gaming32 commented 10 months ago

Can you use the latest build from GitHub Actions, then send me the .cache folder from inside your .minecraft?

C4uTi0N commented 10 months ago

fabric.zip

Gaming32 commented 10 months ago

That is not what I asked you to send

C4uTi0N commented 10 months ago

It's probably bad file naming on my part, but the zip file contains the .cache and the logs folder, nothing more

Gaming32 commented 10 months ago

My bad, my device was interpreting .cache as hidden, so I couldn't see it. There is a new build available that will log even more debug info. Can you download that version and send me the .cache folder after using it?

C4uTi0N commented 10 months ago

cache.zip

this is using the latest commit under Actions (Log exceptions to file)

Gaming32 commented 10 months ago

Can you try with the latest build and send a screenshot of the error?

C4uTi0N commented 10 months ago

It still didn't give an error with the latest build, it just didn't start like before. However i tried downloading the stadard minecraft launcher and making a fabric instancce in that, and it worked with no issue Then after looking i around in GDLauncher settings i found and tried changing a setting which seemed to fix the issue

Setting the startup method to "Symlink" instead of "Default" fixed the issue image

Gaming32 commented 10 months ago

Does this issue happen with 0.14.24 specifically, or does it happen on older Fabric versions with the latest version of Mod Loading Screen?

C4uTi0N commented 10 months ago

it also happen on 0.14.23 and i just tried with 0.14.13 as a random pick and it has the same behavior as the other versions This is with "Startup Method" is set to "Default", so i think it's a GDLauncher compatibility thing, as it works fine when i set it to "Symlink"