PacketNarc

I am absolutely here to help and make the community and Forge better. Interestingly enough, the mod authors themselves, tell people to take exactly this approach when solving conflicts between mods. “Remove what you added, and add them back slowly until it breaks”. From the OPs own words::: problem 1.) “I kinda installed a bunch of mods....” Let’s dig in, ok ? That’s not so much of an issue; IF the user verified compatibility or did even cursory compatibility testing. Clearly that isn’t the case here. Problem. 2.) “I’m not really savvy about this...” This generally predicts failure. It’s cool to be new. That’s what this forums for. Helping new people. My suggestion to the user to remove the mods, and put them back in 1 at a time will accomplish 2 things immediately. 1.) it will allow them to discover dependencies, because the GUI will tell them “Blah blah.mod” requires “libraries.mod” to work. It will even give them a button that opens the mods folder. **That way they can systematically get the pack working, and as soon as they hit a boot error that cannot be resolved by adding back a dependency they can come here with specific problem statements in order to get prescriptive help, and not “maybe try this”. This doesn’t require any skill other than being able to read, and it teaches the user at a high level ; how interaction between different mods can create issues. Now to your comment about it not being helpful, I’ve been in the field going on 25 years, so I’m exceptionally qualified to propose this as a solution. If your authority as a Mod has motivated you to come in here and slap me with a ruler, that’s your prerogative. My post(s) or suggestions have been neither counterproductive nor trolling. If the poster takes my approach they will not only come out the other side with a working pack, but they’ll also learn a heck of a lot more about how this stuff works, in the process. This makes them more self-sufficient. A better community member.

The best recommendation is to Remove all mods, add them back one at a time, play for a bit; until you discover what’s crashing your game. simply dumping a bunch of mods into your folder without knowing how they interact usually ends up like this. You also need to look at your latest.log while the game is loading and spot any errors or incompatibilities that occur during load.

OP - Check your launch script. You have a syntax error I believe. 1.) Can you please go into your Mods folder and disable optifine ? Just temporarily rename it and add -disable to the filename after .jar. (that way it doesn't load up when Forge starts) That way we can eliminate that as a possible issue. 2.) Your Launch flags are shown in the dump : <// JVM Flags: 10 total; -Xmn128M -Xmx8500M -XX:Heap//> Q: Did you mean to Set Nursery heap and not initial heap ?Initial Heap is -Xms, not -Xmn..... Also default initial heap is 1G, (1024M). Java requires you set these in intervals of 1024K or use the G suffix which is for "gigs" where 1G = 1024M. Java Options Doc I would leave it default unless you have a specific reason to change initial heap. (you can just remove the -Xms / -Xmn flag altogether, which will allow Java to use the 1G initial, or you can manually set it to 2GB which I recommend for your initial Heap since you're running a Mods. Also, you have manually set your Max Heap to 8500Megs or 8.5Gig. This is not a supported config and can cause issues. ::From the Java Doc:: Excerpt "-Xmxsize // This value must be a multiple of 1024 and greater than 2 MB!! e.g. 8500 is not a multiple of 1024. This should be changed to -Xmx8G If you are tuning GC you can mess with -Xmn, but I don't recommend it while troubleshooting it just adds more stuff going on in the JVM and right now we're trying to troubleshoot why you aren't loading. So leave it off while we're testing. Try that change to your startup bat, and see if you get a different outcome.

You can’t access the main thread from external to the Java heap. Today anyway. There’s no feasible way to apply Web 2.0 type micro service user interaction concepts, with Minecraft. What you’re describing are just plug-ins external to the server runtime, which is like side loading hooks the same way that was done with vanilla plugins on those other modded servers. This behavior is somewhat successfully accomplished in platforms like Unity with a C# / dotNet API that runs an xml watchdog looking for calls. You can push modification to the running code to some degree, by updating the xml with CRUD processes. This opens the door to the possibility of modifying environmental and player centric behaviors inside the realm. That are isolated to specific entity’s or voxels. There is no provision for being able to do this in Minecraft because those knobs are loaded and registered at launch. Coincidently it’s also why well written Java mods are harder to exploit than the RESTful mods are. less exposure to the runtime / user space. This is why we can’t just push all mods to the client when they log in, and why we have to bounce the server when we add objects. cuz, Java...

First things first, You’re running a 5 year old version of Java on the latest bleeding edge Minecraft release. it’s very easy to see you’re on 8u92. Upgrade to at LEAST 8u151. second. There are approximately 2,000 writtten and video tutorials on how to get a simple forge server spun up in under 3-5 minutes. Please go make yourself familiar with how it’s supposed to look when it works right, so that you can better formulate a question or request for help. upgrade your Java and good luck.