Open Speiger opened 8 months ago
Which version of ForgeGradle is used in MinecraftForge for 1.8.9?
@anatawa12 ty for the answer.
1.8.9 uses FG2.1 classpath 'net.minecraftforge.gradle:ForgeGradle:2.1-SNAPSHOT'
1.10.2/1.11.2 use FG2.2 classpath 'net.minecraftforge.gradle:ForgeGradle:2.2-SNAPSHOT'
confirmed this issue seems to happen with all of 1.8 past forge 1502. aka 1.10.2 and 1.11.2 are simply not going to work either. this is a major issue as the next plugin only supports 1.12.2 when I tried to run it for forge 1.8.9 it said min version 1.12.2
A problem occurred evaluating root project '1.8.9'.
> This mapping 'stable_20' exists only for MC 1.8.8!
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 1s
the buildscript
buildscript {
repositories {
mavenCentral()
maven {
name = "forge"
url = "https://maven.minecraftforge.net/"
}
maven {
name = "sonatype"
url = "https://oss.sonatype.org/content/repositories/snapshots/"
}
}
dependencies {
classpath ('com.anatawa12.forge:ForgeGradle:1.2-1.1.+') {
changing = true
}
}
}
apply plugin: 'forge'
version = "1.0"
group= "com.yourname.modid" // http://maven.apache.org/guides/mini/guide-naming-conventions.html
archivesBaseName = "modid"
minecraft {
version = "1.8.9-11.15.1.2318-1.8.9"
runDir = "run"
// the mappings can be changed at any time, and must be in the following format.
// snapshot_YYYYMMDD snapshot are built nightly.
// stable_# stables are built at the discretion of the MCP team.
// Use non-default mappings at your own risk. they may not allways work.
// simply re-run your setup task after changing the mappings to update your workspace.
mappings = "stable_20"
// makeObfSourceJar = false // an Srg named sources jar is made by default. uncomment this to disable.
}
dependencies {
// you may put jars on which you depend on in ./libs
// or you may define them like so..
//compile "some.group:artifact:version:classifier"
//compile "some.group:artifact:version"
// real examples
//compile 'com.mod-buildcraft:buildcraft:6.0.8:dev' // adds buildcraft to the dev env
//compile 'com.googlecode.efficient-java-matrix-library:ejml:0.24' // adds ejml to the dev env
// the 'provided' configuration is for optional dependencies that exist at compile-time but might not at runtime.
//provided 'com.mod-buildcraft:buildcraft:6.0.8:dev'
// the deobf configurations: 'deobfCompile' and 'deobfProvided' are the same as the normal compile and provided,
// except that these dependencies get remapped to your current MCP mappings
//deobfCompile 'com.mod-buildcraft:buildcraft:6.0.8:dev'
//deobfProvided 'com.mod-buildcraft:buildcraft:6.0.8:dev'
// for more info...
// http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html
// http://www.gradle.org/docs/current/userguide/dependency_management.html
}
processResources
{
// this will ensure that this task is redone when the versions change.
inputs.property "version", project.version
inputs.property "mcversion", project.minecraft.version
// replace stuff in mcmod.info, nothing else
from(sourceSets.main.resources.srcDirs) {
include 'mcmod.info'
// replace version and mcversion
expand 'version':project.version, 'mcversion':project.minecraft.version
}
// copy everything else, thats not the mcmod.info
from(sourceSets.main.resources.srcDirs) {
exclude 'mcmod.info'
}
}
o/ I am right now trying to make automation work with this project. And 1.7.10 & 1.12.2 work fine, but i am convering the range of 1.7.10-1.8.9-1.10.2-1.11.2-1.12.2 And funnily enough 1.8.9 isn't supported but really old versions of 1.8 are?
I wouldn't ask you to add support for 1.10.2 & 1.11.2 but I kindly ask you could you make the 1.8 support the latest patch version of it?