(SOLVED) Launching modded Minecraft from within Eclipse

[MineModder2000]

I have forge 1.14.4 and I have successfully set up my work space / project using gradle. I am able to use ./gradlew build to build mods which are placed in the libs folder, so everything definitely works. However I am not currently able to run the code from within Eclipse. I get "Error : Could not find or load main class GradleStart", from the console...

 

Main Class : GradleStart

Arguments –Guy=<Guy> –qwerty!=<qwerty!>

 

 

Edited September 25, 2019 by MineModder2000

[MineModder2000]

Bump

[DaemonUmbra]

Did you run genEclipseRuns?

Actually that may have been moved into the eclipse task

[MineModder2000]

  On 9/21/2019 at 12:17 AM, DaemonUmbra said:

Did you run genEclipseRuns?

Actually that may have been moved into the eclipse task

Expand  

Yeah i've been searching for a solution all over, can't figure it out...

[DaemonUmbra]

I should also mention that Eclipse doesn't listen for filesystem changes, you have to refresh the project(F5 or right click in the file hierarchy) for it to detect the runconfigs that ForgeGradle generates

[MineModder2000]

  On 9/24/2019 at 2:36 AM, DaemonUmbra said:

I should also mention that Eclipse doesn't listen for filesystem changes, you have to refresh the project(F5 or right click in the file hierarchy) for it to detect the runconfigs that ForgeGradle generates

Expand  

I am familiar with this. The genEclipseRuns does work, but it only builds the data and server runs, no client run is generated... When I try the manual approach using "GradleStart" as the main class and with the username and password as parameters it just doesn't launch. 

[DaemonUmbra]

GradleStart no longer exists and you need to configure more than that to get Forge to load mods in dev.

Please provide your build.gradle

[MineModder2000]

  On 9/24/2019 at 11:13 PM, DaemonUmbra said:

GradleStart no longer exists and you need to configure more than that to get Forge to load mods in dev.

Please provide your build.gradle

Expand  

I see. What do you mean by provide my build.gradle, sorry. 

[DaemonUmbra]

I mean please provide the build.gradle that controls the mod's configuration and build process

[MineModder2000]

  On 9/25/2019 at 3:28 AM, DaemonUmbra said:

I mean please provide the build.gradle that controls the mod's configuration and build process

Expand  

Oh right, I forgot about this guy.

 

  Reveal hidden contents

buildscript {
    repositories {
        maven { url = 'https://files.minecraftforge.net/maven' }
        jcenter()
        mavenCentral()
    }
    dependencies {
        classpath group: 'net.minecraftforge.gradle', name: 'ForgeGradle', version: '3.+', changing: true
    }
}
apply plugin: 'net.minecraftforge.gradle'
// Only edit below this line, the above code adds and enables the necessary things for Forge to be setup.
apply plugin: 'eclipse'
apply plugin: 'maven-publish'

version = '1.0'
group = 'com.yourname.modid' // http://maven.apache.org/guides/mini/guide-naming-conventions.html
archivesBaseName = 'modid'

sourceCompatibility = targetCompatibility = compileJava.sourceCompatibility = compileJava.targetCompatibility = '1.8' // Need this here so eclipse task generates correctly.

minecraft {
    // 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 always work.
    // Simply re-run your setup task after changing the mappings to update your workspace.
    mappings channel: 'snapshot', version: '20190719-1.14.3'
    // makeObfSourceJar = false // an Srg named sources jar is made by default. uncomment this to disable.
    
    // accessTransformer = file('src/main/resources/META-INF/accesstransformer.cfg')

    // Default run configurations.
    // These can be tweaked, removed, or duplicated as needed.
    runs {
        client {
            workingDirectory project.file('run')

            // Recommended logging data for a userdev environment
            property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP'

            // Recommended logging level for the console
            property 'forge.logging.console.level', 'debug'

            mods {
                examplemod {
                    source sourceSets.main
                }
            }
        }

        server {
            workingDirectory project.file('run')

            // Recommended logging data for a userdev environment
            property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP'

            // Recommended logging level for the console
            property 'forge.logging.console.level', 'debug'

            mods {
                examplemod {
                    source sourceSets.main
                }
            }
        }

        data {
            workingDirectory project.file('run')

            // Recommended logging data for a userdev environment
            property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP'

            // Recommended logging level for the console
            property 'forge.logging.console.level', 'debug'

            args '--mod', 'examplemod', '--all', '--output', file('src/generated/resources/')

            mods {
                examplemod {
                    source sourceSets.main
                }
            }
        }
    }
}

