Project Reality Forums

This thread is help educate players on proper communications. Some don't seem to understand that needless chatter is disruptive to others being able to hear other players, hear the environment or themselves think

Please follow these simple rules

1. If you're within local range of someone that youre solely addressing, use local speech. This frees up the squad channel for others in the squad that have no need for hearing that the LAT guy wants an ammo bag from the rifleman. People have a strange habit of calling out for medic using the squad channe when the locational feature of mumble can make it easy if you use local

2. If you're addressing a single squad over squad leader channels, then address that one squad with their channel, and not the "all" channel. This is again disruptive. IF you think the information is important to the entire team then broadcast it, but if you want a crate form the trans squad, tank squad don't care.

3. If you have to use an all-net radio, as commander or squad leader, keep it brief. Big long speeches unless you "have the floor" for something important are disruptive to the most important members of the team. Please do not abuse this channel

Tips for mumble:
- Make a deafen self key. This is extremely handy for when people their abuse privileges over mumble or you just need dead silence
- As stated the locational audio of mumble is handy for telling people where you are, without having to say it. IF you want ammo, medical help or just a hug, use local
- By the same token dont use squad net to say "im over here". Describing your location like "west of the blue house by a few meters" is much easier for a medic than "over here medic pls oh pls im dying oh please oh pls help"
- If you're in the middle of something important such as talking to a teammate or an intense firefight, and another team member is trying to address you for a different problem, instead of just letting them talk over what you're doing, disrupting you and not actually getting anything they've said, simply ask them to "standby" until you're free. This will prevent miscommunication and distraction.
- suggest some here

Yes. i agree with all points something i need to work on when playing PR

Problems I have as a squad leader is when people use global comms when speaking to one another, but it doesn't happen too often. I usually just use global when I do mortars and need fire missions.

I my self have to work on radio discipline as I frequently use squad chat against local. Guess it's just because I forget/can't reach my local key at the moment.

For those that use squad chat in things like armor/in any loud thing in general is to set your mumble to your speakers, and your game audio to your headphones. That way you don't have to use squad comms because you can't hear. Works fantastically.

Fir3w411 wrote:Problems I have as a squad leader is when people use global comms when speaking to one another,

No kidding!!!
I remember once on Khamisiyah...
Some guy running a recon squad didn't know the numpad existed or something.

All you heard:

"Yeah, I am gonna look and lase over there..... I don't see anything yet."
"I got a lase man, how do you not see it??"
"HIT IT NOW!!!!!"

I find it nearly impossible to play when people are doing that....

I really like it when people use comms correctly. "Hey you, this is me"

Ask for clearance before you start talking to a squadleader.

Sometimes you're busy talking to your squad then someone in the squadleader channel starts talking to you and give you all kinds of informations and he didn't say who he was and you were busy talking so you didn't pay attention or didn't hear and don't know who it was and then you have to spam the global channel to ask who said what and... GAH this is annoying!

So always start with "Hey 2, this is 4" and wait for the other to tell you to go ahead or speak or whatever. And call again of course if he doesn't respond, but don't just barf your infos at someone, that's rude, and annoying, and ineffective.

"2. If you're addressing a single squad over squad leader net, address that one squad and not all."

Make sure to always let the other SL know how is calling him, and give him some time to response.

So for example:


SL1: "Squad 1 for Squad 7"
wait a little bit
SL7:"Squad 7 here, whats the matter Squad 1?"
or if you are getting called by a other Squad, but dont have time to talk - for example if you are in a fight
SL7:"Squad 7 here, in a fight!/wait a minute"

Also use local when in vehicles, if you can't hear it turn your volume down.

When I'm addressing a specific squad and my squad is a heavy asset I'll use the following just in case they're unaware:

"Squad 2, this is Squad 4 APC (or tank/CAS/trans), do you require any support?"

Usually it's best to keep it short and sweet but there's also such a thing as not giving enough information. If a squad is in an awkward position, giving full information allows the SL to make an instantaneous call that can be vital to their survival.

I still like to keep it short and to the point unless asked for a full sit rep. But over all chat it's as short as possible and unless majorly important I only say it once.

Repetition for coordinates is also a good idea as sometimes once is never enough to fully remember it.

remember not to leave another SL hanging, if he's trying to get to you but you can't talk right then, a quick 'stand by' or whatever stops him getting frustrated

[R-DEV]Rudd wrote:remember not to leave another SL hanging, if he's trying to get to you but you can't talk right then, a quick 'stand by' or whatever stops him getting frustrated

1000 times this. In the middle of an intense fight this would even legalize using allsqdchat if you REALY dont know who was talking to you, but you want to let them know you heard, but cant respond now.

A lot of chatter is very annoying, but dead silence is even worse.

Is it not possible to implement a kind of "comm request" feature into the game, sort of like how an actual phone call is like?

So far example, SL1 wants to call SL2. He presses "Numpad1" to send a request to radio-com with SL2. SL2 sees the request on his screen, and can press either PgUp to accept or PgDn to deny. If he denies, then SL1 gets a message saying "SL2 has denied your communications request". If he accepts, then SL1 and SL2 can use voice chat to each other. That way, it is clear to all squad leaders who is trying to talk to them and makes it easy for squad leaders to know whether or not their message actually got through to the other squad leader.

I don't think any squad leader should be able to speak to all squads simultaneously. Only the commander should be able to do that.

The current mumble implementation does the job perfectly fine.

SL chat is good to notify all squads of very important intel that can alter the game. I try to avoid SL chat unless the information relates to more than 2 squads.

As I said in my previous post, I always identify the squad I'm talking to and my own squad if I haven't established regular comms, so they will know which squad I am from. Yes it can be annoying that people do not reply but all you can do is wait 10-20 seconds and repeat the message.

It all boils down to being able to cope with multiple tasks presented to you. Personally, if you are unable to juggle communications and the evolving combat environment effectively then squad leading isn't for you. The role of SL is demanding and it's not supposed to be a role any person can step into without practise. Simplifying the SL role in anyway is, personally, a bad idea.

Just a few things:

If another SL calls you, and you can't respond at the moment, you'll say something like "Stand by", but after that don't wait for them to call you again, call them yourself when you can to give them radio clearance.

Also, if you've got critical information for another squad, don't simply start transmiting, ALWAYS ask for clearance. Chances are the SL won't even pay attention because he's too busy leading his squad, I know I don't pay attention when the commander just goes like "Hey Squad, you've got a few guys to the north" and I'm in the middle of an engagement. To make sure the other SL understands you've got critical information, say something like "Squad B, Squad A, Message, Urgent."

Also, leave useless connecting words out of your message, things like "I've got", "There's a". Example, instead of saying "There's a full enemy squad 50 meters north of objective", say "Full Squad, North of Objective, 50 meters". Also, make sure to pronounce each word carefully and clearly, separate the words, kinda like the weird robotic ArmA AI commands. Also, use simple words and expressions, PR is not a Harvard english exam, correct and complex english don't matter. Mess around with the order of your words, to make sure each of them is given the necessary individual emphasis.

Good Afternoon,

Ok, this is a debate that will go on and on and on. There are some general guidelines that most follow but not all. There is no "community leadership" council / board that could really have serious input into this to provide some serious guidance with clarity.

I would rather take a team that talks to much than a team that doesn't talk at all any day of the week.

-SwampFox

This should probably be in the manual.