Was just trying to setup the development environment for MC-Forge 1.10.2, but i think i might have messed something up. Was about to re-do the process but decided to ask here first if it's a known issue.

 

Version for forge: forge-1.10.2-12.18.2.2114-mdk

This is the problem:

 

why is it asking for divine ascendancy?

why is it asking for divine ascendancy?

 

It's the name of the folder. The mod name. I know, kinda ridiculous. Came up with it pretty randomly. But yeah, it has nothing to do with forge.

Re-run the setupDecompWorkspace and eclipse tasks.

 

That didn't work. Will re-download and try again tomorrow. Will post results. It is probably worth saying that i had a wrong JAVA_HOME variable when i ran gradle for the first time (the process did not finish) , i fixed that and ran it again. The process finished this time but it brought up this problem.

Not sure if this helps, but I've never gotten Forge to install properly following the information that Forge provides. This is what I have to do in gradle to get it to install right:

 

gradlew setupDevWorkspace

 

gradlew setupDecompWorkspace

 

gradlew eclipse

Okay so, i deleted the old files and re-did the process. Process ran fine and there are no errors on eclipse except for this:

 

 

What does that mean exactly? I have the latest version of JRE and the latest version of JDK installed. Where is the build path determined?

 

Seems like everything is working like it should though. I can run both client and server, and the "example-mod" is there.

Oh I remember something like this. YOu need to manually switch over to newer JDK otherwise it wants to use 1.6 due to Forge compatiblity?? So  build paths are in Project Properties java build path. You might have 1.6 added there. Add JRE 1.8 instead. I remember first time I made my project the build path had 1.6  so I had to add it manually. But funny enough second and third time I decomp workspace it did it automatically.