Posted August 3, 20196 yr After updating to the newest version of Forge, 28.0.40, Minecraft started up easily, however, later, after installing new mods, Minecraft refused to start up, the output log showing "process crashed with exit code 1." I was unable to highlight the entire output log that the Minecraft launcher showed me for some reason. After researching online, I updated my graphics card driver and restarted my computer. Despite this, no results came. I went into my .minecraft folder and put my debug log into a Pastebin log, so that's that. Help? https://pastebin.com/CcTwgNb2
August 4, 20196 yr The actual error is being hidden by another error due to a change I made, fixing... 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]
August 4, 20196 yr Author I don't follow? Edit: nevermind, I managed to fix it. Edited August 5, 20196 yr by MistaMan
February 23, 20205 yr On 8/4/2019 at 12:34 PM, MistaMan said: I don't follow? Edit: nevermind, I managed to fix it. yo how did you fix it IM having the exact problem as you and I've tried using earlier backups and it doesn't help. Please help
February 23, 20205 yr Please make your own thread with logs 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]
April 23, 20205 yr i have the same isue with minecraft forge the log is following 12:27:41.251 game [12:27:41] [main/INFO] [cp.mo.mo.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmlclient' with arguments [--version, 1.14.4-forge-28.1.0, --gameDir, /home/myusername/.minecraft, --assetsDir, /home/myusername/.minecraft/assets, --username, mercedes7935, --assetIndex, 1.14, --uuid, 4fa1228c8dd647c48fe3b04b580311b8, --accessToken, ❄❄❄❄❄❄❄❄, --userType, legacy, --versionType, release] 12:27:42.031 game Exception in thread "Client thread" [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1050]: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException 12:27:42.032 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1050]: at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:39) 12:27:42.032 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1050]: at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:50) 12:27:42.032 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1050]: at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:68) 12:27:42.033 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1050]: at cpw.mods.modlauncher.Launcher.run(Launcher.java:80) 12:27:42.033 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1050]: at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) 12:27:42.034 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: Caused by: java.lang.reflect.InvocationTargetException 12:27:42.034 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 12:27:42.035 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 12:27:42.035 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 12:27:42.035 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: at java.base/java.lang.reflect.Method.invoke(Method.java:566) 12:27:42.036 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56) 12:27:42.036 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) 12:27:42.037 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1059]: ... 4 more 12:27:42.037 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.Throwable:printStackTrace:648]: Caused by: java.lang.UnsupportedOperationException 12:27:42.038 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.Throwable:printStackTrace:648]: at org.objectweb.asm.ClassVisitor.visitNestMemberExperimental(ClassVisitor.java:248) 12:27:42.038 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.Throwable:printStackTrace:648]: at org.objectweb.asm.ClassReader.accept(ClassReader.java:651) 12:27:42.039 game [12:27:42] [Client thread/INFO] [STDERR/]: [java.lang.Throwable:printStackTrace:648]: at org.objectweb.asm.ClassReader.accept(ClassReader.java:391) Edited April 23, 20205 yr by mercedes7935 i saw grammitical wrong words
April 23, 20205 yr 5 minutes ago, mercedes7935 said: i have the same isue with minecraft forge the log That is not even close to the same as the log the OP posted. You should make your own thread and post your log there.
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.