You can use the following commands in your “~MOVELIST” notecard inside an MST Mover. These commands are listed in roughly order of popularity, with the most popular set commands first.
WAYPOINT=
The waypoint commands describe a location and rotation the mover should head toward, and how fast. You’re not expected to type these out by hand. the mover will print them out for you when you use the printmove command. Just copy them from your chat window and paste them here.
Examples:
[12:10:42] WAYPOINT=home,<0.000000, 0.000000, 0.000000>, <0.000000, 0.000000, 0.000000, 1.000000>, 0.200000, 0.000000
[12:10:42] WAYPOINT=waypoint1,<2.436981, -0.000000, 0.000000>, <0.000000, 0.000000, 0.707107, 0.707107>, 2.200000, 0.000000
[12:10:42] WAYPOINT=waypoint2,<2.400009, 2.393249, 0.162039>, <0.000000, 0.000000, 1.000000, 0.000000>, 2.200000, 0.000000
[12:10:42] WAYPOINT=waypoint3,<0.115204, 2.353912, 0.348673>, <0.000000, 0.000000, -0.707107, 0.707107>, 2.200000, 0.000000
Note: The timestamps at the beginning of the lines are ignored automatically to make copy and pasting easier for you.
VENUE=
The Venue command is used tell the mover to listen to a particular MST centerpoint. If it is set to “ALL” it will configure itself to work with the first MST centerpoint it finds nearby. If it is set to a specific name, the mover will only use configuration info from a centerpoint matching the specified name. Movers will try and ask the specified centerpoint to provide channel information so the mover can achieve highest communication speeds and least crosstalk.
Examples:
VENUE=ALL
VENUE=MainstageCP
ALLOW=
By default the MST mover will only listen to commands, centerpoints, and MST Performance Engines with the same owner as itself. You can use the allow commands to allow your MST mover to accepts commands and configuration from other owners. This is very useful when building performances cooperatively with others. You can allow SL legacy names, usernames, or UUIDs. UUIDs are preferred because they are most foolproof and will work even if the avatar they correspond to leaves the region suddenly or is not logged in.
Examples:
ALLOW=Arrehn Oberlander
ALLOW=3c637a3e-370e-4bca-b18e-92b4692a685a
Note: You can specify multiple ALLOW lines.
DEFAULTANIM=
NOTE: The following defaultanimation command has been moved. If you want to set the default animation, you should do this in the EVENTLIST notecard in your PE, on the “@group” definition line.
Use this to specify your own animation that will trigger immediately when an avatar sits, or whenever an MST eventlist completely finishes. The default is a “waiting” stand.
Example:
DEFAULTANIM=cova dance
FLOATTEXT=
You can use this command to customize your own floating text above the movers before someone sits on them.
Example:
FLOATTEXT=CircusShow - Clown1
WELCOME=
You can customize the text chat that will be sent when someone sits onto this mover.
Example:
WELCOME=Welcome! You may repeatedly tap [PageUp] / [PageDown] keys to adjust height.
@noanim
Include this line if you don’t want the mover to animate anyone who sits on it for any reason. Typically people use this for props that they just want to move around smoothly. It saves some time.
@nofx
Include this @nofx line if you want to customize the shape, transparency, or textures of the mover, or if you want to link it to other objects. If you enable this option, the mover will no longer automatically hide when you sit on it and become visible when you stand up. Advanced uses only recommended.
@nocam
You can include this line if you never want people sitting on the mover to see MST scripted camera views. Usually this is used with @noanim and @nofx but it can be used by itself as well.
@noadjust
Use this if you need to disable the pageup / pagedown adjustment height adjustment feature. If you change this you may also need to change or disable the welcome message.