You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to use File Director to install the Witchery: Resurrected mod (https://witchery.msrandom.net/home/downloads) into a modpack I am developing. After configuring File Director to download the mod off of its website, I launched the pack--the mod successfully downloads, and then the launch process errors and stops. I confirmed that this happens with only File Director and Witchery, no other mods. Log below. First startup.log
However, the strange thing is when I proceed to try to launch the pack again, with the Witchery mod already downloaded, the pack launches correctly and I reach the main menu just fine. Log below. Second startup.log
It would seem that Witchery is attempting to do something during startup that is incompatible with how File Director injects mods into the startup sequence... at least, that's my best theory.
The text was updated successfully, but these errors were encountered:
Witchery: Resurrected does some quirky stuff, affecting coremodding functionality from other mods. This was debated quite thoroughly in a 1.12.2 modding server, possibly affecting File Director likewise. Will keep this updated when there's news.
I am attempting to use File Director to install the Witchery: Resurrected mod (https://witchery.msrandom.net/home/downloads) into a modpack I am developing. After configuring File Director to download the mod off of its website, I launched the pack--the mod successfully downloads, and then the launch process errors and stops. I confirmed that this happens with only File Director and Witchery, no other mods. Log below.
First startup.log
However, the strange thing is when I proceed to try to launch the pack again, with the Witchery mod already downloaded, the pack launches correctly and I reach the main menu just fine. Log below.
Second startup.log
It would seem that Witchery is attempting to do something during startup that is incompatible with how File Director injects mods into the startup sequence... at least, that's my best theory.
The text was updated successfully, but these errors were encountered: