It would be beneficial if there existed an info command that could display some stats about data in the intermediary format.

The protocol version, display name and optional note will be stored in a new struct called MetaData. This data will be stored under the field name metadata.

Things I'm thinking about:

• [x] protocol version
• [x] display name (defaults to protocol version if none is set)
• [x] optional note
• [x] amount of blocks and properties (per type)
• [x] healthcheck to make sure there are no gaps in blockstate ids

Previously, the intermediary command was inside the blocks::intermediary module. This isn't very useful when thinking of the goal of not only supporting blockstates. Hence this pull request moved this command into a separate crate::cmd module.

Currently, the deserialization of the raw data uses some very complex types (Option<LinkedHashMap<&str, Vec<&str>, RandomState>> for example). This pull request is meant to better abstract this away and provide a more readable implementation of this deserialization.

These are the required steps:

• [x] The subdirectory modern under raw isn't required yet until we have a good plan how to tackle 1.8-1.12.2 versions, I would remove this folder for the time being
• [x] There is currently a Deserialize implementation for RawBlockList. This data is again a quite complex type and should be abstracted away. I would also like RawBlockList to be pretty much equivalent to ModernBlockList so the conversion is instant.
• [x] Ideally we should implement some unit tests for all the deserialization and parsing.

With the discovery of DeserializeSeed I see a lot of room for improvement of the current code:

• [x] Instead of manually checking for property collisions after deserializing, this should happen during deserializing.
• [x] Instead of applying property collision rules after deserializing, these rules should be applied during deserialization.

The way a block list generated by Minecraft should be processed by the intermediary command is the following:

1. Check if a rule file was given as an option
2. Deserialize the data into a list of property collisions, (using the provided rules if present)
3. If there are collisions present, display these and exit
4. If no collisions are present, deserialize the data into the compact format, (using the provided rules data if present)
5. Write the compact format to the output (console or file) and exit

This subcommand should be able to compare two data versions (block data for now).

A few requirements:

• [x] one directional comparison (i.e. from a version to another version)
• [ ] easy to read summary of the incompatibilities
• [ ] interactive menu for specifying compatibility fixes (although I think it's better if that was done in a different pr, feels like a separate topic to me)

First gonna figure out the ways block data can cause incompatibilities and list these here as well.