Add custom data tagging support

[luvies]

trafficstars

I plan to add support for using the custom data of blocks to add tags. This is how I plan for it to work currently:

• TIM-managed blocks will still require at least the [TIM] tag
  • This might require disallowing prefixes of nothing, as this would mean tags could be []
• Item tags in the name will still work, and will override anything in the custom data
• Custom data will apply extra item tags to the block, making sure to follow the point above

[pckroon]

Item tags in the name will still work, and will override anything in the custom data

This is going to be tricky. What's the outcome of the following? Name: [TIM components:200] Custom: SteelPlates:1000

[luvies]

Hmm. I will have to sort out the levels of priorities. While it makes sense to give the SteelPlates priority for being more explicit, it also makes sense to give the Component priority since the name tag feel like it should be more important.

I think that maybe the best resolution is to treat name tags as a complete override of the custom data, which in this case would mean the Component would win out. The reason for this, is that the names feel like more explicit and more of a short-term system than custom data. It also means that whatever is in the name is reflected exactly in the inventory, with the custom data only adding to it rather than modifying it.

[Flow86]

that would be awesome to have the information in custom (too?) since it will be saved into blueprints