Guild Wars 2

Does the 30 second delay showing contested status apply to camps as well?
You can easily kill every NPC in a camp in less than 30 seconds with just a few people.

So we’re supposed to place someone in every camp all the time?
This really affects night crews — when you only have a few people in your whole borderlands, having someone at every camp is not feasible.

Currently, you can have “fast-response” teams who wait for swords to appear, then rush to the camp for defense. The point is, you actually get to fight people because if you’re fast enough, you can get to the camp before it’s flipped.

Now camps are just going to be flipped without anyone around. It’ll be much more PvNPC. I’m hoping we won’t end up simply doing camp flipping trains — reflipping whatever just got flipped.

(This is probably not an issue in higher tier servers, but for the lower tiers, having only 10 people in a borderlands at night is not uncommon.)

Yep it will just encourage PvDooring,

yes, it does, and it’s stupid.

Scouting will be key

By the time your scout says “HALP 20+ AT CAMP” the circle will be up.

it does and its stupid

theres no kittening point to scouting a camp, they can be taken within 30 seconds

I believe the purpose this serves is for people who are staying at a keep to tell the server that the enemy is approaching, so by the time the enemy attacks, a defensive team can get to the keep immediately to defend instead of manually walking all the way due to the contested waypoint.

People are too used to “flowing” with the zerg and taking no initiative to defend until it is already under attack. The next logical step is to properly reward people keeping watch at keeps.

It’s basically more PvE in WvW without adding a single NPC. Anet knows what we think about PvE…

^^

It simply means you have to be more observant – you’re not going to have white swords to follow, so instead you actually have to pay attention to your sentries and yaks.

Yes yes we all want to sit at a camp doing nothing when we go to WvW…

Ghedoriah.4290:

It simply means you have to be more observant – you’re not going to have white swords to follow, so instead you actually have to pay attention to your sentries and yaks.

Any small team with a brain knows you take the camp before the sentries and yaks.

a zerg doesn’t.

Yeah, any small team with a brain. You said it yourself of why 95% of the time, the yaks and sentry will go down first.

people don’t realize what scouting should be.

It isn’t sitting at the target waiting for it to be attacked, but watch the only 2 ways to get to the target to attack it.

If you sit at a supply camp waiting for it to be attacked reinforcements are often too far away to help you anyway.

If you see them coming from the passageway underneath hills keep going north on the other hand… – effective scouting.

Or, well, more effective is actually scouting the zerg early as they appear from their own spawn/part of the map and having someone tail them – most zergs don’t exactly look behind/to the side of themselves often after all. That way, you don’t even need stationary scouts unless you’re particularly worried about small roaming groups.

I’m frustrated when they play on mechanics with zero feedback.

Don’t you guys see it? Anet’s slowly trying to shift WvW from Zergdomination to a population spread out on the map with cumulative small changes. I guess QQers will stay QQers.

Pizz.3698:

Don’t you guys see it? Anet’s slowly trying to shift WvW from Zergdomination to a population spread out on the map with cumulative small changes. I guess QQers will stay QQers.

So people are supposed to spread out and sit in every objective and just wait for it to be attacked? And once its attacked you don’t pvp you just jump on an ac and watch them melt. That’s not fun.

If they want to keep the timer then it should be as follows:
30 seconds on keep contests
15 seconds on tower contests
0 seconds on camp contests

They should just make hitting a guard instantly contest any structure. A guard gets hit, they relay information! You want to do something stealth? Use catapults or a treb to hit walls and avoid guards. Wall caps are slower anyway.

Aytrix.4059:

Pizz.3698:

Don’t you guys see it? Anet’s slowly trying to shift WvW from Zergdomination to a population spread out on the map with cumulative small changes. I guess QQers will stay QQers.

So people are supposed to spread out and sit in every objective and just wait for it to be attacked? And once its attacked you don’t pvp you just jump on an ac and watch them melt. That’s not fun.

If they want to keep the timer then it should be as follows:
30 seconds on keep contests
15 seconds on tower contests
0 seconds on camp contests

No, but if you force doesnt consist of one massive blob, then the reaction is way smaller since your travel time is also smaller. If WvW consisted of multiple smaller battles over the map instead of 1-2 or 3 Wxp trains, then the 30second on camp flag wouldnt even be a bother.

I guess this could be a tier issue. Generally my server knows when a camp is going to be taken well before the contested state goes on it. Combining scouts with reading the map this gives at least the smart players who can read a map a tell that a camp is a threat 95% of the time well before its hit. But if lower servers with lower numbers who can’t afford to have scouts and for some reason don’t have roamers, taking these out of the equasion it might be hard to tell all the time. Personally from my experience in Tier 1 I wish they would take the contested state off altogether, because I see it as training wheels on a bike. Our server as can our opponent afford to lose it because we have numbers, we have havoc groups, roamers, scouts, escorts and defenders and someone always knows whats going on.

Pizz.3698:

Aytrix.4059:

Pizz.3698:

Don’t you guys see it? Anet’s slowly trying to shift WvW from Zergdomination to a population spread out on the map with cumulative small changes. I guess QQers will stay QQers.

So people are supposed to spread out and sit in every objective and just wait for it to be attacked? And once its attacked you don’t pvp you just jump on an ac and watch them melt. That’s not fun.

If they want to keep the timer then it should be as follows:
30 seconds on keep contests
15 seconds on tower contests
0 seconds on camp contests

No, but if you force doesnt consist of one massive blob, then the reaction is way smaller since your travel time is also smaller. If WvW consisted of multiple smaller battles over the map instead of 1-2 or 3 Wxp trains, then the 30second on camp flag wouldnt even be a bother.

If someone is at the camp scouting or you are fighting within visual range of the camp being attacked then yeah you will be able to defend it. But since 5 people can cap a camp in 30 seconds, If you can’t see the camp, the camp is flipped before u even know its attacked and you have to wait 5 minutes for the buff to go.

I agree on spreading people out on the maps and making smaller group play more viable, but these changes just don’t cut it for me. The timers make defense of objectives harder unless you have people sitting there with nothing to do until it is attacked. ACs buff makes it easier for people to just sit behind walls and farm xp and loot without ever having to pvp. That’s how I see these things.

Aberrant.6749:

Yes yes we all want to sit at a camp doing nothing when we go to WvW…

+1, there could’t be a more unrewarding job in WvW and yet if you want to hold a keep/waypoint while you are out numbered on a map.. it’s what you have to do.

It’s not fun.

-g