Improve fastbreak verbose message

[SergioK29]

use consistent case, include the target block type

[SergioK29]

@ManInMyVan It would be good to have a standardized verbose format (space and = separated, camel case), I did plan this but I decided against it because people (including myself) are already parsing the verbose and I don't want to break existing setups.

[ManInMyVan]

@ManInMyVan It would be good to have a standardized verbose format (space and = separated, camel case), I did plan this but I decided against it because people (including myself) are already parsing the verbose and I don't want to break existing setups.

majority of checks use thing1=value1, thing2=value2

[ManInMyVan]

standardized verbose format

I wonder if allowing inputting verbose as a Map<String, Object> could be a good idea

[SergioK29]

standardized verbose format

I wonder if allowing inputting verbose as a Map<String, Object> could be a good idea

If I made a PR overhauling verbose using map instead and adding more descriptive verbose to every check, do you think you would merge it?

[ManInMyVan]

using map instead

verbose should still allow string input

and adding more descriptive verbose to every check

these should be seperate prs

do you think you would merge it?

I can't merge prs

[SergioK29]

@ManInMyVan rebased

[ManInMyVan]

FastBreak gets handled before updating the block, you don't need to track the block type, you can use blockBreak.block.getType()

[SamB440]

Status?