world.setBlockState() setting the wrong state?

[thebest108]

Im not sure what's going on here, I set the blockState for a position and it doesn't change the state. worldObj.setBlockState() returns true though, so it should be going through.

 

int heat = nextHeatValues.get(pos);
			if(heat>40){
				IBlockState temp = FlyingFortressBase.hotAir.getStateFromMeta(heat);
				worldObj.setBlockState(pos, temp);
				System.out.print("Ideal:"+heat+" :  Actual:"+FlyingFortressBase.hotAir.getMetaFromState(worldObj.getBlockState(pos)));
			}else{
				worldObj.setBlockToAir(pos);
			}

 

And my BlockHotAir code

 

public class BlockHotAir extends Block{

public static final PropertyInteger heatValue = PropertyInteger.create("heatValue", 0, 1024);

public BlockHotAir(Material materialIn) {
	super(materialIn);
}

@Override
    public void updateTick(World worldIn,BlockPos pos,IBlockState state,Random rand){

}

@Override
    public void onBlockAdded(World worldIn, BlockPos pos, IBlockState state){

}

@Override
    public int tickRate(World worldIn){
        return 1;
    }

@Override
public String getHarvestTool(IBlockState state){
        return null;
    }

@Override protected BlockState createBlockState() { 
	return new BlockState(this, new IProperty[] {heatValue}); 
}

@Override
public IBlockState getStateFromMeta(int meta){
    return getDefaultState().withProperty(heatValue, meta);
}

@Override
public int getMetaFromState(IBlockState state){
    int i =  (Integer) state.getValue(heatValue);
    return i;
}

}

 

The getStateFromMeta and getMetaFromState are working properly, yet the values on

 

IBlockState temp = FlyingFortressBase.hotAir.getStateFromMeta(heat);

worldObj.setBlockState(pos, temp);

System.out.print("Ideal:"+heat+"Actual:"+FlyingFortressBase.hotAir.getMetaFromState(worldObj.getBlockState(pos)))

 

don't match. I have no idea how to get around the game not setting the blockstate properly D:

 

 

Also I've tried doing worldObj.setBlockToAir(pos) and then setting the state, and it's still wrong

[thebest108]

oh >.<

 

Well in that case how can I make a blockstate that holds more than 16 possibilities?

[Choonster]

You can store more than 16 combinations of property values if you store values in a

TileEntity

and override

Block#getActualState

to return the values from the

TileEntity

, but this is mainly useful if the block's model depends on data in the

TileEntity

. You can't use

World#setBlockState

to set the values of properties that aren't stored in the metadata.

 

In this case, you should just store the heat value in a

TileEntity

and forget about the blockstate.

[jeffryfisher]

Do you really need 1024 distinct states, and do you need to store them in the world? Won't your blockstates file then have 1024 cases? 

 

Can you get away with having 16 cases? If you're doing some physics, can you translate 16 states into 16 representative int values?

[thebest108]

No this is for simulating gas spread inside of blimp balloons. If there really isnt a way to store more than 16 states then I'll just program my own storage system.

[Draco18s]

No this is for simulating gas spread inside of blimp balloons. If there really isnt a way to store more than 16 states then I'll just program my own storage system.

 

Have fun with that. Having done chunk-level saved data myself, there are a lot of pitfalls.