Guild Wars 2

Elfo Bianco.3786:

Your proposal is good as it has been described, but I don’t understand why to work with more than one language simultaneously.

It would make it take fewer requests to pull e.g. /v2/items into a local database.

It’s not a bad idea but it would require more refactoring than I have spare time for, I think.

The mastery level in /v2/account/masteries is a 0-indexed reference to the /v2/masteries.levels array — so 0 is the first level, totally omitted is “haven’t started”. I should update the wiki page to be more accurate.

Are you adding the daily_ap and monthly_ap from /v2/account as well? That might cause the difference.

There definitely is a bug somewhere in the AP calculation, but IIRC it’s a difference of 1AP that we haven’t been able to puzzle out.

Nope, cache-control request headers are completely ignored.

Otherwise one of the game db servers would fall over <3

ThatNAESLGuard.6238:

for the record, you guys mixed up NA and EU. obviously not a big deal except your URLs are wrong.

W-wot.

I’ll have that fixed sometime today; literally no idea what’s going on there.

EDIT: deployed a fix for that — leaderboards should return the proper regions now.

Note that the skills API currently only returns the PvE versions of skills — if the test area is using the PvP version (and if the PvP version has a different coefficient) then that would cause the issue.

The original incarnation of /v2/pvp/seasons/:season/leaderboards/:board had a fairly serious design issue wherein the region could not be selected. This has since been fixed in a backwards-compatible way (so that old requests technically still work), but the old request format is now deprecated.

Going forward, applications should use /v2/pvp/seasons/:season/leaderboards/:board/:region e.g.

• this link for season 5 NA
• or this link for season 5 EU.

In two weeks, on Jan 25 2017 I’m going to remove the backwards-compat such that omitting the region will just return a list of regions to bring the endpoint in line with the rest.

Sorry about the mess :<

Just deployed some new functionality to fix this omission.

• Season 5 NA leaderboard
• Season 5 EU leaderboard

In brief, the old URLs will still work (in the old broken way), but new code should append /na or /eu to select a region to pull leaderboards from. Will probably make omitting the region an error in the future, but I didn’t want to horribly break anyone’s stuff without any forewarning.

Thanks for bringing this up; still can’t believe I overlooked that.

Umm.

Huh.

I’ve never claimed to be a smart man. Here’s a tracking issue.

SkyShroud.2865:

The following is some of the log ID containing the unusual item ID
2625051
2624945
2624868
2624681
2624048

That looks like something’s not being parsed right on my end — what’s the guild ID you’re looking at?

There’s a tracking issue for the upgrade_id containing item ids — should have that fixed sometime this week^H^H^H^Hyear.

Oof, not sure how I missed that. I’ll get that fixed sometime this week; here’s tracking issue. I’ll stuff the item id into an item_id field or something just in case it becomes useful in the future.

They’re not currently generated; I don’t know why. I made a tracking issue for this, not sure when I’ll be able to have it finished.

Mushin.3928:

If this is fixed, do you know if it would take effect for old games?

Yeah, it’ll take effect for old games. The stored data is correct — there’s a date/duration for each game — the API frontend is just misinterpreting the date as the start date rather than the end date.

Should have it fixed by the end of the week.

Could you provide some more data? Like, expected start/end, actual start/end for a match or two?

EDIT: nm, Evan poked around in the code for me and you’re totally right; the date the API is reading is the end date, and it’s adding the duration to that. Tracking issue.

The avatar position should have a usable z coord; I can look into adding the current floor id to the JSON blob. Tracking issue.

Completed hero points are available from /v2/characters/name/heropoints with the progression scope. For the rest of the bits, there’s an open issue that I haven’t had time to implement yet.

Will look into it; in the meanwhile here’s a tracking issue.

rating and decay in /v2/pvp/standings are what you’re looking for. Only have the current values — I don’t think we’re currently tracking season best.

I went ahead and whitelisted 1257 — though the data I’m looking at shows it’s worth 5AP. I don’t think it’s the source of the 1AP discrepancy.

Any other missing achievements would show up in /v2/account/achievements, so I don’t think it’s that. It could be something weird with the daily/monthly counts (an off-by-one somewhere in the API code?). Not really sure.

I don’t think the in-game value is wrong though; IIRC someone went through all their achievements and added them up by hand to verify that the in-game value is correct and the API data is wrong. Just haven’t figured out where exactly the error is coming from.

