Useless code? (ItemPickaxe)

[Ernio]

ItemPickaxe when checking for getStrVsBlock() first checks if shit is Material.rock (and/or other materials) and then if it is not, it goes to super class and checks array of blocks which are exceptions.

In that array there are blocks which have alredy been checked (they have Material.rock).

I mean: If block is Material.rock then it will return efficiencyOnProperMaterial, and so why the hell they added blocks to array:

public static final Block[] blocksEffectiveAgainst = new Block[] {Block.cobblestone, Block.stoneDoubleSlab, Block.stoneSingleSlab, etc.}; which alredy are Material.rock.

 

It just seems pointless and unless it is used in other methods I want to know where I can find them (found nutnig for now).

[Draco18s]

Mojang code.  Learn to deal with it.

 

In time you will come to love it.

[Ernio]

Looking at whole mining system makes me cry man Q.Q 1000 methods for one shit

Anyway thanks for making me sure this code is trolling my brain

[Mazetar]

Try reading into basically any other system in minecraft, and you will cry a lot more!

 

[Draco18s]

Like the item function isMap() that is used by nothing (there's actually one reference, fairly obscure).

 

Maps rendering in item frames is handled by if(containedItem == Item.Map) which makes extending ItemMapBase for any reason a real annoyance.