Jump to content

Jinks Bot

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by Jinks Bot

  1. Alright, I give up! I've been adding and removing mods for 2 days straight now. Sometimes the error goes away when I remove a mod then stays away when I re-add it. Sometimes a mod I had previously ruled out suddenly is involved. It seems to be totally random.
  2. Yeah, I thought of that already. The create contraption was wholly self-contained and the router moves blocks from a drawer to a chest on a hopper (both of which I've changed already for other blocks to be sure.) The only common blocks surrounding both are minecraft:grass_block and minecraft:air by now. Edit: This is getting curiouser and curiouser. The modular router wirelessly feeds ores from a drawer into a Immersive Engineering crusher. When I feed directly into the crusher, the NPE happen when I turn the router on, when i feed into a hopper that feeds into the crusher, the NPE happens when I turn the the router off...
  3. It's not a ghost block, The create contraption was built on a clean area that was only grass before. Removing create from the pack reduced the frequency of the NPE from twice a second to once every five seconds. The modular router in the mining dimension still reliably causes it when turned on. (I even moved it around so it's not touching any other block.) I even changed source and target of the router without success.
  4. It's one candidate. In another area I can trigger the same NPE by turning a Modular Router on and off. In another area I can trigger it by breaking and placing a Tinkers' seared tank with lava in it. All I could find out so far is, it's got "something" to do with block updates and it's not the specific mod doing the update that causes the error. The problem with bisecting the pack as a whole is the large number of interdependencies between mods. Turn off the wrong group of mods and you won't be able to load the world any more.
  5. I do not. The modpack is All The Mods 7 (with a few gameplay mods added on top, but I could reproduce it with plain ATM7 as well). The server is completely unaware of anything being amiss. I posted a quick capture of the bug in action at https://imgur.com/a/FMrMVvL. You can see the "short form" of the NPE popping up as soon as the small create contraption enters render distance and stopping when i move back a bit. I also have no idea what causes it to either log a full stack trace or just the short NPE, a factor seems to be how long I am in the area.
  6. Removed all 6 (and KubeJS' dependents ofc), but the error remains the same.
  7. Since a few versions the client in a multiplayer game is throwing repeated NPEs during light updates. I could not track it down to a specific mod yet, but two occasions where I can reliably reproduce it are turning on a Modular Router (when the lasers show, the NPE pops up) or putting lava into a Dimensional Storage tank. There are more occasions though that are not as easy to track down. Another occasion was to do with a Create gearbox. Removing that one gearbox (out of 7) stopped the NPEs from happening in that area, all the other ones had no impact. I've already tried disabling client mods having specifically to do with rendering or with light, but with no success so far. (And before anyone asks, it's not Java 18. I did a test run with Java 17 and the error is identical.) A full log is at https://mclo.gs/I4QMjFH - with the offending error here, beginning with [06:15:36] [Render thread/ERROR] [minecraft/BlockableEventLoop]: Error executing task on Client java.lang.NullPointerException: Cannot invoke "net.minecraft.world.level.block.state.BlockState.m_60734_()" because "p_46606_" is null After a while I don't get a fill stack trace any more, just [05:20:50] [Render thread/ERROR] [minecraft/BlockableEventLoop]: Error executing task on Client java.lang.NullPointerException: null This then happens over and over again, about twice per second until I leave the area. Searching the internet for `"net.minecraft.world.level.block.state.BlockState.m_60734_()"` nets very few results. Right now I'm mainly concerned with tracking down the offending mod in the first place.
×
×
  • Create New...

Important Information

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