dependencies {
    // Specify the version of Minecraft to use, If this is any group other then 'net.minecraft' it is assumed
    // that the dep is a ForgeGradle 'patcher' dependency. And it's patches will be applied.
    // The userdev artifact is a special name and will get all sorts of transformations applied to it.
    minecraft 'net.minecraftforge:forge:1.14.4-28.1.0'

    // 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'

    // These dependencies get remapped to your current MCP mappings
    // deobf '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

}

// Example for how to get properties into the manifest for reading by the runtime..
jar {
    manifest {
        attributes([
            "Specification-Title": "examplemod",
            "Specification-Vendor": "examplemodsareus",
            "Specification-Version": "1", // We are version 1 of ourselves
            "Implementation-Title": project.name,
            "Implementation-Version": "${version}",
            "Implementation-Vendor" :"examplemodsareus",
            "Implementation-Timestamp": new Date().format("yyyy-MM-dd'T'HH:mm:ssZ")
        ])
    }
}

// Example configuration to allow publishing using the maven-publish task
// we define a custom artifact that is sourced from the reobfJar output task
// and then declare that to be published
// Note you'll need to add a repository here
def reobfFile = file("$buildDir/reobfJar/output.jar")
def reobfArtifact = artifacts.add('default', reobfFile) {
    type 'jar'
    builtBy 'reobfJar'
}
publishing {
    publications {
        mavenJava(MavenPublication) {
            artifact reobfArtifact
        }
    }
    repositories {
        maven {
            url "file:///${project.projectDir}/mcmodsrepo"
        }
    }
}

 

[DaemonUmbra]

I see no reason for that to not generate a client run config.

Run eclipse and genEclipseRuns, then click into Package Explorer and press F5

[MineModder2000]

  On 9/25/2019 at 3:57 AM, DaemonUmbra said:

I see no reason for that to not generate a client run config.

Run eclipse and genEclipseRuns, then click into Package Explorer and press F5

Expand  

This I have done twice already...

[DaemonUmbra]

Show a screenshot of your package explorer?

[MineModder2000]

  On 9/25/2019 at 4:10 AM, DaemonUmbra said:

Show a screenshot of your package explorer?

Expand  

 

https://imgur.com/ofAwMms

Edited September 25, 2019 by MineModder2000

[DaemonUmbra]

You have all that with a default build.gradle?

Are there no errors when you run gradlew eclipse genEclipseRuns?

[A-Game]

I have had this exact problem when first trying to load Minecraft through Eclipse. I found I had to restart by re-downloading forge (MDK version), but save any mod code through text files in a folder as a recommendation. Run the gradle cmd and exit it when finished. Then use "cd " followed by the directory to your forge folder, and continuing in the order of:

"gradlew clean"

"gradlew genEclipseRuns"

"gradlew Eclipse"

Run Minecraft in Eclipse before continuing to re-add any code back to ensure it isn't any code that is preventing Minecraft from running. I found sometimes going outside the command order could result in failures such as the one you are currently experiencing. Yes it was a pain cause I on the other hand didn't save all my code in text files... This is for the latest recommended version of forge in 1.14.4, I am unsure if this is the same in prior versions of the game. 

[MineModder2000]

  On 9/25/2019 at 10:57 AM, A-Game said:

I have had this exact problem when first trying to load Minecraft through Eclipse. I found I had to restart by re-downloading forge (MDK version), but save any mod code through text files in a folder as a recommendation. Run the gradle cmd and exit it when finished. Then use "cd " followed by the directory to your forge folder, and continuing in the order of:

"gradlew clean"

"gradlew genEclipseRuns"

"gradlew Eclipse"

Run Minecraft in Eclipse before continuing to re-add any code back to ensure it isn't any code that is preventing Minecraft from running. I found sometimes going outside the command order could result in failures such as the one you are currently experiencing. Yes it was a pain cause I on the other hand didn't save all my code in text files... This is for the latest recommended version of forge in 1.14.4, I am unsure if this is the same in prior versions of the game. 

Expand  

I love you, this worked. I've tried the clean command before, but not all 3 of these in this order. I already had updated my forge so I didn't redo that. But now I can finally debug and test quickly instead of having to use the launcher ?