setRank: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) (locality new) |
Killzone Kid (talk | contribs) mNo edit summary |
||
Line 11: | Line 11: | ||
| Sets rank of given unit. | | Sets rank of given unit. | ||
Possible values: PRIVATE, CORPORAL, SERGEANT, LIEUTENANT, CAPTAIN, MAJOR or COLONEL. | Possible values: PRIVATE, CORPORAL, SERGEANT, LIEUTENANT, CAPTAIN, MAJOR or COLONEL. <br><br> | ||
{{Feature arma3| Since Arma 3 v1.67 this command is {{EffArg|cmd|arg|loc}} {{EffArg|cmd|eff|glob}}}} |= Description | {{Feature arma3| Since Arma 3 v1.67 this command is {{EffArg|cmd|arg|loc}} {{EffArg|cmd|eff|glob}}}}|= Description | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Revision as of 19:36, 10 December 2018
Description
- Description:
- Sets rank of given unit.
Possible values: PRIVATE, CORPORAL, SERGEANT, LIEUTENANT, CAPTAIN, MAJOR or COLONEL.
- Groups:
- Uncategorised
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
Notes
- 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)