-
-
Notifications
You must be signed in to change notification settings - Fork 26
Crash on Launch #275
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
Comments
Ok ignore the above log as I installed the wrong forge v.30 instead of v.3. I do still crash on starting the pack with the correct forge Randomly it does load on second launch. |
Please upload your debug.log |
Please downgrade Forge to 47.1.3 as later versions are currently not supported. Also, try deleting the mods/.connector folder, it might help refresh jars. |
Ok so I downgraded to forge 47.1.3 removed the mods/.connector folder This is what I have so far: Crash log: https://gist.github.com/litjohn50/dce5bcfd73d8fd4dc06cc28453e02608 I am still getting the same timeout jar error |
Does this still occur on the latest version of connector? |
Yes, Sadly, this still occurs. Mainly, once I add a mod/ remove a mod, then it will stop timing out until it do a change to the modpack. But it's pretty recurrent. |
Tried to send you the log but buggered that up. Fixed links below |
I uploaded only a few mods, as soon as the error I expected occurred on fabric-automessage-1.0.0+1.20.1.jar, subsequent server runs are already unsuccessful |
Report: |
Is this still an issue? @DonorKrovi |
Closing as stale / cannot reproduce. If you can provide the necessary logs and information to reproduce the problem or identify the faulty mod, please open a new issue with all necessary details. |
Describe the bug
The modpack won't load
Steps to reproduce
Forge 47.1.30
ConnectorExtras-1.1.0+1.20.1
fabric-api-0.88.1+1.9.11+1.20.1
Connector-1.0.0-beta.14+1.20.1-full
TechReborn-5.8.7
Logs
https://gist.github.com/litjohn50/c0262800168407770e1af8db347a4735
Additional context
No response
The text was updated successfully, but these errors were encountered: