Hi,

I am trying to make a Mod which uses just one Block ID to store all the different blocks, but since the Metadata is just 4 bits of information it wont be easy to save 30 different Blocks in one ID. I would like to know if this number will automatically increase when I use a Tileentity (or do I need to do something in it to make this happen?)

Also some of the blocks should have a normal Tileentity and some should not.

What can I do to make a Block with more than 16 Subblocks and with advanced functions on some of them?

And please don't just write "Make a Tileentity", because this wont help.

 

Busti

 

//Don't recognize my english!

Hi,

I am trying to make a Mod which uses just one Block ID to store all the different blocks, but since the Metadata is just 4 bits of information it wont be easy to save 30 different Blocks in one ID. I would like to know if this number will automatically increase when I use a Tileentity (or do I need to do something in it to make this happen?)

Also some of the blocks should have a normal Tileentity and some should not.

What can I do to make a Block with more than 16 Subblocks and with advanced functions on some of them?

And please don't just write "Make a Tileentity", because this wont help.

 

Busti

 

//Don't recognize my english!

why would you need them all to have the same ID?

 

 

If you want 30 sub blocks of the same block and don't want to use an TileEntity I guess you have to invent your own system for handling them then, since Minecraft only stores metadata + blockID of a given block at a location inn the world and nothing more, except a TileEntity if it has one.

 

Normaly I would have said create a TileEntity and make it do everything for you and behave differently depending on the subtype but since you don't want that answer I guess my only answer can be this:

 

Invent your own system for handling it.

why would you need them all to have the same ID?

 

 

If you want 30 sub blocks of the same block and don't want to use an TileEntity I guess you have to invent your own system for handling them then, since Minecraft only stores metadata + blockID of a given block at a location inn the world and nothing more, except a TileEntity if it has one.

 

Normaly I would have said create a TileEntity and make it do everything for you and behave differently depending on the subtype but since you don't want that answer I guess my only answer can be this:

 

Invent your own system for handling it.

I would like to use a TileEntity but some of the blocks even have an inventory or a special function and i don't know how to handle that inside the TileEntity.

I would like to use a TileEntity but some of the blocks even have an inventory or a special function and i don't know how to handle that inside the TileEntity.

I would like to use a TileEntity but some of the blocks even have an inventory or a special function and i don't know how to handle that inside the TileEntity.

 

Given that TileEntity blocks extend BlockContainer (not Block) and that CHESTS are tile entities....

I would like to use a TileEntity but some of the blocks even have an inventory or a special function and i don't know how to handle that inside the TileEntity.

 

Given that TileEntity blocks extend BlockContainer (not Block) and that CHESTS are tile entities....

I would like to use a TileEntity but some of the blocks even have an inventory or a special function and i don't know how to handle that inside the TileEntity.

Given that TileEntity blocks extend BlockContainer (not Block) and that CHESTS are tile entities....

 

I know how to make an inventory...

But i don't know how to handle that in combination with the different Metadata

I would like to use a TileEntity but some of the blocks even have an inventory or a special function and i don't know how to handle that inside the TileEntity.

Given that TileEntity blocks extend BlockContainer (not Block) and that CHESTS are tile entities....

 

I know how to make an inventory...

But i don't know how to handle that in combination with the different Metadata

I'm in a similar boat so just replying to keep this thread alive.

 

I don't mind using tile entites, but I heard they are more RAM intensive. What uses more RAM between 16 individual blocks, and one tile entity with 16 blocks?

 

If it's not that big a deal, anyone got a good link for tile entity tutorial? Looks like both myself and the OP could do with a read through of it. The one on the wiki is incomplete.

I'm in a similar boat so just replying to keep this thread alive.

 

I don't mind using tile entites, but I heard they are more RAM intensive. What uses more RAM between 16 individual blocks, and one tile entity with 16 blocks?

 

If it's not that big a deal, anyone got a good link for tile entity tutorial? Looks like both myself and the OP could do with a read through of it. The one on the wiki is incomplete.

