Update MDK Readme to describe new FG3 procedures. (#5553)
This commit is contained in:
parent
176e331fc4
commit
5fa02f53d9
1 changed files with 12 additions and 21 deletions
|
@ -19,35 +19,26 @@ http://mcforge.readthedocs.io/en/latest/gettingstarted/
|
||||||
|
|
||||||
Step 1: Open your command-line and browse to the folder where you extracted the zip file.
|
Step 1: Open your command-line and browse to the folder where you extracted the zip file.
|
||||||
|
|
||||||
Step 2: Once you have a command window up in the folder that the downloaded material was placed, type:
|
Step 2: You're left with a choice.
|
||||||
|
If you prefer to use Eclipse:
|
||||||
|
1. Run the following command: "gradlew genEclipseRuns" (./gradlew genEclipseRuns if you are on Mac/Linux)
|
||||||
|
2. Open Eclipse, Import > Existing Gradle Project > Select Folder
|
||||||
|
or run "gradlew eclipse" to generate the project.
|
||||||
|
(Current Issue)
|
||||||
|
4. Open Project > Run/Debug Settings > Edit runClient and runServer > Environment
|
||||||
|
5. Edit MOD_CLASSES to show [modid]%%[Path]; 2 times rather then the generated 4.
|
||||||
|
|
||||||
Windows: "gradlew setupDecompWorkspace"
|
If you prefer to use IntelliJ:
|
||||||
Linux/Mac OS: "./gradlew setupDecompWorkspace"
|
|
||||||
|
|
||||||
Step 3: After all that finished, you're left with a choice.
|
|
||||||
For eclipse, run "gradlew eclipse" (./gradlew eclipse if you are on Mac/Linux)
|
|
||||||
|
|
||||||
If you prefer to use IntelliJ, steps are a little different.
|
|
||||||
1. Open IDEA, and import project.
|
1. Open IDEA, and import project.
|
||||||
2. Select your build.gradle file and have it import.
|
2. Select your build.gradle file and have it import.
|
||||||
3. Once it's finished you must close IntelliJ and run the following command:
|
3. Run the following command: "gradlew genIntellijRuns" (./gradlew genIntellijRuns if you are on Mac/Linux)
|
||||||
|
4. Refresh the Gradle Project in IDEA if required.
|
||||||
"gradlew genIntellijRuns" (./gradlew genIntellijRuns if you are on Mac/Linux)
|
|
||||||
|
|
||||||
Step 4: The final step is to open Eclipse and switch your workspace to /eclipse/ (if you use IDEA, it should automatically start on your project)
|
|
||||||
|
|
||||||
If at any point you are missing libraries in your IDE, or you've run into problems you can run "gradlew --refresh-dependencies" to refresh the local cache. "gradlew clean" to reset everything {this does not affect your code} and then start the processs again.
|
If at any point you are missing libraries in your IDE, or you've run into problems you can run "gradlew --refresh-dependencies" to refresh the local cache. "gradlew clean" to reset everything {this does not affect your code} and then start the processs again.
|
||||||
|
|
||||||
Should it still not work,
|
Should it still not work,
|
||||||
Refer to #ForgeGradle on EsperNet for more information about the gradle environment.
|
Refer to #ForgeGradle on EsperNet for more information about the gradle environment.
|
||||||
|
or the Forge Project Discord discord.gg/UvedJ9m
|
||||||
Tip:
|
|
||||||
If you do not care about seeing Minecraft's source code you can replace "setupDecompWorkspace" with one of the following:
|
|
||||||
"setupDevWorkspace": Will patch, deobfuscate, and gather required assets to run minecraft, but will not generate human readable source code.
|
|
||||||
"setupCIWorkspace": Same as Dev but will not download any assets. This is useful in build servers as it is the fastest because it does the least work.
|
|
||||||
|
|
||||||
Tip:
|
|
||||||
When using Decomp workspace, the Minecraft source code is NOT added to your workspace in a editable way. Minecraft is treated like a normal Library. Sources are there for documentation and research purposes and usually can be accessed under the 'referenced libraries' section of your IDE.
|
|
||||||
|
|
||||||
Forge source installation
|
Forge source installation
|
||||||
=========================
|
=========================
|
||||||
|
|
Loading…
Reference in a new issue