Building Troubleshooting
Here is a guide for troubleshooting if you're having problems developing or playing with the mod.
The most likely cause of this is that the workspace was not setup properly, or the build cache is on automatic garbage collection mode. You can try building the DecompWorkspace (that allows code modification with references to outside libraries), and seeing if that allows the mod to compile:
-
On Windows:
gradlew setupDecompWorkspace -
On macOS/Linux:
./gradlew setupDecompWorkspace
Then, try rebuilding:
-
On Windows:
gradlew build -g TEST_CACHE_BUILD -
On macOS/Linux:
./gradlew build -g TEST_CACHE_BUILD
When running the mod, we always recommend to keep your game's log open at all times during game operation. Many times issues occur extremely early, but you won't actually see them in.game until it crashes, or things start to break. Most issues are caught and get printed to the game's log. The new CEFClient-based Minecraft launcher disables the log by default (it also closes itself when clicking Play, which is also unhelpful when problems occur).
To enable the game log, find the launcher settings:
Enable the option Open output log when games start:
Keeping the launcher open is also extremely helpful at times, and we recommend you enable that too, although it's not neccessary.
Remember to scroll down to see the most recent output; the log doesn't automatically scroll.
Currently, you will spawn in a square grass island (or, Null Island). To get anywhere, you will have to teleport with the /tpll command.
You can check out the list of some cool locations to find places to teleport to.
The amount of memory that the JVM has to use was exceeded. You can edit the JVM's memory allocation by changing its arguments. If you're running a server, follow our instructions to change this.