Guild Wars 2

We’ve got new achievements, and that’s a nice thing. I can see the Daily Tangled Depths Event Completer ingame, and looking at the API for dailies, it appears to be

{
	"id": 2968,
	"level": {
		"min": 80,
		"max": 80
}

but when I look at https://api.guildwars2.com/v2/achievements?id=2968 all I get is

{"text":“no such id”}

Furthermore, there appear two daily event completer at https://api.guildwars2.com/v2/achievements/daily for level 80, as there also is ID 1963 which happens to be Queendale Event Completer, but that one is not ingame?

Ok, so the “double” daily event completer is solved, I should have gone through the 30 page update notes yesterday! We’ve got dailies for both the base game and HoT owner now.

The issue with missing event information is still there, as the API was not updated with the most recent data from ingame regarding ID descriptions, which makes it difficult to implement it into my world boss timer (have to do it manually right now, by comparing ID with ingame information….).

Hello, how have you solved the “double” id ?
If I own HoT, shall I remore “double” id everytimes ? So “double” id isonly for not HoT owners ?

Even
https://api.guildwars2.com/v2/achievements/categories/88
https://api.guildwars2.com/v2/achievements/categories/97
return wrong or missing ids, especially for Fractals Daily Achievements.

Thanks a lot, whitelisting the dailies one day in advance would be great as this way my script would also directly load them in advance (as I fetch the ones for the next day 20 hours in advance) and I could have a look a day earlier at what daily is coming next and adjust my database so it shows up correctly on the timer.

@Elfo Bianco: What I did, in my particular case, was to split up the dailies into non-HoT and HoT, by just checking the ID. I assigned everything before 2100 to pre-HoT-dailies and everything at and after 2100 to HoT dailies. Not optimal, but it works for now, until detailed ID information has been collected.

Aether.7095:

@Elfo Bianco: What I did, in my particular case, was to split up the dailies into non-HoT and HoT, by just checking the ID. I assigned everything before 2100 to pre-HoT-dailies and everything at and after 2100 to HoT dailies. Not optimal, but it works for now, until detailed ID information has been collected.

Mmh, I think I will wait that a new flag will be exposed