Replace manual lookup.py categories with block tags?

[avdstaaij]

Minecraft uses block tags to define all kinds of block categories. These categories might be able to replace the current manual categories in lookup.py.

Advantages:

• The categories would become less arbitrary and more standardized.
• The categories could be (semi-)automatically updated for new Minecraft versions. (!)
• Various new categories, like "mineable/pickaxe", would be added.

Disadvantages:

• Lots of categories would be lost.
• There would only be categories for full block names, so no categories like WOOD_TYPES.
• This would be a substantial breaking change.

Of course, we could also include both, but the main advantage of block tag-based categories is reduced maintenance...

A JSON dataset with all blocks and their default block tags (block tags for their default BlockState) has already been created by @ShinySilver. It is available in the GDMC Discord, though currently only to members with the framework-developer role.

Should the manual categories be replaced with block tag-based categories?

[avdstaaij]

For multiple-version-support (#99), the manual categories will definitely have to go. The block tag plan outlined here would theoretically be possible, but we would have to maintain a list of all block tags for each supported version of Minecraft. I don't think it's a good idea to that in GDPC itself, but it could be viable to maintain a separate repository with this information (a-la https://github.com/SpockBotMC/python-minecraft-data, see also #89). I'll leave this open for now.