So a little while back, I made this tileentity called TileEntityEnergizer and it was working great! It looked for items above it and if it found them, 'absorbed' them and created energy. Then, it would transfer the energy to a player if they stepped on it with a redstone signal. All was good. Then, one day, I decided "I want to make this a multiblock." So, I went and I added some fields and a method to check if it was surrounded by a certain type of block and such. The purpose of that was so that the multiblock would give the player more energy for each item. Now that I've talked all about my troubles, here's the problem:

 

For some reason, whenever I use this.pos or pos or pos.getX() etc... it tells me that the block is at the coordinates 0, 0, 0. This is really weird because it never used to do that. Can someone look through the class and try and help me figure out whats going on with it?

 

I'm not sure if this is the cause, but I also have a method in the block for the tileentity that prints the energy stored to the chat when you click it. Whenever this method runs, it would seem, is when the block begins to think it's at position 0, 0, 0.

 

TileEntityEnergizer: https://github.com/AnZaNaMa/ExpTools/blob/master/src/main/java/com/AnZaNaMa/ExpTools/Entity/TileEntity/TileEntityEnergizer.java

 

Energizer Block: https://github.com/AnZaNaMa/ExpTools/blob/master/src/main/java/com/AnZaNaMa/ExpTools/Block/Energizer.java

Hey,I saw that you called the check in the constructor?

now tileEntities have multiple uses(eg. Rendering datastorage etc.) Wich means it gets called multiple times in different places. On blockplacement for example, all the valeus will be default.(null or 0). so trying to get the block pos in the constructere will not work. Instead try to check all the multiblock things in the update methode.

okay, I'll try that out. Thanks for the help

So, I tried moving all of my multiblock stuff to the update function and the block position is working fine now, but I just can't figure out why it's not detecting the formation of the multiblock.

Debug.Log

 

Er

 

I mean,

System.out.println(...)