
LexForgeFix
Allow some mods for MinecraftForge 47.3.10+ run on NeoForge 47.1.x
About this Mod
MinecraftForge 1.20.1-47.3.10 introduced a new feature: allowing the mod entry class constructor to obtain an FMLJavaModLoadingContext as a parameter, whereas NeoForge 47.1.x at the same time did not support such a mod constructor.
This mod adds the classic parameterless constructor to these mods through bytecode modifications.
Fix these errors:
-- Head --
Thread: Render thread
Stacktrace:
at net.minecraftforge.fml.javafmlmod.FMLModContainer.constructMod(FMLModContainer.java:109) ~[language-java-47.2.2.jar%23416!/:47.2] {}
-- MOD somemod --
Details:
Mod File: <.minecraft>/mods/<somemod>-1.20.1-Forge.jar
Failure message: Some Mod (somemod) has failed to load correctly
java.lang.RuntimeException: Could not find mod constructor. Allowed optional argument classes: ModContainer, IEventBus, FMLModContainer
Mod Version: 1.1.4514
Mod Issue URL: https://example.com/
Exception message: java.lang.RuntimeException: Could not find mod constructor. Allowed optional argument classes: ModContainer, IEventBus, FMLModContainer
Stacktrace:
at net.minecraftforge.fml.javafmlmod.FMLModContainer.constructMod(FMLModContainer.java:109) ~[language-java-47.2.2.jar%23416!/:47.2] {}
at net.minecraftforge.fml.ModContainer.lambda$buildTransitionHandler$10(ModContainer.java:123) ~[core-47.2.2.jar%23415!/:47.2] {re:mixin}
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?] {}
at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1796) ~[?:?] {}
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387) ~[?:?] {}
at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312) ~[?:?] {}
at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843) ~[?:?] {re:mixin,re:computing_frames}
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808) ~[?:?] {re:mixin,re:computing_frames}
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188) ~[?:?] {re:mixin}
-- Head --
Thread: Render thread
Stacktrace:
at java.lang.Class.getConstructor0(Class.java:3761) ~[?:?] {}
-- MOD somemod --
Details:
Mod File: <.minecraft>/mods/<somemod>-1.20.1-Forge.jar
Failure message: Some Mod (somemod) has failed to load correctly
java.lang.NoSuchMethodException: com.example.SomeMod.<init>()
Mod Version: 0.1.0
Mod Issue URL: NOT PROVIDED
Exception message: java.lang.NoSuchMethodException: com.example.SomeMod.<init>()
Stacktrace:
at java.lang.Class.getConstructor0(Class.java:3761) ~[?:?] {}
at java.lang.Class.getDeclaredConstructor(Class.java:2930) ~[?:?] {}
at net.minecraftforge.fml.javafmlmod.FMLModContainer.constructMod(FMLModContainer.java:68) ~[javafmllanguage-1.20.1-47.1.3.jar%23181!/:?] {}
at net.minecraftforge.fml.ModContainer.lambda$buildTransitionHandler$10(ModContainer.java:123) ~[fmlcore-1.20.1-47.1.3.jar%23180!/:?] {}
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?] {}
at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1796) ~[?:?] {}
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387) ~[?:?] {}
at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312) ~[?:?] {}
at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843) ~[?:?] {}
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808) ~[?:?] {}
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188) ~[?:?] {}
Available Versions
How to Install LexForgeFix on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set neoforge Loader
In the panel under "Egg", select the neoforge loader and matching Minecraft version (1.20.1).
Install Mod
Open the mod browser in the dashboard and search for "LexForgeFix". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.20.1
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
LexForgeFix server crashes on startup – what to do?
Most common cause: wrong neoforge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.20.1). You can switch loaders with one click in the panel.
Is LexForgeFix compatible with neoforge?
LexForgeFix officially supports neoforge for Minecraft 1.20.1. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with LexForgeFix – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if LexForgeFix consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install LexForgeFix with just one click on your server.