* VeinMining now activates a BlockBreakEvent for every block broken within the veinmine action
* |-> This excludes the initial block, which is fired regardless by the breaking of the block
* Changed the registration format of VeinMinable blocks. They are now contained under a separate block object
* |-> These custom block objects allow for the specification of data values
* Data values can now be specified in the block list by adding a semicolon ( and a value after the name of the material. More info in the configuration file
* With the changes to registration formats, there are more methods in the main class for API usage
* Some permission nodes have been reorganized:
* |-> "veinminer.blocklist.*" is now a parent permission and allows both of the following:
* |-> "veinminer.addBlocklist" is now veinminer.blocklist.add
* |-> "veinminer.removeBlocklist" is now veinminer.blocklist.remove