1.20.2 Release

[AterAnimAvis]

NeoForge 20.2, for Minecraft 1.20.2, has been released.

---

Whilst the work is still in progress we’d like to keep you up to date which what’s to come. We have a lot of new technology part as part of this release, which we plan to elaborate further within a future blog post. All of the migration guides will be provided in the blog post as well. Howevever, here are a few things to expect as we release NeoForge.

Versioning

NeoForge releases will be using the following version format going forward: <minecraft_minor>.<minecraft_patch>.<number>(-beta). This means that all releases for Minecraft 1.20.2 will be formatted as 20.2.*. The -beta tag indicates that the release is unstable and will likely have breaking changes between 'number' versions.

NeoGradle: The Next Generation

Orion (@marchermans) has been working hard on improving the NeoGradle plugin to make all aspects of mod development easier. This means a complete overhaul in the build process, including massive simplifications of your build scripts.

MojMaps Everywhere (and a bit of Parchment too)

We are swapping out SRG names in favor of using Mojang's Mapping Set throughout the entire codebase to simplify our toolchain, along with a couple of other benefits. Additionally, development on NeoForge now uses Parchment for parameter and Javadocs.

Code changes

All packages names will be migrated from net.minecraftforge.* to net.neoforged.*. There are also numerous overhauls to systems, like capabilities and registries, that are targetted for the 20.2 release.

We would like to thank @Technici4n, @Shadows-of-Fire, @Matyrobbrt, @SizableShrimp, @Minecraftschurli and the others on the team for all of their hard work!

Keeping up to date

If you liked to kept more informed about our current progress make sure to check out our current Work List for 20.2 or to keep up to date and join in on discussion on future changes consider joining our Discord.

[Speiger]

Small warning regarding the use of "Parchment", forge/neoforge gradle + Parchment crashes/fails if you try to use local file jars.
While the use of maven is ofc a good idea, sometimes it is needed to use local jars, even temporary.

Not sure if this accounted for but it is a good thing to know.

Edit: it seems that issue is solved with 1.20.2 neoforge. Have to validate it but we will see ^^

[Minecraftschurli]

this will be a non issue in 20.2 since there will be no fg.deobf anymore messing it up. additionally you will be able to just add mods to your mods folder without needing to add them to your build.gradle if you only need them at runtime and not to compile against.

[Speiger]

@Minecraftschurli that doesn't solve the issue of requiring sourcecode access in development space.
So in other words you have to decompile mods manually and then drag/drop the src into your project is what you are saying?

[Technici4n]

if you need source access it is implementation <standard dependency without fg.deobf>, if you just need it at runtime to test something the mod jar goes into run/mods/

[Speiger]

@Technici4n does that decompile mods too? In other words i can hook any mod up even cursemaven ones or downloaded ones?

[Minecraftschurli]

mods don't get obfuscated anymore in 20.2 so it just works as a dependency