GRRR Squad Forum

I can do Saturday or Monday, but Sunday on the [grrr] server sounds best.

Friday and Saturday is out. Sunday or Monday is good.

I've sent a mail to the league admin in the meantime to see if we can use the GRRR server or not.

Else we may have to play on Monday

Cool - Lee can you book the SGS server for Monday just in case we dont get permission to use the Grrr server. Please book it for 20:30. and let us know the details so that i can post on the do gaming site

HI guys, I think the practise session against BBH went quite well even though they were at a disadvantage with only 7 players in the same chat room etc. However, pulling back 45 tickets and winning by 30 is impressive in anybody's book so well done.

I do however want to apologise for me losing my cool at one stage in the game, Voetsek is correct, that was unnecessary, and I do appologise for going on a rant there. The game is supposed to be a fun game for all to play, so yeah, that was unacceptable from my side and sorry if I offended anybody. I'll try and stay more calm in future.

Skouperd wrote:I do however want to apologise for me losing my cool at one stage in the game, Voetsek is correct, that was unnecessary, and I do appologise for going on a rant there. The game is supposed to be a fun game for all to play, so yeah, that was unacceptable from my side and sorry if I offended anybody. I'll try and stay more calm in future.

Any time where our designated commander has to raise his/her voice to get everyone to keep quiet after already twice asking politely is a failing on the part of us, his/her troops, not the commander's. If at any time during a practice or match we find ourselves talking at the same time as Skoup, it is important for us to stop immediately and listen. Skoup's outburst last night was the result of too many people talking shit over the comms when he was trying to give us important information to regroup and attack a specific flag. No-one likes being shouted at like a child, but if we're acting like children then it's what we deserve. We cannot ask Skoup to take on the role of commander without at least offering him the courtesy of shutting our traps when he's issuing commands. It takes a lot to try and keep this clan organised in the middle of a fire fight, as many of us who have had the experience will agree, so I for one would like to say +1 to Skoups for breaking his usually quiet, humble, background nature and taking on the task. It is a lot more unpleasant to have to yell at your maatjies than it is to be yelled at by one, so rather than say "Shout at us if you need to, skoup!", we should take it upon ourselves to avoid putting him in that situation. I know I'm one of the worst for blabbering unnecessary bullshit in comms, but I'm trying to keep it more concise as should we all. As for anyone being offended - if you weren't talking then the "SHUT UP!" was not directed at you; if you were talking, then you thoroughly deserved the ch00ning, big mouth. Suck it up and zip it up. <--(That last sentence sounds a bit on second reading...)


wrt practice, I enjoyed it immensely. We are playing a lot better as a team and are starting to assess situations and respond to them tactically on the move. Well done to everyone, and BEEG thanks to fly for helping BBH out with numbers.

thanks again S3xy, it was a pleasure to help out, and a bit of an eye opener:

Skoups my apologies as well for talking, especially as i was on the other team.

I wanted to reiterate something. on a few occasions i got the drop on a second enema without the first enema saying he had been KNIFED, IE - THEY ARE RIGHT THE F*&* ONTOP OF US< WATCH YOUR BACK.

I also dont understand why BBH lost the match, as i lost voip with them half way through the 2nd round (or they heard me talking to grrr, and didnt respond)
I did try and make it more difficult for you okes without giving anything away to them, and then the last 20 tickets of the last match, they just blew into the wind, not sure why.

Booking Successful

Server Password will be: bunny

Server you have booked: -= SGS BFBC2 CLAN III Server =- 196.4.79.8:11030
Start Date and Time: 2010-07-19 Mon 20:00
End Date and Time: 2010-07-19 Mon 21:00

Server you have booked: -= SGS BFBC2 CLAN III Server =- 196.4.79.8:11030
Start Date and Time: 2010-07-19 Mon 21:00
End Date and Time: 2010-07-19 Mon 22:00

Fly, you are right with regard to the communication. It is a fine balance between chatter and valid intel. (More on that later.) I don’t know if it was just me, but it really felt as if the team in that last match just shifted into a higher gear, I mean the ticket counter was 115 to 160 against us and we ended up winning that match with 30+ tickets.

