Paint_Ninja

You allocated too much RAM to the game, so the OS, drivers and other things are fighting for resources. Close as many things as you can when playing, allocate 3GB or 3.5GB max, do not set a min. In task manager go to the startup tab and disable things you don’t need to start and have always running when you turn on your PC, but ignore the AMD ones in the list (they’re needed). Use Java 21 instead of Java 17. Consider removing Alex’s Mobs. Update your Radeon drivers (see the FAQ). Consider buying more physical RAM for your PC

Please share a link to your crash report on https://paste.ee, as explained in the FAQ

Forge version: 52.0.0 Minecraft version: 1.21.1 Downloads: Downloads page Note that as this is the start of a new version, it is recommended that you check the downloads page and use the latest version to receive any bug fixes, as the first ever build of Forge for any MC version is usually buggy. Intro: The first build for Forge 1.21.1 has been released! It is based on 51.0.33 for 1.21.0. We expect most existing 1.21.0 mods to work on 1.21.1 without needing any changes, as the only notable differences from Vanilla 1.21.0 -> 1.21.1 are a couple of new languages and a bugfix for an exploit that could be used to crash servers... as such, we strongly encourage all 1.21.0 players and mod developers to move to 1.21.1. From a mod dev perspective, BlockEntities now validate their block during construction - as long as that's fine you should be good to go. 1.21.0 has been moved to our minimal support tier, as explained in our tiered support policy - use 1.21.1 instead. If you find any issues, please let us know on the Discord. Sidenote: I'm sorry for not making these release posts for Forge betas of the past few MC versions. While I forgot to make some posts, we still released Forge builds for newer MC. When in doubt, check the sidebar on the files site. Same-day ports of Forge to new MC versions are common.

First, the solution: use the mdk and don't touch anything in it before checking that it works. You seemed to have changed something that broke it. You're also targeting 1.20.0 - *don't use this!* - it is a known buggy and abandoned version that people dropped in favour of 1.20.1 which came out shortly after. Next, a couple of things about your post: 1) you tagged it with "broken mod", which is commonly used to indicate that your issue has been solved and that the problem was that one of the mod's you installed was broken 2) please use code embeds. It's hard to interpret an arrow pointing to the issue in your error when the arrow doesn't line up properly

Please share a link to your crash report on https://paste.ee, as explained in the FAQ. Dumping it directly into the thread often triggers the anti-spam and makes it hard to read due to word wrapping

This is the Forge forums. We do not support NeoForge here - use Forge instead if you want help.

They were intended to be used on tutorial posts so that people could easily find tutorials based on their skill level, but instead the tags were abused for unrelated things that made the original intent useless... for example, people often posted crash reports with the "beginner" tag, so instead of finding tutorials for beginners, you got crash reports showing up in searches.

You can't mix mods for different MC versions.

Spark definitely has downloads available for Forge 1.20.1 on the CurseForge website. 47.0.35 is a very old beta version of Forge. You should be running 47.3.0

Please share your crash report or log, as explained in the FAQ

Forge version: 43.4.0 Minecraft version: 1.19.2 Downloads: Changelog: (Direct) Installer: (AdFocus) (Direct) MDK: (AdFocus) (Direct) Downloads page Intro: This fourth recommended build for 1.19.2 offers improved performance, a couple of bugfixes and a boatload of backports from newer MC versions. As a reminder, the release policy for recommended builds has changed - we now aim to release new recommended builds for fully supported MC versions more frequently - as long as there's a reasonable amount of changes since last recommended build. This week, we've released new RBs for 5 different MC versions, proving a renewed, serious commitment for long-term support. New: Improve mod loading error message for errors inside mod constructors, backport of #9751 (#9709) No longer shows a vague error if the error happens inside a constructor - Forge now tells you the actual error Optimise path filter in mod loading, backport of #9710 (#9712) 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") Improve mod description formatting in mods screen (#9771) Update to FG6 and Gradle 8, backport 1.20.1's MDK (#9754) Optimise ForgeConfigSpec and make Range public, backport of #9810 (#9827) Make common DisplayTest registration tasks easier, backport of #9822 (#9838) 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.18.2. Add support for running with Java 22 and 23 Make common config screen registration tasks easier, backport of #9884 (#9914) 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.18.2. Optimise capabilities, backport of #9886 (#9918) Fixed: Fix TagsProvider not honouring replace attribute (#9865) Fix NPE when acceptableValues in defineInList() does not allow nulls, fixes #9300, backport of #9903 (#9909)

Please share the full log or join our Discord server for help

Please share your Spark report. Instructions for troubleshooting lag and how to use Spark are in the FAQ

Try giving the game more ram in the launcher settings

The "essential" mod is broken. Try updating Forge or removing the mod