Dev Environment Setup

Setting up your own Forge Mod (or contributing to this one)

Set an environment variable under Win + Break > Advances System Settings > Environment Variables
- Add a JAVA_HOME variable in the top part of the window with the value of your jdk 8 folder path
- Add the jdk 8 \ bin folder path to the Path variable in the bottom part of the window
  - The jdk 8 folder path should look something like this: C:\Program Files\Java\jdk1.8.0_311

Log into github
Fork this repository
Clone the forked project to your local machine
- git command, Eclipse or some GUI (I for example used SourceTree)

Download and Extract the Forge 1.8.9 MDK
Copy the eclipse folder to the folder you cloned this project into
- Sidenote: If you want to start a fresh project you can replace step 6 by starting your own repository, clone that one in step 7 and copy not everything instead of just the eclipse folder in this step 9.
Open the command line (cmd)
Navigate to that folder you cloned this project into using cd <your folder path>
- Tip: you can change drives using e.g. C:, D:, E:, etc.
Setup the Eclipse development environment by typing gradlew setupDecompWorkspace eclipse
Start Eclipse
Select <your folder path>\Modding Workspace\eclipse as eclipse workspace
Switch to Dark Mode if you like: Window > Preferences > General > Appearance > Theme: Dark

Rightclick your Forge project in eclipse and go to Show in > Terminal
Build the projects jar file with gradlew build
- the jar file can be found under build \ libs

Create a new branch and switch to it
- git command, Eclipse or some GUI (e.g. SourceTree)

Now you are all set. Whats next? You can read a little bit about the structure of this Forge mod in the next wiki section, start changing things, test your changes by building the mod and putting the jar in the mod folder (sadly the multiplayer testing environment is broken due to the new Mirosoft login changes), commit and push to your new branch.
- Testing: As the testing environment is broken due to the new Mirosoft login changes, a System.out.println() here and there - which is normally not the way to do things - has become the next best thing you have to a debugger. To see those outputs during runtime once the mod has been build and installed, you have to switch on the output log in the minecraft launcher settings before you start Minecraft Forge 1.8.9.

Once you are you are happy with your result, you can commit and push everything to a new branch of your forked project

If your changes should go towards this example project and you want to create a pull request you can do that on the github page of your forked project
- github automatically offers you that option once you've made changes to your forked project