[1.7.10] Placing a vanilla block using my mod but making it unbreakable

[American2050]

How would it be the way to place a Minecraft Vanilla block in my world, using my mod, but making that block unbreakable?

 

I tried something, but I end up with all the blocks of that type on my world been unbreakable, so I guess I overwrote the original block somehow.

[Failender]

use BreakEvent, if the block is "ur block" cancel the event and it wont get broken

[delpi]

What it sounds like you want to do is to place a regular 'dirt' block, but this dirt block is unbreakable.

 

If you want to do that for any vanilla block, you will have to keep a list of the BlockPos and check against it when BreakEvent happens.  That could get ugly fast depending how many of these you set.

 

 

If you only have a small list of blocks you want to do this with, you could create your own block that uses the same image and display name as the vanilla blocks and it would be cleaner.

 

[American2050]

Well, I know I got it wrong, but.... Why something like this doesn't do the trick?

 

Block dirt = Blocks.dirt.setHardness(-1F);

 

And I use that dirt? I know that doesn't work but....

 

What if I do that, then I place the blocks, and after placing the blocks I back dirt to it's original hardness? Would that be a bad thing also?

[Abastro]

So you want to make it so that all blocks with the block type are unbreakable?

[jabelar]

I think you're missing an important point about how Minecraft handles blocks. There is only every one instance of each block. This is because in a Minecraft world there are millions of block positions and so instantiating the class for each position would cause memory and performance problems. So instead, the blocks in the world are actually not separate blocks, but instead are actually a map of positions of types of blocks.

 

This means that if you change anything in the block class it will affect all the blocks of the same type in the world.

 

However, there are certain things that happen based on the block position. For example, breaking a block obviously only happens to the position you're hitting. So what you need to do, as suggested above, is to somehow remember (probably with a list of block positions) all the positions of unbreakable blocks you want. Then you need to handle the block breaking event and check if the block the player is trying to break matches a position on your list of unbreakable blocks. If it is on the list, then cancel the event so the block doesn't actually break.

 

Anyway, the key point is that you can't change the block instance because that will affect all the blocks in the world.

[American2050]

I think you're missing an important point about how Minecraft handles blocks. There is only every one instance of each block. This is because in a Minecraft world there are millions of block positions and so instantiating the class for each position would cause memory and performance problems. So instead, the blocks in the world are actually not separate blocks, but instead are actually a map of positions of types of blocks.

 

This means that if you change anything in the block class it will affect all the blocks of the same type in the world.

 

However, there are certain things that happen based on the block position. For example, breaking a block obviously only happens to the position you're hitting. So what you need to do, as suggested above, is to somehow remember (probably with a list of block positions) all the positions of unbreakable blocks you want. Then you need to handle the block breaking event and check if the block the player is trying to break matches a position on your list of unbreakable blocks. If it is on the list, then cancel the event so the block doesn't actually break.

 

Anyway, the key point is that you can't change the block instance because that will affect all the blocks in the world.

 

Thanks a lot for the perfect explanation

 

[Draco18s]

Block dirt = Blocks.dirt.setHardness(-1F);

 

And I use that dirt? I know that doesn't work but....

 

Your

Block dirt

there is the same object as

Blocks.dirt

, you didn't create anything new with that code.

Because setHardness looks like this:

 

public Block setHardness(float val) {
   this.hardness = val;
   return this;
}