Setup workspace for 1.13 forge

[Valoeghese]

Hello,

 

ForgeGradle appears to have been rewritten for the 1.13 versions (out in development stage), and commands like gradlew setupDecompWorkspace no longer work.

I am having trouble setting this up with eclipse. Any help would be appreciated.

 

Thanks.

[RgSW]

How did you get an in-development mdk (link)? Maybe I can find a solution for you this way...

Edited December 31, 2018 by RgSW
More clear now

[Kenneth4848]

Ok I did the thing with command prompt how do I open it in eclipse please?

Edited February 15, 2019 by Kenneth4848

[MegaCrafter10]

  On 2/15/2019 at 10:08 PM, Kenneth4848 said:

Ok I did the thing with command prompt how do I open it in eclipse please?

Expand  

I'm waiting for the same answer

[DaemonUmbra]

I believe you can import it from the build.gradle and let Eclipse's Gradle integration handle it.

[MegaCrafter10]

  On 2/16/2019 at 3:15 AM, DaemonUmbra said:

I believe you can import it from the build.gradle and let Eclipse's Gradle integration handle it.

Expand  

build.gradle is not visible as an option when importing. I can import the source folder for the example mod but how do I link it to all the references?

Or is there another way this is done?

[DaemonUmbra]

Gradle import is under "Show other specialized import wizards" (I'm an intellij user so I need to keep looking back at Eclipse).

[BatHeart]

I asked the same question in this thread. I got no replies, but I managed to resolve it myself as I describe in the second post

 

[MegaCrafter10]

  On 2/16/2019 at 9:21 AM, BatHeart said:

I asked the same question in this thread. I got no replies, but I managed to resolve it myself as I describe in the second post

Finally a good and simple answer, Thanks. I can now start modding again.

Expand  

 

 

[MegaCrafter10]

And another problem... I just exported the example mod to see if it works but Minecraft says:" Mod examplemod requires minecraft 1.13, currently minecraft is 1.13.2"

So, I went back to eclipse and changed the version range in the "mods.tolm" from 1.13 to 1.13.2 but now when I start Minecraft, I get a different error saying "Example mod (examplemod) encountered an error during the common_setup event phase DIRT"

 

How can I use 1.13 when the only available Forge version is 1.13.2?

Is there a version setting for this?

Thanks for the help

[BatHeart]

I'm puzzled at a similar point, MegaCrafter10. I don't get the error, but if I try to run Minecraft from within eclipse with just the examplemod - in the src and the toml - it doesn't get loaded. Minecraft starts fine, but there is no sign of examplemod in the list of loaded mods.

My first thought was that 1.13.2 Forge is version 25, so the toml needs to say 25 rather than 24. But I tried that and still got the same result.

That's as far as I've reached right now with 1.13.2.

By the way, you can get versions of 1.13 Forge from here: http://files.minecraftforge.net/maven/net/minecraftforge/test/forge/index_1.13.html

However, I've reached the same point with 1.13 too.

It seems modding in the 1.13.x versions is a matter of solving problem after problem yourself. I wish there was some clear guidance notes somewhere.

 

P.S. I just got the latest mdk (forge-1.13.2-25.0.13-mdk) and I see the version in the toml has been updated from 24 to 25. Still doesn't recognise their own mod, though.

Edited February 16, 2019 by BatHeart
Info from latest Forge mdk

[MegaCrafter10]

  On 2/16/2019 at 1:23 PM, BatHeart said:

I'm puzzled at a similar point, MegaCrafter10. I don't get the error, but if I try to run Minecraft from within eclipse with just the examplemod - in the src and the toml - it doesn't get loaded. Minecraft starts fine, but there is no sign of examplemod in the list of loaded mods.

My first thought was that 1.13.2 Forge is version 25, so the toml needs to say 25 rather than 24. But I tried that and still got the same result.

That's as far as I've reached right now with 1.13.2.

By the way, you can get versions of 1.13 Forge from here: http://files.minecraftforge.net/maven/net/minecraftforge/test/forge/index_1.13.html

However, I've reached the same point with 1.13 too.

It seems modding in the 1.13.x versions is a matter of solving problem after problem yourself. I wish there was some clear guidance notes somewhere.

 

P.S. I just got the latest mdk (forge-1.13.2-25.0.13-mdk) and I see the version in the toml has been updated from 24 to 25. Still doesn't recognise their own mod, though.

Expand  

I can't even start Minecraft from eclipse. But that's not a problem since I can just move the mod into the mods folder and launch Minecraft myself.

I just need someone to solve the error I'm getting about the version.

If Forge 1.12 doesn't work and now 1.13 is busted as well... how is anyone supposed to make mods anyway?

[J Bruni]

I've just completed my first Eclipse workspace setup for Minecraft mod development using Forge for Minecraft 1.13.2

 

I can successfully launch Minecraft 1.13.2 from inside Eclipse, with the mod properly loaded by Forge.

 

You need to import the launch configurations in Eclipse. The launch configuration files, "client.launch" and "server.launch" can be found in the project root folder, after you ran "gradlew eclipse". To import then, go to File > Import... and then expand Run/Debug  select Launch Configurations, and click Next. Browse and select your mod project root folder. Check the project checkbox in the left panel, and select the launch configurations in the right panel. Click Finish to import.

 

Screenshots here: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0446g/CJADBBIA.html

 

The imported launch configurations are available for usage now... go to Run > Run Configurations... and select the client configuration to launch Minecraft with your mod loaded.

Edited February 17, 2019 by J Bruni

[MegaCrafter10]

  On 2/17/2019 at 4:47 PM, J Bruni said:

I've just completed my first Eclipse workspace setup for Minecraft mod development using Forge for Minecraft 1.13.2

 

I can successfully launch Minecraft 1.13.2 from inside Eclipse, with the mod properly loaded by Forge.

 

You need to import the launch configurations in Eclipse. The launch configuration files, "client.launch" and "server.launch" can be found in the project root folder, after you ran "gradlew eclipse". To import then, go to File > Import... and then expand Run/Debug  select Launch Configurations, and click Next. Browse and select your mod project root folder. Check the project checkbox in the left panel, and select the launch configurations in the right panel. Click Finish to import.

 

Screenshots here: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0446g/CJADBBIA.html

 

The imported launch configurations are available for usage now... go to Run > Run Configurations... and select the client configuration to launch Minecraft with your mod loaded.

Expand  

Thanks, I can now launch the game from eclipse and I'm not getting any version errors anymore.

 

EDIT: one more thing, the game says there is 1 mod loaded but "examplemod" is not listed. Is this normal?

Edited February 17, 2019 by MegaCrafter10
extra question

[J Bruni]

What worked for me yesterday is already obsolete today.

 

While we discuss here, the developers have been fixing and changing ForgeGradle and the Eclipse launch configurations code.

 

If yesterday we had "client.launch" and "server.launch" files at project root... today we do not have them anymore!

 

New related commits have been merged into Forge around 5 hours ago:

• https://github.com/MinecraftForge/ForgeGradle/pull/546
• https://github.com/MinecraftForge/MinecraftForge/pull/5482
• https://github.com/MinecraftForge/MinecraftForge/commit/2e2c57dbd104b24a2bfe15194231cf9f2ca904d9
• https://github.com/MinecraftForge/MinecraftForge/commit/1a833a9267cb030dd1592d65b05337b6af968adb

 

I will just wait a bit so new version(s) with these changes are released.

[J Bruni]

Ok... I have researched a bit more... Since Minecraft Forge 1.13.2-25.0.28 (released 5 hours ago), after running gradlew eclipse, we shall run gradlew genEclipseRuns

 

This new gradlew task will create "runClient.launch" and "runServer.launch" configurations. But it is not necessary to import them. The task already does this automatically, including them into the Eclipse project.

 

I've just tried myself, and it works as it should: the mod is compiled/built, Minecraft runs, and the mod is loaded.

 

I can't guarantee that it will be the same tomorrow (we had 8 Forge releases this Monday!)

[MegaCrafter10]

  On 2/19/2019 at 12:52 AM, J Bruni said:

Ok... I have researched a bit more... Since Minecraft Forge 1.13.2-25.0.28 (released 5 hours ago), after running gradlew eclipse, we shall run gradlew genEclipseRuns

 

This new gradlew task will create "runClient.launch" and "runServer.launch" configurations. But it is not necessary to import them. The task already does this automatically, including them into the Eclipse project.

 

I've just tried myself, and it works as it should: the mod is compiled/built, Minecraft runs, and the mod is loaded.

 

I can't guarantee that it will be the same tomorrow (we had 8 Forge releases this Monday!)

Expand  

Thanks for the info

[BatHeart]

... and now this is broken again ...

I've tried with builds 25.0.47 and 25.0.48 and it appears to be the same - you have to run gradlew genEclipseRuns before the Run Configurations appear. However, now the Client launch fails - even if you try to run it with just the examplemod. The problem is a NullPointerException at net.minecraftforge.fml.ModLoader.buildMods(ModLoader.java:161)

 

We can go back to using gradlew runClient - but that's not ideal especially if you want to debug.