Skin vs Default Skin
Patches.7584:
I’m writing a wrapper for the API, at least part of it. Send a message if you want in on the project, I could use some help in places, or just general feedback.
Anyway, on topic.
I’m noticing items have a default_skin attribute, but not an “active” skin attribute. Does default_skin get overridden, or is there something else in play?
I only ask because I’m currently writing a skin information function, and being able to tell the difference between and applied skin and the default would be useful information.
TL;DR – Where does an item store it’s non-default skin ID?
Lawton Campbell.8517:
Items will have non-default skins if they’ve been transmuted (with the wardrobe) — such items will show up in some of the authenticated endpoints, e.g., character equipment. The skin field of those item stacks overrides the item’s default_skin.
Patches.7584:
Noted, thanks.
Will adjust.
Patches.7584:
Side note, sort of off topic.
Is there any particular reason you guys went with the inconsistent “If it’s not there, don’t define it” method of json attributes?
I’ve run into a lot of errors, easily accounted for but tedious, where the error is raised simply because an attribute exists for ONE item, but not for another.
This isn’t just the difference of weapons and accessories, by the way. It can be for the same types.
Example: some items have a “description” attribute, while others don’t. Just depends on the item. I know it’s optional, but a default None value or something would help.
Wouldn’t a simpler solution to make all these optional attributes have a default value whether or not they have something assigned to them?
Instead of not even HAVING a description attribute, why not just an empty one? None? 0?
Adding a bunch of try/excepts for things that sometimes have attributes but some times don’t grated on my nerves slightly and this is an adequate venting process for me.
Just curious, I’m sure you’ve your reasons. Care to share?
Lawton Campbell.8517:
Side note, sort of off topic.
Is there any particular reason you guys went with the inconsistent “If it’s not there, don’t define it” method of json attributes?
Just curious, I’m sure you’ve your reasons. Care to share?
No particular reason 
FWIW, the encoding used by /v2/items is the bane of my existence, but the data coming off that endpoint is fairly complicated to begin with.
Patches.7584:
Side note, sort of off topic.
Is there any particular reason you guys went with the inconsistent “If it’s not there, don’t define it” method of json attributes?
Just curious, I’m sure you’ve your reasons. Care to share?
No particular reason
FWIW, the encoding used by /v2/items is the bane of my existence, but the data coming off that endpoint is fairly complicated to begin with.
It’s actually worth a lot. We will suffer together <3