Gorilla.4120

Code:https://gist.github.com/GorillaNuggets/e72f08c587c11b1a4a9c00527bc9d1e6 This code is split between two functions. 1) Looks for items in all characters inventories. 2) Looks for items in the material storage area.P.S. For some reason, the forums isn't redirecting to my url. You might have to copy and paste it in to your browser.

Thanks for the feedback @werdernator.6105. Hopefully, if anything, this has brought some attention to the problem and a Dev will look in to fixing it. It's a shame that all of the data isn't correct because people have developed some pretty amazing websites and apps to display the information. :(

I'd also like to point out that the examples from https://wiki.guildwars2.com/wiki/API:2/wvw/matches/stats/:id/teams only returns []. I'm just curious if these anomalies are on my end or if there is a problem with the API itself. Please let me know if anyone else is having these issues.

Almost all of the JSON data from https://api.guildwars2.com/v2/wvw/matches/1-2 appears to be accurate with the exception of "kills" and "deaths" when compared to the in-game GUI. Is the game providing false data or is the API incorrect?

I'd also like to point out that the examples from https://wiki.guildwars2.com/wiki/API:2/wvw/matches/stats/:id/teams only returns []. I'm just curious if these anomalies are on my end or if there is a problem with the API itself. Please let me know if anyone else is having these issues.

When I look over the JSON data from https://api.guildwars2.com/v2/wvw/matches/1-2 all of the data (I.e. Victory Points, War Score, etc) matches the current in-game information with the exception of Kills and Deaths. Is there a problem with the API or is there something that I'm not taking in to account? The screen shot below illustrates the difference in values. For Example, the in-game World vs. World Match Overview panel, under the Kill/Death (Total) tab, lists Fort Aspenwood at 22,830 kills with 19,030 deaths. However, when I ran the link above, the API listed Fort Aspenwood at 21,297 kills with 19,648 deaths.

My opinion is simple: Decapitate before the patch: Decapitate after the patch: Any questions? =)

... because when I have 15 stacks of burning and 25 stacks of torment on me, I'd much rather ignore them for 1 second instead of clearing them. /sarcasm:tongue:

"Savage Instinct: This trait no longer removes conditions. Instead, it gives 100% damage resistance for 1 second when activating berserk mode, in addition to breaking stuns." Does this mean ALL damage or just physical damage?

While I'm excited to see Berserker getting some attention, I'm not overly enthused about what I'm reading. If I understand this correctly, we're losing regular burst skills, and we won't be able to utilize primal burst skills until we activate Berserk mode (I'm assuming we'll still need three bars of adrenaline to activate it). While this is alarming to me, if you continue to read the notes, you'll notice a common recurring theme, "This skill no longer grants adrenaline. It now extends berserk duration". So, unless I'm wrong, burst skills are going to be far and few between. Also, is primal burst skills still going to count as one bar of adrenaline expended? :confused:

No. It's a bug. According to the February 22, 2017 patch, "Combustive Shot: This skill now has a radius of 360 at all adrenaline levels." The bug seems to only affect Combustive Shot on Spellbreaker. The skill seems to work fine on core warrior and berserker.