Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

It seems forge is broken when it comes to detecting what mod versions are installed

Ninjaguy169

By Ninjaguy169
in Support & Bug Reports

 Share

Recommended Posts

Ninjaguy169 Tree Puncher

Ninjaguy169

Posted
Posted

To clarify further, forge for 1.16.5 (versions 36.2.0 - 36.2.4) has been having problems with mods. You see, I wanted to play an old kitchensink modpack that I made almost a year ago, and it worked perfectly fine. I grabbed the mod files exactly where I left them off and pasted them into the mods folder. However, I got this error when I loaded forge up:

https://imgur.com/mIPPnow

Now to clarify, not only has this worked previously with me back when I played this modpack long ago, I have also attempted to install specified versions of mods mentioned on the error screen, but to no avail.

 

My theory here was/is that forge is somehow corrupted/broken. To test that theory out, I grabbed my old server files (containing all mods used when firing up this installation of forge, including client side ones since back then I wasn't exactly fluent with minecraft modding) and launched the server successfully. It should be noted that no server-side mods (except performant) were included in my forge mods directory. 

 

In conclusion, I'm asking for any possible solutions to forge simply refusing to detect that the installed mod versions are compatible with each other. Yes, some 1.16.3 mods (as mentioned in the above screenshot) do work on 1.16.5, according to how I launched it myself. Finally, this wouldn't be a proper forge forums post without including my crash report and latest.log file.

 

(It's worth noting that since it crashes so early during the pre-loading phase, no other mods show up in the crash report file)

 

Apologies for any obvious mistakes I may have not noticed while posting this here in advance, if there were any.

 

https://gist.github.com/RaveTr/6a30411b367958c30e8f37dbc9b4d25a

 

https://gist.github.com/RaveTr/56308af48ecdf60f3f32106a3a138170

  • 4 weeks later...
Ninjaguy169 Tree Puncher

Ninjaguy169

Posted
  • Author
Posted (edited)

Apologies for the late reply, but thanks. Turned out the issue was with immersive portals not being up to date with the forge version I was using at the time (mixin changes to be exact). Hope this helps anyone reading this running into this problem, even if its by the slightest

Edited by Ninjaguy169

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

Announcements



  • Recently Browsing

    • No registered users viewing this page.

  • Posts

    • bkbenji
      OpenAL.dll issue (causing crash)

      By bkbenji · Posted

      Is there a fix for this issue? I have tried reinstalling OpenAL.dll, switching Java versions, and even muting my game when it launched, but all of these attempts have resulted in my game crashing nonetheless. I have been dealing with this issue for approximately a week straight. I have not changed any sound settings, so I am very confused. Full Code: https://gnomebot.dev/paste/mclogs/beEBzpm "4/16/2025 12:16:30 AM 1000 Error Faulting application name: javaw.exe, version: **.**.**.**, time stamp: 23 0xd75c3041 24 Faulting module name: OpenAL.dll, version: **.**.**.**, time stamp: 0x647635a125 Exception code: 0xc0000409 26 Fault offset: 0x00000000000a2b05 27 Faulting process id: 0x10A0 28 Faulting application start time: 0x1DBAE81D04A6F2F 29 Faulting application path: C:\Users\********\curseforge\minecraft\Install\java30 \java-runtime-delta\bin\javaw.exe 31 Faulting module path: C:\Users\********\curseforge\minecraft\Install\natives\n32 eoforge-21.1.148\OpenAL.dll 33 Report Id: 28552180-f359-40cc-adeb-08dada7e99d8 34 Faulting package full name: 35 Faulting package-relative application ID:" Any sort of insight would be greatly appreciated, it's giving me a headache.
    • Calcifer
      I can't get this modpack running.

      By Calcifer · Posted

      I'm new to this, if that wasn't obvious. My friend and I are trying to make a modpack for 1.19.2. I've made a modpack previously with 0 issues before and many of the same mods. However, I can't seem to find the issue when trying to load up his new modpack.   Any help would be greatly appreciated.
    • SPROUTBAKES
      blocks addon

      By SPROUTBAKES · Posted

      BLOCK
    • PhysicalJP
      Minecraft modpack crashing on create world.

      By PhysicalJP · Posted

      Im trying to make a customized modpack for just myself using the atm9 modpack as a base. It was working till recently, when curseforge force updated all the mods in the pack. Currently every time I get to the main menu I try and create a world in single player and it just says saving world. then generates a crash report.    Crash Report: https://pastebin.com/xXESPfJs   Latest Log Part 1: https://pastebin.com/Cb2VpUyr  Part 2: https://pastebin.com/9SWVn4Dx
    • Thargor
      Minecraft Crashing upon joining save/server or when placing specific blocks

      By Thargor · Posted

      Okay, for him the config file looked like this: flywheel-client.toml: #Select the backend to use. Set to "DEFAULT" to let Flywheel decide. backend = "DEFAULT" #Enable or disable instance update limiting with distance. limitUpdates = true #The number of worker threads to use. Set to -1 to let Flywheel decide. Set to 0 to disable parallelism. Requires a game restart to take effect. #Range: -1 ~ 12 workerThreads = -1 #Config options for Flywheel's built-in backends. [flw_backends]     #How smooth Flywheel's shader-based lighting should be. May have a large performance impact.     #Allowed Values: FLAT, TRI_LINEAR, SMOOTH, SMOOTH_INNER_FACE_CORRECTED     lightSmoothness = "SMOOTH" There was no "INSTANCING", so we changed "DEFAULT" to "OFF", but this didn't help. Changing it to "INSTANCING" didn't work as well.

  • Topics

×
×
  • Create New...

Important Information

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

  I accept