This project provides a Gradle project template that can compile mods for both Forge and Fabric using a common sourceset, set up to use the Fabric API and its Forge port to minimize the amount of platform-dependant mod code. This allows you to use Fabric API on both platforms with full api compatibility. If you have any questions or want to discuss the project, feel free to create a post on GitHub Discussions.
This template is based on Jared's MultiLoader Template.
Mods created using this template require the Forgified Fabric API. Alternatively, mod authors may choose to ship select API modules as part of their mod jar, eliminating the dependency.
This guide will show how to import the MultiLoader Template into IntelliJ IDEA. The setup process is roughly equivalent to setting up Forge and Fabric independently and should be very familiar to anyone who has worked with their MDKs.
- Clone or download this repository to your computer.
- Configure the project by editing the
group,mod_name,mod_author, andmod_idproperties in thegradle.propertiesfile. You will also need to change therootProject.nameproperty insettings.gradle, this should match the folder name of your project, or else IDEA may complain. - Open the template's root folder as a new project in IDEA. This is the folder that contains this README file and the gradlew executable.
- If your default JVM/JDK is not Java 17 you will encounter an error when opening the project. This error is fixed by
going to
File > Settings > Build, Execution, Deployment > Build Tools > Gradle > Gradle JVMand changing the value to a valid Java 17 JVM. You will also need to set the Project SDK to Java 17. 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. - Open the Gradle tab in IDEA if it has not already been opened. Navigate
to
Your Project > Common > Tasks > vanilla gradle > decompile. Run this task to decompile Minecraft. - Open the Gradle tab in IDEA if it has not already been opened. Navigate
to
Your Project > Forge > Tasks > forgegradle runs > genIntellijRuns. Run this task to set up run configurations for Forge. - Open your Run/Debug Configurations. Under the Application category there should now be options to run Forge and Fabric projects. Select one of the client options and try to run it.
- Assuming you were able to run the game in step 7 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 is developed in the Common project. The Common 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. The Common project has access to the Fabric API and Fabric Loader classes, but does not have a loader set up. The Forge project has access to the ported versions of FAPI and fabric loader, which are fully api-compatible with upstream. However, their implementations differ, therefore you should avoid using any kind of internal code. Code that requires something from a specific loader (such as entrypoints) must be done through the project that is specific to that loader, such as the Forge or Fabric project.
Loader specific projects such as the Forge and Fabric project are used to load the Common project into the game. These projects also define code that is specific to that loader. Loader specific projects can access all of the code in the Common project. It is important to remember that the Common project can not access code from loader specific projects.
