Difference between revisions of "switchMove"
Jump to navigation Jump to search
m (Text replacement - "<!-- Note Section [A-Z]+ --> " to "")
m (Text replacement - " <!-- (DIS)?CONTINUE Notes -->" to "")
|Line 50:||Line 50:|
Revision as of 01:54, 6 April 2021
- Description needed
- This command has global effect when executed locally to the unit and will sync for JIP. In this case the animation on the executing machine is immediate while on remote machines it will be transitional. In order for the animation to change immediately on every PC in multiplayer, use global remote execution (see example 2). When the argument is remote, the animation change on the executing PC is only temporary.
- Syntax needed
- person: Object - unit
- moveName: String - unit animation (see animationState)
- Return Value:
- Return value needed
- Example 1:
player switchMove "AmovPpneMstpSrasWrflDnon";
- Example 2:
- Sit player immediately and globally:
[player, "AmovPsitMstpSlowWrflDnon"] remoteExec ["switchMove", 0];
- Posted on March 25, 2007 - 23:48
- In some cases the movement won't stay. I.e. AI hostages that put their hands behind their heads (_hostage switchMove "AmovPercMstpSsurWnonDnon") won't hold their hands up, unless you first use disableAI "autoTarget" on them. They mostly put their hands down because they 'noticed' unknown objects.
- Posted on August 03, 2008 - 22:43
- This command will not cause an AnimChanged or AnimDone event. However, playMove will.
- Posted on November 12, 2016 - 20:11 (UTC)
When using this command on the player unit outside unscheduled UI contexts, it will cause a minor camera glitch for a single frame.
For example, Draw3D and KeyDown are UI contexts and so are not affected by the glitch, but EachFrame and scheduled scripts are not UI contexts and are affected by the glitch.