PMC Editing Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Custom Callsigns ======

Ever wanted to change that PAPA_BEAR to something else? Well here is how to do it.

Open up your **init.sqs** file and define your callsigns like this:
<code>
abelement = [West, "AirBase"];
hqelement = [West, "HQ"];
</code>

Then open **stringtable.csv** file with your favourite text editor and define the names for "abelement" and "hqelement" as follows:

<code>
STR_CFG_FIREFLYBASE,"AB Element"
STR_CFG_PAPABEAR,"HQ Element"
</code>

Notes: Before you go on, keep in mind that **[West, "Base"],[West, "PAPA_BEAR"]**, and **[West, "HQ"]** are all the same thing. Because of this, you cannot use a combination of the afforementioned three to make different callsigns. To make two different callsigns, you must use **[West, "airbase"]** along with either **[West, "Base"], [West, "PAPA_BEAR"]**, or **[West, "HQ"]**.

When you make a callsign using **[West, "Base"], [West, "PAPA_BEAR"]**, or **[West, "HQ"]**, you must allways use the line //STR_CFG_PAPABEAR,""// to define the callsign in the stringtable.csv file!

When you make a callsign using **[West, "airbase"]**, you must use the line //STR_CFG_FIREFLYBASE// to define the callsign in your stringtable.csv file!

After your callsigns have been defined, you may now use them in your missions like this:

<code>
abelement sideRadio "This is AB Element to all units.";
hqelement sideRadio "HQ Element to Alpha, mission accomplished.";
</code>

If you are making an addon, then of course you can specify as many custom callsigns as you want, but thats not in the scope of this page. This page was to instruct you to make mission callsigns without addons.
PMC Editing Wiki

User Tools

Site Tools

Page Tools
