Repository files navigation

This project provides a Gradle project template that can compile Minecraft mods for multiple modloaders using a common project for the sources. This project does not require any third party libraries or dependencies. If you have any questions or want to discuss the project, please join ourDiscord.

This guide will show how to import the MultiLoader Template into IntelliJ IDEA. The setup process is roughly equivalent to setting up the modloaders independently and should be very familiar to anyone who has worked with their MDKs.

1. Clone or download this repository to your computer.
2. Configure the project by setting the properties in thegradle.properties file. You will also need to change therootProject.name property insettings.gradle, this should match the folder name of your project, or else IDEA may complain.
3. Open the template's root folder as a new project in IDEA. This is the folder that contains this README.md file and the gradlew executable.
4. If your default JVM/JDK is not Java 21 you will encounter an error when opening the project. This error is fixed by going toFile > Settings > Build, Execution, Deployment > Build Tools > Gradle > Gradle JVM and changing the value to a valid Java 21 JVM. You will also need to set the Project SDK to Java 21. This can be done by going toFile > Project Structure > Project SDK. Once both have been set open the Gradle tab in IDEA and click the refresh button to reload the project.
5. Open your Run/Debug Configurations. Under theApplication category there should now be options to run Fabric and NeoForge projects. Select one of the client options and try to run it.
6. Assuming you were able to run the game in step 5 your workspace should now be set up.

While it is possible to use this template in Eclipse it is not recommended. During the development of this template multiple critical bugs and quirks related to Eclipse were found at nearly every level of the required build tools. While we continue to work with these tools to report and resolve issues support for projects like these are not there yet. For now Eclipse is considered unsupported by this project. The development cycle for build tools is notoriously slow so there are no ETAs available.

When using this template the majority of your mod should be developed in thecommon project. Thecommon project is compiled against the vanilla game and is used to hold code that is shared between the different loader-specific versions of your mod. Thecommon project has no knowledge or access to ModLoader specific code, apis, or concepts. Code that requires something from a specific loader must be done through the project that is specific to that loader, such as thefabric orneoforge projects.

Loader specific projects such as thefabric andneoforge project are used to load thecommon project into the game. These projects also define code that is specific to that loader. Loader specific projects can access all the code in thecommon project. It is important to remember that thecommon project can not access code from loader specific projects.

While this template has support for many modloaders, new loaders may appear in the future, and existing loaders may become less relevant.

Removing loader specific projects is as easy as deleting the folder, and removing theinclude("projectname") line from thesettings.gradle file.For example if you wanted to remove support forforge you would follow the following steps:

1. Delete the subproject folder. For example, deleteMultiLoader-Template/forge.
2. Remove the project fromsettings.gradle. For example, removeinclude("forge").