Minecraft Forge 1.16.4-35.1.32, with an *ACTUALLY* secure version of Log4j.
Go to file
LexManos ca72710937 Initial 1.13.2 update. Major thing to note is that Dimensions have been completely revamped.
DimensionType is not unique per Dimension. See DimensionManager for more details.
Vanilla now has a chunk loading system, so Forge's will need to be deprecated/adapted.
2019-02-14 15:08:53 -08:00
.github Update github stale so issues can be Assigned 2019-01-11 18:32:16 -05:00
gradle/wrapper Zeroth pass on 1.13 2018-09-05 12:56:01 -07:00
jsons Fix more apache exclusions. 2018-08-22 11:56:35 -07:00
mdk Clean up the mod loading context objects. There is only one ThreadLocal now. 2019-02-13 22:13:59 -05:00
patches/minecraft/net/minecraft Initial 1.13.2 update. Major thing to note is that Dimensions have been completely revamped. 2019-02-14 15:08:53 -08:00
patches_old/minecraft/net/minecraft/client/renderer/block/model Port CommandEvent and custom entity selectors to 1.13 (#5411) 2019-02-08 17:41:50 -08:00
patches_old_unknown Finish off most old patches, fix issue for mounted entities. 2019-02-08 17:40:07 -08:00
src Initial 1.13.2 update. Major thing to note is that Dimensions have been completely revamped. 2019-02-14 15:08:53 -08:00
.gitattributes Fix JKS to be stored as binary 2019-02-11 13:51:13 -05:00
.gitignore Add my 'patches_old' directory, so that people can see my "progress". 2018-11-22 13:43:17 -08:00
.travis.yml Tell travis to skip 1.13 builds - they don't work there. 2019-01-19 23:35:20 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md 2016-06-22 17:06:56 -04:00
CREDITS.txt Fix new launcher jar packaging. 2018-12-31 16:48:23 -08:00
EnergySystems.md Create EnergySystems.md 2016-09-12 20:45:52 -04:00
Jenkinsfile Add a a test publish stage to jenkins file for PRs. Should allow for full publish cycle test without actually publishing. 2018-11-15 14:00:18 -08:00
LICENSE-header.txt Its 2019. Update licence headers to match. 2019-02-10 17:57:03 -05:00
LICENSE.txt Its 2019. Update licence headers to match. 2019-02-10 17:57:03 -05:00
NewFML.md Update NewFML.md 2018-09-05 10:54:20 -07:00
README.md Update README on github to fix the CLA section 2018-07-15 13:09:57 -07:00
SUPPORT.md Fix up logging and log4j configuration (#4802) 2018-03-17 18:41:16 -07:00
build.gradle Initial 1.13.2 update. Major thing to note is that Dimensions have been completely revamped. 2019-02-14 15:08:53 -08:00
gradlew Zeroth pass on 1.13 2018-09-05 12:56:01 -07:00
gradlew.bat Zeroth pass on 1.13 2018-09-05 12:56:01 -07:00
icon.ico Update assets to new Forge brand (#3464) 2016-11-30 14:56:31 -08:00
l4jManifest.xml Added FG2 buildscript + updated for Gradle 2.4 2015-06-29 21:56:35 -05:00
mods.toml Expose a couple of mods.toml properties properly. Half-implemented 2019-01-20 21:26:31 -05:00
settings.gradle Zeroth pass on 1.13 2018-09-05 12:56:01 -07:00
skipped_commits.md Add list of so-far skipped 1.12 commits 2019-01-11 18:32:17 -05:00

README.md

How to install Forge: For Players

Go to the Forge website and select the minecraft version you wish to get forge for from the list.

You can download the installer for the Recommended Build or the Latest build there. Latest builds may have newer features but may be more unstable as a result. The installer will attempt to install forge into your vanilla launcher environment, where you can then create a new profile using that version and play the game!

For support and questions, visit the Support Forum.

Here is a short video from Rorax showing how to install and setup Forge:

HOWTO Install Forge

How to install Forge: For Modders

See the "Getting Started" section in the Forge Documentation.

How to install Forge: For those wishing to work on Forge itself

If you wish to actually inspect Forge, submit PRs or otherwise work with Forge itself, you're in the right place!

See the guide to setting up a Forge workspace.

Pull requests

See the "Making Changes and Pull Requests" section in the Forge documentation.

Contributor License Agreement

We require all contributors to acknowledge the Forge Contributor License Agreement. Please ensure you have a valid email address associated with your github account to do this. If you have previously signed it, you should be OK.