map cosmetic type to microtransaction category

[lvlvllvlvllvlvl]

Abstract

Ensure that cosmetic_type field does not cause errors and allows items to be categorized correctly

Action Taken

As mentioned in #104 (comment), the data in CosmeticTypeName does not precisely match the previous data that was exported in the cosmetic_type field. Heuristics are employed to match the previous format, and a cosmetic_target field is added to contain more specific data when available.

• Custom mappings are added for skin transfer, vanishing dye, and invisible buff effect
• Certain other CosmeticTypeName values are mapped to specific cosmetic_type and cosmetic_target values
• Unique items names are matched from UniqueStashLayout.dat; if a match is found cosmetic type is guessed based on the stash tab
• Next, base items are matched and cosmetic type is guessed from the item class
• Next, gem tags are tested: if a match (e.g. 'Aura Effect') is found cosmetic type is set to 'Skill Gem Effect' and cosmetic target is set to the gem tag
• Otherwise a warning is printed and the cosmetic type field is deleted

Caveats

• The data in CosmeticTypeName is not very clean; several apparent typos have been worked around with manual mappings
• It is assumed that all unique item mtxes are skins; helmet attachments or weapon effects for unique items will be miscategorized
• It's possible weapon types should also be tested and mapped to 'Weapon Skin'; the only existing item that this applies to is '[DNT] Annihilation Wand', which has a CosmeticTypeName of 'Wand Skin'