Modpack (1.20.1, Forge 47.3.0) crashing on launch due to Palladium (same issue, closed original issue too early) #122
Labels
No labels
documentation
duplicate
help wanted
invalid
Palladium 4 / 1.20.1
Palladium 5 / 1.21+
question
Review requested
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ThreeTAG/Palladium#122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Using a custom modpack I made for Minecraft 1.20.1 on Forge 47.3.0, and the modpack crashes on launch/while loading. I removed Palladium and the modpack loaded fine. However, Palladium is required to run one of the key mods in the modpack. Is there something I can do to stop my game from crashing while keeping palladium?
When the game crashes, no crash report is created. I've wiped the logs and crash reports folders to no avail.
I already submitted this issue once but closed the issue too soon as the game was functioning (this turned out to be a fluke). I apologize for the inconvenience. Thank you for your time.
Can you send an updated version of your latest.log file
latest.log
here is my most recent latest.log
thank you for putting up with my stupidity lol
Does your Minecraft even work with just Palladium installed? Really clueless here lol
works fine with just palladium
sorry i'm not giving much to work with, i'm pretty clueless too lol
Eeehhh, are there any other log files in your log folder which you could provide? Taking anything now, dont know what else to look for
Would it be helpful for me to just send the modpack as a zip?
Sure
Also is happening to my modpack. Same Forge and Minecraft version. My modpack is publicly on curseforge, but not the version with the mod, which is a dev version that I test with my Minecraft staff. Here is the log
latest.log
Ive looked into this again, both logs seem to close before the actual crash happens. Is there any update on this? Is this still happening?