Open Game crash when pointing at Colossal Chest interface block

  • This section is closed. Please do bug reports over at the FTB GitHub repos.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
V

VeeDubRunner

Guest
Summary of the problem Game crash when pointing at Colossal Chest interface block

Pack Version 3.0.6

What is the bug? After crafting a few items, I noticed they did not show up in my Refined Storage system. I have two colossal chests attached, so i manually looked through the one they should have been in. They weren't there, so i moved to the next chest. When my cursor moved over the interface block, I was disconnected from the server (playing SSP). I relogged several times and it dc'ed every time i looked at the block. The last crash was a hard freeze with a spinning windows cursor.

Mod & Version Colossal Chests 1.5.0
Refined Storage 1.2.18

Link to log file http://paste.feed-the-beast.com/view/26497b6e

Is it repeatable? I have tried both connected and unused interfaces on wood and gold tier chests. all interface blocks in a multiblock crash the game.

Known Fix none
 

Savos

New Member
Jul 29, 2019
28
0
0
I'm curious, because I had a similar issue before, is there disks or anything that "stores" other data in there right now?
 
V

VeeDubRunner

Guest
I'm curious, because I had a similar issue before, is there disks or anything that "stores" other data in there right now?
No. I built the chests before i had a Refined storage system, so I never needed to build any drives. The only items in the chests that contain other items would be the loot bags, but they are pulled quickly by machines to be opened. No drives or other storage devices (taped up drawers, etc) are in them.
 
V

VeeDubRunner

Guest
Going to abandon this thread, as it appears the issue is happening in more than one mod. 3.0.6 has caused storage blocks with high numbers to cause an NBT overload somehow. I have successfully removed the problem by removing as many items with extra data (durability on tools, stats on chicken eggs) as I could stand to lose, but as soon as the storage begins to fill again the problem returns. Hoping for some sort of fix soon, but for now the only way to prevent it is to simply not look at the block.
 
D

Doug_W

Guest
I've been having this same problem repeatedly since I upgraded to 3.0.6 yesterday. For anyone who gets stuck in a crash loop because they crashed while looking at the interface block and now can't log in, you can use MCEdit to fix it. Open your world, click on the Players tool, and position yourself so you're not looking at the interface block. Select your player and click on Align to Camera. That'll change where your player is looking when you log in. Make sure to save changes before you exit MCEdit.

I'm not sure why, but when I do this there are two players in my single-player world; the second one appears to be a duplicate that follows me around. It might be one of the mods creating a simulated player. In any case, I make sure to move both of them at the same time so they stay lined up.
 

Quetzi

Jack of All Trades
Retired Staff
Aug 20, 2012
826
329
100
quetzi.tv
According to the Colossal Chest issue tracker there is a maxSlotsPerPacket set in the configuration, lowering this should help avoid this problem.
 
D

Doug_W

Guest
According to the Colossal Chest issue tracker there is a maxSlotsPerPacket set in the configuration, lowering this should help avoid this problem.

It looks like that config option was changed to maxPacketBufferSize, but I tried cutting that in half and I still got the crash.

EDIT: I've added a comment github.com CyclopsMC/ColossalChests/issues/40 to let the author know about this. (url mangled because I'm not allowed to post urls here yet.)
 
Last edited: