Leaderboard

This is a Twitch Launcher issue, nothing Forge can do to fix Twitch hosting corrupted libraries. A workaround is installing Forge manually into standalone Minecraft (This works even with the launcher installation Twitch uses just as long as you don't launch it THROUGH twitch), then create a launcher profile and point its Game Directory option to the folder of your modpack instance.

Open a GUI with NetworkHooks.openGui Register a GUI with ModLoadingContext#registerExtensionPoint (I think) IIRC you can either create an InteractionObject or make your TE implement IInteractionObject, idk which one is recommended.

If it were me, I'd try removing the movingworld mod, and see if that stops the crashing. Also make sure you are downloading your mods from curseforge, or directly from the developers, and not from shady websites like 9 minecraft and such.

Don't download from 9minecraft, they distribute mods without permission, and there is the potential for there to be malware added to the mod jars, as well as potentially out of date mods. I would delete any mods downloaded from 9minecraft and redownload them from curseforge. https://stopmodreposts.org/

BlockFluid#isSource

Main Page? Anyways, 'Recommended' is a manual promotion. It's to mark a build as 'stable'. Meaning people have tested it and all known major issues have been resolved. This process requires modders/users to actually test and give feedback. So go forth and test!

No, MCP is the core and it will continue to be the core. I create MCP and thus I can trust in it's stability and availability. If modders want to make a translation tool between the two so that Fabric can load on SRG names. Then go for it. I have spoken many times about how a system should be designed. But the people who have said they wanted to help haven't followed through. Anyways, getting tired of answering this. Forge will never use Fabric. Fabric's core design of "screw it everyone's a coremod!" is NOT feasible for a large compatible modding ecosystem. Forge's major rewrite is done, which means updates should be back to our normal same day target. Sorry for being 'slow' because we decided to cleanup 8 years of technical debt and plan for the next 10 years. Anyways, don't bump old threads.