Matthew6164 Posted December 16, 2019 Posted December 16, 2019 (edited) I've been trying to get All The Mods 4 to work for the past few days, but I keep getting the same problem: https://gyazo.com/4ec8de003e9a4f5f144584cd5f801177 I am giving minecraft 5.4k MB to run. If it matters, I am trying to run Version 0.2.5 because we have a server running on that version. I see the error code that says it cant find the forge client jar Things I have tried: Renaming the forge- 1.14.4-28.1.104.jar file to forge- 1.14.4-28.1.104-client.jar (It just created a new instance of forge- 1.14.4-28.1.104.jar and ignored the new file) Reinstalling ATM 4 Repairing the profile Manually installing and launching Forge Client Reinstalling MC Using a friend's .minecraft files Disabling my firewall and reinstalling ATM 4 Full Game output log here: 13:37:00.648 Preparing to launch minecraft client for forge-28.1.104 14:03:52.510 Prepared asset index 14:03:52.529 Have 2077 total files to check or download 14:03:52.534 Waiting for 2077 futures 13:37:00.797 Couldn't fetch SHA1 checksum for https://s3.amazonaws.com/Minecraft.Download/versions/1.14.4/1.14.4.jar 13:37:00.825 Have local file C:\Program Files (x86)\Minecraft\Install\versions\1.14.4\1.14.4.jar but don't know what size or hash it should be. Have to assume it's good. 13:37:00.981 Checking installations. 13:37:00.982 Minecraft client forge-28.1.104 is ready to start. 13:37:00.982 Starting! 14:03:52.846 Nothing to download! 14:03:52.846 Extracting 7 files! 13:37:01.170 Using default game log configuration client-1.12.xml (outputs XML) 14:03:53.045 Installing versions! 13:37:01.782 ModLauncher running: args [--username, Matthew6164, --version, forge-28.1.104, --gameDir, C:\Program Files (x86)\Minecraft\Instances\All the Mods 4, --assetsDir, C:\Program Files (x86)\Minecraft\Install\assets, --assetIndex, 1.14, --uuid, 4d13cbe3e7624b698a7777ea0de02db9, --accessToken, ❄❄❄❄❄❄❄❄, --userType, mojang, --versionType, release, --width, 1920, --height, 1080, --launchTarget, fmlclient, --fml.forgeVersion, 28.1.104, --fml.mcVersion, 1.14.4, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20190829.143755] 13:37:01.785 ModLauncher 4.1.0+62+5bfa59b starting: java version 1.8.0_51 by Oracle Corporation 13:37:02.184 Added Lets Encrypt root certificates as additional trust 13:37:02.245 Failed to find Minecraft resource version 1.14.4-20190829.143755 at C:\Program Files (x86)\Minecraft\Install\libraries\net\minecraftforge\forge\1.14.4-28.1.104\forge-1.14.4-28.1.104-client.jar 13:37:02.245 [java.lang.ThreadGroup:uncaughtException:1052]: java.lang.RuntimeException: Missing minecraft resource! 13:37:02.246 [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraftforge.fml.loading.FMLCommonLaunchHandler.lambda$validatePaths$4(FMLCommonLaunchHandler.java:124) 13:37:02.246 [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraftforge.fml.loading.FMLCommonLaunchHandler$$Lambda$136/40075281.accept(Unknown Source) 13:37:02.246 [java.lang.ThreadGroup:uncaughtException:1052]: at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948) 13:37:02.246 [java.lang.ThreadGroup:uncaughtException:1052]: at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) 13:37:02.247 [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraftforge.fml.loading.FMLCommonLaunchHandler.validatePaths(FMLCommonLaunchHandler.java:121) 13:37:02.247 [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraftforge.fml.loading.FMLLoader.setupLaunchHandler(FMLLoader.java:195) 13:37:02.247 [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraftforge.fml.loading.FMLServiceProvider.initialize(FMLServiceProvider.java:92) 13:37:02.248 [java.lang.ThreadGroup:uncaughtException:1052]: at cpw.mods.modlauncher.TransformationServiceDecorator.onInitialize(TransformationServiceDecorator.java:68) 13:37:02.248 [java.lang.ThreadGroup:uncaughtException:1052]: at cpw.mods.modlauncher.TransformationServicesHandler.lambda$initialiseTransformationServices$7(TransformationServicesHandler.java:107) 13:37:02.248 [java.lang.ThreadGroup:uncaughtException:1052]: at cpw.mods.modlauncher.TransformationServicesHandler$$Lambda$84/1108924067.accept(Unknown Source) 13:37:02.248 [java.lang.ThreadGroup:uncaughtException:1052]: at java.util.HashMap$Values.forEach(HashMap.java:972) 13:37:02.255 [java.lang.ThreadGroup:uncaughtException:1052]: at cpw.mods.modlauncher.TransformationServicesHandler.initialiseTransformationServices(TransformationServicesHandler.java:107) 13:37:02.256 [java.lang.ThreadGroup:uncaughtException:1052]: at cpw.mods.modlauncher.TransformationServicesHandler.initializeTransformationServices(TransformationServicesHandler.java:59) 13:37:02.256 [java.lang.ThreadGroup:uncaughtException:1052]: at cpw.mods.modlauncher.Launcher.run(Launcher.java:75) 13:37:02.256 [java.lang.ThreadGroup:uncaughtException:1052]: at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) 13:37:02.620 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0 13:37:02.620 Process crashed with exit code 1 Edited December 16, 2019 by Matthew6164 Adding in debug level of game output log Quote
DaemonUmbra Posted December 16, 2019 Posted December 16, 2019 Delete .minecraft/versions/1.14.4/1.14.4.jar and reinstall Forge Quote 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 Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. 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). 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. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init 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 git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push 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) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
Matthew6164 Posted December 16, 2019 Author Posted December 16, 2019 Alright I tried that, Im still getting the same error code and crashing Quote
Matthew6164 Posted December 17, 2019 Author Posted December 17, 2019 forge-1.14.4-28.1.104-installer.jar.log Quote
Recommended Posts
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.