Skip to main content

Tile Entities

Make a tile entity that kills nearby mobs.

A tile entity is a simplified version of an entity that is bound to a specific block the the world. It knows its position, can react to ticks and saves data when the world is reloaded. Some vanilla examples are chests, furnaces and beacons.


Start by making a block for your tile entity. It will have its own class just like we made for other advanced blocks in the last tutorial.

public static final RegistryObject<Block> MOB_SLAYER = BLOCKS.register("mob_slayer",
() -> new MobSlayerBlock(Block.Properties.copy(Blocks.IRON_BLOCK)));

Then you will need to register your tile entity. Make a new class called TileEntityInit. We will start by getting a deferred register just like for blocks and items.

public class TileEntityInit {
public static final DeferredRegister<TileEntityType<?>> TILE_ENTITY_TYPES = DeferredRegister.create(ForgeRegistries.TILE_ENTITIES, FirstModMain.MOD_ID);

Then register your tile entity. The string you pass in is the registry name which can be anything you want (all lower case, no weird characters as usual). Then you need a supplier for a TileEntityType which has a builder to use. The builder takes a supplier to make new instance of your tile entity. For this, use a method reference to the constructor of your tile entity class (we'll make this class in the next step). Then you need to tell it the types of blocks that your tile entity is allowed to be bound to. I'll just have one (the block we made earlier) but you can have multiple, just separate them with commas. Then we call the build method of the builder to get the type.

public static final RegistryObject<TileEntityType<MobSlayerTile>> MOB_SLAYER = TILE_ENTITY_TYPES.register("mob_slayer",
() -> TileEntityType.Builder.of(MobSlayerTile::new, BlockInit.MOB_SLAYER.get()).build(null));

The null argument passed to the build method is a "data fixer type". Honestly, I have no idea what that means. It seems to not be used for anything and leaving it null has always worked for me. If you happen to know what it does, please let me know, I'm curious.

Like with the item and block registries, you have to tell minecraft that you're trying to register things. Add this line to the constructor of your main class:


Block Class​

There are two methods you need to override on your block to add your tile entity. hasTileEntity should simply return true and createTileEntity should return a new instance of your tile entity. I'm using the tile entity type's create method but you could directly call the constructor once you make your tile entity class).

public class MobSlayerBlock extends Block {
public MobSlayerBlock(AbstractBlock.Properties props) {

public boolean hasTileEntity(BlockState state) {
return true;

public TileEntity createTileEntity(BlockState state, IBlockReader world) {
return TileEntityInit.MOB_SLAYER.get().create();

Tile Class​

Now create the tile entity class you referenced earlier (make a new tile package to keep organized). As you may have guessed, the class will extend TileEntity. Pass your tile entity type to the super constructor.

public class MobSlayerTile extends TileEntity {
public MobSlayerTile() {


To react to ticks, your tile entity must implement ITickableTileEntity. The tick method will be called every tick.

public class MobSlayerTile extends TileEntity implements ITickableTileEntity {
public MobSlayerTile() {

public void tick() {
// do stuff here

You can do anything you want here but I want my tile entity to kill nearby monsters. I'll start by writing some logic for when to hurt the mobs.

I'll need a timer field (because I don't want to deal damage every tick, that would be too op) and an isActive field (because I want the player to be able to turn it off sometimes). So I'll check that we're on the server side (because that's where logic like dealing damage should be processed) and that the tile should be active. Then, each tick I'll increment the timer and only if 20 ticks (1 second) has passed since last time, I'll reset the timer and call a hurtMobs method (that I haven't defined yet).

int timer = 0;
boolean isActive = true;

public void tick() {
if (!this.level.isClientSide() && this.isActive){
if (this.timer > 20){
this.timer = 0;


I'll start by deciding the top left and bottom right corner of the area I want to target. I'll do this by adding the my chosen range to all the coordinates of the tile entity to get the top and subtracting to get the bottom. Then I'll make an AxisAlignedBB from these points. This represents a cube centered on my tile entity going out RANGE blocks in all 3 dimensions.

Then I'll use the world's getEntities method to get all the entities within that area of effect. The first argument is an entity to ignore (arrows use this to not hit themselves) but I want to get everything so I'll leave it null. The second argument is obviously the AxisAlignedBB to get entities within. Then I'll loop through the list it returns. For each entity, I'll check that it is living (not an arrow, item, etc) and not a player (I don't want my new tile to hurt me!). If it meets my criteria, I'll deal one heart of magic damage.

final int RANGE = 5;
private void hurtMobs() {
BlockPos topCorner = this.worldPosition.offset(RANGE, RANGE, RANGE);
BlockPos bottomCorner = this.worldPosition.offset(-RANGE, -RANGE, -RANGE);
AxisAlignedBB box = new AxisAlignedBB(topCorner, bottomCorner);

List<Entity> entities = this.level.getEntities(null, box);
for (Entity target : entities){
if (target instanceof LivingEntity && !(target instanceof PlayerEntity)){
target.hurt(DamageSource.MAGIC, 2);

Note: instead of doing that check in the for loop, I could have passed in a Predicate<Entity> which would return true only if it was something I want to target. That would probably run faster but not significantly enough to matter and I have a personal preference for how I did it.

Processing Block Interactions​

I want to be able to toggle my mob slayer on and off by right clicking the block. I'll start by making a function that will preform the toggle.

public void toggle(){
this.isActive = !this.isActive;

Then I need my block to notify my tile entity when it is right clicked. I'll override the use method as we did in the last tutorial. After checking that I'm on the server side and processing the main hand (so it doesn't get called twice), I'll get the tile entity at that position. To be safe, I'll check that it's the right type of tile entity but in practice it always will be. I'll cast it to my tile entity class and call the toggle method. For dramatic effect (and so its easier to tell that our click was processed), I'll make it play a sound as well.

public ActionResultType use(BlockState state, World world, BlockPos pos, PlayerEntity player, Hand hand, BlockRayTraceResult hit) {
if (!world.isClientSide() && hand == Hand.MAIN_HAND ){
TileEntity tile = world.getBlockEntity(pos);
if (tile instanceof MobSlayerTile){
((MobSlayerTile) tile).toggle();
world.playSound(player, player.getX(), player.getY(), player.getZ(), SoundEvents.ANVIL_LAND, SoundCategory.PLAYERS, 1.0F, 1.0F);
return ActionResultType.SUCCESS;

return super.use(state, world, pos, player, hand, hit);

NBT Data​

Currently, when I save the world and reload it, the isActive variable will default back to true. We can override a few methods to save it with the rest of the world's data.

The format Minecraft uses for most of the data it saves is called NBT (Named Binary Tag). This is basically a map of keys and values (just like a more limited version of a HashMap) that can easily be serialized to a binary representation to store in files.

In code, the class that is used for this format is CompoundNBT. There are many types of data you can store in an NBTCompound: boolean, int, String, double, float, long, an array of longs, byte, an INBT (like another CompoundNBT or a ListNBT). You've got all the primitives and more so with enough effort you can make an nbt representation for any object. The general methods to use are compoundNBT.putType(key, value), compoundNBT.getType(key) and compundNBT.contains(key). The key is always a String and the value can be any supported type (just change the method name, ie getString, etc).

Tile entities use the save method to get the data to store as a CompoundNBT when the world is saved and load to read back that nbt into normal variables. I'll use this to simply store my isActive field and read it back. Make sure to call the super methods to let Minecraft store the tile entity's base data.

public CompoundNBT save(CompoundNBT nbt) {
nbt.putBoolean("active", this.isActive);

public void load(BlockState state, CompoundNBT nbt) {
super.load(state, nbt);
this.isActive = nbt.getBoolean("active");

Note that the nbt keys id, x, y, z, ForgeData, ForgeCaps and the registry name of the tile entity type (for me that's mob_slayer) are reserved for the default data Minecraft has to store about your tile entity. Do not try to use them.

Syncing Data​

With my tile entity, I've been careful to do everything on the server side. If you're doing something more complex, you may have to sync data between the client and the server. There are a few ways to do this. I will cover examples where you need to use these in a later tutorial on doing custom rendering with a tile entity. Join the discord server to be notified when it is released.

On chunk load: getUpdateTag() returns the data that the server wants to send as a CompoundNBT. handleUpdateTag(BlockState state, CompoundNBT tag) reads it back on the client side.

On block update: gotta use a packet! (but you can use one from vanilla). getUpdatePacket is sent from the server, onDataPacket is read on the client.

public SUpdateTileEntityPacket getUpdatePacket(){
CompoundNBT nbtTag = new CompoundNBT();
// save data to nbt
return new SUpdateTileEntityPacket(this.worldPosition, -1, nbtTag);

public void onDataPacket(NetworkManager net, SUpdateTileEntityPacket pkt){
CompoundNBT tag = pkt.getNbtCompound();
// read data

To trigger that you can call world.notifyBlockUpdate(BlockPos pos, BlockState oldState, BlockState newState, int flags)

Custom packet: a more versatile solution would be to make your own packets that you can send whenever you want (not just for block updates). I will cover packets in a future tutorial. Join the discord server to be notified when it is released.


The block to which you bound your tile entity is a block like any other. Don't forget to give it a block model, item model, block state definition, loot table and lang entry.


  • Make the mob slayer we made in this tutorial directional. That is, instead of the area of effect being centered on the block, have the block rotateable from like the last tutorial and only attack mobs in the forwards direction.
  • Make a tile entity that teleports nearby mobs on top of it
    • hint: entity.setPos(x, y, z);