I really don't know how else to put it.

 

This is my block class:

public class MyBlock extends Block {
    public MyBlock() {
        super(Properties.create(Material.ROCK)
        .harvestTool(ToolType.PICKAXE)
        .harvestLevel(0)
        .hardnessAndResistance(1.5f, 6f)
        .sound(SoundType.STONE)
        );
    }
}

 

Yet I can still break it with my bare hands and it will drop the block. I scorched various classes and the internet clean to try to find what was causing this, and have had no luck.

 

Could someone point me in the right direction?

 

Cheers.

Edited July 7, 20205 yr by CommandCore
Bug Fixed!

Fixed it. I have no clue why this fixes it but I added 

.func_235861_h_()

 

to my properties list like so:

 

public class MyBlock extends Block {
    public MyBlock() {
        super(Properties.create(Material.ROCK)
        .harvestTool(ToolType.PICKAXE)
        .harvestLevel(0)
        .hardnessAndResistance(1.5f, 6f)
        .sound(SoundType.STONE)
                        .func_235861_h_()
        );
    }
}

 

And now everything functions like it's supposed to. This is 1.16.1 by the way. Sorry for the unsupported version but hey, there ya go for anyone that has having trouble in the beta version. 👍

 

Edit: Don't know why I didn't test this before posting, but it fixed the bare hand mining thing, but still can be harvested outside of a given harvest level (I put the method on a different block with a higher harvest level.) Still need help!

Edited July 2, 20205 yr by CommandCore
Found that the issue still exists.

harvestLevel and harvestTool still need to be reevaluated. Until then, they will not work.

13 hours ago, ChampionAsh5357 said:

harvestLevel and harvestTool still need to be reevaluated. Until then, they will not work.

Darn. Well, at least I know what's causing it, thanks man.

 

I guess the thread can stay open until its fixed? Or would that be necrobait? Or how does that work for things that don't have solutions at the moment, sorry I'm new here.

5 minutes ago, CommandCore said:

I guess the thread can stay open until its fixed? Or would that be necrobait? Or how does that work for things that don't have solutions at the moment, sorry I'm new here.

Here is a forum. It operates under "forum" rules: threads stay "open" by default. The only reason to close threads (as in, a moderator locks it) is if it has been necro'd or is off topic (asking for help with unsupported versions falls into "off topic").

 

I don't know why so many people think that this place operates likes Stack Overflow.

1 hour ago, Draco18s said:

Here is a forum. It operates under "forum" rules: threads stay "open" by default. The only reason to close threads (as in, a moderator locks it) is if it has been necro'd or is off topic (asking for help with unsupported versions falls into "off topic").

 

I don't know why so many people think that this place operates likes Stack Overflow.

Sounds good, thanks for the info! 😁

Bug Fixed!

 

 

Build: 1.16.1-32.0.55 - Mon Jul 06 21:12:45 GMT 2020
	richard:
		Fix harvest level and tool type not actually getting set #6906 (#6922)

 

Just make sure to keep .func_235861_h_() in the properties and your harvest levels and tool types will work like a charm. 😉

 

Thanks Richard!

This was a problem for me as well in Minecraft 1.16.1, and Forge 32.0.98. The

func_235861_h_()

 solved the issue.

Edited August 2, 20205 yr by Karutoh

Update your mappings guys, the unmapped function func_235861_h_() is now setRequiresTool().

On 8/2/2020 at 5:52 AM, Beethoven92 said:

Update your mappings guys, the unmapped function func_235861_h_() is now setRequiresTool().

Looks like it's .requiresCorrectToolForDrops() now.