not sure if this crash is related to cor, lib or nei but it's urs
Jiraiyah opened this issue ยท 49 comments
Hi cb, when i move the forge above 1224 i get this :
I am still having this crash, and I am not a mod developer. Just a regular player making a private mod compilation. Here is the log: http://pastebin.com/qFTmNwbj
Is it fixed? if so, what do I need to do?
You need to disable the coremodsearch of ForgeGradle. This is basically the hotfix for it
I can't do that. I will repeat exactly what I said above: I AM NOT A MOD DEVELOPER. I do not understand how to do that, and I am assuming it may affect my modpack's playability.
Where are you crashing? This should only be an issue, if you are developing the mod in an IDE and try to run it indev. This should be no issue while running in a normal launcher.
The fix for this is to update to the latest versions of CCC, and NEI. CCL is autodownloaded by CCC.
Whether it a the Dev env, or the game, this should fix it.
For some reason I am still getting this crash.
I think I also had to use a fresh clone of my repo to solve this. Deleting only the gradle cache, the .gradle and all other non-repo files did not work (probably some hidden cache somewhere)
@thatsIch Is there any way you could recompile CodeChickenCore to fix this? Because most of this I do not understand at all.
@thatsIch @Chicken-Bones @AbrarSyed any help? A recompile anything? Please help asap.
no one will give a recompile, for mods it's up to developers, and i can confirm that if you download the latest builds of chicken bone's stuff (not the recommended ones) you should have no problem playing the game
the issue we are speaking about happens only in development environment, latest releases solved it for playing environment though
It is now fixed it turns out I had an old copy and a new copy of NEI in my modpack -_- Thanks!
I'm getting the same error with the 1.8 files, only mods i have are codechicken core, nei and my mod i'm developing. (this is in a dev environment) is their anyway of fixing. http://pastebin.com/JnTwP5pw
I am using the latest downloadable versions. I should add it works when just in my mods folder, but when I add to build path to use as libraries, I get the error.
Ok I have found the problem, I need to put the jars in in the jar folder not mods folder.
cb it's not related to other mods, i'm developing a mod myself, every time i tried to use a snap shot, i had the same error in the dev env too
but in case it is the problem, get ready for a huge list :
by the way, if you found him, speak with abrar sied, he found something wrong in nei and was wondering why nei works at all !
I got the same with latest FG + Forge + NEI + CCL + CCC
http://pastebin.com/c9x2na0y
Here are the potential problems:
- NEI is compiled for forge pre-1217, after which forge uses ASM5 and all coremods need to be updated. Or perhaps you are using an older version of forge while NEI is compiled for the newer version.
- NEI does something that requires specific names.. And this could cuases issues with people not using the same MCP snapshot as NEI. I think this error is unlikely.
for what its worth.. the following versions have worked 100% fine together in my testing.
minecraft { version = "1.7.10-10.13.2.1232" }
compile "codechicken:CodeChickenLib:1.7.10-1.1.1.105:dev"
compile "codechicken:CodeChickenCore:1.7.10-1.0.4.29:dev"
compile "codechicken:NotEnoughItems:1.7.10-1.0.3.66:dev"
compile "mcp.mobius.waila:Waila:1.5.6_dev1_1.7.10"
I'm studying for exams over the next few days, so I won't be able to look at this immediately
@AbrarSyed where did you get the hands on Waila 1.5.6, I am gonna try this in dev later on though
I didnt. someone else was having an issue I was debugging.. and thats the dependencies they had.
thatsIch i recommend adding waila dev4 to the dependency, that version had many things solved and it's 1.5.6 yet
1.5.6_dev4_1.7.10
@Jiraiyah just tried it, no luck. Were you able to get it running?
@Jiraiyah I got it working by making a fresh clone of the repository and working on that.
also my problem is that i depend on other stuff like buildcraft and malisis core and cofH, and separated my build to multiple files, not sure if i want to start on an empty and fresh repo
@Jiraiyah with the same as he said, only updated FMP cause of some minor bugs I think.
not working in my case, as i said, i think i will wait for cb to read the report and fix it himself
I am inclined to believe that this is a result of a forge and CCL version mismatch. Since forge updated ASM, coremods needed to be recompiled. I think you guys are using older versions of chicken stuff when you should be using newer ones.
ook, confirmed, using abrar's recommendation work only if we have --noCoreSearch in the program arguments. at least dev env works now, but normal launcher gaming won't work :/
Haven't been able to verify. My dev environment is now running the latest forge (10.13.2.1236) with all my mods and then some, no crash. Please try latest versions of NEI, CCC and CCL
cb, dev env with forge 1232. nei : 3.66, cclib : 1.105, ccc : 4.29, waila : 1.5.6_dev4
but as i said, if i don't put that arg, it will spit that error again
Added Waila to my dev, no crash. Perhaps someone can supply me with an environment, or obfuscated modpack?
cb you can try my project, although i'm reworking the factory ui stuff to hook it to malisis core but getting the minecraft instance up and running should work.
Compilation of your mod with gradle fails http://puu.sh/cTbjz/2b0592bc84.txt
yah they are are defined in the build.settings, and also you need cofHLib in libs folder, didn't know how to put it in the dependencies because can't find the artifact's correct path :/
https://github.com/Jiraiyah/JPistonMod/pull/1
Also steps I followed:
- Clone repo
- run gradlew runClient
- create world, open inventory
- no crash, close game
well sue me cb but --> http://prntscr.com/57y7c8
whithout arguments, this is my consol !
also, here is the log --> https://gist.github.com/Jiraiyah/f1ec139d888a8c2b60d8