Playing the game wrong

[Arnoldio]

Not me, but some people seem to absolutely miss the point of AAS it seems...

There is always a squad wich would not "rush" to the second flag you have to take, but the third, expecting that in that time, the rest of the team will cap 2 flags before enemy comes to the second flag, where the squad was set up.

Ok, i understand, go one flag ahead if you see that the first one has enough people to cap it quickly, but after that, whole team should regroup on the flag they had to defend and send out attacking grouups or defend like a whole team. (especially when there is no alternative flags to capture) So, i understand that the reason why AAS was made is, to concentrate the team on a smaller area so the gameplay would be actually more full and tense, to create a line between two teams. The point is to push the line or stop the enemies from overruning you on that point.

How it should be played in my opinion and i think its the quickest way while being strong and not fragile is to "alternate bounding overwatch" all the forces on the ground wich are combat ready from flag to flag, so 2 squads move on the first flag, sets up, while second pair heads for the next, sets up at sedon there, first one joins and passes the second group and goes for the next flag an so on.

On all maps, the amount of flags is about 4-5, count in that you do not control every one of them. You have 6 FOBs at disposal, use 2 or 3 of them in close proximity to the objective itself, that leaves you at least another 3 to use on flanking/backup/strategical positions. But people still fail to realize this and place fobs just because their squad can respawn, because they will get killed in at the gates of enemy main, "holding the enemy back".

Think about what can you contribute to the team, and not what can the team offer you. Calling in choppers on enemy AAs and asking for armour suppor to destroy the tow will only get the asset and the operator killed, because you didnt think about the situation, "wouldnt it be better to destroy the direct threath" and then call for support when you are in control of the situation and you know whats happening.

Same goes for use of assets, its easier to leave the logi truck in the middle of nowhere, than calling in a helicopter to get you to your squad. Remmember, assets such as chopeprs are made to transport you, not the logi trucks.

Simple, eh? Not for everybody.

[L4gi]

One good squad sent to the enemys first flag will cause loads of confusion and failure on the enemy team. Even though people always complain about "rushing", I find it hilarious that the people complaining never do anything about it. If you know someone is going to rush you, do something about it. If a squad on your team is doing it, be happy that you will have less pressure capping the flags before.

[rampo]

Sometimes those solo specialists behind the lines can be quite usefull in taking off FOBs and softening the enemy before the main force's arrive. But this just works when the rest of the team is doing it's job

[charliegrs]

Im pretty sure about 50 percent of the players on the public servers arent playing anywhere near correctly.

[ComradeHX]

I fail to see how...

Rushing into "accurate defensive fire" does not seem to work well.

[IAJTHOMAS]

The problem usually isn't trying to get a toe-hold in forward flags, it that people fail to recognise when this isn't working and won't pull back and help. By all means gamble and hope the team catches up with you before you're overrun, but don't hang around when it become obvious that the team is struggling, as by the time you've got transport to somewhere useful its often too late.

[Epim3theus]

One good squad sent to the enemys first flag will cause loads of confusion and failure on the enemy team. Even though people always complain about "rushing", I find it hilarious that the people complaining never do anything about it. If you know someone is going to rush you, do something about it. If a squad on your team is doing it, be happy that you will have less pressure capping the flags before.

Sometimes these tactics are practised by "good" squads when it is obvious that teams aren't equal provided in experienced players. Especially when one team automaticly gets stacked with (clan players) that are used to play together, they will always be much quicker of the bat, gaining advantage.
In public play imo it's a Game not a match, winning from an obviously less organised, less strong team, round after round on a public server because of this ancient tactic, that's just unimagineble bad sportsmanship to me.
It's just a lame tactic to do on a public server, against players that aren't used to play together.

I think there has been a thread about this some time ago.

[mangeface]

I'm going to first, laugh, and second laugh some more at L4gi's response.

[Arnoldio]

It quite sad though...

Then they whine why were we beaten, they blitzed us and whatnot... well if you would really help to defend and push them back instead of just being mowed down 3km ahead, the thing would be different.

[AgentMongoose]

I fail to see how rushing an hostile objective to defend it from capture is unsportsmanlike.
But it really pisses me off when there are usmc squads at south city on mutrah when the docks are falling.

[PLODDITHANLEY]

it comes down to two factors:

Rushing takes advantage of the other teams slowness to get organized.

Teamwork is everything on 0.9, until 90% of players are on Mumble and working together 0.9 game play will be a bit 'bizarre'.

I think PR 0.9 needs organized events like no other update, but atm no one is keen on running them for some reason

[Pariel]

I'm going to first, laugh, and second laugh some more at L4gi's response.

I'm with you on that one. First response too...

I fail to see how rushing an hostile objective to defend it from capture is unsportsmanlike.
But it really pisses me off when there are usmc squads at south city on mutrah when the docks are falling.

