Of course, the issue isn't on Minecraft's end, it has to do with Coord4D hashing. Coord4D no longer extends BlockPos to prevent hash issues

This commit is contained in:
aidancbrady committed 2016-05-09 21:07:18 -04:00
1 parent c6f3c162f9
commit ddfe83c495
70 files changed
+458 -1032

No files matched your search

@@ -118,11 +118,11 @@ public abstract class TileEntityMultiblock<T extends SynchronizedData<T>> extend
for(EnumFacing side : EnumFacing.VALUES)
{
Coord4D obj = Coord4D.get(this).offset(side);
TileEntity tile = obj.safeTileGet(worldObj);
TileEntity tile = obj.getTileEntity(worldObj);
if(!obj.isAirBlock(worldObj) && (tile == null || tile.getClass() != getClass()))
{
obj.getBlock(worldObj).onNeighborChange(worldObj, obj, getPos());
obj.getBlock(worldObj).onNeighborChange(worldObj, obj.getPos(), getPos());
}
}
@@ -179,7 +179,7 @@ public abstract class TileEntityMultiblock<T extends SynchronizedData<T>> extend
{
for(Coord4D obj : getSynchronizedData().locations)
{
TileEntityMultiblock<T> tileEntity = (TileEntityMultiblock<T>)obj.safeTileGet(worldObj);
TileEntityMultiblock<T> tileEntity = (TileEntityMultiblock<T>)obj.getTileEntity(worldObj);
if(tileEntity != null && tileEntity.isRendering)
{