MCreator has literally broken

Started by BirdstarCat13 on Sat, 09/30/2017 - 23:38

Topic category: Help with MCreator's application

Last seen on 15:24, 10. Mar 2018
Joined Aug 2017
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
MCreator has literally broken
Sat, 09/30/2017 - 23:38

I'm trying to export my mod and I keep getting a "problematic mod" popup, but the list is empty. The application won't export if it thinks there's something wrong (which there clearly isn't if the problematic mod list is empty) so how do I fix this?

Last seen on 21:49, 7. Sep 2019
Joined Apr 2016
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
How are you trying to export
Sun, 10/01/2017 - 01:59

How are you trying to export it, are you exporting the mod to the test enviornment or exporting the mod as file?

Last seen on 07:34, 23. Jul 2019
Joined Apr 2014
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
I had the same error, try to
Sun, 10/01/2017 - 04:25

I had the same error, try to be logged in, and press recompile before export to zip

Last seen on 20:22, 21. Oct 2019
Joined Jun 2016
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
Try to press show gradle log
Sun, 10/01/2017 - 06:33

Try to press show gradle log and copy the log here

Last seen on 15:24, 10. Mar 2018
Joined Aug 2017
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
The gradle log is useless…
Sun, 11/12/2017 - 16:13

The gradle log is useless because it is only showing mods that I have had since the beginning which I never changed.

Last seen on 21:50, 16. May 2019
Joined Jun 2015
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
I use this method to test…
Sun, 11/12/2017 - 17:24

I use this method to test for errors, it may take a while but it is reliable to solving problems:

1.Save the whole mod as a MCR file on the desktop

2. Depending on how many mod elements you have. Delete each one or a group of mods(eg. groups of 5 mods).

3. Export mod

if it does not work, delete a few more mods and try again.

 

If it does work, import the MCR file back in and edit the mod which you found out was the problem.

If you did it in groups, import the MCR and delete one mod of the group and export mod, repeat if it does not work until you find the mod. Import the same MCR again and edit the mod element.

 

Last seen on 15:24, 10. Mar 2018
Joined Aug 2017
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
It turned out it was a…
Sat, 03/03/2018 - 15:24

It turned out it was a really random error in the code of one of the tools (had been there since the beginning but only now is it showing up as an error) but I changed the internal name of the tool and that fixed it.

Last seen on 19:11, 19. Feb 2019
Joined Mar 2018
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
This is error help me???? :…
Thu, 04/12/2018 - 15:19

This is error help me????

:\Pylo\MCreator178\forge\build\sources\main\java\mod\mcreator\modname.java:40: error: cannot find symbol
 mcreator_openSUSEElight mcreator_1 = new mcreator_openSUSEElight();
 ^
  symbol:   class mcreator_openSUSEElight
  location: class modname
C:\Pylo\MCreator178\forge\build\sources\main\java\mod\mcreator\modname.java:41: error: cannot find symbol
 mcreator_openSUSEElightOre mcreator_2 = new mcreator_openSUSEElightOre();
 ^
  symbol:   class mcreator_openSUSEElightOre
  location: class modname
2 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.