Jump to content
🛡️FORUMS ARE IN READ-ONLY MODE Read more... ×
Sign in to follow this  
rangerrambo

"CALLSIGN" globalChat sideChat groupChat

Recommended Posts

Trying to have the sideChat example:

PAPABEAR=[West,"HQ"]; PAPABEAR SideChat "Hi there";

Which gives something to CROSSROAD: "Hi there"

How do I change the callsign? or make a new one?

Tried so far:

1.

PAPABEAR=[West,"Almighty"]; PAPABEAR SideChat "Hi there";

2. Using setIdenty on a unit and configing it in description txt.

class CfgIdentities
{
class Bob
{
 name="Almighty";
 face="Face20";
 glasses="None";
 speaker="Dan";
 pitch=1.1;
};
};

http://community.bistudio.com/wiki/sideChat

http://community.bistudio.com/wiki/setIdentity

Share this post


Link to post
Share on other sites
unit [url="http://community.bistudio.com/wiki/setGroupId"]setGroupID[/url] ["Name for group"];

Share this post


Link to post
Share on other sites

Don't know what I am doing wrong but this is what I did:

1. Made a civilian on the map, named him bob and changed init to

group this setgroupId ["Almighty"];

2. When I use the command

bob globalChat "test";

I get :

Civilian: "TEST"

I want:

Almighty: "TEST"

P.S. Also I would like to avoid using a unit for this, its more like a server msg for team dm status.

Share this post


Link to post
Share on other sites

Try making a gamelogic named bob say it. It's saying civillian because its a civillian. Mess around with it, try other units and get an idea of what's going on, then try using a gamelogic or more naming commands.

Share this post


Link to post
Share on other sites

Use a GameLogic in that case. Place it down and name it whatever:

almighty globalChat "pine nuts";

Will display as:

PINE NUTS

If it really must say "Almighty" and be on Global Chat use:

almighty globalChat "Almighty: pine nuts";

Share this post


Link to post
Share on other sites

Very nice ;)

Also, tested this just 'cuz I'm bored.

Radio Alpha trigger On Act.

almighty globalChat "almighty: pine nuts";

Gamelogic named almighty.

Displays:

ALMIGHTY: PINE NUTS

Share this post


Link to post
Share on other sites

That's what I said! :) And the name of the gamelogic doesn't matter since it won't display.

Share this post


Link to post
Share on other sites

Ok I guess that will work for me. Thought you can rename the 1-1-A (player) name and rename that in a different callsign.

Here is my final result.

bob globalChat "Almighty: ""BLUFOR lost a plane."""

Thanks kylania and Grimes for the assistance.

Share this post


Link to post
Share on other sites

Sure thing. Yeah, I used to think and deathly hope you could change the 1-1-A (callsigns defined by the game) on the unit screen to something actually cool and fitting, but was sadly disappointed. Hope that happens someday. I'm going to put that on my AA3 wishlist right now actually.

Share this post


Link to post
Share on other sites

Well, you can use setGroupID to rename them within game communication. And you can use the Description field to rename the units on the slots page, so you "kinda" can, but not as well as you'd like.

Maybe make setGroupID execute pre-game or add a new group description field or something.

Share this post


Link to post
Share on other sites

I just tested setGroupID, and here are the effects:

group this setgroupId ["Black Mamba","GroupColor7"];

Can't get the color to work though.

2k0obm.jpg

Share this post


Link to post
Share on other sites

No, the color was to do with the actual callsign name, back in OFP when groups were called things like ALPHA BLACK. It's not to change the colour of the text.

Share this post


Link to post
Share on other sites
No, the color was to do with the actual callsign name, back in OFP when groups were called things like ALPHA BLACK. It's not to change the colour of the text.

That's what I was wondering when I read the biki :P

Share this post


Link to post
Share on other sites

It is possible to change the vanilla callsigns from these non unit non logic based chats, but you have to do it using stringtable.csv. The only thing truly unique is FIREFLYBASE, the remaining three units will share whatever callsign you give them.

Another, slightly more advanced and not trivial to setup, method is to use kbTell if you like chatter without text being forced to uppercase and doesn't want to setup cfgRadio and use the radio commands (which aren't very flexible).

Hopefully we'll get the new TAKOH radio commands eventually, but so far these new commands are so far radio only, not chat.

Share this post


Link to post
Share on other sites
Sign in to follow this  

×