Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

Minecraft 1.15.2, Forge 31.1.19 "Failed to find Minecraft resource"

PhoenixMercurous
 Share

Recommended Posts

PhoenixMercurous Tree Puncher

PhoenixMercurous

Posted
Posted (edited)

I'm trying to run 1.15.2 with Forge and have had the same crash on all versions of 31.1.x I've tried, including the latest 31.1.19 and a couple others.  The console output, including debug, is in the spoiler below:

 

Spoiler

19:58:34.338
launcher
main
Minecraft client forge-31.1.19 is ready to start.
19:58:34.339
launcher
main
Starting!
19:58:34.339
launcher
main
Nothing to download!
19:58:34.339
launcher
main
Extracting 8 files!
19:58:34.444
launcher
main
Using default game log configuration client-1.12.xml (outputs XML)
19:58:34.444
launcher
main
Installing versions!
19:58:35.057
cpw.mods.modlauncher.Launcher
main
ModLauncher running: args [--username, PhoenixMercurous, --version, forge-31.1.19, --gameDir, C:\Users\[redacted]\Twitch\Minecraft\Instances\test 2, --assetsDir, C:\Users\[redacted]\Twitch\Minecraft\Install\assets, --assetIndex, 1.15, --uuid, 2fc9405902094e20b2b942d38760c811, --accessToken, [redacted], --userType, mojang, --versionType, release, --width, 1024, --height, 768, --launchTarget, fmlclient, --fml.forgeVersion, 31.1.19, --fml.mcVersion, 1.15.2, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20200122.131323]
19:58:35.060
cpw.mods.modlauncher.Launcher
main
ModLauncher 5.0.0-milestone.4+67+b1a340b starting: java version 1.8.0_51 by Oracle Corporation
19:58:35.399
net.minecraftforge.fml.loading.FixSSL
main
Added Lets Encrypt root certificates as additional trust
19:58:35.440
net.minecraftforge.fml.loading.FMLConfig
main
Configuration file C:\Users\[redacted]\Twitch\Minecraft\Instances\test 2\config\fml.toml is not correct. Correcting
19:58:35.446
net.minecraftforge.fml.loading.FMLConfig
main
Incorrect key [defaultConfigPath] was corrected from null to defaultconfigs
19:58:35.460
net.minecraftforge.fml.loading.FMLCommonLaunchHandler
main
Failed to find Minecraft resource version 1.15.2-20200122.131323 at C:\Users\[redacted]\Twitch\Minecraft\Install\libraries\net\minecraftforge\forge\1.15.2-31.1.19\forge-1.15.2-31.1.19-client.jar
19:58:35.461
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]: java.lang.RuntimeException: Missing minecraft resource!
19:58:35.461
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraftforge.fml.loading.FMLCommonLaunchHandler.lambda$validatePaths$4(FMLCommonLaunchHandler.java:124)
19:58:35.461
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraftforge.fml.loading.FMLCommonLaunchHandler$$Lambda$137/2053591126.accept(Unknown Source)
19:58:35.461
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
19:58:35.461
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)
19:58:35.462
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraftforge.fml.loading.FMLCommonLaunchHandler.validatePaths(FMLCommonLaunchHandler.java:121)
19:58:35.462
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraftforge.fml.loading.FMLLoader.setupLaunchHandler(FMLLoader.java:195)
19:58:35.462
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraftforge.fml.loading.FMLServiceProvider.initialize(FMLServiceProvider.java:92)
19:58:35.462
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at cpw.mods.modlauncher.TransformationServiceDecorator.onInitialize(TransformationServiceDecorator.java:68)
19:58:35.463
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at cpw.mods.modlauncher.TransformationServicesHandler.lambda$initialiseTransformationServices$7(TransformationServicesHandler.java:107)
19:58:35.463
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at cpw.mods.modlauncher.TransformationServicesHandler$$Lambda$83/311239812.accept(Unknown Source)
19:58:35.463
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at java.util.HashMap$Values.forEach(HashMap.java:972)
19:58:35.463
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at cpw.mods.modlauncher.TransformationServicesHandler.initialiseTransformationServices(TransformationServicesHandler.java:107)
19:58:35.468
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at cpw.mods.modlauncher.TransformationServicesHandler.initializeTransformationServices(TransformationServicesHandler.java:59)
19:58:35.468
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at cpw.mods.modlauncher.Launcher.run(Launcher.java:75)
19:58:35.468
STDERR
main
[java.lang.ThreadGroup:uncaughtException:1052]:     at cpw.mods.modlauncher.Launcher.main(Launcher.java:65)
19:58:35.815
launcher
main

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
19:58:35.815
monitor
Process Monitor
Process crashed with exit code 1

 

The emphasis on the error is my addition.  This crash occurs with and without any mods installed, so it seems to be something with Forge itself.  I've deleted the file it crashes on and let it reinstall it, which didn't work, and I've tried an uninstall/reinstall of Twitch, which also didn't work.  I've made sure to install Java 8.x, and the crash still occurs.

I've included the log file for this instance of the launcher.  There doesn't seem to be a debug log specific to that instance, so I'm including the debug.log file from the \Minecraft\Install folder, which is the only debug file I can find.
 

latest.log debug.log

Edited by PhoenixMercurous
Added clarification.
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Try repairing the instance, otherwise there is a video in my signature about how to run a Twitch modpack without using Twitch

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]

 

PhoenixMercurous Tree Puncher

PhoenixMercurous

Posted
  • Author
Posted
4 minutes ago, DaemonUmbra said:

Try repairing the instance, otherwise there is a video in my signature about how to run a Twitch modpack without using Twitch

Repairing had no effect, the same crash occurred after running repair.

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Then I can only recommend my video on bypassing Twitch for launching packs, this is a Twitch issue and not a Forge issue.

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]

 

  • 3 weeks later...
idonotexist66 Tree Puncher

idonotexist66

Posted
Posted
On 3/15/2020 at 1:06 AM, DaemonUmbra said:

Then I can only recommend my video on bypassing Twitch for launching packs, this is a Twitch issue and not a Forge issue.

Where can i find this video

 

  • 4 months later...
jocko Tree Puncher

jocko

Posted
Posted

My friend was also having this issue what fixed it was changing his Minecraft Path in the twitch launcher he moved it to his other drive.

 

The only difference between his installation and mine was the fact that his windows username had a space in it ie: C:/users/John Smith/ but mine for example is C:/users/johns/

Spaces in the file path could be a issue for users using windows if the launcher is doing something to the file path before it reads from the disk.

 

This may be a red herring but try changing your minecraft path in twitch launcher to a different path without spaces.

 

 

  • 2 months later...
gmanpohl Tree Puncher

gmanpohl

Posted
Posted

Hello 

 

My friend is experiencing the same problem and i think it is because of the spaces but he attempted to move Twitch to a different path but it moves it back to his user folder which has spaces. Please help.

 

Gmanpohl23

  • Guest locked this topic
Guest
This topic is now closed to further replies.
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

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

  I accept