#Crashing mod instance
1 messages · Page 1 of 1 (latest)
try reinstalling the pack
basically
don't update mods in already existing modpacks
this is my own custom one that ive been udating for months its just today it brok i cant re install it or i will lose my world
is there any other way to see the crash logs other than here cause if i can find that ill be able to see whats wrong
nvm i realised i was lookin in the wrong place here is the crash log
is somone able to tell me what the log says is wrong please im unsure how to read it
Looks like some mods have been updated. Have you updated your instance?
yeah i udated a few mods
mod updates can break stuff
Yup, the dtb mods are complaining that the version of the ftb library is too high for a start. You should never update mod packs as the kids have usually been picked at specific versions for compatibility. You want to restore the mod versions back to what they were
i may or may not have suffered from being a little stupid child and mass updating the mods in my own modpacks and wondering why it wouldn't work again
It's a regular thing. Either having the wrong forge version on servers, op people updating mods on the client hosted version. It happens, it's a learning experience:)
yes hi sorry made a message but didnt hit enter lol
it was ftb library which was the problem
i set it back to a previious version and the thing now works
update all and btw: there is an chance if you have "rubidium" mod and "embeddium" at the same time; try removing rubidium: embeddium is just way better