Started by
Homk
on
Topic category: Troubleshooting, bugs, and solutions
When I try to test my mod, every world is frozen. The player can still move and break blocks, but mobs are frozen, commands don't work, items don't drop and new chunks never generate. Nothing in my mod directly causes any of these things and this has happened to multiple of my mods, practically forcing me to quit working on them. Does anyone know a solution to this? I don't know if anyone has already asked this before
Is there anything in your mod that runs a lot of code?
it only has mod elements and procedures, no custom code
Do any of the procedures run lots of things every tick? Or anything like that? If not, I don't know.
It is also worth checking console for any error logs
The procedures that run every tick are mostly for living entities (to be specific, chickens and pigs only) that have a low chance to do something every tick. Also, I noticed the test worlds work normally for 1 or 2 minutes before everything freezes.
This was before i updated mcreator to 2023.4 but now, all mods fail to open due to a 'main mod file not compiling properly' even in mods with very few elements
On a test mod, this is in the console when trying to run minecraft:
Executing Gradle task: runClient
Build info: MCreator 2023.4.52316, forge-1.20.1, 64-bit, 7883 MB, Windows 11, JVM 17.0.9, JAVA_HOME: C:\Program Files\Pylo\MCreator\jdk, started on: 2024-01-23-19:18:49
> Task :compileJava FAILED
C:\Users\corey\MCreatorWorkspaces\testmod\src\main\java\net\mcreator\testmod\init\TestmodModTabs.java:26: error: package TestmodModItems does not exist tabData.accept(TestmodModItems.TEST_ITEM.get());
^
C:\Users\corey\MCreatorWorkspaces\testmod\src\main\java\net\mcreator\testmod\TestmodMod.java:52: error: package TestmodModItems does not exist TestmodModItems.REGISTRY.register(bus);
^
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.
> Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 2s
1 actionable task: 1 executed
BUILD FAILED
Task completed in 5 seconds
I believe this new issue isn't related to the 0 tps thing