Labyrinthine
Administrator
Hero Member
Posts: 5814
Abuya?!?
|
 |
« on: October 20, 2006, 03:34:25 PM » |
|
Ok everybody, I thought about this one long and hard. I wrote up static strategies, and then thought about how we already know the basic strategies, and there isn't much wiggle room in regards to those strategies. In DoD: S you could attack a map from any number of angles with any number of squads and do ok. Sadly, CSS isn't the same. Thus I am going to try something which I've only used twice before: Fluid/Liquid Strategy, or strategy on the fly.
Only thing is, we're going to modify it slightly for use in CSS. Normally with liquid strategy a team would adapt to whatever is happening when it happens. What we are going to do is the following: base our strategies off of the popular static strategies, but use them very liquidly. The key to doing this is teamwork, organization, communication and some basic ground rules:
-------------
(For Terrorist)
1. The squad of whoever recieves the bomb will be calling the bombsite/strategy. Because you won't know who is going to get the bomb until the begining of the round, both squads are going to need to know what they would be doing next round if they had the bomb. Premeditate next round's strategy while you are dead, and then tweak it to fit your needs while your alive.
2. The squad who is not calling the bombsite/strategy will be playing a supporting role to the other squad. For example, if Squad A gets the bomb on Dust 2 and calls bombsite B, squad B would be responsible for making sure Squad A doesn't get flanked, bumrushed, etc... It's not your job to plant, just to make sure the other squad can do their job.
3. Squads stick together. (unless absolutey necessary to split up) A squad of 5 CTs has a much better chance of taking out one T than 1 CT vs 1 T
(For CT)
1. Both squads will need to formulate their own strategies for defusing the bomb, and can come together to work as a whole if they want to. The squad leaders will be responsible for talking to each other and coordinating their efforts in the event of intersquad cooperation. Preferably, stay seperate.
The reason behind this is because if you are working with more than 5 people, there is too large of a chance that something could go totally wrong. Everyone is flanked, walks in to an ambush, encounters a squad of T's on the way, etc... Stay seperate. In the case of something disasterous happening squad leaders need to relay the information to each other.
2. Again, squads stick together.
-------------
I don't know how fluid strategy will work out, but we'll give it the old college try. If it fails we'll run very rigid strategies, but if we can come together and make it happen, fluidity is a very nice thing to have. It gives us an edge against all of those who run rigid, canned strategies.
|
