My mod doesn't work on my minecraft client but works on my eclipse workspace

[Robatortas]

SOO I am just opening this thread to discuss this.

I made a mod, and I just added an item. I run the runClient.launch file on eclipse.
And the mod works perfectly! The "MODS" tab on the minecraft menu registers the mod with all the info that I inputted on the mod.toml file.

I then wanted to try the mod on my actual Minecraft Client with my account.
To rebuild my mod into a jar file that can be usable by minecrafy I just did:
gradlew build
On my project folder.

The jar gets built successfully in the build/libs dir.

I move the jar file to my mods folder on my Minecraft Client, run the game.
I can see the mod registered on the "MODS" tab on the Minecraft Menu, just like in the eclipse run.

But once I boot a world I look for the object I added in the mod and it is nowhere to be found.

I already tried a lot of different things like remaking the mod, rebuilding the gradle project and more things, none of them have worked.

If someone know about this, can you help me out?

Thanks!

[Luis_ST]

Please post a git repo of your Mod and the .jar which you created by gradlew build.

[Robatortas]

Sure thing!
The jar file is named "breaking-1.0.jar" and is located on the root.

https://github.com/Robatortas/BreakingBadMod

[warjort]

You have 3 classes and all of them have an @Mod annotation for the "breaking" mod.

e.g. https://github.com/Robatortas/BreakingBadMod/blob/db29fed424212e7fc238b629ae4b734b1bafe13c/src/main/java/io/github/robatortas/breaking/Registers.java#L17

You need to decide which of them is really your mod class.

 

This could be regarded as a bug.

It should really throw an error if it finds duplicates @Mod annotations for the same mod id instead of just picking one at "random".

[Robatortas]

On 9/9/2022 at 4:49 AM, warjort said:

You have 3 classes and all of them have an @Mod annotation for the "breaking" mod.

e.g. https://github.com/Robatortas/BreakingBadMod/blob/db29fed424212e7fc238b629ae4b734b1bafe13c/src/main/java/io/github/robatortas/breaking/Registers.java#L17

You need to decide which of them is really your mod class.

 

This could be regarded as a bug.

It should really throw an error if it finds duplicates @Mod annotations for the same mod id instead of just picking one at "random".

Thank you for your answer.
It worked.

And yes, this should throw an error in case this happens.

I appreciate the help!