[Solved] Modding with IntelliJ | The asset problem

[DamnRelentless]

Hey guys,

 

after some weeks of getting experienced with Minecraft modding, I want to submit an issue here that occurs when you use the IDE IntelliJ for your mods.

I started with a very basic mod to implement my own items. Therefor, I had to learn about modding and first of all, gradle.

 

Since I am no Java newbie, I know how projects were structured and how to handle with IDEs. I've always used IntelliJ. Eclipse is good and has a ton of

features but I am still preferring IntelliJ. So here is the problem.

 

There are several articles and forum topics mentioning the setup of workspaces for your mods in IntelliJ. This is also one of the topics in the official

Minecraft Forge documentation. The steps to setup such a workspace aren't hard and were done very fast. But when I tried to test my mod, I ran into the

first issues.

 

The textures simply didn't load and I couldn't explain why this happens. I checked every file I wrote at least 10 times, I checked the textures, I

copied whole repositories from people that offered Minecraft modding tutorials, I even forked famous mods just to see how they handle their item

implementation and why my textures weren't working. Nothing worked. I always got the famous purple-black texture ingame and several errors about

missing textures and models. Since I realized that not even my localization file was being loaded, my assumption was that the assets folder wasn't loaded

at all and when I tested it with some log messages, my assumption was quickly confirmed.

 

Nothing what I did seemed to fix this issue and I was about to give up but after some hours of searching through all the internet pages I've found about

that issue or even about little keywords, I finally found a little post about IntelliJ messing around with the assets folder.

 

There is a simple solution. You can put the following code at the end of your build.gradle and everything will work perfectly fine:

sourceSets { main { output.resourcesDir = output.classesDir } }

No errors, no warnings, all textures instantly loaded, all models loaded, everything was localized.

 

So... why do I post this?

There is still something wrong. Why does not a single post mention this code? Why is it marked as deprecated? Why do no popular mods use this code

in their build.gradle?

 

Well, most mod creators use Eclipse, that's for sure and Eclipse doesn't have this issue. Lucky for them but what about modders that actually use

IntelliJ and don't have this issue?

 

I quickly realized that this code might help with the local testing environment but you can't build your mod with it. It will give you an error.

You can only build your mod when you remove it again but the local client instance doesn't work then. Interestingly when I build the mod, the assets

are copied just fine and everything works in the real game when you load the mod. However, you can't get working textures in the IDE when

you don't put this code in your build.gradle.

 

So what is the solution of this? How do you get IntelliJ to run without problems if you want to test AND build within the same project.

The only thing that comes to my mind would be a work around to load an artifact whenever you start your client which copies the assets

manually but that sounds too difficult for making a Minecraft mod. I am open for suggestions, thanks for reading.

 

Greetz,

Relentless

 

Solution for this problem:

 

Edited October 11, 2019 by DamnRelentless

[DaemonUmbra]

How did you get your run configs?

[DamnRelentless]

  On 10/10/2019 at 6:07 PM, DaemonUmbra said:

How did you get your run configs?

Expand  

What do you mean exactly?

Our current project looks like that: https://github.com/RLNT/IHMAM/tree/minecraftforge

[DaemonUmbra]

To me, so much of that build script looks like stuff that doesn't need to be done.

[DamnRelentless]

  On 10/10/2019 at 6:18 PM, DaemonUmbra said:

To me, so much of that build script looks like stuff that doesn't need to be done.

Expand  

You can ignore the build script. It also didn't work with the standard one that is generated when you initiate the project.

You should focus on the issue I described.

Edit: I would also be happy if you suggest improvements for the build.gradle.

Edited October 10, 2019 by DamnRelentless

[DaemonUmbra]

Is the repo you linked the mod you're having this issue with?

[DamnRelentless]

  On 10/10/2019 at 6:29 PM, DaemonUmbra said:

Is the repo you linked the mod you're having this issue with?

Expand  

Yes.

But I could also create one from scratch and the same thing would happen. I could also fork a popular mod and the same would happen. It's always like that in IntelliJ.

No offense but you should maybe read the text again. I already answered all these questions.

[DamnRelentless]

  On 10/10/2019 at 7:29 PM, diesieben07 said:

After finding out your example is not on master...

 

I agree with Daemon. Please provide a test case with a stock build.gradle and without all that... junk in there.

Expand  

I updated the repository to a state where we didn't use such a filled build.gradle. Now it's the one which is generated by default.

I should mention that this seems to occur with IntelliJ Ultimate only as far as I know.

It's the minecraftforge branch again.

Edited October 11, 2019 by DamnRelentless

[DamnRelentless]

  On 10/11/2019 at 7:37 AM, diesieben07 said:

Some recent version seems to have changed the default way IntelliJ compiles Gradle project. It used to be that it still used the IntelliJ build system, which puts resources and classes in one folder. Now "Delegate to gradle" seems to be the default, and gradle puts resources and classes in two separate folders.

Make sure to set IntelliJ to not delegate to Gradle (https://www.jetbrains.com/help/idea/work-with-gradle-projects.html#delegate_build_actions).

Expand  

This is the solution. It works flawlessly now. Thank you very much!

Interesting that this isn't written somewhere in any guide or the forge documentation.

[solitone]

  On 10/11/2019 at 1:12 PM, DamnRelentless said:

This is the solution. It works flawlessly now.

 

Expand  

Yes, it does work.

 

BTW, I need to set this parameter only for Forge 1.10.2, while for 1.14.4 I can build and run using Gradle.

 

I'm on IntellJ IDEA 2019.

[XLoL2007]

  On 10/11/2019 at 1:12 PM, DamnRelentless said:

This is the solution. It works flawlessly now. Thank you very much!

Interesting that this isn't written somewhere in any guide or the forge documentation.

Expand  

 

The cmd now works but when i try running the client in Intellij it doesn't run minecraft, help?

[XLoL2007]

  On 10/11/2019 at 1:12 PM, DamnRelentless said:

This is the solution. It works flawlessly now. Thank you very much!

Interesting that this isn't written somewhere in any guide or the forge documentation.

Expand  

The cmd now works but when i try running the runClient in Intellij it won't launch minecraft, help?

[foxcell]

thank you very much

it real help me to build my mod😄

now it work perfect

[Li_plum]

THANKS!!!

It solved my problem bothering me for a long time in version 1.12.2.

It's exactly as you said, I used the Eclipse to program formerly. 

Edited April 30, 2021 by Li_plum

[syumjoba]

What if I told you ... that still recources won't load?

I can't even get forge to read the mcmod.info file ... has JetBrains done yet another wild stunt?

 

[Mort_Games11]

It's a pity that it didn't work because I've been trying to solve the problem of loading the assets folder in Intellij Idea for 3 days

[infinityoofs]

Mort, did you ever find a solution