[Solved] [1.7.10] Make a block drop itself?

[IceMetalPunk]

I have a block called BlockWeatherDetector. I want it to be harvestable with any tool, including an empty hand, and drop itself when harvested. I thought it would be as simple as calling .setHarvestLevel(null, 0) and setting .getItemDropped() to return the item obtained from the block class, but it's not working. In survival mode, with tile drops turned on, if I break the block without a pickaxe...it doesn't drop anything. Am I doing something wrong?

 

Constructor:

protected BlockWeatherDetector() {
	super(Material.iron);
	this.setCreativeTab(CreativeTabs.tabRedstone).setHardness(0.5F);
	this.setStepSound(Block.soundTypeMetal).setBlockName("weatherDetector");
	this.setBlockTextureName("weatherworks:weather_detector").setHarvestLevel(null, 0);
}

 

getItemDropped:

	@Override
public Item getItemDropped(int metadata, Random rand, int fortuneLevel) {
	Item item=Item.getItemFromBlock(WeatherWorks.weatherDetector);
	System.out.println("Item dropped: "+item);
	return item;
}

 

Intantiation/Registration (in WeatherWorks.java):

public static final BlockWeatherDetector weatherDetector = new BlockWeatherDetector();
// ...skipping irrelevant code...
GameRegistry.registerBlock(weatherDetector, "weather_detector");

 

The console log is never output unless using a pickaxe, so I know getItemDropped() isn't even being called when breaking it with your hand.

 

What am I doing wrong?

[ovikk]

You're calling setHarvestLvl() after the setBlockTextureName() with a dot. Not good. It should be like this:

 

this.setHarvestLvl(CODE);

NOT

this.setBlockTextureName(CODE).setHarvestLvl(CODE);

 

Btw, why do you want material iron? If you want the step sound, you can get it from soundTypeIron in setStepSound(); Material iron sets the harvest lvl to pickaxe..

[IceMetalPunk]

I actually did have it separate; I only chained them up here for shorter code. I'm 100% sure (because I just checked) that those property-setting methods, including setTextureName(), are chainable (they return the instance itself). Either way, even if I split it, it doesn't fix the problem.

 

As for the material, I want iron pickaxes and better to harvest it faster, but I still want it harvestable overall with anything, including a hand. I thought setHarvestLevel() would override that; if not, do I need to use a different material and then override isToolEffective()? If I do that, how can I get the level (wood, gold, iron, diamond, etc.) of the tool, since it looks like that method only takes the type and the metadata?

[Draco18s]

I actually did have it separate; I only chained them up here for shorter code. I'm 100% sure (because I just checked) that those property-setting methods, including setTextureName(), are chainable (they return the instance itself). Either way, even if I split it, it doesn't fix the problem.

 

This is correct.  You can chain them, but its not good practice to do it in the constructor.

 

As for the material, I want iron pickaxes and better to harvest it faster, but I still want it harvestable overall with anything, including a hand. I thought setHarvestLevel() would override that; if not, do I need to use a different material and then override isToolEffective()? If I do that, how can I get the level (wood, gold, iron, diamond, etc.) of the tool, since it looks like that method only takes the type and the metadata?

 

For iron picks to harvest it faster all you have to do is nothing.  Iron will automatically be faster than stone, than wood, than by hand.

 

That said, there's three options:

1) Override

getHarvestTool

and return null.  This will say "this block is always harvestable."

2) Override

getDrops

which will let you drop the item, "harvested" or not.

3) Override

getPlayerRelativeBlockHardness

which will let you dictate how long it takes to break.  Note: this will be the hardest method.