MAJOR ISSUE! THIS MOD WILL CRASH MINECRAFT,I SPENT HOURS SORTING IT OUT DOWN TO ONE MOD AND IT WAS THIS ONE,Below is the error,Forge & Mod version,And how to reproduce
Vince079 opened this issue ยท 13 comments
Issue Info
- Forge Version: 32.0.98
- Mod Version: Latest (as of 8/3/2020) For Minecraft 1.16.1
- Can you reproduce this issue with relevant mods only?: yes/no Yes this was the only mod for me causing a crash in my 98 mod pack,I made sure to narrow it down just to ONE mod all by its self and it was this mod,How to reproduce. Step 1. Make sure you have the latest mod version AND The same forge version listed above (2) Put this mod in the mod folder (3) Crashes with the error... Crash report is below (Use the link)
For me no fixes yet,Just to remove the mod until it is fixed in some other way.
Crash Report: https://pastebin.com/vbg2w6gL
I did, It was in my mods folder....Then i deleted it,Isnt that installing or am i missing something??
Ok i will do that,Just to be clear installing a mod is downloading the jar and putting it the mods folder (yes i have java and forge set up) Is that right?
And i keep on getting numerous errors with almost all of my mods right now so i feel like something is going wrong
Ok i will do that,Just to be clear installing a mod is downloading the jar and putting it the mods folder (yes i have java and forge set up) Is that right?
Yes. And the last log clearly shows you need to update SimpleFarming
I took simple farming out and i still get errors for now other mods like cfm,quark and others. I will comment back once i install fruit trees (proly in the next 30 seconds) so be aware
With all the errors maybe i should just unistall and re--install minecraft,I keep having errors with 20 differnt mods and numerous game crashes (not just your mod) But your mod has the same message and result while the others always have differnt errors
https://paste.ubuntu.com/p/ZGhxRKqcJd/
Hopefully that helps! Lmk if you need anything else!
Also i have come across other issues with other mods that were recently stated in the dbug log**