Jump to content

Doug Wagner

Members
  • Posts

    2
  • Joined

  • Last visited

Doug Wagner's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. I have the same issue. While the forge version is named ....32, It's actual version is ....22. In addition, the latest videos on installing forge showed using version ....40. Something wacky is going on with forge updates and fixes. For me, it is still broken on windows 11. Here is an important update. I got forge to work on my computer. First, I used forge in MC 1.18. So everything was previously set up. So, I deleted the 1.18 mods out of my mods folder, but I still had the problem described above. Then, I found an older post, something like 2017. I have gone to far to retrieve it now. It said to delete the file.....forge-client.toml in .minecraft/config So, I tried it, but it did not work. I then said what the h..l, there is also forge-common.toml right below the deleted forge-client.toml. I then deleted it along with the newly created forge-client. SUCCESS! I have been playing in the world for the last two days with no issues. When I restarted a world, or maybe when I started the launcher, both files were created. But now, the exit code one stopped appearing. Perhaps, someone here can clearly explain why this worked. I tried it because I suspected the "common" file had config data related to multiple accounts or multiple MC configurations. I just proceeded with NO FEAR. After all, at worst I would reinstall the launcher or MC.
  2. I have the same issue. While the forge version is named ....32, It's actual version is ....22. In addition, the latest videos on installing forge showed using version ....40. Something wacky is going on with forge updates and fixes. For me, it is still broken on windows 11.
×
×
  • Create New...

Important Information

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