Placing a pump next to compressor. Severe server permanent crash.

  • 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

Twigleaf

New Member
Jul 29, 2019
11
0
0
I have had this happen twice on our Direwolf 1.1.2 server. Once by me, and once by another player. A compressor alone, works absolutely fine. But just coincidence, I put a pump next to it, connected to a water source so i could hopefully pump water into the compressor to make snowballs & Ice. At first, I just randomly placed it there with no reason to use it with the compressor.

Anyway, the server had a sever error all of a sudden, I got the pump broke down in the game before the server finally died, but from then on, it would refuse to start ( crashlog.log posted below ). I had to use the crash log, to find the effected region chunk.... R-3-3 . Now, even with JUST the compressor still there, the server refused to boot, and would immediately crash, generating new crashlogs. Its like the pump changed the compressor into an invalid process that is terminal death for the server.
Anyway, my world backup was 1 day old, so I could either grab the working chunk from it to overwrite the bugged one, but I ended up just downloading the chunk and using MCEdit to delete the offending tile - Name: Compressor // ic2.core.block.machine.tileentity.TileEntityCompressor . Re-uploaded the chunk without the compressor, and all was well. I also had to do this with one of the players who did the similar thing. The FTB wiki mentions to place a pump next to a compressor for it to work. This was a description of my mod problem. I know these are from the IC2 pack, but I have it up to date, so something else in interacting with it that I cannot figure out. For now, all I can do is tell players not to put a pump next to a compressor. Any other thoughts or ideas on why this is happening?

Crashlog: Information
-- Head --
Stacktrace:
at ic2.core.block.machine.tileentity.TileEntityCompressor.getValidPump(TileEntityCompressor.java:126)
at ic2.core.block.machine.tileentity.TileEntityCompressor.canOperate(TileEntityCompressor.java:76)
at ic2.core.block.machine.tileentity.TileEntityStandardMachine.func_70316_g(TileEntityStandardMachine.java:141)

-- Tile entity being ticked --
Details:
Name: Compressor // ic2.core.block.machine.tileentity.TileEntityCompressor
Block type: ID #250 (blockMachine // ic2.core.block.machine.BlockMachine)
Block data value: 5 / 0x5 / 0b0101
Block location: World: (-1186,88,-1253), Chunk: (at 14,5,11 in -75,-79; contains blocks -1200,0,-1264 to -1185,255,-1249), Region: (-3,-3; contains chunks -96,-96 to -65,-65, blocks -1536,0,-1536 to -1025,255,-1025)
Actual block type: ID #250 (blockMachine // ic2.core.block.machine.BlockMachine)
Actual block data value: 5 / 0x5 / 0b0101
Stacktrace:
at net.minecraft.world.World.func_72939_s(World.java:2362)
at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:803)
 

draeath

New Member
Jul 29, 2019
456
0
0
Bug reports go here, though it's likely to be seen here as well.

It's happening because of something going wrong with this:
at ic2.core.block.machine.tileentity.TileEntityCompressor.getValidPump(TileEntityCompressor.java:126)

For some reason the code is exploding when an IC2 compressor is passed to getValidPump().
 

draeath

New Member
Jul 29, 2019
456
0
0
Nothing to apologize for, I just wanted to make sure this (nasty looking) bug got the right eyes on it ;)