Jump to content

Recommended Posts

Posted (edited)

Hey, I just recently started a Minecraft forge server for the server pack named "All the mods 6". I started off on version 1.4.1 which uses forge version 35.1.36. So far I have had no issue until I updated my profile on curse forge and started Minecraft. I'm currently experiencing issues on starting Minecraft up. Every time I hit the "play" button it starts loading for about a second or two and then stops, giving me this error message. "ERROR Game Crashed An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0". I've tried to look through the logs but was unable to find out what the problem was. I also noticed that once the forge version changes(from 35.1.36 to 36.0.21) after I update the profile on curse forge, my Minecraft always crashes on start up. I tested this by downloading every version after the one I was currently on (1.4.1) and starting them up. I also updated the server itself to version 1.5.2 for "All The Mods 6" and it works fine. I've had friends join and do the same as I and updated there profiles on curse forge and they have had no issue so far. The only thing I'm unable to do is actually start the launcher on my end I'm unsure on what to do now. PLEASE HELP!! 

 

Edited by neji813
Read in EAQ to no attach my log file to my post.
Posted (edited)

Ok. So I just deleted it and did a fresh install. Started it up and got the same error i posted earlier in the thread. Here is the log file that I just received.

 

Edited by neji813
Posted (edited)

Just changed the "$" to a "S" uninstalled and reinstall. Still getting the same crash with he same error code. here is the log file again

 

Edited by neji813

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.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

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