TileEntity's aren't as big and nasty as they may sound like, they are just objects where the code get's executed regulary (During it's Update() call) and on interaction (When it's block is clicked, destroyed, added etc.). In addition to that they can store much more data than metadata.

 

I know how to make an inventory...

But i don't know how to handle that in combination with the different Metadata

 

Well so far I'm not understanding what you are trying to do really.

You can if you want to get the metadata passed onto the TileEntity, but you can't have more than 16 blocks on the same ID using that system.

(Yes there's a way of having more *looks at redpower* but I'm sure it's a bit more advance than TileEntity's)

So why do you need 30 blocks inn 1 ID? We got a few thousand block ID's to work with now days so using two or three ain't that bad

 

Having the same TileEntity do different things upon metadata is quite simple to implement, depending on what you want them to do?

 

 

TileEntity's aren't as big and nasty as they may sound like, they are just objects where the code get's executed regulary (During it's Update() call) and on interaction (When it's block is clicked, destroyed, added etc.). In addition to that they can store much more data than metadata.

 

I know how to make an inventory...

But i don't know how to handle that in combination with the different Metadata

 

Well so far I'm not understanding what you are trying to do really.

You can if you want to get the metadata passed onto the TileEntity, but you can't have more than 16 blocks on the same ID using that system.

(Yes there's a way of having more *looks at redpower* but I'm sure it's a bit more advance than TileEntity's)

So why do you need 30 blocks inn 1 ID? We got a few thousand block ID's to work with now days so using two or three ain't that bad

 

Having the same TileEntity do different things upon metadata is quite simple to implement, depending on what you want them to do?

 

 

Do what I do and use an item to place the blocks (look at ItemBlock or ItemRedstone). Use the item damage value in a switch() statement and place the block you want accordingly. This also allows you to set metadata and TileEntity data as needed.

Sample code (do not simply copy and paste it, as it uses some of my own functions from my API):

public boolean onItemUse(ItemStack par1ItemStack, EntityPlayer par2EntityPlayer, World par3World, int x, int y, int z, int side, float par8, float par9, float par10) {
	if (!ReikaWorldHelper.softBlocks(par3World.getBlockId(x, y, z)) && par3World.getBlockMaterial(x, y, z) != Material.water && par3World.getBlockMaterial(x, y, z) != Material.lava) {
        if (side == 0)
            --y;
        if (side == 1)
            ++y;
        if (side == 2)
            --z;
        if (side == 3)
            ++z;
        if (side == 4)
            --x;
        if (side == 5)
            ++x;
        if (!ReikaWorldHelper.softBlocks(par3World.getBlockId(x, y, z)) && par3World.getBlockMaterial(x, y, z) != Material.water && par3World.getBlockMaterial(x, y, z) != Material.lava)
            return false;
    }
	AxisAlignedBB box = AxisAlignedBB.getBoundingBox(x, y, z, x+1, y+1, z+1);
	List inblock = par3World.getEntitiesWithinAABB(EntityLiving.class, box);
	if (inblock.size() > 0)
		return false;
    if (!par2EntityPlayer.canPlayerEdit(x, y, z, 0, par1ItemStack))
    	return false;
    else
    {
    	if (!par2EntityPlayer.capabilities.isCreativeMode)
           --par1ItemStack.stackSize;
        ReikaWorldHelper.legacySetBlockWithNotify(par3World, x, y, z, mod_RotaryCraft.engine.blockID);
        TileEntityEngine eng = (TileEntityEngine)par3World.getBlockTileEntity(x, y, z);
		if (eng != null) {
			par3World.playSoundEffect(x+0.5, y+0.5, z+0.5, "step.stone", 1F, 1.5F);
			eng.type = EnumEngineType.setType(par1ItemStack.getItemDamage());
		}
	}
    	int i = MathHelper.floor_double((double)((par2EntityPlayer.rotationYaw * 4F) / 360F) + 0.5D);
        while (i > 3)
        	i -= 4;
        while (i < 0)
        	i += 4;
        switch (i) {
        case 0:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 2);
        break;
        case 1:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 1);
        break;
        case 2:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 3);
        break; 
        case 3:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 0);
        break;
        }
    return true;
}

Do what I do and use an item to place the blocks (look at ItemBlock or ItemRedstone). Use the item damage value in a switch() statement and place the block you want accordingly. This also allows you to set metadata and TileEntity data as needed.

Sample code (do not simply copy and paste it, as it uses some of my own functions from my API):

