Confusion about Confusion
Cookiezz.5261:
I was looking at the trait “Mistrust” (API Link) for Mesmers as an example earlier, just playing around with the API, and the Confusion portion … confused me.
It refers to it (Confusion) as a type of “Buff”, is that correct? Also the description doesn’t reflect that it does damage over time now.
I then switched to Blinding Dissipation (API Link) since it applies Blind. This one also came back as a type of Buff.
I then wanted to look for CC effects so I used Confounding Suggestions (API Link) for the daze, which is defined as a “Time” type.
I had hoped to look for conditions (among other things) in the traits, however it does not appear the Type column is what I had expected it to be. Is this to be expected? I figured I would ask before I start building a dictionary to define conditions / buffs / CC / etc.
Thanks!
Eearslya.6309:
The traits/skills API is..unintuitive, and the devs have admitted this. It was never structured to be crawled through programmatically. All this data is simply what is used to render the tooltip, not actually what goes in to calculating the skill.
However, in those two cases I’d simply check the status field for Buff/Condition, and the text field for Stun/Daze. It may not work 100% of the time unfortunately, but there’s really no better option right now.
Lawton Campbell.8517:
All this data is simply what is used to render the tooltip, not actually what goes in to calculating the skill.
Pretty much this. That’s the closest we have to a normalized form for skill details. Unfortunately it isn’t very normalized at all — in the stun case it does the “right” thing in the primary use-case and displays a stun icon with the text “Stun” and a duration.
It’s not ideal for machine-readability, but it’s the best thing we have at the moment.
Cookiezz.5261:
Thanks for the reply’s! I can handle the parsing on my end, I just wanted to make sure I wasn’t doing more work than I had to. One day hopefully it’ll get cleaned up.
Thanks again!