STOP USING THE "*"

[parch]

if i'm in contact and trans contacts me offering a crate i do not have time to open up caps lock and search for their squad nor look bottom left while i'm chucking a grenade and spitting orders. and if not that intense at the very least i'd rather be scanning than taking a good 3-5 seconds unattentive.

Not a reason, just answer them when it's safe. Do not justify your laziness with your milsims xD

[Hunter291]

WHAT ***************************************************

[fecht_niko]

Insulting the spammer pretty hard works too...

[Jabil_One]

And what can i do as SL when i see a clusterfuck of bluedots from different squads heading towards into enemy tank but their squadleaders are in a complete different location?

Should i press 3 or 4 different SL channels and tell 4 times to an SL that their mates running into a enemy tank?!?

No, never gonna happen, i press * and tell that info one time.

[parch]

And what can i do (...)

Marking the tank on the map would be a good start

[Jabil_One]

Marking the tank on the map would be a good start

And than everyone knows magically that he must open the map because i made a marker?

[doop-de-doo]

I tend to do it more than I should, but at least I'm succinct. The worst offenders are usually trans heli pilots.

As someone who flies trans often enough, many squads don't realize they should include their return information. This is what you end up with, and usually at the most inconvenient moments:
"Trans, take us/bring crates/extract us/etc. to...", or worse, "Trans, come in/can you hear me/are you there/can you respond, please/etc?"


All this means is that someone is spamming my comms and I don't know who it is because I didn't have time to look.

That means the team has to deal with a "*": "Which squad was trying to reach trans?"

--------------------------

The other situation is the guy who doesn't realize you are really busy escaping/trying to land/ etc. and this
guy is insulted that you haven't responded yet.

"6 to trans?
6 to trans...copy?
6 to trans? This is 6!
TRANS THIS IS SQUAD SIX! ... etc." Good stuff.

Even if he's told me his squad number, I'll mash the "*" as I know I will reach him. I just don't have enough time to look closely at the keypad. Better telling him in "*" comms then to tell the wrong squad leader to shut up by hitting the wrong button.

[Suchar]

Hey, we are not talking about "do not use * in general" but about "do not spam * in SL chat".
That's the difference.
Its okay to tell other SLs about enemy tank or just some another useful intel.
Spamming is when you are telling something useless. You don't really need to tell to all SLs that you need supply (when talking to TRANS sq).

[Jabil_One]

Hey, we are not talking about "do not use * in general

Name of the Thread says STOP USING THE "*" and many said yes. So people talking here about to stop using it.

Another scenario: Enemy jet spotted D4 heading southeast.

Should i start looking which squad is in CHARGE of the AA manpad or which squad is close to an active Stinger Emplacement?

OffTopic:

To all YES sayers, please stop using "H" when you are wounded to call the medics from different squads.
Because its the same shit. You spamming your help requests and my medic isn't able to understand what i or my squadmates telling him in Squadchannel. Please, start looking what medic from what squad is close to you and ask the SL if the medic can do the job. Lets look how much time getting wasted.

[Suchar]

Name of the Thread says STOP USING THE "*" and many said yes. So people talking here about to stop using it.

Another scenario: Enemy jet spotted D4 heading southeast.

Should i start looking which squad is in CHARGE of the AA manpad or which squad is close to an active Stinger Emplacement?

1. Well, if some ppl dont really know how to use * its not really reason to disable this option.
2. IMO devs will not disable this, cuz it would be stupid move, it would rather decrease teamwork level.

To all YES sayers, please stop using "H" when you are wounded to call the medics from different squads.
Because its the same shit. You spamming your help requests and my medic isn't able to understand what i or my squadmates telling him in Squadchannel. Please, start looking what medic from what squad is close to you and ask the SL if the medic can do the job. Lets look how much time getting wasted.

I agree.

[parch]

And than everyone knows magically that he must open the map because i made a marker?

There is a text "enemy tank spotted"

[agus92]

There is a text "enemy tank spotted"

Wich is mostly ignored. IMo, the best approach is to comm individually with squads, and as commander giving them an observe mmarker to the thread. But sometimes the * is still necessary.

[Tommygun]

I think spamming * for Armour and Cas info is ok...as well as typing and marking. Not much else.

[Smiley1967]

I think this thread is more about:

sq6 - [*] This is sq 6 we need supply crate at Alpha 6 kp 4
trans sq - [sq 6] Copy that, Im on the way!
sq 6 - [*] OKAY trans sq, but please drop it exactly at [..somewhere..]

At the same time in every other SLs head appears a question.
WHY THE FUCK CANT YOU USE YOUR NUMPAD AND TALK DIRECTLY TO TRANS SQAD??!?!?!?!

This is the most annoying thing in SLing. (confirmed)

True words have been spoken,
but still the bigger problem is that the SQLs are not communicating with each other most of the times. Where to build FOBs or even super FOBs who is going to attack who is going to defend and so on. Sometimes the SQL Radio is a little bit to quiet.

[bahiakof]

And what can i do as SL when i see a clusterfuck of bluedots from different squads heading towards into enemy tank but their squadleaders are in a complete different location?

Should i press 3 or 4 different SL channels and tell 4 times to an SL that their mates running into a enemy tank?!?

No, never gonna happen, i press * and tell that info one time.

Within a teamwork.
The squad leader reports the contacts to the commander. The commander analyzes the situation of the team and makes the necessary marks for the squads, and if the commander needs to give a voice guidance to all the leaders, he does so using the "*"

But in the current universe of Project Reality, each SL has become a squad commander and even the team. And so there are no commanders in Project Reality because the squad leader has taken his place.

If a commander who does spam is bad, can you imagine 2 or 3 squad leaders making spam? At least the commander can remove it using the "mutiny" button.

[QuickLoad]

Within a teamwork.
The squad leader reports the contacts to the commander. The commander analyzes the situation of the team and makes the necessary marks for the squadrons, and if the commander needs to give a voice guidance to all the leaders, he does so using the "*"

But in the current universe of Project Reality, each SL has become a squad commander and even the team. And so there are no commanders in Project Reality because the squad leader has taken his place.

If a commander who does spam is bad, can you imagine 2 or 3 squad leaders making spam? At least the commander can remove it using the "mutiny" button.

yep, squad leaders can do the job of commander if commander isn't there / commander wasn't there / commander is inefficient, which is odd but that's how things are.

also using * is also used like you say so, sometimes like "Squads 3 and 6 will attack from north and i'll take my squad from the south" this is literally commanders job but so easily replaced by the SLs abroad

[parch]

This whole thread is people making excuses. Today I had some games with especially bad comms between SLs and I'm really sick of this.

Wich is mostly ignored. (...)

Perhaps you should be paying more attention.
Audio is easily ignored as well. Or missed. Especially if there are other people speaking to you at the same moment. On the other hand, a well placed marker will stay on the map and every single player within team will be able to see it, so they don't even have to rely on SL to pass the info.