setRank: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " \| *(([^=\| ]+)('''|\[\[)([^=\| ]+)) * +\|p1=" to " |s1= $1 |p1=") |
Lou Montana (talk | contribs) m (Text replacement - " \{\{GameCategory *\| *arma1 *\| *(New )?Scripting Commands\}\}" to "") |
||
Line 41: | Line 41: | ||
</dl> | </dl> | ||
{{GameCategory|arma2|Scripting Commands}} | {{GameCategory|arma2|Scripting Commands}} | ||
{{GameCategory|arma3|Scripting Commands}} | {{GameCategory|arma3|Scripting Commands}} | ||
{{GameCategory|tkoh|Scripting Commands}} | {{GameCategory|tkoh|Scripting Commands}} |
Revision as of 02:43, 13 June 2021
Description
- Description:
- Description needed
- Groups:
- Unit Identity
Syntax
Examples
- Example 1:
player setRank "COLONEL"
Additional Information
- See also:
- ranksetUnitRank
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 Mar 26, 2009 - 19:24
- Wolfrug
- Changing a unit's rank using either setUnitRank or setRank will also REPLACE their current rating dependent on their new rank (colonels have a rating of 7500 etc). That is to say REPLACE, not add to: the unit's old rating will disappear with the rank change.
- Posted on April 12, 2014
- Waffle SS.
- Behavior when used on players in multiplayer seems unpredictable. (Arma 3 1.00)