3
I messed up maybe
i was deleting texture packs from the modrinth app and i deleted some i was using and this happened: java.lang.IllegalStateException: Texture does not exist, can't get it before something initializes it.
i was also downloading a bunch of mods from simply/fabulously (i forget which) optimixed because i play on a potato laptop cause my mom wont let me get a computer
here is the crash report
i was also downloading a bunch of mods from simply/fabulously (i forget which) optimixed because i play on a potato laptop cause my mom wont let me get a computer
here is the crash report
Create an account or sign in to comment.
5
Can you explain the issue more, like what exactly happend:
I get it, you deleted some packs, you mean from your computer right? (the app is a launcher)?
I get it, you deleted some packs, you mean from your computer right? (the app is a launcher)?
this
In the “content” section of a modrinth app modpack I clicked on the “resource packs” filter and clicked the trash can icon on a pack that was enabled in that installation. Around the same time I was also downloading a bunch of performance mods from the modpack “simply optimized”
I don't know modrith, but your description implies you deleted a resource pack while simultaneously installing a mod pack; this raises the posibilty that the deleted pack was either part of the pack being installed (or that the pack being installed had 'read' what packs were already present and was installed with the expectaion that each would be available).
First thing is to secure the last (pre-issue) backup of your world[s], then make backups of the world[s] in their preasent state (hopefully you've not opened them since having this issue).
You might then try rebuilding a new MC installation equivalent to what you had starting from a clean version from MS/Mj then adding back whatever packs etc. you had before the modrith 'adventure' (in as near the same order as previously).
At that point, test the new installation of MC using [yet another] copy of your world. Assuming you have restored the status que ante, go back to modrith and make the updates you previously tried to make, but allow each action to complete before initiating the next. [If you can tolerate the tedium, testing after each step might be wise.]
It would also be well to take another read through the docs for the various bits to be clear about what the “simply optimized” modpack requires/expects in order to work.
First thing is to secure the last (pre-issue) backup of your world[s], then make backups of the world[s] in their preasent state (hopefully you've not opened them since having this issue).
You might then try rebuilding a new MC installation equivalent to what you had starting from a clean version from MS/Mj then adding back whatever packs etc. you had before the modrith 'adventure' (in as near the same order as previously).
At that point, test the new installation of MC using [yet another] copy of your world. Assuming you have restored the status que ante, go back to modrith and make the updates you previously tried to make, but allow each action to complete before initiating the next. [If you can tolerate the tedium, testing after each step might be wise.]
It would also be well to take another read through the docs for the various bits to be clear about what the “simply optimized” modpack requires/expects in order to work.
maybe some mods were connected
