test content
Logo
What is the Arc Client?
Install Arc
Why backcap at 500-200? And AFKers...
kingjon555
Member Posts: 46
My team was demolishing the enemy, holding positions 3 and 2 on Hotenow PvP map; every attempt to backcap 3 or beat us toe-to-toe was quickly smashed by our team. We were up 500-200 and our margin was increasing quickly. Looked like we'd win at a ratio greater than 2-to-1.
Our cleric began trying to cap 1 even though this was the case, failed miserably due to us not supporting him-what we were doing was working splendidly already.
FIRST QUESTION: People said on my prior thread that this (backcapping 1) was the correct thing to do. WHY??? In a case where you're crushing the enemy team anyway, unless you outnumber the enemy team and want to end it quicker, it's senseless. You could either win 1000-500 quickly by holding 3&2 (or 1&2) or keep #2 in a state of perpetual neutrality while occasionally grabbing the opponent's home node, and take ages to win.
I am a 20k GF, very experienced pvper, and I have NEVER seen backcapping be helpful in such a situation (where your team is already winning). Now, if we were in a bit of trouble- losing toe-to-toe, teammates werent playing any defense, etc... then backcapping has many advantages.
SECOND QUESTION/COMMENT: That cleric I mentioned was so mad at us that he AFK'd in spawn and we barely pulled that game off, as it was 4v5 and the enemy team had a good cleric, with a score of about 1000-950... Why is there no method to punish/report/kick/anything players that do this? They're worse than the quitters of two weeks ago because they leech glory.
Our cleric began trying to cap 1 even though this was the case, failed miserably due to us not supporting him-what we were doing was working splendidly already.
FIRST QUESTION: People said on my prior thread that this (backcapping 1) was the correct thing to do. WHY??? In a case where you're crushing the enemy team anyway, unless you outnumber the enemy team and want to end it quicker, it's senseless. You could either win 1000-500 quickly by holding 3&2 (or 1&2) or keep #2 in a state of perpetual neutrality while occasionally grabbing the opponent's home node, and take ages to win.
I am a 20k GF, very experienced pvper, and I have NEVER seen backcapping be helpful in such a situation (where your team is already winning). Now, if we were in a bit of trouble- losing toe-to-toe, teammates werent playing any defense, etc... then backcapping has many advantages.
SECOND QUESTION/COMMENT: That cleric I mentioned was so mad at us that he AFK'd in spawn and we barely pulled that game off, as it was 4v5 and the enemy team had a good cleric, with a score of about 1000-950... Why is there no method to punish/report/kick/anything players that do this? They're worse than the quitters of two weeks ago because they leech glory.
Post edited by kingjon555 on
0
Comments
We were only dominating because we were together, not spread too thin, and playing defense, especially against attempted enemy backcaps. As soon as the cleric started trying to get 1, things started going much worse. Instead of listening to my teammate's advice to just hold the line, he refused and the team began falling apart, almost to the point of losing as I described.
Why fix something that isnt broken?
back capping doesn't seem to be the issue to me, Rogue DC going off alone and then raging, because he got no support from his team, which 95% of the time he would probably get that support from others going to back cap.
So lack of teamwork and communication almost made your team fall apart.
sounds about typical of a pug group
WAI.
EDIT: Also, I would have you know, Stalesmoke, that it was a 4man premade with the cleric addition, and my teammates were all communicating to hold 2 and win simply instead of attempting a likely-to-fail full-cap... The cleric refused. So in fact, it was the lack of listening of the final player that threw us all off. Trust me, I wish we could have found a 5th from our guild to fill that slot, but we couldnt.
Next time help the DC, or even better, send a perma or GWF to enemy node.
Just don't forget they need help as well
Back capping is a great way to separate the enemy team. An all out fight on point 2 is not necessarily a good tactic. In fact it's a bad one IMO. You want to spread out the enemy and normally this is done by sending your tanks or annoying to kill classes to back-cap but since the better back capping classes did not back cap the cleric chose to go which is normally a better plan than waiting for the enemy to decide to do the same to you.
Should the cleric have raged and AFKed, no.
But his tactic was a sound tactic and neither myself or the others who responded to your thread so far can fault his decision to back-cap or his frustration in the situation you described.
Moreover, it is also a double-edge strategy. When you go for backcap, it means you leave your team at a disadvantage in numbers at mid. Also, it makes you an easy target for ganking since the enemy camp is right next to it or simply get owned by someone with better skills/gears. Finally, for someone who goes for backcapping, he/she should be ready for the worst situation that is getting killed without capping.
In my opinion, the DC failed in both doing his/her class role (supporting the team and wandering alone), reading the current combat flow(afking when his/her team is winning), understanding the nature of the strategy(ready to fail) and ego-management(nerd rage after a fail backcap).
If the OP and his team didn't want to back cap, then they shouldn't have to, regardless if most of you 'think" it is better or not.
The DC should either conform to the team, or make his/her own.
Either way, try to find a 5th so this doesn't happen again, or try your best to either
A - Work with the DC (Or other random) if possible, maybe even follow their plan if it works
B - Hope he/she listens to you after they die a few times.
C - Explain your plan and pray they listen in the first place.
D - Leave them to it.
But like you said, you guys were already winning and if it ain't broke don't fix it.
I guess this is just a case of miscommunication more than anything.
Again, I think this is just miscommunication between the two parties.
hope not, because i afk all the time if i have to be the boosting factor and do more usefull stuf then they re doing by not playing for circles for example.
or at clearly losses, where again people don`t play for circles
i think it`s a waste of time to send such pictures. even 1 video wouldn`t show enough maybe.
it would be fun if vid showed people not playing for circles so not actualy playing the game would get trouble ;p
but no they go waste costumer service time with reporting while they re the baddies themselves.
have to listen to that kind of weird stuf every day.
it just feels weird also playing obviousy losing games. while you re playing for 50% reward you re giving the other team each second double reward.
till the 15 min cap.
after that it `s even worse, playing for 0 reward.
I had a match the other day which consisted mostly of players just riding back and forth between nodes 1 and 3, with an occasional brief stop at node 2. Almost no fighting. It was long, but we won.
Contesting just means an enemy player stands there. They were contesting 2 everytime they came out of the spawn. Keep someone running to backcap and someone running to their home to keep them contested more than not and the op would have lost, because the enemies home would have been the only base ticking most of the time.
Back capping is usually the way to go IF you have someone who can survive and handle it. It pulls the team out across the map and stoops them from focus firing your team. But this is too generic, that would be like saying "every time you are close to the free throw line, shoot for 2 points." Doesn't make sense by itself.