OaKleYz 1 Posted November 21, 2020 (edited) [20Nov2020 21:44:18.861] [Worker-Main-13/ERROR] [net.minecraft.util.Util/]: Caught exception in thread Thread[Worker-Main-13,5,main] java.lang.NullPointerException: null at net.minecraft.world.lighting.SectionLightStorage.func_215521_h(SourceFile:96) ~[?:?] at net.minecraft.world.lighting.LightEngine.func_215471_c(LightEngine.java:129) ~[?:?] at net.minecraft.world.lighting.LevelBasedGraph.func_215469_a(LevelBasedGraph.java:122) ~[?:?] at net.minecraft.world.lighting.BlockLightEngine.func_215623_a(BlockLightEngine.java:118) ~[?:?] at net.minecraft.world.lighting.WorldLightManager.func_215573_a(SourceFile:41) ~[?:?] at net.minecraft.world.server.ServerWorldLightManager.func_215579_a(SourceFile:135) ~[?:?] at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625) ~[?:?] at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:658) ~[?:?] at net.minecraft.world.server.ServerWorldLightManager.func_223117_a(SourceFile:135) ~[?:?] at net.minecraft.world.server.ServerWorldLightManager.func_215603_b(SourceFile:170) ~[?:?] at net.minecraft.world.server.ServerWorldLightManager.func_223124_c(SourceFile:155) ~[?:?] at net.minecraft.util.concurrent.DelegatedTaskExecutor.func_213148_e(SourceFile:94) ~[?:?] at net.minecraft.util.concurrent.DelegatedTaskExecutor.func_213145_a(SourceFile:137) ~[?:?] at net.minecraft.util.concurrent.DelegatedTaskExecutor.run(SourceFile:105) ~[?:?] at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1429) ~[?:?] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) ~[?:?] at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016) ~[?:?] at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665) ~[?:?] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598) ~[?:?] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183) ~[?:?] I am able to explore my server multiplayer world just fine for several minutes and then all the sudden it'll hang and crash. The same thing happens when I use a mod to try and pregen the world. Each seed I try seems to have a specific spot where the server just can't load a chunk and then it'll just always crash when I get close to it. The above error is what I see in the console before the server watchdog kicks in. The attached crash report is what is given but I don't know that it's helpful because it seems to just talk about the watchdog event. I have been testing out the mods you see in the crash report and everything works great with the exception of this occasional error. I am ready to start using the modpack but now I am afraid to explore the world Edit: Debug log: https://gist.github.com/aharrisw/90dc31749c3448e9e726ccc58960c1c9 crash-2020-11-21_02.10.15-server.txt Edited November 21, 2020 by OaKleYz Added debug log link Quote Share this post Link to post Share on other sites
DaemonUmbra 534 Posted November 21, 2020 The amount of data loading exceptions in this log is disgusting. Remove Engineers Tools, start the server, stop the server, and provide debug.log again 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. Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch'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] Share this post Link to post Share on other sites
OaKleYz 1 Posted November 21, 2020 (edited) New debug log: https://gist.github.com/aharrisw/02a6dd742dce96ddad05a5b0d2dfa41f I only removed Engineers Tools but I assume I should also take out Engineers Decor now that I look at the log. I had Immersive Engineering in the pack at one point but took that out and I guess these two Engineers mods were related. Edited November 21, 2020 by OaKleYz Quote Share this post Link to post Share on other sites
OaKleYz 1 Posted November 21, 2020 I am able to keep duplicating. It's random as to when it happens but after a few minutes of exploring, the same error will occur. This time the server watchdog didn't even close it, the server just sat there. Debug log: https://gist.github.com/aharrisw/50ccb8afb357da248eb22889594384cf Quote Share this post Link to post Share on other sites
OaKleYz 1 Posted November 23, 2020 Any thoughts by chance? Quote Share this post Link to post Share on other sites
diesieben07 7610 Posted November 23, 2020 The only thing I can gather from that log is that the last thing generating something seems to be Dungeon Crawl. This generation produces a bunch of warning and error log and then the game crashes. So I would try it without that mod. Quote Share this post Link to post Share on other sites
OaKleYz 1 Posted November 27, 2020 I tried without Dungeon Crawl and then also removed others like Ice and Fire / Quark since they also do their own structure generation. It still ends up crashing. I've given up :shrug: Quote Share this post Link to post Share on other sites
OaKleYz 1 Posted December 2, 2020 I've finally been able to get the world to stop crashing while loading chunks. One of the crashes gave me coordinates (see below) and with WorldEdit using the //distr command it was able to tell me that Sky Stone blocks were around there. So, I disabled meteorites (which is what Sky Stone is used for) in the applied energistics config file and re-loaded the same seed without those meteorites. I'm not sure if it was clashing with another generation mod or why meteorites were the problem but I'm glad I have a workaround. I'll probably submit something to AE to see if they can see what's going on. Example message related to coordinates for documentation purposes: [20Nov2020 21:39:59.208] [Worker-Main-9/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:39:59.225] [Worker-Main-9/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:39:59.235] [Worker-Main-19/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:39:59.954] [Worker-Main-9/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:39:59.963] [Worker-Main-9/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:39:59.984] [Worker-Main-13/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:00.661] [Worker-Main-10/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:00.682] [Worker-Main-10/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:00.704] [Worker-Main-10/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:01.508] [Worker-Main-8/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:01.527] [Worker-Main-8/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:01.542] [Worker-Main-9/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:02.121] [Worker-Main-8/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:02.134] [Worker-Main-8/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} [20Nov2020 21:40:02.146] [Worker-Main-8/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=-190, y=56, z=-384} Quote Share this post Link to post Share on other sites
DaemonUmbra 534 Posted December 3, 2020 Please provide a fresh debug.log any time you change something about the game 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. Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch'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] Share this post Link to post Share on other sites
OaKleYz 1 Posted December 3, 2020 My reply was to say the issue is resolved from this forums perspective. I no longer see the issue happening. Thanks for the help. Quote Share this post Link to post Share on other sites
