I doubt there's any way to fix it now so have this post as a warning. I've been playing on a modified cobblemon pack that I added some things to. When I closed the app last night, it forced an update I didn't want and now that I've opened it this morning, cobblemon completely bricked. I couldn't open my world or make a new one. I have no clue what they did and I had to delete that instance.
I've spent the past 5 or so hours trying to remake the modpack with what I added but one of my most import mods, Peacefulhunger, wont even work with cobblemon anymore, let alone the other mods I was using. I had everything perfectly balanced and now I don't think I can get it that way again. Everything I used is suddenly incompatible no matter what I change. Not only have I lost all my Pokémon friends, but I'll never be able to catch them again cuz their mods just won't work with each other anymore. This is including fakemon, pokemon not in the base cobblemon, and about 15 legendries I worked hard to get. All added with extra mods that were working just fine last night!
Be careful and make sure to take screenshots of your friends. I didn't and look where that got me. 🙁
by LaptopArmageddon
10 Comments
Modrinth bricked my custom packs yesterday too and I cannot figure it out. So sorry this happened to you too.
Can’t ya just restore from backup?
why the fuck is modrinth forcing an update lmao do they know how mods work
Can you copy the save world and try to reinstall the previous version? If not could you use another app with the same mods and paste the file there?
In theory, if you haven’t deleted your saves you can create a new instance of the pack and if it works copy the saves over.
If not maybe an instance on Prism
…yeesh. Kinda glad I switched to Prism now.
Can you downgrade the modpack tho or even mod?
This is why people Prism.
Prism is absolutely amazing.
I think Modrinth updated the way saves are pulled into the instance, Minecraft is probably trying to pull from a missing or incomplete save file that modrinth modified to work in their hotswap instance ecosystem. Likely only needed to wait for a bug-fix since it looks like this is a widespread issue.