Class BlockState

The main thing you need to know about block states is that the object is in fact immutable. Each object has a runtime ID. Each runtime ID refers to a block state object with a specific combination of property values. If you change the value of a property, for example using BlockState.setValue method, it is not changed in the object, but another object with another runtime ID and needed property values combination is returned.

This also means that if you want to change the value of a block property on specific coordinates in the world, you have to call BlockSource.setBlockState with an object obtained after changing the value of a property.

Example:

// suppose that the block we are getting is an anvil,
// not checking not to distract you
const anvil = world.getBlockState(x, y, z);

// as ANVIL_DAMAGE is a property of Java enum type,
// convert it to integer type to work with it in JS/TS
const ANVIL_DAMAGE_INT = KEX.VanillaStates.ANVIL_DAMAGE.toIntegerProperty();

// getting anvil damage value
const damageValue = anvil.getValue(ANVIL_DAMAGE_INT);
// if anvil is damaged
if(damageValue != KEX.BlockStates.AnvilDamage.UNDAMAGED) {
     // resetting anvil damage and storing
     // the returned object in the same variable
     anvil = anvil.setValue(ANVIL_DAMAGE_INT, KEX.BlockStates.AnvilDamage.UNDAMAGED);
     // setting the modified block state in the world (mandatory if changes made)
     world.setBlockState(x, y, z, anvil, 0);
}

One more important thing to note is that a certain block with specific ID cannot store any block property by default. If you are initializing a block which you want to hold some properties, you have to specify them all using BlocksModule.registerStateForBlock method, providing block's numeric ID and property object.

Since this class released in KEX 5.0, InnerCoreBlockState was replaced with KEX's BlockState everywhere it was used.