Regarding communications, I am all for communicating valid intel, and things like, “I’ve been stabbed” is in my opinion valuable intel as that not only reminds your squad medic that you are down and that you need a revive, it also tells them that there is somebody very close to you. We could even take it one step further, if I had to choose between the following two options:
“I’ve been stabbed at concrete hill” versus, “I’ve been stabbed by Chaos” I am not sure which one I will prefer, I am tempted to say the latter, because if the medic does go in to revive you and he does kill somebody, if that somebody is not Chaos, then he knows there is one more baddy around. The medic should know exactly where everybody else in his squad is in any event as such location is not that important here, and if he doesn’t know where you are, he can see you on the mini map, if he cannot see you on the minimap, then he can see you on the bigger map, point is, location is not that critical in this instance. The counter argument, if you say “I’ve been stabbed at concrete hill” then perhaps somebody from the other squad on the opposite side might have a shot at that person, but I find it unlikely. So if anything, “I’ve been stabbed by Chaos” should give your fellow squad members sufficient information. As we learn to play together, and distinguish each other’s voices, and learn where each other is, then communication will automatically come down.

The problem is when we are losing, and we all hit panic stations and everybody is starting to shout out orders while that is exactly the time it is critical to keep quiet and rather wait for your squad leader’s orders. But in the game yesterday, the SL cannot give their orders without two other people giving other (and conflicting) orders, how can we expect that we all work together then? Everybody in the squad is extremely experienced players, and as Mega once said, when you are dead, take that 15 seconds to assess the situation. Don’t just go rushing in, calm down.

If I could break down a rough guide on who is to give what kind of communication and approximately how much of the TS should be filled with it, then this is more or less the breakdown:

1. Commander relaying attack / defence orders, 5% (“Alpha squad spawn at “B” and attack “C””, “Bravo defend “B””, “Charlie squad, help Bravo squad with that APC”, “Everybody, let’s regroup at “B” and attack “C””, “We need to preserve our ticket bleed, need more medics”, “Lee, how is it going with “B”?”, “Voetsek, what is happening at “B”?”)
2. Squad leaders keeping the squad together 10% (“Murgs, pull back a bit you are too far forwad”, “Slodaz move forward a little bit”, “Shadey you cover that door, I’ll cover this door”)
3. Squad leader giving orders 10%, (“Bravo squad, let us advance a bit forward”, “Alpha squad, get bodies on the flag”, “Squad, hold your spawn, wait for me to get into position”, “Murgs spawn assault”, “Shadey, take the UAV”, “Jono, ninja around to “A””, "Ok Alpha squad, spawn on Paul and go for the flag, Paul, hold your spawn”,"Slodaz, dart the APC, Murgs, help Slodaz".
4. Squad members 50%, (“Paul, I am reviving you in 2”, “I’ve been sniped from concrete hill”, “2 enemies moving to “C” via dirt road”, “Murgs, drop me some ammo”, “Squady, I am waiting to spawn”, “UAV is up”, “UAV is down”, “The 2 guys that ran to concrete hill is down”. “Sensor mine on us”, “APC darted”, “one shot in on the APC”, “APC being repaired by 2 engineers”

Now as one will expect, the squad members will do most of the talking on TS sharing valid intelligence, the key though is that squad members should try and distinguish between “orders” and “intelligence” and only give “intelligence” in a clear and concise manner. Also, when your squad leader is talking, listen to what he is saying, orders from the squad leaders should always take precedence over any intel a squad member may have. If after the order the intel is still relevant, give it then, but give your squad leader time to talk first. All the squad leaders have very distinctive voices, (and commanding voices), so it should be very easy to hear them speak when they speak. Even if it ain't your squad leader talking, but the other squad's given them the curtousy to keep quiet so that that squad could hear the commands as well. When I have my commander hat on, I normally try and wait for a gap in TS before I speak, and if I really have something urgent to say, I normally ask for some silence before speaking. Saying that, I am also guilty of giving "inteligence" or "squad member talk" when squad leaders are trying to give orders, and that is something I'll try and work on as well.

I know one ting that did help with bringing out tickets back, was everytime Alpha lost the flag it was defending, we went to take the flag the enemy were no longer defending. This kept us with having two flags for the majority of the match. We didn't try immediately go back and fight over the flag we just lost.