More work on EIM. Found some inconsistency/incomplete mechanics in the new multiblock system, no longer should be an issue

This commit is contained in:
Aidan C. Brady committed 2015-03-03 00:15:18 -05:00
1 parent 1c0fe96fed
commit 978e0801fa
9 files changed
+70 -35

No files matched your search

@@ -22,19 +22,19 @@ import io.netty.buffer.ByteBuf;
public abstract class TileEntityMultiblock<T extends SynchronizedData<T>> extends TileEntityContainerBlock implements IMultiblock<T>
{
/** The tank data for this structure. */
/** The multiblock data for this structure. */
public T structure;
/** Whether or not to send this tank's structure in the next update packet. */
/** Whether or not to send this multiblock's structure in the next update packet. */
public boolean sendStructure;
/** This tank's previous "has structure" state. */
/** This multiblockblock's previous "has structure" state. */
public boolean prevStructure;
/** Whether or not this tank has it's structure, for the client side mechanics. */
/** Whether or not this multiblock has it's structure, for the client side mechanics. */
public boolean clientHasStructure;
/** Whether or not this tank segment is rendering the structure. */
/** Whether or not this multiblock segment is rendering the structure. */
public boolean isRendering;
public TileEntityMultiblock(String name)