CHOREOGRAPHY DESIGN SYSTEM - MOVERS & CONFIGURATION PARAMETERS

• Overview of Features
• Quick Start and Glossary - Start Here
• Features
• Movers and Configuration Parameters
• Notecards
• Multiple Notecards
• Using with Performance Director
• Using with Group Formation System
• FAQ and Tips and Tricks

Use the optional configuration parameters below by adding an "@" command line to your MOVER notecard.  
These parameters are entered in your notecard one command per line above the #BEGIN NOTECARD line. See NOTECARDS for entering route data.

@height_offset <number>

**New in Mover 2.0**

Using this parameter removes the need for dancers to remember to "page up" or "page down" when sitting on a mover to adjust to the proper height. Add this parameter to your notecards in the proper amount for each of your dancers. You must supply the integer, either positive for "page up" or negative for "page down."
​

• Each "Page Up" = 1
• Each "Page Down" = -1

​
TIP: Set this during rehearsal and while your dancers are in costume!

Example Line In Mover Notecard:

​@height_offset 2

@invisible

Used mainly for props, the @invisible parameter in a Mover's notecard will render that Mover 100% transparent until you remove the command from the notecard.  

Example Line in Mover Notecard:

@invisible

@silent_mode

Only owners can see the routine progress chat from the movers however you can turn that off. When this option is enabled, all output from the Mover is suppressed except for the line that shows which notecard was loaded.  Critical errors will still be sent but routine progress chat is disabled.

Example Line in Mover Notecard:

@silent_mode

@spot_dancer <number>

ONLY for use with the Performance Director HUD.
​
Parameter to be added to Mover notecard to enable the Mover to function with the Spot On Performance Timer HUD auto invite and group assignment. This parameter is only of use to people using the Spot On Performance Director HUD. <number> is the number of the dancer/mover that is included in the Director HUD group definition. If the @text is used in the Mover notecard (see above) then the @spot_dancer number is also added to the text.

Example Line in Mover Notecard:

Example GROUP Line in Performance Director HUD:

@spot_dancer 2

@group backup|2,3,4

This example shows Spot Dancers 2, 3 and 4 in a group called "backup."

@text <your text>

This parameter will make <your text> appear above the Mover. The text will hide when a dancer sits on the Mover. It is intended to allow you to name a Mover easily so that you can direct your dancers to their assigned Movers. It is suggested you keep names short and simple. When this parameter is active and the @spot_dancer parameter is active, the @spot_dancer number will be added to <your text>.

Example Lines in Mover Notecard:

Example Lines in MOVER for Use with Performance Director HUD

@text Nancy

@spot_dancer 1
​@text Nancy

"1: Nancy" will appear in hovertext above the Mover.

@user_channel <number>

​Assigns a chat channel to the mover allowing the mover to be controlled via chat command or by assigning a channel to the Choreography System HUD that comes with the system. Just add a channel to the notecard inside the hud and reset it (or take it off and wear it again).  Commands that may be issued via a HUD or typed in chat are: 

• play 
• pause
• reset

​The command pause will cause the mover to pause at the next Waypoint it reaches.  The command reset causes the mover to move back to the Designer Ring.

Note: Channel 0 is public chat and cannot be used.

Example Line in Mover Notecard: 

Example Chat Command:

Example Line in Performance Director HUD:

@user_channel 15

/15pause

89|SAY:15:pause

---

THE FOLLOWING PARAMETERS HAVE BEEN REMOVED FROM VERSION 2.0 

@barre_group <barre group number>
Have your dancers automatically invited to your Barre HUD and assigned to a Barre group as soon as they sit on the Mover. Add the command to a mover and give it the appropriate group number which you want that dancer to join. (For specific instructions on use of the Barre Groups feature, please see your Barre HUD documentation. This feature can only be used with the latest version of the Barre Dance HUD.)
Example line in Mover notecard:	@barre_group 2

@loop
Simply add the @loop command to the Mover's notecard and when it reaches the end of the route, it will automatically return to the start position and continue to play as long as there is an avatar on it.  As soon as an avatar hops off, the Mover will go back to the start position and wait for the next avatar to sit on it.  For the best visual of a looping route, it is advisable that you place your last waypoint close to the start position.
Example line in Mover notecard:	@loop

@play_on_sit
Great for models or an automated tour of an area, add the @play_on_sit command to a Mover's notecard to have it automatically begin play when sat on by anyone without the owner even being present. It will continue on its route until the avatar either jumps off or it reaches the end of the route. The mover will then return to the start position until another avatar sits on it. The Mover will continue to obey any Spot On HUD commands as well. To automatically animate an avatar when they sit on the Mover, please see Using Animations in the Mover (Up to Three) If you would like the route to continuously loop, use the @loop command.
Example line in Mover notecard:	@play_on_sit

@private_emote
As an addition to the capability of a mover to "chat" emotes in local or commands (See Features) to other devices on channels other than 0 (local), movers can now just chat or "emote" to the person on that particular mover privately so you do not spam local for others to see. As with the standard "chat" capability of the Mover, SL limitations require that you use 125 characters or less, including spaces. If you try to use more, only the first 125 will show in chat and the rest will get discarded by SL.
Example line in Mover notecard:	@private_emote

@user_channel_public
Used WITH the @user_channel <number> command above, this allows others to be able to send commands to your movers.
Example lines in Mover notecard:	@user_channel 25 @user_channel_public
Example in local chat from anyone:	/25play
Example command in Performance Director HUD:	89|SAY:25:play This sends the PLAY command from the Performance Director HUD to the mover at 89 seconds into the routine.

JUMP TO WAYPOINT:
A mover that is NOT currently playing can now be moved via a chat command to a specific waypoint.  This is useful in the design phase for editing the ends of routes without having to play the entire route.  Your movers should be assigned channel numbers using the @user_channel parameter described above when using this feature.  

  Syntax:  /<channel number>jumpto <waypoint number>
  
  Example:  /7jumpto 12    - all movers listening on channel 7 will jump to waypoint 12
  
Note:  If you press play after using the jumpto command, the movers will play from that waypoint and continue back at the start point.  Again, this is for the DESIGN PHASE ONLY.  It does not work while a mover is in PLAY.

This does not affect your animation sequence in Performance Director or Smooth Dancer however.  If you want to play your animations from that waypoint on for editing purposes, you will need to create a new sequence starting from that animation / waypoint.