Loex.5104:

Why can my browser display the images but okhttp quits its service on the same URL cal?

Caches.

render.guildwars2.com is currently broken ;__;

EDIT: I think I fixed it.

Yeah, pretty much all of render.guildwars2.com has been broken since yesterday — any successes have been CDN cache hits. Hopefully will have it fixed today/tomorrow?

EDIT: it might be working again.

The “training” field of /v2/professions.

They’re only on /v2/continents/… for now, e.g. Queensdale, in the skill_challenges section. It’s kind of an inconvenient place for them, admittedly; might be worthwhile to add a /v2/heropoints that provides the floor/region/map/coords (even if that means some data duplication).

Elfo Bianco.3786:

After more than 2 months bugs are still here -_-

I just got back from a two month leave of absence :>

Elfo Bianco.3786:

Title ids=214,216 are missing and I’m not sure that there aren’t other missing titles in API:2/Title so when you can please check them all.

214 = The Magnanimous; it’s awarded via achievement so I’m not entirely sure why that’s not coming through (https://api.guildwars2.com/v2/achievements/2030).
216 = Deer Commander; ditto above (https://api.guildwars2.com/v2/achievements/2049).

Not really sure what’s going on with those. Tracking issue.

Elfo Bianco.3786:

Achievements id=2562 returns “bits”:[{"type":“Text”,“text”:“Ally: Canach”},{"type":“Text”,“text”:“Ally: Caithe”},{"type":“Text”,“text”:“Ally: Braham”}] , but now I have noticed that these bits are of another achievement, so for the id=2562 “bits” should be null.

Blergh, that’s super annoying. Those bits are associated with the achievement, they’re just not referenced from the achievement tracking part. Will have to add some stuff to filter those out. Tracking issue.

Elfo Bianco.3786:

Achievement id =1257 is still missing as I have read from other posts on the forum.

That’s a bugged achievement — need to look into whether it is actually counted towards total AP. Empirically I’ve heard that it doesn’t. Debating on whether to whitelist it on /v2/achievements or to blacklist it from /v2/account/achievements.

Valento.9852:

And by extent, the character model render so we can have WoW-like armory inspired websites.

I briefly looked at the time it would take to implement and shed a thousand tears.

Maybe next year ;____;

The character proportions (and face/hair selections) are something I can easily knock together though. I don’t know why I didn’t link it originally, but here’s the tracking issue for that bit.

I think the Mumble Link data has a unique id in the “shard” field which could theoretically be used — that’d be more accurate than /ip (which is not necessarily unique).

But anyway, the event state bits probably aren’t ever coming back :<

I’m hoping to have both the skill rating and maybe leaderboards up on the API by Dec 13.

I’ll try to put together a PR on Github later today for preview/review.

You can write a standalone program which reads the data without Mumble running. It’s just a shared memory page that you can map into your application.

The wiki needs to be updated. binding/bound_to should be straightforward, but the stats.id references /v2/itemstats and indicates which stats were selected for a choosy-stat item.

Oof, here’s a new tracking issue, since this seems to be something different than the original.

It’s a long-requested feature; the main issue is that most of the chat (and the combat logs in their entirety) aren’t stored in a network-accessible manner — the implementation would have to use some sort of local API which is a pretty large undertaking. As such I don’t really have a timeline

Malediktus.9250:

But “Mini Mushroom Stomper” is still missing, it is an unlock from Guaranteed Wardrobe Unlocker, so it probably skips the whitelisting queue.

Whitelisted. The mini whitelist is tied to their item unlocks, IIRC, so that should appear eventually as well.

Malediktus.9250:

https://api.guildwars2.com/v2/achievements/1257 needs whitelisting

I’m going to go ahead and whitelist 1257, but it’s a broken achievement (it doesn’t have a name — so the client won’t render it, IIRC). It’s … kind of strange that there are accounts with it? But it’s worth 5 AP, so there’s that.

Malediktus.9250:

https://api.guildwars2.com/v2/achievements/561 probably should be blacklisted because it gets converted to https://api.guildwars2.com/v2/achievements/863 upon logging in. It seems only people who did not log in between the first release of the super adventure box in April 2013 can have this achievement. (this is most likely because the achievement got an additional reward at the 2nd SAB release in 2013.

Makes sense; I’ll go ahead and blacklist it.

cassius.5809:

Seeing some of the IIS errors this forum gets guessing it’s built in .NET? Professionally develop .NET web applications so would gladly rip it apart and put a working search in!!!

Ruby on Rails, actually. IIS is load balancing, I think.

I think I whitelisted all of those yesterday; my script says all achievement items are currently whitelisted.

The HTTP API can’t get any live information — everything served from api.guildwars2.com is up to 5-minutes out-of-date. There is a mumble link API available which provides some very basic information. Not planning on adding any additional fields to the mumble link API, so what’s there is all we’ll likely ever expose. That’s about as close as we can get with regards to official support, I’m afraid

The API provides a list of all endpoints. I’ll add that to the github stuff now; that particular endpoint was implemented before the feature was announced and I totally forgot to actually write documentation for it.

The forum software for these forums is proprietary and maintained in-house. AFAIK it is totally bespoke and isn’t based off an existing forum software.

Other than the world bosses which are on a set schedule, there hasn’t been a way to get the event statuses from the API since megaservers were launched (since there’s no way to tell which instance you’re on, and they all have separate state).

You might be able to find the specific app you’re taking about in the list on the wiki or in the Overwolf catalog.

Drant.5902:

Have the tiles been regenerated? It’s been a week, and with a fresh browser cache I still see the corrupt tiles.

Ah, sorry, I dropped the ball on this one. I’m pulling the latest live assets and start generating them now; will have them uploaded over the existing ones sometime tomorrow.

I’m seeing the same issue with my API key — it appears to be returning bogus values. Looking into it.

EDIT: Found the bug, it was something incredibly stupid. It’s a bit late in the day to do a deploy so I’ll put it off until 5PM tomorrow.

Uhh, that reminds me — I still need to write the frontend bits for it. Here’s what I’m thinking — let me know if there’s a better structure.

Unfortunately, because kills/deaths are tracked in a totally separate system (that has no persistent storage) I haven’t been able to add those into the skirmish data — but the scores at skirmish end (for all skirmishes in the match) are in there.

Elfo Bianco.3786:

Well there are the following ids = 79342,79320,79322,79319 that are missing as API:2/Items for the achievement id 3089

Blergh, not sure why whitelisting that achievement didn’t also whitelist the items. Whitelisted the manually while I try to figure out why that isn’t working.

Sorry, I should have broadcasted this change more widely. The answer ids turned to strings because they weren’t actually unique ids — they’re only unique within the context of a backstory question.

:(

It should be ready with the next release.

Meant to have it in for this one, but the implementation turned out to be fairly complex and I slipped the cutoff date by a few days

Woot, thanks for the ids — that made it super easy.

Went ahead and whitelisted both of those achievements.

This is a known issue. It’s pending a deployment of the backend component that handles gems which is totally outside my purview.

Hrm, would it be useful to do the filtering on the API side? e.g., expose an endpoint that returns skins (perhaps by armor weight/weapon type?) that have the ShowInWardrobe flag set?

Yeah, some of the skins are a bit wonky — it’s tempting to blacklist them, but it’s possible that someone has an item in their bank or something that uses that griffon skin, for example.

The Mistward skins are almost certainly from the HoT beta that we did on live — probably just an implementation artifact from trying to ensure that the beta bits didn’t affect non-beta features.

Probably gonna wontfix across the board. The way the wardrobe interface on the client filters skins is (1) enumerate all skins, note the ones that have ShowInWardrobe, (2) for any skins that have HideIfLocked, remove them from the list if the user hasn’t unlocked them, then (3) render out any remaining skins. Having extra bits and bobbles in the API shouldn’t affect anything, I think :<

Malediktus.3740:

Is it the same for Challenger of the Arena, Soldier of the Arena, Veteran of the Arena, Master of the Arena and Legend of the Arena? They are legacy pvp titles that were awarded via items

Yep, those look to be the same. The item just awards you the achievement on use, then the achievement gives you the title.

I’ll go ahead and whitelist those achievements too so that their respective titles show up.

It currently does not; there’s an open issue for it, but I’m not sure what the status of that is anymore. Will look into it shortly.

EDIT: Ah, nevermind, that one’s actually added via achievement. The achievement just wasn’t whitelisted until just now; the title should appear shortly I think.