Guild Wars 2

I do have similar problem. Latest patch broke Audio Device drop down – it now shows only “Default Device” although I have multiple audio devices… I’m not able to use Corsair USB Headset unless I set it as default device in my OS, this is just dull. I use the headset only for GW2 and I don’t want to to have it as default for all applications.

This worked as expected before the patch, now it’s just broken.

Today, it happened to me 8 times in a row – I’m not kidding. Eight kitten times in a row it was 4v5 for our team. That’s just ridiculous and depressing. I’m sick of this, WildStar here I come.

Healix.5819:

Since event_details is an extension to event_names, it makes more sense to have the IDs be the keys, since when you already know the ID, you just look it up, rather than iterating through the entire array to search for it.

What makes you think that event_details is an extension to event_names? If it would be like this, it would maybe make (a little) sense, but it’s not the case. There is no event_id argument passable into events_details API. You have to fetch everything and thus event_details is more like “one-time get all event informations and cache it” API. And that’s the argument for my initial post – the API should be the same as event_names. There’s no reason to have dynamic key names in JSON, that’s just miles far away from JSON best practices.

Many libraries for JSON parsing in .NET (RestSharp, JSON.NET) and Java can handle what you say automatically without custom parsers when the JSON API is standardized (my suggested image from post above) and you’ll have an dictionary with <eventID, event> created automatically by those libraries … dynamic keys just makes everything harder to parse, in .NET for example your simplest solution is to use <dynamic> (e.g. var events = RestClient.Execute<dynamic>(new RestRequest(“event_details.json”)).Data[“events”];), but it’s just not that pretty as automatic deserialization into your own POJOs/POCOs.

ANet, please get rid of dynamic keys in (some of) your JSON APIs.

Is it just me or do you also see the inconsistency in Event Details API? I mean – why do you even use dynamic keys as event IDs? There is a standard JSON approach in Event Names API (flat array with id keys), why don’t you just use the same approach in Event Details API? I would remove the GUID array completely and make it flat events with event_id inside of each of them … The way it is now it just makes the JSON parsing unnecessarily complicated for libraries like RestSharp.

See attached screenshot for explanation what exactly is on my mind.

So let me summarize that – I was looking forward for this event for almost a month after Mad King’s event and:

1. On Friday the event started, was kind of laggy – I said, what the hell – it’s okay, this can happen and I logged of and logged in few hours later to complete the event chains – but I was stucked at Noll because Noll was bugged, I did wait few tens of minutes but wouldn’t able to complete it.

2. But suddenly a red post on your forums appeared that Noll will be fixed and WE WILL BE ABLE TO FINISH PHASE1 EVEN AFTER PHASE2 STARTED.

3. Phase2 started and it was pretty cool, I explored the new map and was kind of happy. Then the patch came up – Noll was fixed but Miyani and whole scavenger hunt chain was removed.

4. Few hours later red post appeared saying that Miyani chain was too much work to fix it and it was removed.

Seriously guys? Why did you lie to us that we’ll be able to complete Phase1 and then you just removed the chain completely? And what the duck means ‘too much work, removed’ – seems like you do not really care about your gamers.

Devs: “What the heck, it’s weekend, I won’t be fixing any events, it’s freakin’ Saturday and those guys did already paid us for the game. Lets just remove the chain.”

Bottom line: I guess that you didn’t really impressed the free trials that much.