Ni In.6578

There is a [sEA] guild on CD, too. I think the driver is currently on break but should be returning soon.

In T2 - T4 NA, Red BL is where you go for free keep caps as green or blue. It's simply not defended.

As we know, the Desert BL poll was sent out ~2 years ago to see whether or not to change Red BL from Alpine to Desert. Many of those who play WvW on a regular basis have had various complaints about Desert including size, tower location relative to spawn and garri, map exploits, and so forth. The above issues are exacerbated by assigning Red to that BL. The server that came in last place likely does not have the defensive coverage to maintain such a large BL where towers cannot be easily defended from spawn (due to time it takes to get to the tower) or from garri (e.g. trebbing NWT/NET). This means that the server with likely the least coverage in the match up receives a BL that is harder to defend thus potentially causing them to decrease the PPT they receive over the match. And I acknowledge some people do indeed enjoy Desert BL for their own reasons. Is it time to remove Desert BL and replace it with Alpine BL? Would you keep Desert BL? Or would you keep Desert BL and rotate which color received the BL (knowing that it won't always be 'fair' as ANet can't ensure that a server wouldn't get it N weeks in a row)?

The longbow range is not bugged, it is working as intended. Since there is a slight arc in the projectile, it may travel farther than the stated range. This would be similar to other projectiles that travel in arcs.

No effort to...? I try to avoid ktrains. They make me fall asleep.

Salt is the meta endgame of WvW. Without it, this would be a game mode of capping structures over, and over, and over again. How boring would that be?

ANet isn't in Seattle. That's about 30-45 minutes away depending on traffic.

I was under the impression Mike Obrien did the netcode, that was his contribution to WoW after all.. though I suppose running the company takes up his time now. Netcode is part of it. Server-side code (the code that performs the calculations) is also part of it. This can only be multi-threaded so much. After all, skills must operate on a FIFO basis.

Not saying they can't; the question will be is there a financial incentive to do so provided the complexity of the spaghetti code? Probably not.

I'd say a vast majority of players run whatever they want. Meta is reserved for the WvWers who know what they're doing/want to primarily PK.

Skill lag is not a client engine problem. Changing the version of D3D in use will not improve performance. This is a server side issue. ANet knows it and likely does not have the developers who originally worked on the server-side service in depth.

When did WvW not have a meta?

You don't. There are viable, even meta, non-PoF builds. Backline hammer rev, for example.Lol nobody runs revenant. Herald has been and will always be meta. I believe you are confused because everyone say rev, but what they mean is herald. Because revenant literally does not exist in the meta. If you go look at metabattle now there are 24 builds listed, 3 of them are revenant - all of them worst in their categories and none is for WvW. I mean it's not like people would claim that vanilla guardian is meta for the frontline just because everyone say "bring a guard!"?You wasted an entire paragraph on this? Of course "hammer backline rev" means herald. You're talking to someone who mains it. And I should really spend a paragraph on this just for you, but I won't: Herald does not require PoF, disproving your assertion that PoF is required.

You don't. There are viable, even meta, non-PoF builds. Backline hammer rev, for example.

The performance issues client side (such as texture or geometry loading) should be classified as a bug, as well. There's (probably) no good reason that the client has such poor loading performance. Server side, it at some point the actions all players make must be serialized. This does not lend well to multi-threading. Imagine trying to have multiple threads and merging them so often to determine who hit what and when. It wouldn't work. Likely we're just looking at too many instructions being passed through a single threaded portion of code server-side. There's no resolving that -- perhaps improving, as in there may be optimizations that could be made in those serialized instructions, but again, it brings no financial gain to work on the engine at such a low level when it mostly "works" today.

ANet has already transferred from in-house servers residing in TX to AWS on the east coast region. So we've already had a 'hardware' change with no improvement. It's certainly possible that they're similarly specc'ed but to be honest, they know what the load is on these servers. If just scaling up doesn't work, it's an engine problem.

There have been numerous threads about this. ANet devs have been aware/acknowledged this issue for years. The problem is it is a core engine issue -- something that may not be able to be resolved; or resolved without significant impact, thus testing, thus -- from a development perspective, flushing money down the toilet. Don't expect to ever see a fix. I certainly hope I'm wrong, but from a financial perspective, it doesn't make sense to fix this.

[GvG] Reform would like to participate.

Was it? The implementation was poor. Remember where OW used to be? Or how NET currently is for defenders? Or where you can just bail off any ole cliff as a defender to escape being killed? Gliding was not and is not beneficial to the game mode.

@"Gaile Gray.6029" don't be afraid to save face. It's OK for a company to do. Maxis did it by refunding Sim City sales. Bethesda (despite ongoing issues) has apologized about the state of Fallout online. And there are more examples in the games industry if you hunt for them. It's OK to apologize. Everyone has been there, we all understand it and ultimately people are grateful for apologies when they truly mean it. https://www.wpr.org/new-study-reveals-importance-apologizing

I see this on occasion, but usually only after entering immediately upon reset and it takes a minute or so to clear up. In the distant past I have seen this persist for quite some time or even have objectives be the wrong color (e.g. green circle when red owns the objective).

Should have been on late NA reset last night. Farmed the hell out of AR and NSP in SMC, then moved onto AR EBG keep front gate while NSP was attacking double gate. Capped AR keep with little resistance and then farmed NSP.

We know. .

Gankers aren't "bad players", they're playing the game as intended. Block people from reaching an objective. Militaries perform blockades all the time, this is effectively a gankers role. As someone who really only plays in zergs with a glassy build, gankers suck. But they're not bad.

I approve of this message.