Jump to content

Crash on launch

Recommended Posts



I've been trying to setup a new 1.16 instance using the CurseForge/twitch tool. The Minecraft launcher works fine once the instance is installed, but every time I ty to lanuch the forge profile on it, the game just launch to crash instantly.


So far, I've tried to:

- Update Java; it is now on the latest version on my PC

- Repair the Twitch profile

- Deleting and reinstalling the instance sevral times using different profile names

- Launching the instance without any mod; just Forge alone


without any success. Every time, the logs produce the same lines:


[20:51:40] [main/INFO]: ModLauncher running: args [--username, Smog_Shadowseth, --version, forge-32.0.75, --gameDir, C:\Users\Smog ShadowSeth\Documents\Curse\Minecraft\Instances\Smogcraft 16, --assetsDir, C:\Users\Smog ShadowSeth\Documents\Curse\Minecraft\Install\assets, --assetIndex, 1.16, --uuid, f8c423f984f9427180b0b76650958a28, --accessToken, ????????, --userType, legacy, --versionType, release, --width, 1024, --height, 768, --launchTarget, fmlclient, --fml.forgeVersion, 32.0.75, --fml.mcVersion, 1.16.1, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20200625.160719]
[20:51:40] [main/INFO]: ModLauncher 5.1.0+69+master.79f13f7 starting: java version 1.8.0_51 by Oracle Corporation
[20:51:41] [main/INFO]: Added Lets Encrypt root certificates as additional trust
[20:51:41] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.8 Source=file:/C:/Users/Smog%20ShadowSeth/Documents/Curse/Minecraft/Install/libraries/org/spongepowered/mixin/0.8/mixin-0.8.jar Service=ModLauncher Env=CLIENT
[20:51:41] [main/WARN]: Configuration file C:\Users\Smog ShadowSeth\Documents\Curse\Minecraft\Instances\Smogcraft 16\config\fml.toml is not correct. Correcting
[20:51:41] [main/WARN]: Incorrect key [defaultConfigPath] was corrected from null to defaultconfigs
[20:51:42] [main/FATAL]: Failed to find Minecraft resource version 1.16.1-20200625.160719 at C:\Users\Smog ShadowSeth\Documents\Curse\Minecraft\Install\libraries\net\minecraftforge\forge\1.16.1-32.0.75\forge-1.16.1-32.0.75-client.jar
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: java.lang.RuntimeException: Missing minecraft resource!
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at net.minecraftforge.fml.loading.FMLCommonLaunchHandler.lambda$validatePaths$4(FMLCommonLaunchHandler.java:124)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at net.minecraftforge.fml.loading.FMLCommonLaunchHandler$$Lambda$158/238357312.accept(Unknown Source)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at net.minecraftforge.fml.loading.FMLCommonLaunchHandler.validatePaths(FMLCommonLaunchHandler.java:121)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at net.minecraftforge.fml.loading.FMLLoader.setupLaunchHandler(FMLLoader.java:199)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at net.minecraftforge.fml.loading.FMLServiceProvider.initialize(FMLServiceProvider.java:94)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at cpw.mods.modlauncher.TransformationServiceDecorator.onInitialize(TransformationServiceDecorator.java:68)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at cpw.mods.modlauncher.TransformationServicesHandler.lambda$initialiseTransformationServices$7(TransformationServicesHandler.java:107)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at cpw.mods.modlauncher.TransformationServicesHandler$$Lambda$83/1636506029.accept(Unknown Source)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at java.util.HashMap$Values.forEach(HashMap.java:972)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at cpw.mods.modlauncher.TransformationServicesHandler.initialiseTransformationServices(TransformationServicesHandler.java:107)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at cpw.mods.modlauncher.TransformationServicesHandler.initializeTransformationServices(TransformationServicesHandler.java:59)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at cpw.mods.modlauncher.Launcher.run(Launcher.java:75)
[20:51:42] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: 	at cpw.mods.modlauncher.Launcher.main(Launcher.java:65)


I've noticed something in these logs: the files directories are all wrong. I have no "Users" folder on my C: drive, but an "Utilisateurs" (users in french, the language on witch my Windows 10 is installed) instead; could this be the problem? I'd think that windows could handle translation for such critical folders.

Other than that, the fml.toml file is in the right folder (the "users" part asside), but I have no "forge-1.16.1-32.0.75-client.jar" file at the folder pointed; just those instead: "forge-1.16.1-32.0.75.jar", "forge-1.16.1-32.0.75-clientdata.lzma" and "forge-1.16.1-32.0.75-universal.jar"


Help pls?

Link to comment
Share on other sites

I believe this is Twitch failing to install Forge properly.


I recommend using Twitch only to install packs but not run them.

  1. Install the pack on Twitch
  2. Get the latest version of Forge for the Minecraft version the pack uses and install it
  3. Open the Minecraft Launcher
  4. Make a new "Installation"
  5. Set the Installations Forge version and set the Game Directory to the folder where twitch installed the pack (in Twitch's Instances folder with the same name as the pack)

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.


Logs (Most issues require logs to diagnose):


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:

  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.






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:


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:


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:


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]


Link to comment
Share on other sites

12 hours ago, DaemonUmbra said:

I believe this is Twitch failing to install Forge properly.

Thank you for your anwser; it look like it is! I folowed your instructions and got my pack to launch and run like a charm. Like you said, I must use the Minecraft launcher and not the Twitch one for the pack to run, otherwise it crashes every time, producing the same logs. Guess I need to report the issue to Curse/Twitch then.


Thanks again for your help!

Edited by Smog Shadowseth
correcting some words
Link to comment
Share on other sites

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.

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.


  • Create New...

Important Information

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