public boolean onItemUse(ItemStack par1ItemStack, EntityPlayer par2EntityPlayer, World par3World, int x, int y, int z, int side, float par8, float par9, float par10) {
	if (!ReikaWorldHelper.softBlocks(par3World.getBlockId(x, y, z)) && par3World.getBlockMaterial(x, y, z) != Material.water && par3World.getBlockMaterial(x, y, z) != Material.lava) {
        if (side == 0)
            --y;
        if (side == 1)
            ++y;
        if (side == 2)
            --z;
        if (side == 3)
            ++z;
        if (side == 4)
            --x;
        if (side == 5)
            ++x;
        if (!ReikaWorldHelper.softBlocks(par3World.getBlockId(x, y, z)) && par3World.getBlockMaterial(x, y, z) != Material.water && par3World.getBlockMaterial(x, y, z) != Material.lava)
            return false;
    }
	AxisAlignedBB box = AxisAlignedBB.getBoundingBox(x, y, z, x+1, y+1, z+1);
	List inblock = par3World.getEntitiesWithinAABB(EntityLiving.class, box);
	if (inblock.size() > 0)
		return false;
    if (!par2EntityPlayer.canPlayerEdit(x, y, z, 0, par1ItemStack))
    	return false;
    else
    {
    	if (!par2EntityPlayer.capabilities.isCreativeMode)
           --par1ItemStack.stackSize;
        ReikaWorldHelper.legacySetBlockWithNotify(par3World, x, y, z, mod_RotaryCraft.engine.blockID);
        TileEntityEngine eng = (TileEntityEngine)par3World.getBlockTileEntity(x, y, z);
		if (eng != null) {
			par3World.playSoundEffect(x+0.5, y+0.5, z+0.5, "step.stone", 1F, 1.5F);
			eng.type = EnumEngineType.setType(par1ItemStack.getItemDamage());
		}
	}
    	int i = MathHelper.floor_double((double)((par2EntityPlayer.rotationYaw * 4F) / 360F) + 0.5D);
        while (i > 3)
        	i -= 4;
        while (i < 0)
        	i += 4;
        switch (i) {
        case 0:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 2);
        break;
        case 1:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 1);
        break;
        case 2:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 3);
        break; 
        case 3:
        	ReikaWorldHelper.legacySetBlockMetadataWithNotify(par3World, x, y, z, 0);
        break;
        }
    return true;
}

I want to make a system where you have only one block id to handle all of the different Blocks and SubBlockClass thingies to handle the functions of the different blocks and (optional) subtileentityclass thingies to handle the advanced stuff and the rendering for the different metadata 

I want to make a system where you have only one block id to handle all of the different Blocks and SubBlockClass thingies to handle the functions of the different blocks and (optional) subtileentityclass thingies to handle the advanced stuff and the rendering for the different metadata 

I want to make a system where you have only one block id to handle all of the different Blocks and SubBlockClass thingies to handle the functions of the different blocks and (optional) subtileentityclass thingies to handle the advanced stuff and the rendering for the different metadata

 

Nice! I look forward too see it in action

I want to make a system where you have only one block id to handle all of the different Blocks and SubBlockClass thingies to handle the functions of the different blocks and (optional) subtileentityclass thingies to handle the advanced stuff and the rendering for the different metadata

 

Nice! I look forward too see it in action

You can if you want to get the metadata passed onto the TileEntity, but you can't have more than 16 blocks on the same ID using that system.

(Yes there's a way of having more *looks at redpower* but I'm sure it's a bit more advance than TileEntity's)

So why do you need 30 blocks inn 1 ID? We got a few thousand block ID's to work with now days so using two or three ain't that bad

 

Having the same TileEntity do different things upon metadata is quite simple to implement, depending on what you want them to do?

 

RedPower's "way of having more" is TileEntities.

You can if you want to get the metadata passed onto the TileEntity, but you can't have more than 16 blocks on the same ID using that system.

(Yes there's a way of having more *looks at redpower* but I'm sure it's a bit more advance than TileEntity's)

So why do you need 30 blocks inn 1 ID? We got a few thousand block ID's to work with now days so using two or three ain't that bad

 

Having the same TileEntity do different things upon metadata is quite simple to implement, depending on what you want them to do?

 

RedPower's "way of having more" is TileEntities.

RedPower's "way of having more" is TileEntities.

And please don't just write "Make a Tileentity", because this wont help.

 

Nice! I look forward too see it in action

Challenge accepted!