Repository navigation
Why "incorrect_for_wooden_tool"? #987
Description
Activity
Can confirm, it's probably due to how it was automatically generated, 1.20.5 added the #incorrect_for_wooden_tool tag, and since block-data never supported more than one material, for some reason it picked the new one instead of the correct "mineable/pickaxe", it's weird this hasn't been addressed yet.
The unit tests on prismarine-block should have caught this, except the test that would have found it is only done for '1.17', 'bedrock_1.17.10', 'bedrock_1.18.0', '1.20'. And the one test that is done on 1.20.5 only checks for breaking stone which is correct for a wooden pickaxe and thus unaffected by this issue.
Submitted a data-level fix as #1193 — flips
materialfromincorrect_for_wooden_tooltomineable/pickaxeon the 800+ blocks that have a populatedharvestToolsfield, which restores vanilla-accurate dig times without changing the harvest gate. Covers 1.20.5-1.21.11.Hello. I've implemented fix in data-generator
PrismarineJS/minecraft-data-generator#71
I've used most obvious fix and don't know if it's rightReacted by Vasilis
Since version 1.20.5 in data/pc/**/block.json for some blocks in the "material" property it says "incorrect_for_wooden_tool".
I just want to know the reason.
Is it possible to just insert "mineable/pickaxe"? (: