Skip to content

Instantly share code, notes, and snippets.

@LexManos
Created December 8, 2018 20:06
Show Gist options
  • Save LexManos/76765455e6938892aed59544a9061321 to your computer and use it in GitHub Desktop.
Save LexManos/76765455e6938892aed59544a9061321 to your computer and use it in GitHub Desktop.
1.13 Announcement.
So about 1.13. As we have been stating since the public release of 1.13,
the Forge update is a time we are taking to re-write everything from the
ground up. Not just Forge, but the entire toolchain, launcher, installer,
and core of Forge is being rewritten. Every line of code is being inspected,
and re-validated. This whole process takes a while. To give you (the reader)
an idea of what has been done so far:
ForgeGradle has been rewritten to support modern gradle versions, with better tools
to be expandable and used for more than just setting up a Minecraft/Forge
dependency project. It's also much cleaner and organized this time around
so that future changes to the tools used by FG don't break FG.
The launcher is re-written to support modern Java versions, meaning you can
now run Forge 1.13+ on Java 9+. To have achieved this, we've had to rewrite
the core modding system to be safer and more open as a platform, as well as
getting rid of 8 years worth of patch updates to ModLoader's (yes, Risugami's
thing) legacy code that prevented us from making these better systems. Along
with speeding up loading times, better launch stages, and mod interaction order,
this new launcher is very clean and should clean up mod code for better
intercompatibility.
The installer has been rewritten, specifically in that a lot of steps that
were done every launch are now done at install time! Deobfuscating the
Minecraft jar, applying patches, etc. is now done at installation, so
the launch sequence is now THAT much faster. Likewise, since the dependencies
are generated at install time, external tools can now interact with both
Minecraft and Forge in more stable ways and should address common installer
issues.
Now about the progress and speed of work being done. There are many factors
that play into all that has been done so far that took longer than expected,
people that I've relied on took longer than expected or didn't get the work
done causing delays to continue work. Regardless of these delays, we should
be able to still achieve the goal of a New Years-ish release, but remember,
this entire project and all the work being done is provided to the community
on volunteer time, for free, with all volunteers having plenty of other real
world responsibilities. Help is always appreciated and has been asked for
many times. Forge is currently in a state where modders can start testing things,
providing feedback, and squashing bugs. Not all features/patches have been
ported yet and the ease of use is still being worked on, but things are always
progressing.
As for all of you guys hounding for ETA's instead of searching for yourself
and finding the progress: Remember, Forge and most of it's tools are open source,
on GitHub. You can see everything in progress as it's happening. You'll want to
pay attention to the 1.13-pre branch, and patches_old directory:
https://github.com/MinecraftForge/MinecraftForge/tree/1.13-pre/patches_old/minecraft/net/minecraft
All of those files still need to be ported.
So, there you go. A good old todo list. Now, go help, or shut up!
@jeromy-cannon
Copy link

I really appreciate all of the volunteers and the hours you are putting into this project! Great works gals/guys! Keep up the good work! My daughter and her friends (and myself...) love Forge!

@Akoot-zz
Copy link

Akoot-zz commented Feb 9, 2019

final patch hype

@VL4DST3R
Copy link

final patch hype

Been lurking this page and following the git repo progress for so long, seeing less and less stuff left in there. This is so exciting!

@ThePizzaMill
Copy link

To be completely honest, if people want to create or show me a guide to what's going on I'd be willing to help. I'd just need help getting started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment