Jump to content
  • Sign Up

5 PVE-Dailies for level 80 characters?


Scavenger.6013

Recommended Posts

Hey guys :-) ,I try to create a list with all dailies for level 80 (API:2/achievements/daily). To keep it simple for accounts that have GW2, HOT and POF.After filtering the PVE-dailies (max level 80), I receive the following list (for today):"id": 1970, ... "id": 3784, ... "id": 1937 ... "id": 1960, ... "id": 1916 ...There should be only 4 dailies for PVE. The "id": 1937 ("Daily Maguuma Wastes Vista Viewer") seems to be wrong, or am I missing something? (The required_access attribute for all dailies is "GuildWars2", "HeartOfThorns", but it was already mentioned in another post).

What am I missing? :-)Thanks!

Greetings

Link to comment
Share on other sites

thanks for your reply.The dailies today in the mentioned scenario with POF, HOT and GW2 are: "Daily Desert Forager, Daily Kryta Vista Viewer, Daily Morgan's Leap Jumping Puzzle and Daily Verdant Bring Event Completer"

From https://api.guildwars2.com/v2/achievements/daily , I get 8 PVE: 3760,1980,1985,1839,2945,1951,1951,1929 (1951 different level)The given id's from the REST API correlated to the given dailies in the game are: 3760,1839,1929,2945

3760 (min: 80, max: 80) [ok]1839 (min: 11, max: 80) [ok]1929 (min: 31, max: 80) [ok]2945 (min: 80, max: 80) [ok]The details of the other entries are:1980 Daily Maguuma Wastes Forager (min: 80, max: 80) [would not be filtered and is wrong?]1985 Daily Shiverpeaks Forager (min: 1, max: 79) [would be filtered due to level]1951 Daily Metrica Province Event Completer (min: 11, max: 79 and min: 80, max: 80) [the first one would be filtered due to level, the second one would not be filtered and is wrong?]

-> So today I see 6. What am I missing ? =)Thanks!

Link to comment
Share on other sites

@Scavenger.6013 said:thanks for your reply.The dailies today in the mentioned scenario with POF, HOT and GW2 are: "Daily Desert Forager, Daily Kryta Vista Viewer, Daily Morgan's Leap Jumping Puzzle and Daily Verdant Bring Event Completer"

From https://api.guildwars2.com/v2/achievements/daily , I get 8 PVE: 3760,1980,1985,1839,2945,1951,1951,1929 (1951 different level)The given id's from the REST API correlated to the given dailies in the game are: 3760,1839,1929,2945

3760 (min: 80, max: 80) [ok]1839 (min: 11, max: 80) [ok]1929 (min: 31, max: 80) [ok]2945 (min: 80, max: 80) [ok]The details of the other entries are:1980 Daily Maguuma Wastes Forager (min: 80, max: 80) [would not be filtered and is wrong?]1985 Daily Shiverpeaks Forager (min: 1, max: 79) [would be filtered due to level]1951 Daily Metrica Province Event Completer (min: 11, max: 79 and min: 80, max: 80) [the first one would be filtered due to level, the second one would not be filtered and is wrong?]

-> So today I see 6. What am I missing ? =)Thanks!

To reiterate part of what I said earlier, the expansion achievements will replace up to 2 core achievements if you have access to the content. If you have no expansions then you will receive all 4 of the core dailies and will not see the Desert Forager or Verdant Brink ones. If you have PoF, you will get Desert Forager instead of Shiverpeaks Forager. If you have HoT, you will get Verdant Brink instead of Metrica Province event completer.

Link to comment
Share on other sites

  • 1 month later...

Well, before PoF, filtering was very easy, as there were only two possibilities, either you have the base game, or you own the expansion which includes the base game. If they had just separated all daily achievements for PoF release (rising the number of achievements you could do each day and show them depending on the expansion you own), the filter could still work. Instead what ArenaNet did was to mix up all possible dailies without a plan on who owns what and when and where, as now you could also have either of the expansions, but not both.I don't want to be the API developer right now, it must be a mess to figure out a way to output the new formula into the JSON so that's actually somehow usable afterwards. That's probably why it hasn't been done yet. Either that, or they just decided to not support that part of the API anymore, wouldn't surprise me either.

Any way or the other, this is just straight unacceptable for us website and tool developers, it's been months now. We deserve some information on this issue.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...