Add "team-color" attribute to Armor Kits

[destial]

When ever I create maps, most of the time I have to create a separate kit for the teams while trying to find the correct color that corresponds to their color.

Like so:

<helmet color="cd00cd" unbreakable="true" material="leather helmet"/>

So, I added an attribute that automatically uses the team's color so that I can just use the default kit and it will automatically use the team's color when applied.

Like so:

<helmet team-color="true" unbreakable="true" material="leather helmet"/>

I made it so "team-color" overrides the "color" attribute since it is applied during the match and not beforehand.

[CoWinkKeyDinkInc]

I don't really see what is the issue here that this resolves, a colour picker is easy to find and search online while referring to the documentation in another tab while writing XML. Since they are hex colours, what would be the default values you would use for the team colours?

[Pablete1234]

I don't really see what is the issue here that this resolves, a colour picker is easy to find and search online while referring to the documentation in another tab while writing XML. Since they are hex colours, what would be the default values you would use for the team colours?

It's simply convenience, also removes the need of having 3 kits, one main one and one per each team that have the other as parent, it simplifies XML

[Pugzy]

Did the Stratus (or was it Walrus) implementation work with blocks too (glass, clay, wool etc)?

I recall some funky repair integration too. Anyone got a link to their docs?

[Electroid]

Since this is syntax sugar, it'd be nice to make it even simpler: color=<hex|true|false>

[destial]

color is parsed under parseItemMeta and set's the item meta once passed. it doesnt take the armorkit as a parameter, so it would be more complicated.

[Electroid]

On second thought, I think the syntax you've proposed is good.

[Electroid]

Congrats on your first PGM feature! (and one of the most requested ones by map makers!)