Ender IO Zoo

Ender IO Zoo

968k Downloads

Capacitor dropping items following chunk unload

xenoflot opened this issue ยท 5 comments

commented

Hi folks,

Running 1.7.10-2.3.0.421_beta in a custom pack on a server. I've got 3 jetpacks and I keep two in the capacitor while using the third. After returning from a distant travel (far enough to cause my base to become unloaded), I find the jetpacks that were in the capacitor are now sitting on the floor.

This appears reproduceable and affected both basic caps and vibrant.

The server map has just started so I'll be able to test/retest if/when updates are made available.

Cheers

commented

I take it that means I can send you a debug version for this?

commented

Sure, I'd be happy to help.

commented

Thx. Then please use this version: http://loenwind.info/EnderIO-1.7.10-2.3.0.422t0_beta.jar

Get it to drop some items and then find lines likes this in the logfile:

[19:57:07] [Server thread/INFO] [EnderIO]: Ordering CapBank TileCapBank [getLocation()=X: -264  Y: 56  Z: -312, inventory=[1xitem.darkSteel_leggings@0, null, null, null]] to drop items when joining Network CapBankNetwork [id=12, type=SIMPLE, inventory=InventoryImpl [inventory=[1xitem.darkSteel_leggings@0, null, null, null], capBank=TileCapBank [getLocation()=X: -264  Y: 56  Z: -314, inventory=[1xitem.darkSteel_leggings@0, null, null, null]]], capBanks=[TileCapBank [getLocation()=X: -264  Y: 56  Z: -313, inventory=[null, null, null, null]], TileCapBank [getLocation()=X: -264  Y: 56  Z: -314, inventory=[1xitem.darkSteel_leggings@0, null, null, null]], TileCapBank [getLocation()=X: -264  Y: 56  Z: -315, inventory=[null, null, null, null]], TileCapBank [getLocation()=X: -264  Y: 56  Z: -312, inventory=[1xitem.darkSteel_leggings@0, null, null, null]]]] where inventory is held by CapBank TileCapBank [getLocation()=X: -264  Y: 56  Z: -314, inventory=[1xitem.darkSteel_leggings@0, null, null, null]]
commented

Not sure what's happening. Still using 421b, it wasn't faulting in SSP so I set up a local server and that's working fine, too. Just to infuriate me, now that I'm back on the main server (hosted with Nodecraft) it's also working fine. I can only suggest that it might be client/server latency issue. There're only 2 people on the server at the moment. I'll try again later when it's busier.

commented

Don't panic, if it was easy to reproduce, we'd have found it ages ago. The game is not trying to annoy you personally ;)