The problem isn't with people rushing a hostile objective to prevent the enemy from capping it as fast. The problem (I would say this happens the most on Yamalia) is the squads that just run off to an objective that can't be capped because they don't want to play defense.

In AAS, defending is at least, if not more important than attacking. You can win without playing offense for the whole game, you cannot win without playing good defense.

There's a reason there's a ton of transport options on Yamalia -- so infantry squads don't have to walk everywhere. If you're playing infantry, you should be waiting at a flag while you either capture or defend it, and then jumping in a transport to head to the next flag.

[Sgt. Mahi]

Ahh! The endless frustrations from playing PR on public servers

[HunterMed]

I also saw a lot of strange game situations lately. But now again they are not strange anymore but normal I guess.

I sum it up like this: People are too flag-greedy.

okay rushing might be a good idea, BUT the other team rushes too.
So often I see the situation that 1 squad which defends or even trys to cap the first grey flag is overrun by "rushing" squads.

So in the end both teams have 1 squad defending and that squad being overrun all the time.
Though the "attacking" squads say: "hey they will cap it back for sure 1 sec and then we can cap this one!!!!"
And even smarter SLs say: "hey I am sure we will cap that grey flag soon, and look, already 3 other attacking squads here on the enemies second flag and no resistence, LET'S move to the next flag!!!!"

Sadly the defending squad is always unheard and no matter how often you write in teamchat or as CO tell other squads to move back to cap that flag they DONT.

Squads dont defend anymore - even less that in the past.
I saw some matches where 2 flags were grey in the back and the "attacking" team is already capping main base.
It is just rushing forward all the time from both teams, thus no flag gets really secured and is greyed again by those "rushing" squads.

DEFEND PEOPLE! DEFEND!!!

It shouldn't be like this:

1 Defend squad
1 attacking squad
4 "rushingubersquads"

The mainforce should defend and not attack...

Seeing that I dont know why people want to attack anyway, they will have less contacts than any defending squad. why?
Because the other team is attacking too with their whole team. LOL

[Outlawz7]

I'd have to agree with L4gi and everyone else at the same time, sure a well coordinated rush can help your team and tear apart the enemy team depending on how well organized they are, but you still need a main force and rushing is also useless if everyone is doing it. Organization would be the key word here.

[Arnoldio]

it comes down to two factors:

Rushing takes advantage of the other teams slowness to get organized.

Teamwork is everything on 0.9, until 90% of players are on Mumble and working together 0.9 game play will be a bit 'bizarre'.

I think PR 0.9 needs organized events like no other update, but atm no one is keen on running them for some reason

It happens on a server with 100% of people on mumble.. some people are just...fail...


And, why would you want to slow down the enemy with one squad, rather than help YOUR team to cap all flags quickly, because the maps are pretty much designed (when capping is needed by both sides) to be balanced when it comes to flags, so if both teams advance as the should, so, from flag to flag, both teams should meet in the middle...

[Mellanbror]

Some valid points made by some here. But in context towards opening statement: one squad "jumping ahead" is very often a good tactic. See them as scouting patrol. But if it flag behind doesn't get capped squad ahead must adapt too what the team as a whole needs. The biggest problem as I see it in PR is dividing of wills between all squads, almost all the time. There need to be only one mind controlling all...one will, simply put; a commander. Rarely there is a commander pressent on any server...except for after 40 minutes or so to launch J-dam. And here is also my only wish for PR dev, spice up the commander role so people will enjoy playing the part. How it should be done?...sry but really dont know. Bribe? Give the US commander a colt 1911. More selfused assets (for Co)? Mortartruckdeployment with a 400 meter range or so to get him on the move. But for now I think we should all just try and convince our buddys to command

[Drop_Deadx]

I believe if it works, then it's not wrong...

[ghoststorm11]

Bounding overwatch is a hard maneuver to pull off at any level. I believe it can work well as long as the SLs and Commanders are in sync. Another aspect is to have the bounding element not mask the suppressive fire given by the overwatch element. This can be very hard to do in a game. Also, The overwatch element should be no more than 150 -250 meter behind the bounding element to give sufficient and accurate suppressive fire. At the strategic level, it can be a cluster f*** if your squads/team isnt working together. Basically, have this planned out before you use it in a game.

[Dzanic]

Normally attacking uncappable flags is forbidden on servers. But this causes confusion on servers that do not apply this rule and only apply to forbid attacking an mainbase.The question here is what is the definition of a mainbase? The static spawnarea? The area protected by ABC or the area marked with a crossed flag?

The map Silent Eagle is a clear example. There are no mainbases on this map. Still you can get kicked for attacking uncappable flags. So you cannot rush to the airfield as Russian wich you would have done on any other map.