scriptName: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\| *(arg|eff|mp|serverExec|gr[0-9]) *= *(.*) * *\|([^=0-9]{12})" to "|$1=$2 |descr=$3") |
Lou Montana (talk | contribs) m (Text replacement - "\| *arma2 * * *\| *([0-1]\.[0-9]{2}) * \|game2" to "|game1= arma2 |version1= $1 |game2") |
||
| Line 1: | Line 1: | ||
{{RV|type=command | {{RV|type=command | ||
| arma2 | |game1= arma2 | ||
|1.00 | |version1= 1.00 | ||
|game2= arma2oa | |game2= arma2oa | ||
Revision as of 01:23, 14 June 2021
Description
- Description:
- Assign a user friendly name to the VM script this command is executed from. Once name is assigned, it cannot be changed.
- Groups:
- Program Flow
Syntax
Examples
- Example 1:
scriptName "leetScript.sqf";- Example 2:
scriptName format ["%1ARTY\data\scripts\ARTY_sadarmDeploy.sqf (_this: %1)",_this];
Additional Information
- See also:
- spawnexecVMscriptDone
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on 17:39, 13 June 2009 (CEST)
- Vigilante
-
scriptName is good when you want to load the handle of some spawn or call with some name:
example_scripthandle = [] spawn { scriptName "Example"; systemChat str example_scripthandle; // System: Example }