Nitrama Posted August 1, 2019 Share Posted August 1, 2019 Hello, I've wanted to play Minecraft again for a long time. Unfortunately I can't get it to work. Unfortunately I didn't find anything. Therefore I post the log and a screenshot. [01Aug2019 17:33:01.648] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher running: args [--username, Nitrama, --version, 1.14.4-forge-28.0.29, --gameDir, /home/martin/.minecraft, --assetsDir, /home/martin/.minecraft/assets, --assetIndex, 1.14, --uuid, d4a1d6fa82e645658900d8c474cc9752, --accessToken, ❄❄❄❄❄❄❄❄, --userType, mojang, --versionType, release, --launchTarget, fmlclient, --fml.forgeVersion, 28.0.29, --fml.mcVersion, 1.14.4, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20190719.225934] [01Aug2019 17:33:01.652] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher 3.1.1+59+e32e753 starting: java version 1.8.0_211 by IBM Corporation [01Aug2019 17:33:01.929] [main/INFO] [net.minecraftforge.fml.loading.FixSSL/CORE]: Added Lets Encrypt root certificates as additional trust [01Aug2019 17:33:02.715] [main/INFO] [cpw.mods.modlauncher.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmlclient' with arguments [--version, 1.14.4-forge-28.0.29, --gameDir, /home/martin/.minecraft, --assetsDir, /home/martin/.minecraft/assets, --username, Nitrama, --assetIndex, 1.14, --uuid, d4a1d6fa82e645658900d8c474cc9752, --accessToken, ❄❄❄❄❄❄❄❄, --userType, mojang, --versionType, release] [01Aug2019 17:33:04.465] [Client thread/INFO] [net.minecraft.client.Minecraft/]: Setting user: Nitrama [01Aug2019 17:33:09.631] [Client thread/INFO] [net.minecraft.client.Minecraft/]: LWJGL Version: 3.2.2 build 10 [01Aug2019 17:33:10.468] [modloading-worker-9/ERROR] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: Failed to resolve handler for "biomesoplenty.core.BiomesOPlenty$$Lambda$2128/000000007400F6F0@64808e6d" [01Aug2019 17:33:10.469] [modloading-worker-11/INFO] [net.minecraftforge.common.ForgeMod/FORGEMOD]: Forge mod loading, version 28.0.29, for MC 1.14.4 with MCP 20190719.225934 [01Aug2019 17:33:10.470] [modloading-worker-11/INFO] [net.minecraftforge.common.MinecraftForge/FORGE]: MinecraftForge v28.0.29 Initialized [01Aug2019 17:33:10.473] [modloading-worker-2/ERROR] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: Failed to resolve handler for "squeek.appleskin.AppleSkin$$Lambda$2131/000000006800B050@30a96057" [01Aug2019 17:33:10.473] [modloading-worker-2/ERROR] [net.minecraftforge.fml.javafmlmod.FMLModContainer/LOADING]: Failed to create mod instance. ModID: appleskin, class squeek.appleskin.AppleSkin java.lang.IllegalStateException: Failed to resolve consumer event type: squeek.appleskin.AppleSkin$$Lambda$2131/000000006800B050@30a96057 at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:194) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:161) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:156) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:151) ~[eventbus-0.10.6-service.jar:?] at squeek.appleskin.AppleSkin.<init>(AppleSkin.java:24) ~[?:1.0.11] at java.lang.J9VMInternals.newInstanceImpl(Native Method) ~[?:2.9 (04-17-2019)] at java.lang.Class.newInstance(Class.java:1848) ~[?:2.9 (04-17-2019)] at net.minecraftforge.fml.javafmlmod.FMLModContainer.constructMod(FMLModContainer.java:131) ~[?:28.0] at net.minecraftforge.fml.javafmlmod.FMLModContainer$$Lambda$2066.00000000AF38A8B0.accept(Unknown Source) ~[?:?] at java.util.function.Consumer.lambda$andThen$0(Consumer.java:76) ~[?:1.8.0] at java.util.function.Consumer$$Lambda$2065.00000000AF38A470.accept(Unknown Source) ~[?:?] at java.util.function.Consumer.lambda$andThen$0(Consumer.java:76) ~[?:1.8.0] at java.util.function.Consumer$$Lambda$2065.00000000AF38A470.accept(Unknown Source) ~[?:?] at net.minecraftforge.fml.ModContainer.transitionState(ModContainer.java:112) ~[?:?] at net.minecraftforge.fml.ModList.lambda$null$10(ModList.java:133) ~[?:?] at net.minecraftforge.fml.ModList$$Lambda$2119.00000000740037F0.accept(Unknown Source) ~[?:?] at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:195) [?:1.8.0] at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1393) [?:1.8.0] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:523) [?:1.8.0] at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:302) [?:1.8.0] at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:742) [?:1.8.0] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:300) [?:1.8.0] at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) [?:1.8.0] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) [?:1.8.0] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:168) [?:1.8.0] [01Aug2019 17:33:10.468] [modloading-worker-9/ERROR] [net.minecraftforge.fml.javafmlmod.FMLModContainer/LOADING]: Failed to create mod instance. ModID: biomesoplenty, class biomesoplenty.core.BiomesOPlenty java.lang.IllegalStateException: Failed to resolve consumer event type: biomesoplenty.core.BiomesOPlenty$$Lambda$2128/000000007400F6F0@64808e6d at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:194) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:161) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:156) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:151) ~[eventbus-0.10.6-service.jar:?] at biomesoplenty.core.BiomesOPlenty.<init>(BiomesOPlenty.java:39) ~[?:?] at java.lang.J9VMInternals.newInstanceImpl(Native Method) ~[?:2.9 (04-17-2019)] at java.lang.Class.newInstance(Class.java:1848) ~[?:2.9 (04-17-2019)] at net.minecraftforge.fml.javafmlmod.FMLModContainer.constructMod(FMLModContainer.java:131) ~[?:28.0] at net.minecraftforge.fml.javafmlmod.FMLModContainer$$Lambda$2066.00000000AF38A8B0.accept(Unknown Source) ~[?:?] at java.util.function.Consumer.lambda$andThen$0(Consumer.java:76) ~[?:1.8.0] at java.util.function.Consumer$$Lambda$2065.00000000AF38A470.accept(Unknown Source) ~[?:?] at java.util.function.Consumer.lambda$andThen$0(Consumer.java:76) ~[?:1.8.0] at java.util.function.Consumer$$Lambda$2065.00000000AF38A470.accept(Unknown Source) ~[?:?] at net.minecraftforge.fml.ModContainer.transitionState(ModContainer.java:112) ~[?:?] at net.minecraftforge.fml.ModList.lambda$null$10(ModList.java:133) ~[?:?] at net.minecraftforge.fml.ModList$$Lambda$2119.00000000740037F0.accept(Unknown Source) ~[?:?] at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:195) ~[?:1.8.0] at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1393) ~[?:1.8.0] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:523) ~[?:1.8.0] at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:302) ~[?:1.8.0] at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:742) ~[?:1.8.0] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:300) ~[?:1.8.0] at java.util.concurrent.ForkJoinTask.doInvoke(ForkJoinTask.java:412) ~[?:1.8.0] at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:745) ~[?:1.8.0] at java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:171) ~[?:1.8.0] at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:185) ~[?:1.8.0] at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:244) ~[?:1.8.0] at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:429) ~[?:1.8.0] at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:594) ~[?:1.8.0] at net.minecraftforge.fml.ModList.lambda$dispatchParallelEvent$11(ModList.java:133) ~[?:?] at net.minecraftforge.fml.ModList$$Lambda$2118.00000000AF491660.run(Unknown Source) ~[?:?] at java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1397) [?:1.8.0] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:300) [?:1.8.0] at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) [?:1.8.0] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) [?:1.8.0] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:168) [?:1.8.0] [01Aug2019 17:33:10.492] [modloading-worker-11/ERROR] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: Failed to resolve handler for "net.minecraftforge.common.ForgeMod$$Lambda$2159/000000006C0052D0@26b5798c" [01Aug2019 17:33:10.492] [modloading-worker-11/ERROR] [net.minecraftforge.fml.javafmlmod.FMLModContainer/LOADING]: Failed to create mod instance. ModID: forge, class net.minecraftforge.common.ForgeMod java.lang.IllegalStateException: Failed to resolve consumer event type: net.minecraftforge.common.ForgeMod$$Lambda$2159/000000006C0052D0@26b5798c at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:194) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:161) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:156) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:151) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.common.ForgeMod.<init>(ForgeMod.java:91) ~[?:?] at java.lang.J9VMInternals.newInstanceImpl(Native Method) ~[?:2.9 (04-17-2019)] at java.lang.Class.newInstance(Class.java:1848) ~[?:2.9 (04-17-2019)] at net.minecraftforge.fml.javafmlmod.FMLModContainer.constructMod(FMLModContainer.java:131) ~[?:28.0] at net.minecraftforge.fml.javafmlmod.FMLModContainer$$Lambda$2066.00000000AF38A8B0.accept(Unknown Source) ~[?:?] at java.util.function.Consumer.lambda$andThen$0(Consumer.java:76) ~[?:1.8.0] at java.util.function.Consumer$$Lambda$2065.00000000AF38A470.accept(Unknown Source) ~[?:?] at java.util.function.Consumer.lambda$andThen$0(Consumer.java:76) ~[?:1.8.0] at java.util.function.Consumer$$Lambda$2065.00000000AF38A470.accept(Unknown Source) ~[?:?] at net.minecraftforge.fml.ModContainer.transitionState(ModContainer.java:112) ~[?:?] at net.minecraftforge.fml.ModList.lambda$null$10(ModList.java:133) ~[?:?] at net.minecraftforge.fml.ModList$$Lambda$2119.00000000740037F0.accept(Unknown Source) ~[?:?] at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:195) [?:1.8.0] at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1393) [?:1.8.0] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:523) [?:1.8.0] at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:302) [?:1.8.0] at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:742) [?:1.8.0] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:300) [?:1.8.0] at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) [?:1.8.0] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) [?:1.8.0] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:168) [?:1.8.0] [01Aug2019 17:33:10.516] [Client thread/FATAL] [net.minecraftforge.fml.ModLoader/LOADING]: Failed to complete lifecycle event CONSTRUCT, 3 errors found [01Aug2019 17:33:10.517] [Client thread/FATAL] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: EventBus 0 shutting down - future events will not be posted. java.lang.Exception: stacktrace at net.minecraftforge.eventbus.EventBus.shutdown(EventBus.java:278) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:86) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2040.00000000AF2DB3D0.run(Unknown Source) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader.begin(ClientModLoader.java:68) ~[?:?] at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:453) ~[?:?] at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:365) ~[?:?] at net.minecraft.client.main.Main.main(SourceFile:155) ~[1.14.4-forge-28.0.29.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) ~[?:1.8.0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) ~[?:1.8.0] at java.lang.reflect.Method.invoke(Method.java:508) ~[?:1.8.0] at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56) ~[forge-1.14.4-28.0.29.jar:28.0] at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$360.00000000AD8FC1C0.call(Unknown Source) ~[?:?] at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-3.1.1.jar:?] at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:50) [modlauncher-3.1.1.jar:?] at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:68) [modlauncher-3.1.1.jar:?] at cpw.mods.modlauncher.Launcher.run(Launcher.java:80) [modlauncher-3.1.1.jar:?] at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) [modlauncher-3.1.1.jar:?] [01Aug2019 17:33:11.679] [Client thread/INFO] [com.mojang.text2speech.NarratorLinux/]: Narrator library successfully loaded [01Aug2019 17:33:25.967] [Server-Worker-7/ERROR] [net.minecraftforge.fml.ModLoader/LOADING]: Skipping lifecycle event SETUP, 3 errors found. [01Aug2019 17:33:25.968] [Server-Worker-7/FATAL] [net.minecraftforge.fml.ModLoader/LOADING]: Failed to complete lifecycle event SETUP, 3 errors found [01Aug2019 17:33:25.968] [Server-Worker-7/FATAL] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: EventBus 0 shutting down - future events will not be posted. java.lang.Exception: stacktrace at net.minecraftforge.eventbus.EventBus.shutdown(EventBus.java:278) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:86) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2040.00000000AF2DB3D0.run(Unknown Source) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader.startModLoading(ClientModLoader.java:94) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader.lambda$onreload$3(ClientModLoader.java:76) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2320.00000000AF6890E0.run(Unknown Source) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:84) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2040.00000000AF2DB3D0.run(Unknown Source) ~[?:?] at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1637) [?:1.8.0] at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1629) [?:1.8.0] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:300) [?:1.8.0] at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) [?:1.8.0] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) [?:1.8.0] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:168) [?:1.8.0] [01Aug2019 17:33:28.513] [Server-Worker-6/ERROR] [net.minecraftforge.fml.ModLoader/LOADING]: Skipping lifecycle event ENQUEUE_IMC, 3 errors found. [01Aug2019 17:33:28.513] [Server-Worker-6/FATAL] [net.minecraftforge.fml.ModLoader/LOADING]: Failed to complete lifecycle event ENQUEUE_IMC, 3 errors found [01Aug2019 17:33:28.514] [Server-Worker-6/FATAL] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: EventBus 0 shutting down - future events will not be posted. java.lang.Exception: stacktrace at net.minecraftforge.eventbus.EventBus.shutdown(EventBus.java:278) ~[eventbus-0.10.6-service.jar:?] at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:86) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2040.00000000AF2DB3D0.run(Unknown Source) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader.finishModLoading(ClientModLoader.java:107) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader.lambda$onreload$4(ClientModLoader.java:78) ~[?:?] at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2322.00000000AF689880.run(Unknown Source) ~[?:?] at java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:716) [?:1.8.0] at java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:698) [?:1.8.0] at java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:454) [?:1.8.0] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:300) [?:1.8.0] at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) [?:1.8.0] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) [?:1.8.0] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:168) [?:1.8.0] [01Aug2019 17:33:28.601] [Client thread/INFO] [net.minecraft.client.audio.SoundSystem/]: OpenAL initialized. [01Aug2019 17:33:28.602] [Client thread/INFO] [net.minecraft.client.audio.SoundEngine/SOUNDS]: Sound engine started [01Aug2019 17:33:28.880] [Client thread/INFO] [net.minecraft.client.renderer.texture.AtlasTexture/]: Created: 512x512 textures-atlas [01Aug2019 17:33:29.982] [Client thread/INFO] [net.minecraft.client.renderer.texture.AtlasTexture/]: Created: 256x256 textures/particle-atlas [01Aug2019 17:33:29.984] [Client thread/INFO] [net.minecraft.client.renderer.texture.AtlasTexture/]: Created: 256x256 textures/painting-atlas [01Aug2019 17:33:29.985] [Client thread/INFO] [net.minecraft.client.renderer.texture.AtlasTexture/]: Created: 128x128 textures/mob_effect-atlas [01Aug2019 17:34:37.298] [Client thread/ERROR] [net.minecraft.util.Util/]: [01Aug2019 17:34:37.299] [Client thread/ERROR] [net.minecraft.util.Util/]: (xed:10234): Gdk-CRITICAL **: 17:34:37.298: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Quote Link to comment Share on other sites More sharing options...
DaemonUmbra Posted August 1, 2019 Share Posted August 1, 2019 Open terminal or cmd and type java -version, what shows up? 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] Link to comment Share on other sites More sharing options...
Nitrama Posted August 1, 2019 Author Share Posted August 1, 2019 java version "1.8.0_211" Java(TM) SE Runtime Environment (build 8.0.5.35 - pxa6480sr5fp35-20190418_01(SR5 FP35)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190417_414854 (JIT enabled, AOT enabled) OpenJ9 - 777635f OMR - 16b77d7 IBM - 72459d3) JCL - 20190409_01 based on Oracle jdk8u211-b25 Quote Link to comment Share on other sites More sharing options...
DaemonUmbra Posted August 1, 2019 Share Posted August 1, 2019 Yeah you need HotSpot Java, OpenJ9 isn't compatible with the hacky stuff Forge does. https://adoptopenjdk.net 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] Link to comment Share on other sites More sharing options...
Nitrama Posted August 1, 2019 Author Share Posted August 1, 2019 Which version should I use? OpenJDK 8 (LTS) OpenJDK 11 (LTS) OpenJDK 12 (Latest) Quote Link to comment Share on other sites More sharing options...
Nitrama Posted August 1, 2019 Author Share Posted August 1, 2019 OpenJDK 8 (LTS) it works Thanks ? Quote Link to comment Share on other sites More sharing options...
DaemonUmbra Posted August 1, 2019 Share Posted August 1, 2019 8 is what Minecraft targets 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] Link to comment Share on other sites More sharing options...
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.