Jump to content

Recommended Posts

Posted (edited)

Forge version: 40.3.0
Minecraft version: 1.18.2

Downloads:

Intro:

After two long years, we have our third recommended build for 1.18.2. This contains a slew of backports from newer versions of Forge which includes a lot of bugfixes, convenience features for modders, fixes for the JarJar system, and the CrashReportAnalyzer.

Sorry it took a while for a new recommended build of 1.18.2 to be released. The primary cause of this was our broken build system for the branch, which was recently fixed. As always, 1.18.2 remains covered by our tiered support system.

New:

  • Make mixins work with JarJar, backport of #8900 (#9506)
  • Add Forge "bosses" tag (#9513)
  • Add new helper without duplicate neighbour update call (#9235)
  • Improve logging for server connections (#9624)
  • Add a CrashReportAnalyser that tries to identify the mod that crashed the game
    • This feature scans your crash report as it is being generated and lists suspected mods that could be the cause of the crash, accounting for coremodding as well.
    • This makes it easier to find the culprit as it is often listed clearly in the crash report itself (e.g. "Suspected mods: buggymod")
  • Add support for displayTest in mods.toml, backport of #8656 (#9775)
  • Optimise ForgeConfigSpec and make Range public, backport of #9810 (#9828)
  • Make common DisplayTest registration tasks easier, backport of #9822 (#9839)
    • Before: 
      ModLoadingContext.get().registerExtensionPoint(IExtensionPoint.DisplayTest.class, () -> new IExtensionPoint.DisplayTest(() -> "ANY", (remote, isServer) -> true));
    • After: 
      ModLoadingContext.get().registerDisplayTest(IExtensionPoint.DisplayTest.IGNORE_ALL_VERSION);
    • The old method still works for backwards-compatibility. The new method has also been backported to 1.20.1, 1.19.4 and 1.19.2.
  • Improve mod description formatting in mods screen (#9840)
  • Add support for running with Java 22 and 23
  • Make common config screen registration tasks easier, backport of #9884 (#9920)
    • Before: 
      ModLoadingContext.get().registerExtensionPoint(ConfigScreenHandler.ConfigScreenFactory.class, () -> new ConfigScreenHandler.ConfigScreenFactory((mc, modsScreen) -> new MyConfigScreen(modsScreen));
    • After: 
      MinecraftForge.registerConfigScreen(modsScreen -> new MyConfigScreen(modsScreen));
    • The old method still works for backwards-compatibility. The new method has also been backported to 1.20.1, 1.19.4 and 1.19.2.
  • Bump CoreMods to 5.2.5, which adds new features such as ES6, better documentation, and long-awaited bug fixes (changelog, #10268)
  • Add some vanilla ResourceLocation methods (#10238)
  • The MDK now uses ForgeGradle 6 (#10285)

Fixed:

  • Fire TickEvent.WorldTickEvent on ClientLevel tick (#9304)
  • Fix Forge grindstone hooks allowing stacks of non-stackable items (#9458)
  • Fix incorrect SpecialSpawn fire location (#9481)
  • Fix PlayerInteractEvent.EntityInteractSpecific being called too late (#9494)
  • Fix inconsistent vaporization in BucketItem & FluidType (#9341)
  • Fix fluids not evaporating correctly. Fixes #9514
  • Fix NPE when acceptableValues in defineInList() does not allow nulls, fixes #9300, backport of #9903 (#9910)
  • Choose the default JarJar mod file type based on the parent Jar, fixes #8878, (#10026)
  • Add optional fix of use item duration, disabled by default and found in the server config (#10243)
  • Add client config to allow mipmap lowering to be disabled, fixes #10155, (#10249)
Edited by Jonathing
Added everything up until 40.2.33, added intro

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.