Posted February 13, 201510 yr When running the runClient task in intelliJ, the build process seems to be run twice, or at least all the files are copied to the jar twice, and cause the client to crash on start. However running the standard build task will copy the files correctly... build.gradle; buildscript { repositories { mavenCentral() maven { name = "forge" url = "http://files.minecraftforge.net/maven" } maven { name = "sonatype" url = "https://oss.sonatype.org/content/repositories/snapshots/" } } dependencies { classpath 'net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT' } } apply plugin: 'forge' version = "" group= "com.paul.powinvert" archivesBaseName = "powinvert" minecraft { version = "1.7.10-10.13.2.1291" } //Optional: change the project structure sourceSets.main { java { srcDirs 'src' srcDirs 'api' } resources { srcDirs 'resources' } } 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' } } sourceSets { main { output.resourcesDir = output.classesDir } }
February 14, 201510 yr Author anyone else getting this? or anyone that isn't could you mention what forge package you're using please? I cant for my life figure out how this is actually happening so I can only think that the runClient task/s are broken in the current version. Standard build works perfectly fine so I'm currently stuck having to copy the jar to a test client and do without any debugging... edit; oh yea, and its completely independent on intelliJ (identical results via command-line) and I have wiped and re-added the gradle files and folders repeatedly...
February 21, 201510 yr sourceSets { main { output.resourcesDir = output.classesDir } } This section can actually cause your classes to be duplicated. While it does work around the FML bug that doesn't load resources in Idea, it causes side effects like this.
February 23, 201510 yr Author so then why does build work fine but the run-commands not? and commenting out that line just leaves everything else bar .class files being copied twice... edit; no, the build scripts don't verify files before handling them, deleting the entire build directory fixed that and all files are copied correctly...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.