[1.8] Easy way to replace blocks?

[veggis]

Do anyone know if there's a method to get a list of blockpos between chords? Basically like getEntitiesWithinAABB - but for blocks? What im trying to do is to find an easy way to replace them. Thanks 

 

 

[Draco18s]

It's called a for-loop.

 

for(x -10 to 10) {
  for(y -10 to 10) {
    for(z -10 to 10) {
      BlockPos pos = new BlockPos(x,y,z)
    }
  }
}

Pseudocode, of course.

[veggis]

I got it to work with this:

 

  @Override
  public ItemStack onItemRightClick(ItemStack itemStack, World world, EntityPlayer player)
  {
	if(!world.isRemote) {
		EntityPlayerMP entityplayermp = (EntityPlayerMP)player;
		MovingObjectPosition movingobjectposition = this.getMovingObjectPositionFromPlayer(world, entityplayermp, true);
		if (movingobjectposition != null && movingobjectposition.typeOfHit == MovingObjectType.BLOCK) {
			BlockPos blockpos = new BlockPos(movingobjectposition.getBlockPos());
			int x = blockpos.getX();
			int y = blockpos.getY();
			int z = blockpos.getZ();
			for(int i = 0; i < 10; ++i) {
				for(int j = 0; j < 10; ++j) {
					for(int k = 0; k < 10; ++k) {
						x = blockpos.getX() + i;
						y = blockpos.getY() + j;
						z = blockpos.getZ() + k;
						BlockPos pos = new BlockPos(x,y,z);
						world.destroyBlock(pos, true);
						System.out.println(blockpos);
						}
					}
				}
			}
		}
	return itemStack;
}

 

Next step is to destroy blocks relative to where the player is facing. Thanks

[jabelar]

[quote name="Draco18s" post="147117" timestamp="1426176890"]
It's called a for-loop.

 

By the way, BlockPos now provides a cool function called getAllInBox() which returns an Iterable with all the BlockPos within a 3-D region.  You'd still use a for loop to go through it, but coding-wise it is a bit cleaner to use an iterator for the looping as you don't need to nest the loops.

[Draco18s]

By the way, BlockPos now provides a cool function called getAllInBox() which returns an Iterable with all the BlockPos within a 3-D region.  You'd still use a for loop to go through it, but coding-wise it is a bit cleaner to use an iterator for the looping as you don't need to nest the loops.

 

I had no idea, that's awesome.