Guild Wars 2 Dev Tracker

Thanks! (:

Oh, thanks! I didn't even realize until you said something xD

Absolutely brilliant!

Seeing all of your reactions, watching the videos and streams, it's been awesome. Y'all are fantastic and I'm glad that the reception has been mostly positive. I will say, I'm reading everything here and on the forums, talking to people in game. We're listening to all of you. Your feedback, whether praise or critique, is being taken into account.

Thank you for all of your support. You're an amazing community. Keep rockin'.

Thank you <3

A few of my commanders in WvW say PvD (Door) whenever we attack a tower/keep :-)

omg thank you! this is the first cake day I've actually ever been noticed on lol

Player versus Door? thats WvW! :-)

You are welcome!

That's very kind of you! I'm always worried I talk a bit too much or just say dumb things, lol. So it's nice to hear when things go well.

I appreciate the support, and glad to hear you enjoyed the Guild Chat. Looking forward to tomorrow!

I'm glad you enjoyed it! <3

Sunqua Peak CM is built, like Nightmare and Shattered Observatory before it, for hardcore endgame replayability.

Hey! The Pyre gloves are in the guaranteed wardrobe unlock now

What we encountered in early 2012 was that the recommended way to deploy those VMs was to add up all our CPU and memory usage and then, as they say, over-commit, assuming that your underlying hypervisor will always do the right thing. And maybe in 2020 they do. But in early 2012 where we had a mix of game servers that hammer the CPU and other servers that use very little CPU but hold important state we found that the servers that use very little CPU wouldn't get scheduled for a long enough period of time that the game would experience timeouts waiting on those servers. AWS has two types of server instances: ones that are over-committed (T-series) and most of the others that are not. This gives us the control to allocate our resources very specifically.

Back in 2012 we had to get rid of the over-commit for the entire system to run reliably, at which point, what was the point of having a hyper-visor? I had to rewrite how every single network connection was made but o...

By "macro-service" I meant, "A really big micro-service." The game servers scale horizontally just as the micro-services do in terms of players and concurrency. The one thing they can't do is scale an individual map across multiple cores or servers. Certain maps are slow because they are doing really complicated things and that's why we announced that it is not just a single thing that causes lag; every map has some unique game play element which might be causing lag that needs to be analyzed and optimized. And sometimes a map ships and is fine in terms of lag but uses a skill or effect that later on gets a feature added to it which slows down that effect. It's fine in most cases, but maybe in that older map, the effect or skill was used a lot, and that map slows down. I love our designers. They manage millions of lines of script code across an enormous game. Sometimes there are unexpected interactions in all of those millions of lines of script and it takes a bit of time...

Whoops. Yes, that.... Let's go with that and ignore my frantic, hype (yet sleepy) typo! :D

It's something we can't answer now. But what I can say is that everything is deliberate. Multiple teams spend a lot of time ruminating over seemingly small details, and that goes for everything we showed today.

It's fascinating for us to read your interpretations and speculations!

Everyone here is following the reactions. We love that you're all excited!

There are no breaks on this hype train!

So excited that this trailer is now out for you all to watch~ :D

LET'S GOOOOO