![]() ![]() The modid must be between 2 and 64 characters, and must consist of lowercase letters, numbers, underscores ( _) and hyphens ( -). Use your IDE's find-and-replace function to quickly replace these values.All references to examplemod in the buildscript should be replaced with your modid.The lines above it are required for the Forge MDK to work correctly, and should not be modified without proper knowledge. These values should be replaced with your own mod's information.Īll edits should be done below the apply plugin: '' line. The MDK provides default values for the buildscript and mods.toml file. For Visual Studio Code: the task is genVSCodeRuns.For IntelliJ IDEA: the task is genIntellijRuns to run in the IDE directly, open the Gradle on the right, expand the project folder, double-click Tasks > fg_runs > genIntellijRuns.For Eclipse: the task is genEclipseRuns to run in the IDE directly, open the Gradle Tasks tab on the bottom panel, wait until the tasks have loaded then expand the folder, expand the fg_runs folder, then double-click genEclipseRuns.These tasks can be run on the command line using (Windows) gradlew gen***Runs or (*nix). Generate the run configurations for your IDE using the appropriate Gradle task.Wait for the setup process to complete and the Minecraft sources are decompiled.For IntelliJ IDEA: File > Open, select and open the folder, select the adle file, click OK, click Open as Project.For Eclipse: File > Import > Gradle > Existing Gradle Project, select the folder for the Project root directory, click Finish.Open your IDE of choice, and import the project as a Gradle project.Download the MDK from the official Minecraft Forge download site and extract the MDK into an empty folder.README.txt - Readme file with basic setup instructions.LICENSE.txt - File containing the licensing information for Forge and libraries.gradlew.bat - The Windows batch file for executing the Gradle wrapper.gradlew - The *nix shell file for executing the Gradle wrapper.gradle.properties - The Gradle properties file, for defining additional variables and options.CREDITS.txt - Forge's credits/ thank you file.changelog.txt - The Forge version changelog.adle - The Gradle buildscript, which defines the project and tasks. ![]() gitignore - Used by Git for specifying intentionally untracked/ignored files gitattributes - Used by Git for specifying attributes for files pack.mcmeta - File used by Minecraft to identify data and resource packs.mods.toml - The mods.toml file, where mods are declared.META-INF - The folder for metadata information files.resources - The resources for the main source set.java - The java sources for the main source set.gradle/wrapper/ - The folder containing the Gradle wrapper, Forge uses Gradle 6.9.This post was created as part of the README for my Panda's mod, but given my habit of not completing things I thought I'd share this part here in case it helped others. Perfect! At this point, let's calls this version 0.1.0 I'm going to to use MultiMC because it works all 3 major operating systems and makes creating Minecraft instances with the exact versions and mods you want so easy. Great, it works! At this time, before we commit we probably want to create a `.gitignore and add a couple of things to it.īefore I get too far into modding, I want to know that we can build our mod correctly as well. Let's do that though, so we have a starting place, and we can test this setup worksĬopied the src directory from our unzipped MDK directory. Forge comes with a sample mod, but the instructions don't tell us to copy that. The two commands we want for testing are:īefore we do that, we need a mod. gradlew setupDecompWorkspace is successful. Your instructions to get a JDK installed for likely differ, so I'll leave this part out. Ok, it looks like I don't have the java compiler (or JDK) installed on this computer. gradlew setupDecompWorkspace, since the working directory isn't in the path. Since this is Linux, the correct command is. The next step is to run gradlew setupDecompWorkspace. I'll leave out gradlew.bat since I'm developing on Linux. The docs say to only copy adle, gradlew.bat, gradlew, and the gradle directory. Ok, the MDK is downloaded, let's unzip it. That way, if things get broken or strange, I can use git to backup, and you and I get a nice history we can look back on. Oh, before we get too far along, I'm planning to track my progress with git commits and this readme. The files can be found at, and I think I want the MDK, but let's see if the docs tell us. Let's see how it goes!įirst, let's download Forge. In addition, I'd like to try to do this using VSCode, instead of the usual IDEs recommended for this. It's been a while since I created one, and I want to see if I still remember how things work. Hi! This is my documented journey to create a Minecraft Forge mod. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |