Jump to content
View in the app

A better way to browse. Learn more.
Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

Immediate Crash for Forge 1.14.4

skarmoryharmony
in Support & Bug Reports

Featured Replies

Posted

Hello. I had recently posted this under someone else's thread but I read the rules and decided to make a separate one. I was trying to update my forge server at first but then I didn't see the new latest 1.14.4 release for forge in the launcher. SO I installed the forge client after however whenever i try to use forge 1.14.4's installation in the minecraft launcher, it crashes. The server loads up in the vanilla latest release just fine and i've tried running it without mods. 

 

 

 

crash-2019-07-20_10.04.54-server.txt

I have the same issue with Forge crashing instantly on my client when I click on play. I don't really know where I can find my logs that I need so if anyone could give me a tip that'd be great so I can post them.

 

PS: I do not have any mods installed.

Edited by Snellibee

  • Author

Thank for replying! I removed all items pertaining to Worldedit and launched the forge 1.14.4 server and it hasn't crashed. So that fixes that problem. However the launcher still crashes when I press the play button with the forge.1.14.4 release installation. Clicking on the view report button doesn't seem to open anything in which i can view the crash report. 

 

 

https://pastebin.com/m1v31e3e

Edited by skarmoryharmony
Added Latest log crash report

I'm having the same issue, both installations for the 1.14.4 forge instantly crash. And I can't open the crash report to find out why. Is this just a bug with the forge or my computer?

  • Author
2 minutes ago, Nora Lamkhidda said:

I'm having the same issue, both installations for the 1.14.4 forge instantly crash. And I can't open the crash report to find out why. Is this just a bug with the forge or my computer?

Go to your .minecraft/logs/latest.log and judge it by the date of the report. That's what you'll need to see the crash report.

Update Forge, this was just fixed.

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]

 

    • Thanks 1
    • 3 months later...

    I still cant use forge.it crashes on every forge version with or without any mods.i also have 1.14.4 mods and corresponding forge versions.Oh andi get no crash report just an immediate crash on launch.please reply fast and help me.

     

    BYE

    • Guest locked this topic
    Guest
    This topic is now closed to further replies.
    https://forums.minecraftforge.net/topic/73283-immediate-crash-for-forge-1144/
    Go to topic listing

    Important Information

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

    I accept

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.