Added property for specially registered tools

[littlecube8152]

What

This PR adds another IMaterialProperty called ExtraToolProperty. This new property will

• Override existing tool properties. For example, boosting the durability flint mining tools is possible now.
• Add new tool that are not generated. However, the recipe should still be added manually.

Implementation Details

Now ExtraToolProperty and ToolProperty are two different classes inherited from SimpleToolProperty.
ToolProperty keeps all its original functionality, while ExtraToolProperty holds a modification mask for every other tools.
These tool masks are distinguished by the strings defined in ToolClasses.

The get method now takesIGTTool into consideration of overriding the specified properties. Hence, all the tools generated will now adapt the overridden stats.

The soft mallet and plungers are also re-defined using the new method. Now the tool stats are registered in SoftToolAddition and the recipe still registered from ToolRecipeHandler.

Outcome

By introducing this new method, #2692 is fixed since the tools are now correctly generated.
Also, modpacks can now have finer controls over the built-in tools. They are now able to change specific stats of some tools instead of modifying the whole set of tools from a material.

Potential Compatibility Issues

Most modpacks that tweaks the tools by the NBT will likely broken. However, I believe the bug similar #2692 will be fixed.

[littlecube8152]

Crafttweaker and GroovyScript integrations are not implemented yet.
However, I think these code should be reviewed first before we start these.

[littlecube8152]

The previous one (until 2cfcfdb) is faulty as many properties were not applied properly.
Now it is fixed and the GroovyScript integration is added. The usages are as follows.

OverrideToolProperty Builder

All properties are build through the methods overrideToolBuilder(). It is very similar to toolBuilder(), with the following property:

• It is a builder of OverrideToolProperty (of course)
• It has two initialization method: overrideToolBuilder() or overrideToolBuilder(float harvestSpeed, float attackDamage, int durability, int harvestLevel). The first is for only overriding some properties, and the second is for creating new tools (probably for tools without toolStats).
• Only harvestSpeed, attackDamage, durability, attackSpeed, harvestLevel, enchantment, and durabilityMultiplier can be set in this builder (the missing ones are magnetic, unbreakable, and ignoreCraftingTools).

Overriding Tool Stats on Creation (Adding Material Properties)

Use

overrideToolStats(String toolId, ExtraToolProperty.Builder builder)

toolId is a string indicating the target overridden tool (for example, "pickaxe", "hammer", "knife"), and builder is a builder obtained from previous method.

Overriding Tool Stats on Modification

Use

Material.setOverrideToolStats(String toolId, ExtraToolProperty.Builder builder)

The usage is exactly the same as above.

[M-W-K]

Is there any reason for the explicit casting and separating the *= apart? The += and *= operators implicitly perform the casting for integer types, iirc.

[littlecube8152]

No, but the operands are floating point numbers, so I just wanted to be clear here.

[M-W-K]

Since ToolProperty now extends this, and this class now contains most of the functionality of ToolProperty, I think it would be better to call this ToolProperty and the current ToolProperty MaterialToolProperty instead.

[littlecube8152]

Ok, these classes are renamed.

[M-W-K]

It's an edge case, but it might be better to do this.overideMap.hasKey(toolID) instead here.

[littlecube8152]

Changed to Map.containsKey method.