WESTCAT.5264

From what I know, this endpoint only gives you an array or list of recipes that are unlocked in your account, which the format would be:

`https://api.guildwars2.com/v2/account/recipes?access_token=`

If you would like to see the actual recipe names and info, the list would need to be resolved with `/v2/recipes`.

Some sort of hot fix would be nice at least... This is literally the only thing preventing me from completing the first Visions collection :(

> @"Daniel Snider.6241" said:

> > @"Guddler.2569" said:

> > Hi there,

> >

> > I see a similar question here but that is related to guilds:

> > [https://en-forum.guildwars2.com/discussion/21361/request-last-login-time-for-guild-roster](https://en-forum.guildwars2.com/discussion/21361/request-last-login-time-for-guild-roster "https://en-forum.guildwars2.com/discussion/21361/request-last-login-time-for-guild-roster")

> >

> > Is it possible to get the last time I logged in to my account via API? I don't explicitly see anything under account. Is there an indirect way?

> >

> > If not, could a simple last_login be added to the account response (or some other appropriate name)? I'm surprised this is not a more frequently requested feature (assuming it can't already be done).

> >

> > Thanks.

>

> I definitely think this definitely warrants looking into.

>

> Some API users workaround this lack of information by caching the account age and comparing after each lookup to see if the number has increased (which indicates the account was used). This is obviously not a solution for apps that want to see how recently the player logged in (without constantly polling the API) and it's certainly an added burden to any app developer.

>

> As far as I can tell without a full investigation, it would actually be quite difficult to expose a last_login field. On the other hand, it is much easier to expose something like a last_updated field for account and character data, which you could perhaps interpret in a useful way.

>

> Does this sound like something useful?

YES I know our 4 guild community would find something like this very useful. I'm rather new to API key use, but have managed to build an excel data sheet that I can search guild member names in all of the guilds at once. Now I'm experimenting with the other API features, and was looking to see if this was an option to be able to search and sort by the other parameters like achievement points and when they were last online, like you can while in-game. So for large guild community management it would be a nice feature to add the same search parameters that are in-game. However being new to this type of knowledge, I'm not sure how that can be added in.if at all.

> @"knell.5970" said:

> Are the chests borked again?

Iron Marches one still is for me :( one day, I will be a Freebooter.... One day... Only one I haven't been able to open. Tried the rezoning thing, all the suggestions here. No luck.

Tried again last night, one in Iron Marches is still 'buggy'. I only can loot that chest, but it does not consume the key or give credit towards completing the achievement. I did screenshot and send in an IG bug report. Free loooooots!

> @"Gaile Gray.6029" said:

> > @"Sirian.3689" said:

> > I tried to open the first chest of 10 again after the bug was stated fixed in release notes today, result it looks like it opens but no gain and I still have 31 spare keys.

>

> Thank you for that info!

>

> Is anyone else coming across this as well?

I was able to all of the ones in the achievement except the Sunken Chest in Iron Marches. I have tried the last few days after the patch was released, on different toons, and also tried the log out to character select screen and then back in. It will allow me to loot the chest, however does not give progress toward the "Master Diver" achievement or the "Master Diver: Iron Marches". At least I got loot! :smiley: lol

EDIT: I just looked, it gave me loot and opened the chest with both toons I tried, however did not consume the key

This is actually addressed in the Bug Discussion thread:

https://en-forum.guildwars2.com/discussion/42614/spam-filter-6-5-2018-update-bug#latest

They are aware of this issue.

> @"SlippyCheeze.5483" said:

> > @"WESTCAT.5264" said:

> > > @"MHaastrup.6978" said:

> > > The chat filter is more aggressive in some channels than others. Try posting your item in /d or /p.

> >

> > It's not about posting an item, but more of linking WP's and locations. It is in the /d and /p where it is affected. Also adding something like "go here [WPlink]" instead of just the WP link flags as message suppressed

>

> So, to be clear: you get suppressed even if you say:

>

> * please go to [explosive waypoint]

> * for the love of the six, head to [explosive waypoint]

> * will you stop with the cookies already, and go to [explosive waypoint]

>

> Is that correct?

Haha yes, I tried multiple combinations. However though, from reading on the Reddit thread I believe they are aware of the issue and are working on resolving it. Please correct me if I'm wrong though. *fingers crossed*

> @"MHaastrup.6978" said:

> The chat filter is more aggressive in some channels than others. Try posting your item in /d or /p.

It's not about posting an item, but more of linking WP's and locations. It is in the /d and /p where it is affected. Also adding something like "go here [WPlink]" instead of just the WP link flags as message suppressed

It would be FANTASTIC if we could get some guidance on this, as there is nothing in the patch notes for this being a new thing.

HP trains for example; you have max 50 people in a squad and need everyone to rally at a WP. You ping it once. But, alas, the topic of cheesecake and brownies comes up by one hungry member in squad chat. RIP that WP ping, and you have 30+ people who were trying not to be eaten by that Veteran Hydra asking where they are supposed to be. They go to look at squad chat but must scroll up through 20 msgs of how amazing brownies are to find the ONE post by the comm because they can't ping the WP again due to 'excessive messaging'. I'm sure this can be worked around, hoping that you have other squad members that were not dying AND paying attention to be able to ping it again for you. This is only just one example I can think of.