When trying to setup a new env I keep on getting errors. At first I was using 1.7.10 because I wanted to create an addon for another mod but it was not working. I gave up and tried to create a new mod using 1.8.9 but when running gradlew setupDecompWorkspace I get this error:

 

[embed=425,349]C:\Users\mohha\Desktop\RedFusion>gradlew setupDecompWorkspace

This mapping 'stable_20' was designed for MC 1.8.8! Use at your own peril.

#################################################

        ForgeGradle 2.1-SNAPSHOT-da90449

  https://github.com/MinecraftForge/ForgeGradle

#################################################

              Powered by MCP unknown

            http://modcoderpack.com

        by: Searge, ProfMobius, Fesh0r,

        R4wk, ZeuX, IngisKahn, bspkrs

#################################################

:deobfCompileDummyTask

:deobfProvidedDummyTask

:getVersionJson

:extractUserdev UP-TO-DATE

:extractDependencyATs SKIPPED

:extractMcpData

 

FAILURE: Build failed with an exception.

 

* What went wrong:

Could not resolve all dependencies for configuration ':forgeGradleMcpData'.

> Could not resolve de.oceanlabs.mcp:mcp:1.8.9.

  Required by:

      com.yourname.modid:RedFusion:1.0

  > Could not resolve de.oceanlabs.mcp:mcp:1.8.9.

      > Failed to download SHA1 for resource 'http://files.minecraftforge.net/maven/de/oceanlabs/mcp/mcp/1.8.9/mcp-1.8.9.pom'.

        > For input string: "<!"

  > Could not resolve de.oceanlabs.mcp:mcp:1.8.9.

      > Could not get resource 'https://libraries.minecraft.net/de/oceanlabs/mcp/mcp/1.8.9/mcp-1.8.9.pom'.

        > Could not HEAD 'https://libraries.minecraft.net/de/oceanlabs/mcp/mcp/1.8.9/mcp-1.8.9.pom'. Received status code 403 from server: Forbidden

 

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

 

BUILD FAILED

 

Total time: 11.408 secs

[/embed]

 

 

Anyone?  :'(

I have recnetly stubbled accross this post when struggling with a similar issue and i recently found a fix that worked for me if you are still struggleing with this issue please respond with the current operating system you are using as my issue was one releated to windows 10 however i switched to windows 8.1 on a diffrent computer on the same network and it seemed to work fine