Jump to content

Recommended Posts

Posted

Hello i just installed forge 1.12.2

i started the forge many times it crashes the second after start up and i have no mods in the mod folder (freezes and does nothing so you have to make it crash)  i tried deleting the config , restarting , updating java , trying different forge 1.12.2 versions ( recommended version and newest), and allocating  more ram (up to 8gb) but still it freezes and does nothing 2 seconds after the start up

I'm not sure if it gives any crash report but it does say this :
An unexpected issue occurred and the game has crashed. we are sorry for the inonenience

Posted (edited)
12 minutes ago, diesieben07 said:

Do you have a file called hs_err_pid_xxxx in your game directory? If so, please post it.

i don't think i have it , but i would like to know which folder is it in ?

edit : (im sure i dont have it)

Edited by elmainer
Posted
Just now, diesieben07 said:

Then there is literally zero information, because the log just stops.

a lot of people are having the same problem as mine , maybe something wrong with forge ? because it seems like i has a lot of issues with getting files from the servers

Posted
1 minute ago, diesieben07 said:

a lot of people are having the same problem as mine

i am seeing quit a few reports on 1.12.2 start up crashes

also thanks for you effort and time

Posted
6 minutes ago, diesieben07 said:

"It crashes" literally means nothing.

This forum has seen reports of "it crashes" for years, regardless of version.

99.9% of the time it is either user error or a broken mod.

I don't want to disturb this thread with selfishness but I appended the debug.logs to my thread so perhaps now you can solve the puzzle

Posted
Just now, diesieben07 said:

Having a wonderful day, in fact.

Here's how your reply looks to me:
"Oh look, they are replying in this other thread, lets show my issue there to get their attention". To me that is rude.

 

 

Absolutely not, I'm helping on a different forum about C/C++ and appreciate it when other users notify me about the status change of their threads. Next time don't think someone immediately has bad intentions.

Posted
29 minutes ago, Reloading said:

I don't want to disturb this thread with selfishness

So you disturbed me with a "please look at my thread again" DM

From now until Christmas Day everything you post will need to be approved by a mod

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

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



×
×
  • Create New...

Important Information

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