Second Life Wiki - User contributions [en]

MLPV2 Rez Prop Independent of Pose Master

2015-11-27T21:25:56Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

//MASTER "~prop permanent rezzer" script 
//version 1.2 by Chaz Longstaff 2014-02-9 
 
//PURPOSE 
//to rez an item semi-permanently from MLP menu independent of a pose 
//with this script, users rez an item by clicking a button (e.g. a Throne, a campfire, etc.) 
//when the item is rezzed, it will stay rezzed until it hears a command to go away 
//allows multiple props to be rezzed at the same time, the only maximum is how many you allow the user to rez / prim limits on land 
 
//there are 3 parts needed: 
//1. Your menu commands in the MLP menu notecard; 
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script; 
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later. 
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter. 
 
 
//instructions 
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts 
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently" 
//3. add menu buttons to your MLP .MENUITEMS notecard as follows 
// 
//format of menu buttons: 
// 
//LINKMSG Rez AThing| 0,-4,987790,Rez##Tiki Torch bb Rezable ##X#.15#.70 
//LINKMSG DeRez AThing | 1,-4,987790,DeRez##ItemToRez 
//LINKMSG Clear Everything| 1,-4,987790,DeRezAll##dummytext 
 
//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ. Separate each of them with a single # 
//Yes, that means the rotation is hard coded, so you just need to make your prop something that doesn't need rotational adjustments during rezzing. Sorry about that, rotations do 
//my head in so I suck at them! Someone whose head can handle rotations is welcome to mod this to add flexible rotations on if they want... 

Script: 
<lsl> 
integer ch; 
string ObjectName; 
vector TargetVector; 
integer x; 
 

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

LlOwnerSay

2014-09-27T15:49:36Z

Chaz Longstaff: Corrected incorrect grammatical use of "less" in "This can convey 1024 ASCII characters, or less if non-ASCII are present." to "fewer"

{{LSL_Function
|inject-2={{LSL_Function/limits}}{{LSL_Function/chat||msg}}
|func_id=292|func_sleep=0.0|func_energy=10.0
|func=llOwnerSay|p1_type=string|p1_name=msg
|func_desc=Says {{LSLP|msg}} to the object's owner only, if the owner is currently in the same [[region]].
|return_text
|spec
|caveats=
* If {{LSLP|msg}} is longer than 1024 bytes, it will be truncated to 1024 bytes. This can convey 1024 ASCII characters, or fewer if non-ASCII are present.
* Silently fails ~45 seconds after the owner leaves the region the object is in.
* Silently fails when the object to which the script is attached is [[deed]]ed to a group.
* Some viewers do not display llOwnerSay text when {{LSLP|msg}} is empty ({{String}}).
* Produces swirly particle effects for the owner (who sees the message) but these effects do not appear to be visible to other avatars (who don't).
|constants
|examples=
<lsl>
default
{
touch_start(integer num_detected)
{
llOwnerSay("Ouch!");
}
}
</lsl>
|helpers=
<lsl>
// llOwnerSay extension for preventing silent failures
// paste this code at the top of the script and replace
// any calls to llOwnerSay with uOwnerSayPlus

uOwnerSayPlus(string inputString)
{
key owner = llGetOwner();

// single owner that the region still has a handle for
if (llKey2Name(owner))
{
llOwnerSay(inputString);
}
// group owned, must send the message publicly
else if (llList2Key(llGetObjectDetails(llGetKey(), [OBJECT_GROUP]), 0) == owner)
{
llWhisper(0, "/me : " + inputString);
}
// single owner, not present, send them an IM
else
{
llInstantMessage(owner, inputString);
}
}
</lsl>
|also_functions=
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llRegionSayTo]]|Sends private chat region wide}}
{{LSL DefineRow||[[llInstantMessage]]|Sends private chat anywhere on the grid}}
|also_events
|also_tests=
{{LSL DefineRow|[[llOwnerSay Test]]|}}
|also_articles
|notes
|permission
|negative_index
|cat1=Communications
|haiku={{Haiku|Speak to me only.|Murmur secrets in my ear:|Clandestine whispers.}}
|cat2
|cat3
|cat4
}}

MLPV2 Reference Manual

2014-09-26T17:43:15Z

Chaz Longstaff: /* API */

{{Multi-lang}}
{{Navbox/MLPV2}}

== .MENUITEMS* NOTECARDS ==

Menu notecards create menus.

When MLP2 starts up, it reads all *.MENUITEMS* notecards ("*" can be anything), in the same order as they're shown in object contents. You can have as many MENUITEMS notecards as you wish, or just one. MLP2 essentially reads all MENUITEMS notecards as though they've been concatenated into one big file.

The first two things (other than comments) MLPV2 reads from the first *.MENUITEMS* notecard MUST be two POSE statements, first for "default" and second for "stand" -- even if you don't use the STAND button anywhere. Note that these must not be repeated in subsequent *.MENUITEMS* notecards. See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.)

After the first two POSE statements, it expects directives and then MENU commands to build menus.

An example, to be clear:

POSE stand | stand | stand | stand | stand | stand | stand
POSE default | sit_ground | sit_ground | sit_ground

MENUORDER
// NORELOAD

MENU MAIN MENU | ALL
(etc)

Don't insert anything else at the top of the main MENUITEMS notecard, or you may experience strange errors such as "No Unused TOMENU"

The first MENU created is the main menu, which a user gets on touching the MLP2 object. The remaining menus are reached via buttons configured using TOMENU.

There are several built-in commands that you use to build your menu, as well as several options.

Most commands cause buttons to be added to menus. In this case, the command format is usually like this:

COMMAND ''ButtonLabel''

Replace ''ButtonLabel'' with whatever you want to appear as the button label. In many cases, this is optional, and the button label will match the command name. (Whenever something in a command format is in ''italics'', it means that you replace that text with what you want.)

=== COMMENTS ===
Comments in MENUITEMS notecards must be preceded by "//".

Any subsequent text on that line is ignored by the scripts.

Example 1:
//all this text is ignored

Example 2:
STOP // STOP is read by the scripts; but this part of the line is ignored.

=== DEFAULT / STAND ===

Place these are the very top of the first *.MENUITEMS* notecard, which is usually the one named ".MENUITEMS". (You may insert commented lines before this; commented lines don't count.)

Example:
POSE stand | stand | stand | stand //pose before starting and when stopping
POSE default | sit_ground | sit_ground | sit_ground //default pose when no animation entered

You may use other animations; the ones in the example are standard ones built into the SL, and don't need to appear in object inventory. {{Footnote|For a list of other built-in animations, see here: [https://wiki.secondlife.com/wiki/Internal_Animations#User-playable_animations].}}

See [[#TIP.21_Default_Pose| the default pose tip]] for help on setting coordinates for the default pose.

=== DIRECTIVES ===

Directives affect the overall behavior of MLP2. It usually doesn't matter where in the .MENUITEMS* files they are, but by convention, they appear after the default and stand poses. Directives do not cause a menu button to appear.

All are case-sensitive and so therefore you must use them in upper case as shown here.

If you want a directive to be acted upon, type its name into your menu card. If you don't, either just leave it out, or comment it out.

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| AUTOBACK ||

(MLPV2.1)
Automatically inserts BACK before any MORE--> automatically added by the AUTOMORE feature (see below). This does not add a BACK to every menu page, only those with "MORE-->" inserted by the AUTOMORE feature.

|-
|| AUTOMORE ||

Automatically inserts "More-->" button for menus with more than 12 buttons *except* for the main menu. If you need a "More-->" on the Main Menu, you must add one manually.

You would add a manual one like this:

MORE More-->

"MORE" is the command; "More-->" is the button label.

|-
|| MEMORY ||

(MLPV2.5)
This directive changes the maximum memory limit for the ~menu script.

MEMORY ''MemoryLimit''

Sets the limit to ''MemoryLimit'' in Byte on the ~menu script if encoutered in .MENUITEMS notecards.

MLPV2.5c and up reduce their memory limits after reading the configuration, to reduce parcel memory usage. This happens by default without any change to notecards.
MEMORY commands for all notecards set the amount of free memory to reserve after reading configuration. Lower numbers use less region (sim) script memory but also increase risk of
stack-heap errors. Set MEMORY to 65536 to get max permissible memory. If MEMORY commands are omitted, defaults are used.

When MLPV2 prints memory for a script as "(~scriptname: 10000 bytes free, 40000 byte limit)" 10000 bytes are available for the script's use. If it gets stack-heap errors, configure a higher MEMORY limit for that script's notecard. 40000 bytes is the limit: if this number is below 65535, you can configure more MEMORY for that script. If it's at 65535, you're maxxed out; you might have to reduce (remove poses, shorten pose names, etc -- see wiki for tips)

The "Adjust" menu button now prints free memory. During "Adjust" mode, ~memory script's limit is set to max, to allow storing new pose positions. Its limit goes back down when you leave Adjust mode.

Some scripts have hard-coded limits that can't be changed by notecard. If you get stack-heap errors for these, you can try modifying the script, increasing the number passed to llSetMemoryLimit().

<nowiki>|</nowiki>MEMORY|''MemoryLimit''|

Sets memory limit of ~props script in .PROPS notecards.

MEMORY | ''MemoryLimit''

Sets memory limit of ~swap script in .SWAP notecards.

|-
|| MENUORDER ||

This directive causes all menu buttons to appear in menus in the same order as they appear in the .MENUITEMS* files. If absent, menus are in the group-by-3-backwards order typical of SL menus, like original MLP. If present *anywhere* in any of the .MENUITEMS notecards, it affects all menus regardless of what .MENUITEM notecard they are in.

|-
|| NORELOAD ||

This directive causes MLP2 not to do a menu reset when rezzed. MLPV2.1 does not autoreload on rez, and this directive has no effect with MLPV2.1. (Automatic reset on rez was added to fix a problem where multiple copies of the same MLP object responded to each others' menus. A better fix was found in MLPV2.1.)

|-
|}

=== MENU COMMANDS ===

These will cause buttons to appear on menus.

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| ADJUST||

Adds a button to make the balls turn into long, translucent beams for easy editing to manoeuvre them into their proper positions for each pose.

ADJUST ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "AdjustPos".

See [[#TIP.21_ADJUST_Beams| tip on adjusting beams.]]

|-
|| BACK ||

Creates a button labelled "BACK" that, when pressed, displays the menu one level up in the menu hierarchy.

BACK ''ButtonLabel''

''ButtonLabel'' is optional.

If you use the AUTOMORE and AUTOBACK, you will only need to manually enter this on the last page of a submenu (including the only page of a menu with 12 or fewer buttons).

|-
||BALLUSERS ||

Creates a button to cycle through the access levels governing who can sit on the poseballs.

The levels are OWNER, GROUP and ALL

BALLUSERS ''ButtonLabel'' | ''Level''

''ButtonLabel'' is the optional button label.
''Level'' is ALL, GROUP, or OWNER.

If it is set to GROUP, avatars with the same active group tag as the MLP object can use the balls. The group for the MLPv2 product can set by right-clicking the product and selecting Edit, More >> General tab - Group: Set.

|-
||CHAT||

Adds a button to toggle on/off whether the MLP object will chat the name of each pose as it is selected.

CHAT ''ButtonLabel'' | ''OnOff''

''ButtonLabel'' is the optional button label.
''OnOff'' is the default, either ON or OFF.

|-
||CHECK ||

Adds a button that find poses with no positions and vice versa.

CHECK ''ButtonLabel''

''ButtonLabel'' is the optional button label. Typically, it's "CheckPos".

'''Note!''' This will reload all .POSITIONS.* files, so first backup any positions that have been saved using SAVEPOS but not manually entered into a *.POSITIONS* notecard!

|-
|| DUMP ||

Adds a button to dump the saved pose positions, suitable for saving into *.POSITIONS.* notecards.

DUMP ''ButtonLabel''

''ButtonLabel'' is the optional button label. Typically, it's "Dump Pos".

The positions are chatted to owner only. Positions for all poses are dumped. The user may then copy/paste this into *.POSITIONS* notecards so that the positions will be retained across a position reset, or a full restart or shutdown.

NOTE! *.POSITIONS* notecards should be released to customers with full permissions, to allow them to save positions that they've adjusted to fit their avatars.

If the MLP product has several *.POSITIONS* notecards, the end user may copy/paste all the info into the main .POSITIONS notecard, and delete all the other *.POSITIONS* notecards in the prim. They are no longer needed; all their information has now been amalgamated into .POSITIONS. However, builders may want to keep modules separate; they can do so by manually sorting the entries into their respective *.POSITIONS* files.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
|| (DUMPPROPS) ||

(MLPV2.1)
To add a button that will save prop configurations, use the following line:

LINKMSG Dump Props | 0,-4,1,DUMPPROPS // dump all prop configs

This adds a button named "Dump Props" (or whatever you prefer) that causes all the prop positions to be printed to the screen. They are visible to the MLP product owner only. The user may then copy/paste this text to *.PROPS* notecards for permanent storage.

If the MLP product has several *.PROPS* notecards, the end user may copy/paste all the info into the main .PROPS notecard, and delete all the other *.PROPS* notecards in the prim. They are no longer needed; all their information has now been amalgamated into .PROPS. However, builders may want to keep modules separate; they can do so by manually sorting the entries into their respective *.PROPS* files.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
|| HIDE ||

Adds a button that causes any MLP pose balls rezzed to become invisible. Not many MLP product makers bother with offering this button. The opposite is the SHOW command.

HIDE ''ButtonLabel''

''ButtonLabel'' is optional.

|-
|| INVISIBLE ||

Adds a button to toggle visibility for the prim that the MLP scripts are in. Note: this does not apply to the balls or any other prims, even linked ones.

INVISIBLE ''ButtonLabel''

''ButtonLabel'' is optional.

|-
|| LINKMSG ||

Adds a button that will send a specified link message to other scripts in the object when the button is pressed. This is useful for adding scripted features to MLP2 without having to modify MLP2 scripts.

LINKMSG ''ButtonLabel'' | ''menu'',''primnum'',''lm-num-arg'',''lm-str-arg''

{|{{Prettytable}}
|+
|-{{Hl2}}
!Parameter
!Explanation
|-
|| ''ButtonLabel'' || What you want the button to be called on the menu.
|-
|| ''menu'' || Set to 1 if the script receiving the button will pop up a menu. It causes MLP2 not to repost its menu, to avoid menus stacking up. Set to 0 otherwise -- (note: this doesn't inhibit MLP2's redo menu feature.)
|-
|| ''primnum'' ||
Set to -1 to send the link message to all prims

Set to -4 for just the prim the script is actually in
|-
|| ''lm-num-arg'' || 'num' arg for llMessageLinked()
|-
|| ''lm-str-arg'' || 'str' arg for llMessageLinked()
|-
|}

The menu user's UUID key is passed automatically as the 'key' argument for llMessageLinked().

|-
|| MENU ||

Creates a menu that can be reached from other menus. The first MENU configured becomes the main menu, which the user gets on 'touch'.

A menu's buttons are configured following the MENU statement.

MENU ''ButtonLabel'' | ''who''
or
MENU ''ButtonLabel'' | ''who'' | ''ballcolors''

This creates a menu named ''name1'', and a button named the same on the main menu.

Those who can access it are specified by ''who'', one of the following:

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| ALL || Anyone can use it
|-
|| GROUP || Only those who are wearing a group tag that matches the object's group can use it
|-
|| OWNER || Only the object owner can use it
|-
|}

''ballcolors'' is a list of zero to four ball color names, separated by vertical bars ("|"). The color name MUST be in UPPER-CASE. The following ball color names are supported:
{|{{Prettytable}}
|+
|-{{Hl2}}
!Version
!Colors
|-
|| MLPV2 || BLUE PINK
|-
|| MLPV2.1 || PINK, BLUE, PINK2, BLUE2, GREEN, MAGENTA, RED, ORANGE, WHITE, BLACK, YELLOW, CYAN, RED2, TEAL, GREEN2
|-
|}

See under Menu Parameters section for greater details.

For example:

MENU MyMenu | ALL | PINK | BLUE

Creates a menu named Mymenu. Poses in this menu will have 2 balls, a pink and a blue one.

Subsequent menu configuration lines add buttons to this menu, until the next MENU command. There is a limit of 12 buttons to a menu, unless AUTOMORE is used.

Note that, unless you use the MENUORDER directive, these menu items will be offered to users in the usual SL ass-backwards-by-three manner.

How do we get a button to get to this menu? There are two ways.

The first way is the same as with original MLP: use the TOMENU command to create a button to get to this menu:

TOMENU ''MenuName''

The button label must match the menu name. Menu names are case-sensitive.

The second way requires "TOMENU -" configuration lines in the main menu. For any MENU statement where no preceeding TOMENU matches the menu name, a menu button is automatically added to the main menu. (For this to work, the main menu must be filled with "TOMENU -" statements, which create blank spaces for this purpose. When MONO comes out and memory is less of an issue, we will try to make this simpler!)

|-
||MENUUSERS ||

Adds a button that cycles through the access levels governing who can use the menu.

MENUUSERS ''ButtonLabel'' | ''Level''

''ButtonLabel'' is optional.

''Level'' specifies the default, and must be one of the following: OWNER, GROUP, or ALL

If it is set to GROUP, avatars with active group tag amtching the MLP object's group can use the main menu. (You can restrict access to sub-menus on a per menu basis. See MENU above for more info.) The group for the MLPv2 product can set by right-clicking the product and selecting Edit, More >> General tab - Group: Set.

|-
|| OFF ||

Adds a button to turn the MLP system off.

OFF ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "Shutdown!"

When turned off, MLP deletes any balls, turns off all the scripts except for one that will turn it back on again when the owner touches it.

This reduces any contribution the MLP might be making to lag.

Any saved poses or prop configurations that have not been saved to *.POSITIONS* and *.PROPS* files are irrevocably lost.

|-
|| POSE ||

Adds a button for a pose.

POSE ''PoseName'' | ''AnimList''

''PoseName'' is the button label, and also the pose name (found in the *.POSITIONS* and *.PROPS* notecards).
''AnimList'' is a list of animation names, separated by vertical bars ("|").

The number of animations must match the number of ball colors listed in the corresponding MENU configuration.
That is, if the MENU has 3 poseballs, you must provide 3 animation names.

The animations are applied to the balls specified, in order. That is, if the ball colors are "PINK BLUE PINK", three animations should be listed. The first applies to the first pink ball, the second to the blue ball, and the third animation applies to the third ball, which is pink. (See also "Ball Colors" option below for more information.)

The ball positions are specified in a .POSITIONS* file, discussed below. If there is no .POSITIONS entry for a pose, the default pose is used. It's a good idea to always set up the default pose first for a new MLP product, to avoid balls rezzing underground or in other inconvenient locations.

Each animation name must have a corresponding animation in the object's contents, unless it is a built-in animation. Yyou cannot refer to animations by UUID.

|-
|| REDO ||

Adds a button to enable/disable popping the menu back up after making a selection.

REDO ''ButtonName''

''ButtonName'' is optional.

By default, when a user makes a choice on an MLP menu, the menu re-presents itself for further use.

If you offer this command button to users, and they click it, it will toggle this feature off and on.

Few MLP product makers offer this button to users, because turning off the menu coming back can create the perception that something is broken.

|-

|| RELOAD ||

Adds a button to reload *.POSITIONS* and *.PROPS* notecards.

RELOAD ''ButtonName''

''ButtonName'' is optional. Typically, it's "Reset Pos".

This button is useful after changing *.POSITIONS* or *.PROPS* notecards, to verify that you did what you intended. It's considerably faster than a complete reset since the menu isn't reread.

General rule: if you changed a .MENUITEMS card, do Menu reset. If you changed a .POSITIONS or .PROPS card, do Pos Reset.

|-
|| RESET ||

Adds a button to reload *.MENUITEMS* notecards.

RESET ''ButtonName''

''ButtonName'' is optional. Typically, it's "Reset Menu".

In addition to re-reading the notecards, it resets most of the MLPV2 scripts.

|-
|| RESTART ||

Adds a button to do what both RESET and RELOAD do, combined.

RESTART ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "Reload".

RESTART is therefore the most thorough command to use for a complete reboot.

|-
|| SAVE ||

Adds a button to save ball positions for the current pose.

SAVE ''ButtonName''

''ButtonName'' is typically "Save Pos".

Immediately after adjusting a pose, always, '''''ALWAYS''''' click this button! You will no doubt, like all of us, lose a few adjustments that you make when you first start out with MLP before this gets scarred into your habits.

'''Caution!''' This is not permanent. Anything that causes the *.POSITIONS* cards to be re-read will wipe these settings out from script memory. A pose is permanent only if it's saved in a *.POSITIONS* card.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

Note: the poseballs cannot be more than 10 metres from the MLP item for this to work.

|-
|| (SAVEPROP) ||

To add a button to save the prop location for the current pose, use the following command:

LINKMSG Save Prop | 0,-4,1,SAVEPROP // save position/rotation for a prop

where "Save Prop" is the button name (and can be whatever you choose).

You use this button after you have adjusted a prop. This stores information about the position, etc, to script memory.

This information will also be printed to the screen (only the owner can see it.) This information should be copied to the .PROPS notecard for permanent storage. You can either do this right on the spot, or arrange and save a whole bunch of prop positions, and then use the DUMPPROPS command to print out all the prop info at once for copying and pasting to the .PROPS notecard.

'''Note:''' a prop cannot be more than 10 metres from the MLP item for this to work.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
||SHOW ||

Adds a button that causes any MLP pose balls rezzed to become visible.

SHOW ''ButtonName''

Not many MLP product makers bother with offering this command. The opposite is the HIDE command.

|-
|| STOP ||

Adds a button to delete any balls and unseat any participants.

STOP ''ButtonName''

''ButtonName'' is optional.

Note though that, unlike OFF (covered above) it does not significantly reduce any contribution the MLP system might be making to lag.

|-
|| SWAP ||

Adds a button to swap positions between the first and second balls for any pose.

SWAP ''ButtonName''

''ButtonName'' is optional.

It has no effect on any third or fourth balls in a pose. However, this behavior may change in future versions.

Note: In some animation menuing systems such as XPOSE (as of summer 2008), hitting the SWAP button only swaps the current pose; the swap is lost at the next pose. In MLP, the SWAP is maintained until a user chooses to SWAP back.

IMHO, the XPOSE behavior is better, and I might change this in a future version. [Lear Cale]

|-
|| TOMENU ||

Adds a button to get to another menu.

TOMENU ''MenuName''

''MenuName'' is used as the button label, and must exactly match the name of the menu (case-sensitive).

If a menu (say, "Foo") exists, and there is no "TOMENU Foo" statement on a preceeding menu, and if there are unused "TOMENU -" statements for the main menu, a button for "Foo" is added to the main menu, using up a "TOMENU -" line.

Don't worry about supplying lots of TOMENU - slots on your main menu. If MLPv2 doesn't need them, it will just ignore them!

Note that if you are offering [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| modules]], you must provide some "TOMENU -" slots on your main menu for the module menu buttons to appear.

|-
|| Z* ||

The Z command adds a button that allows end users to easily adjust for themselves the height of the poseballs.

Z ''sign'' ''number''

For this command (and only for this command!), no spaces are allowed between the items (Z, ''sign'', and ''number). For example:

Z+1
Z+5
Z+25
Z-1
Z-5
Z-25

The numbers are treated by MLP as being a measurement in centimetres. Each time a user clicks a button, say Z+5, the height will be increased by 5 centimetres. If they have previously clicked the Z+5 button, then the height will be increased by an additional 5 centimetres.

A Z-5 button, if offered, would decrease the height by 5 cm.

Z adjustments chosen by users apply to all the poses, not just the one currently being used.

Note: the ongoing tally of these adjustments are stored in the Object Description of the prim that holds the MLP scripts, so any descriptions you put there will be replaced.

To clear them, you need to either use the Z buttons to set the offset back to 0, or, edit the object, select the MLP prim if it's not the root prim, and clear the description.

Traditionally, MLP product makers have put these Z commands under the OPTIONS menu.
These were recently moved to a HEIGHT submenu, to make room for the Props commands.

See the [[#TIP.21_OPTIONS_Menu_2| Tip! Options Menu]] for more info on how exactly to do this.

|-
|}

See the [[#TIP.21_OPTIONS_Menu_2| Tip! Options Menu]] table at the end of this page for helpful advice on arranging many of these menu commands into a tidy sub-menu.

=== MENU PARAMETERS ===

Info that you can add to MENU statement lines.

==== Ball Colors ====

If a MENU has no pose ball colors listed, it should have no POSE buttons.

When, however, a particular MENU will contain POSE statements in it, then the MENU statement must be followed by a set of ball colors to be used for all poses in this particular menu.

One to four balls can be specified, supporting poses for up to four participants. The balls are rezzed as necessary when a pose in the menu is selected.

Supported colors as of summer 2008 are:

{|{{Prettytable}}
|+
|-{{Hl2}}
!
!
!
!
!
|-
|| PINK || PINK2 || BLUE || BLUE2 || WHITE
|-
|| GREEN || GREEN2 || RED || RED2 || BLACK
|-
|| MAGENTA || ORANGE || YELLOW ||CYAN ||TEAL
|-
|}

PINK2, BLUE2, RED2, and GREEN2 are darker their respective colors with no number after them.

Note: The colors must be given in uppercase as shown above.

Examples:

MENU boy-girl | ALL | BLUE | PINK

MENU Boy Only | ALL | BLUE | HIDE

MENU Girl Only | ALL | PINK

MENU Anyone | ALL | GREEN

MENU 3Some | ALL | PINK | BLUE | PINK

MENU 4Some | ALL | PINK | BLUE | PINK | BLUE

=== POSE PARAMETERS ===

Info that you can add to POSE statement lines.

==== Animations (Facial) ====

In the POSE line, add the suffixes listed below to the animation names to cause facial expressions. (You don't change the animation name in inventory, just add the suffix to the anim name in the POSE line.)

NOTE: There is currently (April 2011) no menu button to allow MLP users to turn facial expressions off and on.

{|{{Prettytable}}
|+
|-{{Hl2}}
!suffix
!expression
|-
|| * || mouth open
|-
|| ::1 || mouth open
|-
|| ::2 || surprise
|-
|| ::3 || tongue out
|-
|| ::4 || smile
|-
|| ::5 || toothsmile
|-
|| ::6 || wink
|-
|| ::7 || cry
|-
|| ::8 || kiss
|-
|| ::9 || laugh
|-
|| ::10 || disdain
|-
|| ::11 || repulsed
|-
|| ::12 || anger
|-
|| ::13 || bored
|-
|| ::14 || sad
|-
|| ::15 || embarrassed
|-
|| ::16 || frown
|-
|| ::17 || shrug
|-
|| ::18 || afraid
|-
|| ::19 || worry
|-
|| ::20 || sleep
|-
|| ::21 || random (for MLPv2.4v or higher, produces random surprise / pleasure expressions)
|-
|}

''Note: 20 is a combination of disdain and smile, the closest that could be found for sleep.''

There must be NO SPACE between the animation name, and the suffix. Example:

POSE Sleep 01 | Sleep 01 femalesleep::20 | Sleep 01 malesleep::20

To make the expression happen periodically rather than constantly, add another extension and the length of the repetition cycle (in seconds).

For example, to use MyAnim with open mouth every 5.5 seconds:

POSE Mypose | MyAnim::1::5.5

If during menu boot you get an error that says "animation xyx not found", but you know that animation xyx really is in there, check to see that you didn't put a space before the expression suffix after all.

Note that this suffix appears only in the POSE line of a MENU; the actual name of the animation in the object's contents folder should *not* be changed to have this suffix. (Many animations are sold no mod; so you wouldn't be able to, anyway.)

== .POSITIONS* NOTECARDS ==

The .positions notecards, as their name implies, provide a place for storing information about positions of the poses in the menu.

As long as any position adjustments you have made have only been saved via the SavePos buttons, assume them to be temporary. They are only saved in script memory, and script memory is volatile. If you hand the MLP v 2.0 object to someone else, or if your sim crashes really terribly or if the script blows up with a stack-heap error, etc ... you may lose all the work you'd thought you'd saved.

The *.POSITIONS* notecards provide a safety against losing your work.

You create *.POSITIONS* notecards by your manually copying and pasting in information from the "Save Pos" or "Dump Pos" buttons (SAVE and DUMP commands described above). SL does not allow scripts to write data to notecards, so you must do this yourself.

NOTE: If the .POSITIONS notecard is no modify, or is placed in a no modify prim, people will not be able to open the notecard at all. This is a SL system limitation.

The lines in the .positions notecard look something like this:

{LieHold1} <-0.253,0.157,0.285> <0.0,0.0,0.0> <-0.146,0.000,0.177> <0.0,0.0,90.0>

where "LieHold1" is the name of a pose (from the POSE statement in a *.MENUITEMS* file).

The 4 vectors in the above example represent in order:
first ball position, first ball rotation, second ball position, second ball rotation

If there are 3 and / or 4 balls also involved in a given pose, then the pattern repeats on for them as well.

If you rename a pose in the menu that you have already stored a position in the notecard for, be sure to edit the .positions card, locate that pose in it, and give it the new name as well to match.

Be sure to purge out position lines for which menu items no longer exist. This is one instance in which tidiness really does pay off: all that old, unneeded position information is read into the scripts' memory, which can make you think that your MLP product is "full" (that fatal stack-heap message) and can't hold any of the other poses you had planned to add.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on .positions cards when using modules.

Note: Comparing positions to menu items is easier and the work of seconds as opposed to minutes if you keep the positions information cleaned up. See [[#TIP.21_Positions_Notecard_tidying| the tip on tidying .POSITIONS notecards]], if you wish to do this extra (not-required) work.

Remember that purchasers of your MLP2 product should be able to adjust poses to fine-tune them to their own heights, sizes, etc. All *.POSITIONS* notecards should be supplied to end-users with MODIFY rights so that they too can permanently save all their hard work. {{Footnote|Some furniture makers prefer to sell their furniture no mod so that others can't just disassemble it and copy the dimensions of the pieces and thereby duplicate the furniture -- fair enough. However, if the .positions notecard is in a no-mod prim, notecards inside it will also be no mod.

There doesn't seem to yet be a way around this. While llAllowInventoryDrop in a small add-on script might seem promising (and the change event could be set to delete the old .positions card), the problem remains that by then, a fresh positions card the user had dropped in would already be named .positions 1, an invalid file name. Because you can't rename objects inside a prim, you'd have to then have your script delete that .positions 1 card as well, and then invite the user to drop his/her fresh .positions notecard in a second time, which would be very confusing. Or, using the LINKMSG feature, create a button that tells a script to delete the .positions notecard, and then invites the user to drop a new one in. But you'd want that script to ask the user if s/he really knew what they were doing.

Note as well that a no-mod prim prevents the option of allowing customers to purchase add-on modules for you -- unless provision is made for an llAllowInventoryDrop.}}

(MLPV2.5) to set a memory limit on the ~memory script, use a line like this:
{MEMORY} <''MemoryLimit''>

== SEQUENCE NOTECARDS ==

SEQUENCE | seqence-name | NOCHAT 
use NOCHAT to inhibit chatting of poses 

MENU | menu-name 
set number & colors of balls 

POSE | pose-name | chat-chan | chat-message 
start a pose (chan & message are optional; message is whispered). 

AVWAIT | 0 1 2 3 | chat-message-if-waiting 
pause the entire sequence set until the balls listed are sat on (0 1 2 3 in this example) 
 
examples: 
to wait for two people: AVWAIT | 0 1 | Waiting for both people to get on the balls 
to wait for three people: AVWAIT | 0 1 2| Waiting for three people to get on the balls 
to wait for four people: AVWAIT | 0 1 2 3| Waiting for four people to get on the balls 
 
Only have one (1) AVWAIT line per sequence set, or you may get stack-heap blow-ups. 
 

WAIT | wait-seconds 
pause before executing next command 

GOTO | label-name 
go to a label, to loop a portion of a sequence 

LABEL | label-name 
set a target for GOTO 

REPEAT 
repeat the whole sequence 

SAY | chat-chan | chat-message 
say the given text on the given chat chan 

WHISPER | chat-chan | chat-message 
whisper the given text on the given chat chan 

SOUND | sound-name | 0 to 1.0 
plays sound from '''prim contents''' at volume 0 to maximum 

MEMORY | ''MemoryLimit''

(MLPV2.5) Sets memory limit of the ~sequencer script.

NOTE: The chat messages can include the first names of participants using /0 for avatar on first ball, /1 for av on 2nd ball, etc.

=== Sequence scripting debugging ===

(very advanced) 

Put any one of these are the very top of your sequences notecard, outside of any defined sequence, in order to turn on debugging for the sequences script:

debug | 1 
sequence start/stop 

debug | 2 
echo each command as executed 

debug | 4 
avatar hop on/off 

debug | -1 
all debugging 

=== Sequences and Props ===
Yes, props will still work for items used in sequences.

== TIPS ==

{{box|TIP! ADJUST Beams |Finding the ADJUST beams hard to see? First, make sure that you have set world to noon. If you still find them difficult to edit, haul the ~ball out of your prim.

Edit the ~ball script in it, and look for this part of the script in the listen event:
<lsl>
} else if (str == "ADJUST") {
llSetAlpha(0.2,ALL_SIDES);
llSetText("Adjust",<1.0,1.0,1.0>,1.0);
llSetScale(<0.1,0.1,5.0>);
</lsl>
It's the llSetAlpha setting it to only .2 that makes it hard to see. Try it at .4, or .6, or higher.

Save, take the ball into inventory, then delete the old one in the prim and replace it with your adjusted one.}}

{{box|TIP! Animations Caveat|
Though all animations will work with MLPv2, not every single one you come across will work reliably.

Some animations, if they happen to have been made by the creator in a certain way, will work as expected after certain other animations, but not after others. You'll get different results depending on which pose you ran last.

The problem is animations that have their hip position the same in their T frame and first animation frame. They just won't work with MLP.

Example: if you have 3 anims, 2 with hip positions set and one without, the hip position for the one without will be the hip position left over from whichever of the last two anims you used. It's the way SL animations work. If there's no change in any joint between the "T" frame (first frame in bvh file) and the first animation frame (second frame in bvh file), SL ignores that joint for the whole animation. And when all other animations are turned off, this means that these joints are left free to do whatever SL does with them. It leaves them as they were from the previous anim, or overrides them with SL builtin motions like typing, head movement, arm pointing while editing, etc.

The values in the hip joint aren't important; what's important is that that they *be* different between T frame and 1st animation frame. For MLP, you want every joint in the animation to have been moved (except head, if you want it to be able to move with the mouse.)

This problem can be avoided when making animations if you move the hip even just 1 degree, and normally the stomach 1 degree in the opposite direction.

So sadly, in the course of things, odds are, you're just going to buy some animations that just ain't going to work with MLP. And there is no way of knowing in advance.

When creating animations for MLP, Lear Cale highly recommends using priority 3. This disallows the typing while chatting animation, but allows head movement (if the head joint is not moved in the beginning of the animation). It also allows someone to create a priority 4 animation and run it to override MLP animation behavior (until the next pose is selected). }}

{{box|TIP! Animations Permission|
The ball user, upon first sitting on a ball, will be asked permission to animate them. S/he must say yes to yes, or they will end up just "hovering" on the poseball.

The "permission pls" menu often gets hidden behind the MLP main menu (if you are the one who called up the menu.) You need to click the ">>>" to cycle through the menus on your screen to find the permissions prompt. This is SL behaviour and there's no way to fix it, other than turning "redo" menu off in MLP.

NOTE: in their great wisdom, SL modified the 1.20 viewer to show something other than ">>>" for this button. Damn them.

If you are wondering why permission must be asked, when normally sitting on something is taken as implying permission to be animated, it's because it's not actually the balls that are doing the animating -- it's a script in the MLP. Because one script is not allowed (for security reasons) to pass permission to another script, the scripts in the MLP itself can't take advantage of any permissions the poseballs have acquired.}}

{{box|TIP! Animation Synchronization |Animations appear to start separately per ball once an avatar sits on it. Thus, they're not in sync.

In fact, the animations are started at the same time. However, it takes time for the animations to get sent between SL and the client, so as a result they don't look synchronized.

There is no simple feature in MLPV2 to automatically synchronize poses as such. You can manually synchronize by shifting to another pose and then shifting back again. (Starting with

There is no built-in feature to automatically synchronize, as there is with couples danceballs. Prior to MLPV2.4z4, you can manually synchronize by changing to another pose and then back. Starting with MLPV2.4, you can manually resynchronize by selecting the same pose again.

There is an advanced feature of MLPV2 that you could use to get automatic periodic synchronization: Sequences.

A sequence is simply a list of poses that MLPV2 will play at the touch of a button, with the option to repeat the sequence or a portion of the sequence. See the example sequence in the distribution. You could set up a simple sequence that plays one pose, waits some time that's at least as long as the animations, and repeats, like this, which goes in .SEQUENCES notecard:
<pre>
SEQUENCE | snuggle-seq | NOCHAT
MENU | couples
POSE | snuggle
AVWAIT | 0 1
POSE | snuggle
WAIT | 30
REPEAT
</pre>

}}

{{Box|TIP! Animations and balls|
Animations remain in the main MLP object; they are never placed in the poseballs. The animations are played from within the main MLP product; the poseball is just the delivery vehicle. Consequently, poseballs can be deleted or lost without the main product being affected. And, the poseballs themselves are just copies of the one inside the MLP product.

A ball will commit suicide if left behind somewhere (the MLP object needs to be within 20 metres.)}}

{{Box|TIP! Ball text|
By default, both the poseball floating text and the right-click menu 'sit' choice text is the word "LOVE". You can set these to whatever you want by editing the description of ~ball in object contents. If you type in that field the word "none" (without the quotes), or just type in a space or two, there will be no floating text, and the right-click menu 'sit' choice text becomes the system default of just "Sit Here" (for English viewers).}}

{{Box|TIP! Phantom Balls|
To make your balls rez as phantom, put an asterisk in the ~ball description line.}}

{{Box|TIP! More than 6 balls|
There are no plans to expand beyond 6 balls active at once. If this is totally necessary for you, you'd be better off just going with a product that actually supports the number of avatars you want, such as XPOSE. You'll save yourself and your customers time and confusion by going with a product that was designed to handle larger numbers from the ground up.}}

{{Box|TIP! Balls are buried in furniture|
Sometimes when you position the balls correctly for an animation, the balls end up buried in furniture.

This is a property of the animation: the hip position in the animation is too high. While it is in theory possible to fix this in MLP scripts, it would be hard to do, especially without using up lots of memory for poses.

Most people know that when this happens they can select another pose first, jump on, and then change to the pose they want. Consequently, the simplest workaround is to make sure the first pose in each menu has all balls visible.

Alternatively, you could ask the creator of the animation to adjust it, but the chances of them doing this just for your piece of furniture are not high.

If someone stands up while on balls that are buried in furniture, they will get ejected from the furniture unceremoniously. This won't happen if they use the STOP button on the menu instead.

Vesta Martynov suggests another workaround -- changing the offset that the ball is rezzed at. (Note that this will apply to all poses, not just the problem ones.) Her work-around is, before you start on a MLP product, to take the ball out and rez it on the ground. Edit the script in the ball, and search for this SitTarget line:

llSitTarget(<0.0,0.0,0.1>,ZERO_ROTATION);

The .01 there is the vertical offset. She changes it to something like this:

llSitTarget(<0.0,0.0,-0.25>,ZERO_ROTATION);

Save your changes, take the ball back into your inventory, and use it to replace the one that was inside the MLP.

After you do this, all the balls and animations will be lifted, so you can go in and lower the animations, but you will no longer have balls sinking into your furniture.

(Vesta Martynov, conversation in MLP group, 2009-06-11 19:46)
}}

{{Box|TIP! Ball scripts|
When updating your version of MLPv2 scripts, make sure you update the script in ~ball as well.
}}

{{Box|TIP! Changing the number of active Balls|
When going from a pose in a menu with 4 ball colors to a pose in a menu with 2 balls, the 2 balls are deleted. Assuming you're not using phantom balls, if the balls rez again (say you go back to a pose in a menu with 4 balls), the balls should bump anyone standing in their way out of the way. People wanting to use the newly re-rezzed balls and be animated by them will have to hop back on them. When changing the number of balls active, bear in mind that the number of animations in a POSE line must match the number of ball colors in the MENU line above. You can't mix poses with 2 anims and poses with 4 anims in the same menu section. This is not supported.}}

{{box|TIP! Default Pose |
You need to set position coordinates for the default pose. To do this, on the MLPV2 main menu click the "adj-default" button, then ADJUST the default pose position, save, and copy the coordinates to the .positions notecard as per normal. When you have finished, delete the .menuitems.zz-default notecard from the prim.

If on the main blue menu you do not see a button called "adj-default", do the following steps:

1) Create a notecard with the file name of: 

.Menuitems.zz-default

Paste the following in as content:

<pre>
// The "default" pose below is for adjusting "default" position.
// Since there are currently no other items in this menu, you can comment out the whole menu 
// or simply delete this file when you've done that.

MENU adj-default | ALL | BLUE | PINK | BLUE | PINK
POSE default | sit_ground | sit_ground | sit_ground | sit_ground
SWAP
ADJUST
SAVE Save Pos
DUMP Mem Dump
BACK
</pre>

Tip! If the product you are making is only for 1 or 2 people, then you don't need to include all 4 balls that are listed in the menu above. For a solo product, you can just do instead:
<pre> MENU adj-default | ALL | BLUE
POSE default | sit_ground
ADJUST
SAVE Save Pos
DUMP Mem Dump
BACK
</pre>

Drop this notecard into the prim where you are working with MLPV2.

2) Make sure the main menu notecard has a spare TOMENU slot to fit the adj-default choice into:

TOMENU -

3) restart the MLPV2 product.

4) ADJUST the default pose position, save, and copy the coordinates to the .positions notecard as per normal.

5) When you have finished, delete the .menuitems.zz-default notecard from the prim.}}

{{box|TIP! Notecard Editing|
If the MLP prim contains many animations, access to a notecards contents can be PAINFULLY slow.

First, make sure the prim is ready to let you open the notecard. Right-click on the notecard that you see in the contents folder. If you get a big menu of choices, rather than just the standard 4 of Open, Properties, Rename, Delete, then the prim isn't ready to let you open the notecard. You simply have to wait. Sometimes, you may need to wait up to 2 to 4 minutes. Yes, ridiculous -- but that's SL.

Make all your changes before saving. Once you save, the notecard you have open may no longer be the notecard that is inside the prim (sic.) Once you have saved, even if you did so by accident out of habit, leave the notecard opened for a few seconds, then close it, and wait until the prim is ready to let you open it again if you need to do further edits.

Note: as of summer 2008, the wait time for notecards to open from inside prim folder contents seems to be getting increasingly worse, and the system seems to be getting increasingly intolerant of allowing repeated saves on the same opened notecard. Thus, the advice to close and re-open after a save.}}

{{box|TIP! Modules -- multiple .menuitems and .positions notecards|
There can be several *.MENUITEMS* and *.POSITIONS* notecards in an MLP product (where "*" is any text that's allowed in a notecard name). This is to allow the addition of modules to the product. This allows you the option, for example, of letting customers purchase an MLP product for couples, and then coming back later to purchase an odd-on for 3Somes. Customers then pad home, edit the contents folder of their MLP product, plop in the add-on stuff, and restart their MLP.

'''Note:''' a module's menu appears as a button on the MLP product's main menu. For this to actually happen, you *must* provide a blank slot for it by supplying a TOMENU - parameter on the main menu. Normally, there should be a bunch of these in the main menu.

The add-on will consist of a .menuitems card, a .positions card, and the associated animations (with permissions set correctly.)

For you as a vendor to make a module, you create a .MENUITEMS.xxx notecard, and a corresponding .POSITIONS.xxx notecard (where xxx can be anbything and is normally thought of as the name of the module.) If this module uses props, you also create a .PROPS.xxx notecard.

A *.MENUITEMS* card for a module should have no default or stand pose, etc. It normally has only the actual menus being added and the associated poses.

Example:

<pre>MENU myAddOns
TOMENU myAddOn1
TOMENU myAddOn2

MENU MyAddOn1 | ALL | PINK | BLUE
POSE Whoohoo! | Bump1 | Bump2
POSE Zowee | Grind1 | Grind2

MENU MyAddOn2 | ALL | PINK | BLUE | PINK
POSE Fubar | Dance1 | Dance2 | Dance3</pre>

To test, you would then drop all associated notecards (.menuitems.xxx, .positions.xxx and .props.xxx if using) into the MLP product, along with the necessary animations and props, of course, and restart the MLP product. (Of course, if you were selling it as a separate add-on, you would after remove the above components from the main product, and package them separately.) Remember if you make any pose position adjustments during testing that the position information should be copied and pasted to the relevant .positions.xxx notecard -- not the main .positions notecard, because you are preparing a sold-separately module. Ditto for any prop adjustments, which go into the .props.xxx notecard.

Purchasers of an add-on need to always keep that .menuitems.xxx notecard in their product. However, the .positions.xxx and the .props.xxx notecards have, in a way, a limited lifespan. When you do a DUMP command, you copy / paste all that info into the notecard named simply .positions -- that is the main .positions notecard. Or, into .props notecard, in the case of a DUMPPROPS command. All the info that the subsidiary .positions.xxx and .props.xxx notecards hold is now amalgamated into the main notecard, and the subsidiary ones are no longer needed. They can be deleted. But to be clear, do not delete their corresponding .menuitems.xxx notecards.

Multiple .positions notecards are read by the script in the same order they appear in object inventory.

Note: it is best to be using the MENUORDER directive when offering modules.}}

{{box|TIP! Sub-Menus|Can you add a module menu ie: .MENUITEMS.myposes and have it show as a top menu item with sub menus? Something that would give a My Poses button that when clicked would open a sub menu dialog with buttons for my poses 1, my poses 2 etc.

Abolutely, and that's the best way to do it.

Start your .MENUITEMS.mystuff with the parent menu. Fill it with "TOMENU" statements like this:

<pre>
MENU WhizBangInc | ALL
TOMENU WBI-cuddles
TOMENU WBI-fun
TOMENU WBI-freaky
TOMENU WBI-illegalin42states</pre>}}

{{box|TIP! Options Menu|
By tradition, most of the common functionality command buttons are stored under a MENU called "OPTIONS".

Such commands include ADJUST, SAVE, DUMP, Show/Hide (aka INVISIBLE), MenuUsers, BallUsers, Chat, Dump Props, Save Prop, etc.

As well, the z commands for height adjustment were traditionally offered there as well.

With the rapidly-increasing number of functions available within MLPv2, however, the OPTIONS submenu is becoming very crowded.

Consequently, consider taking all the z height adjustment options out from under OPTIONS and put them in a sub-menu like this:

<pre>MENU HEIGHT | ALL
Z+1 //adjust Z = height offset in cm - use any integer to set the step size
Z+5
Z+25
Z-1
Z-5
Z-25
BACK
</pre>

Then, in the OPTIONS menu, just make this button linking to the HEIGHT submenu:

TOMENU HEIGHT}}

{{box|TIP! Positions Notecard tidying|
The lines in the .positions notecard look like this when copied and pasted in directly from chat:

[7:46] Animated Living Sofa Combo Couple & Solo 2.1e: {Lie&Hold} <-0.413,0.130,0.245> <1.0,-9.0,-0.9> <-0.539,0.207,0.155> <-0.1,-8.9,-1.1>

The extraneous chatter before the {LieHold1} parameter in the curly brackets (aka braces) is ignored by the scripts, so there is no need to delete it.

Still, if you as an MLP professional wish cleaner, easier to read content (which is a boon for easier maintenance and troubleshooting), then copy the contents of the .positions card in question into a simple text programme (such as Notepad on a Windows PC), and using the example above, you would search for:

[7:46] Animated Living Sofa Combo Couple & Solo 2.1e: [including the final space at the end of it]

and just replace it with nothing, and then paste the cleaned up text back into the .positions card.

The cleaned up text then looks like this.

{LieHold1} <-0.253,0.157,0.285> <0.0,0.0,0.0> <-0.146,0.000,0.177> <0.0,0.0,90.0>

You may wish to also to SORT the positions in alpha order to make it easier to find them.

So that instead of:

{Massage} <-0.230,-0.133,-0.287> <0.0,0.0,-86.0> <-0.287,0.259,0.161> <0.0,0.0,-82.0> 
{Sprawl 1} <0.960,0.000,-0.190> <0.0,0.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 
{Lie 01} <-0.115,-0.069,0.694> <0.0,0.0,-90.0> <-32.417,-199.035,-518.585> <0.0,0.0,0.0> 
{Couch 1} <-0.179,0.001,0.143> <0.0,-19.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 

You have 

{Couch 1} <-0.179,0.001,0.143> <0.0,-19.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 
{Lie 01} <-0.115,-0.069,0.694> <0.0,0.0,-90.0> <-32.417,-199.035,-518.585> <0.0,0.0,0.0> 
{Massage} <-0.230,-0.133,-0.287> <0.0,0.0,-86.0> <-0.287,0.259,0.161> <0.0,0.0,-82.0> 
{Sprawl 1} <0.960,0.000,-0.190> <0.0,0.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 

You can do this sorting in seconds by copying & pasting the (cleaned-up position chatter) into something such as Microsoft Word, or a spreadsheet, and telling it to sort, and then copying & pasting the sorted positions back into the .positions notecard. (This really works best though if you have stripped the initial chatter info from them.) }}

{{box|TIP! Notecard reading order|
Q: I have a question about animation packs. I know the readme notecard says that the scripts read the notecards in alpha order. If I were to name the notecards as A, B, and C would the buttons on the menu then be in that order as well? I'm picky--I like my buttons in a certain order.

A: Yes.}}

{{Box|TIP! Portable use of an MLPv2 product|
Attach the MLPv2 object to your HUD. You can use its default shape and color for a clickable bar on one of the edges of your screen (to move HUD position: Right-click and Edit it and use the arrows). While in edit mode, you can also edit color/transparency/size/position.

Note that the balls will appear relative to the initial MLPv2 position. Adjust the height offset with a (Z) command.}}

{{Box|TIP! Props|
Props are objects the MLP product will rez for poses. When you choose another pose or hit STOP, any rezzed prop disappears. If you delete the MLP object, any prop will disappear within 3 minutes.

Props support starts with MLPV2.1.

To add a prop, edit a .PROPS notecard or add a new one (named .props.xxx where xxx is the name of the module, for a modular config). Copy the following example line and paste it into your .PROPS notecard.

<pre>| mypose | myobject | <1,1,1>/<0, 0, 0></pre>

Then: 
*Replace "mypose" with the pose name;
*Replace "myobject" with the name of the prop object. The object name cannot contain vertical bars;
*Add the "~prop" script (from inside the "~pillow" object that comes with the standard distribution) to your prop object, and drop your prop object into the MLP prim's inventory. The prop and everything in it will need to be copiable for next owner;
*Make sure your menu has the SAVEPROP and DUMPPROPS command on it.

Restart the MLP, and then select the pose. The prop should appear. It might be underneath the MLP object, so look around -- it may be best to do this using a single prim MLP floating in the air, the first time so that it doesn't rez in the ground!

Move the prop to where you want it, and use MLP menu command "SAVEPROP". To make the change permanent, select the chat information that is printed out on your screen (including the first vertical bar, and optionally any text before it) and replace the corresponding line in your .props.xxx file. Or, do all your props and use DUMPPROPS. (This procedure is similar to that for saving positions in .positions.xxx notecards.)

To get MLP to reread .props.xxx files, restart the product (which resets positions as well as props).

Keep in mind that props and positions are saved as two separate steps. If you adjust a pose and its prop, you need to save both pose position and prop.

Tip: We are all so used to hitting the button to save positions. If you find that a prop position isn't saving, check your chat history to make sure you didn't hit the save position button instead of save prop just out of habit!

 '''Hand-held Props''' For props to be used as hand-held items, use the ~give script add-on found here [[MLPV2_Give_Item_Add-on]] and have people wear the items. 

'''Number of Props''' 
For any pose, you can have at most one prop. If you need more than one prop to rez, you'll have to link the items so that they can be treated by MLP as one object. Alternatively, if you have a scripter friend to help you, you might try having the rezzed object rez another object from its contents. Your scripter friend would need to make the rezzed child object listen for the same die command as the main object that was rezzed.

Or, you *might* perhaps try the rezzed object as a coalesced object, making sure that each item has in it a script (created custom for you by a scripter friend) so they can die when required to -- experiment with that somewhere in the open at first in case it goes all over the place. 
}}

{{Box|TIP! STOP in every menu|
STOP and BACK buttons should be on every menu.

Why STOP on every menu? It solves so many problems. For example, if you use STOP, you don't get ejected like a James Bond villain if the poseball happens to be buried in the furniture. After moving or rotating a bed, STOP resets the position (Lear put in code to do this automatically, but there's no event that tells you when rotation stops.) And no doubt, SL and MLPV2 have bugs, and I've seen funky and unrepeatable oddness that STOP fixes in a jiffy. Plus it makes the poseballs go away.}}

{{box|TIP! Scripting -- call on MLP Menu from another script via linked msgs|
If you just want the MLP menu to come up from another script in the object (same prim or different one), simply do what the ~touch_passer script does (the llMessageLinked() call). If your script is in the same prim as MLP scripts, change LINK_ALL_OTHERS to LINK_THIS.
}}

{{box|TIP! Scripting -- call on MLP Menu from another script via chat|MLP listens for menu responses on this channel, minus one:

<pre>
// Return a channel number that's based on the prim's key -- unique per object
integer channel() {
return (integer)("0x"+llGetSubString((string)llGetKey(),-4,-1));
}</pre>

Note that the key here is the key of the MLP object.

Oh, warning: it also checks to see if the chat came from the same user as whoever used the menu recently. If they don't match, it sends a menu (dialog) -- in this case, to your object, which won't do anything. So, I suspect that this will work only if you keep users from getting access to the MLPV2 menu directly.}}

== API ==

When the MLP is ready for use, the menu script in its ON state sends out a linked message on channel -11003 saying "READY" (from MLP version 2.4p1 and onwards.)

llMessageLinked(LINK_SET, -11003, "READY", NullKey);

{{Footnotes}}

== Illegal Pirated Animation Kit FYI ==
http://wiki.secondlife.com/w/index.php?title=62_Animation_MLP_Set

For "free" status of Sexgen animation kit released October 2011 by Stroker Serpentine, see here: https://wiki.secondlife.com/wiki/Stroker_Serpentine_Sexgen_Animation_Set

[[Category:MLPV2]]

MLPV2 Troubleshooting Tips

2014-09-06T00:52:41Z

Chaz Longstaff: /* Balls won't rez when I choose a pose! */

{{Navbox/MLPV2}}
These MLPV2 troubleshooting tips are for normal end users and builders.

== User issues ==

These issues can be seen by any MLPV2 user even when the furniture is reasonably set up.

=== Why am I not being animated? ===
Try turning off your Animation Overrider, if you have one. Whether this is an issue for you depends on a techical detail: the priority of the animations in your AO and the priority of the animations in the MLP/MLPV2 product.

=== Why am I floating? ===
Sometimes we can be using a pose and suddenly we rise about 1 meter higher and stay there. Sometimes this happens in everyone's view, and other times it only appears for some. This is an SL bug and happens with any animation system, not just MLP/MLPV2. The problem usually goes away if you select the pose again, or stand and sit again. Sometimes it may be necessary to relog.

=== Balls won't rez when I choose a pose! ===
First, try STOP. If the balls got deleted for any reason, they won't rez when you pick a pose and the MLP still thinks the balls are there. STOP fixes this. (The timeout in many MLP objects also help avoid this, by doing a STOP if nobody's used it for a while.)

Second (if first doesn't work), try resetting via the MLPV2 menu: "OPTIONS -> Shutdown... -> Restart".

Consider if maybe they *are* rezzing, but way below you or way above you -- check the description line of the MLP object to see if there is a number in there, in which case set it to 0.

Check to make sure that the ~ball object inside the MLP has not been deleted by mistake.

=== Menu doesn't come up ===
Make sure you're on land where you are allowed to run scripts. There is a "no scripting" icon at the top of the viewer screen if you can't.

If you can't, try setting your group to the land's group. If that makes the no-scripting icon go away, set the MLP object to the land's group. (Do this in the Edit tab, or be wearing the group tag when you rez the object.)

If that isn't the problem, most likely it had a stack/heap error when you were away.

If the object permissions allow it, select the object and use "Reset Scripts". (In original style viewers, this is SL menu "Tools -> Reset Scripts in Selection". For SL2, I have no idea where it is. Naughty LL for goofing everything up.)

If this is a recurring problem, there is an MLPV2 recovery script; ask the MLPV2 group for more info. Alternatively, delete some of the poses, to allow more room.

=== "Animate me" permission popup not happening===

You won't get the animate permission popup if you were the last person on a particular poseball. It keeps your permission. You also don't get animate permission for yourself when MLP is used as a HUD, because worn items give permission automatically. (So do sat-upon items, but in the case of MLP, the script that takes permission is in the furniture, not the ball.)

=== avatar != perm key ===
This is some debugging code that Lear had left exposed by mistake in some versions. It can be ignored; it is not really an error.

If it is annoying, just update to the latest script set. (Users can do this if the item is modifiable, but users should ask the maker first in case the maker has made custom modifications or is using add-on scripts.)

=== OPTIONS menu doesn't work after deeding to group ===
If you deed an MLP, you lose the OPTIONS menu unless you remember to change all the OWNER menus to GROUP menus, and even then you won't be able to use full shutdown.

=== Could not find animation '00000000-0000-0000-0000-000000000000' ===
Often one user will get this, and not another. Some have speculated it could be AO issues (even if the AO is turned off) or something indeterminate related to the avi. The speculation comes from forums where users have reported the issue and said that it went away as inexplicably as it started, by either a relog, clearing network cache, tping away and back, taking AO off completely for a bit, etc. Or went away over night.

It could also be the asset server playing silly buggers, and a sim reboot (if possible) might solve it.

In any event, what's certain is that there is nothing wrong with the actual MLP product.

== Builder issues ==

=== Animation xyx not found ===
* Check that the animation is indeed in the prim
* Check the spelling
* If you are using expression suffixes, check that you didn't put a space before the expression suffix
* Check that as a separator in POSE lines you have used only <pre>|</pre> or <pre>space|space</pre> You can also use two spaces on each side of the vertical bar, but you cannot use three spaces: the superfluous space is not stripped away while reading the notecard; instead, it gets treated as part of the animation name, and thus the animation name can't be found.
* Also check for invisible soft-returns that may have come in if you were doing your work in another program such as Microsoft Word.

=== Animation won't remember its position ===
This can occur that even though you've triple-checked all your work; there will be an animation that sometimes will come out in the right position, sometimes not. After a bit of head-banging, you realize it all depends on which animation you played just before it. If the creator of that animation did not set a hip position for it, you will get different results depending on which pose you ran last. That is, if you have 3 animations, 2 with hip positions and one without, the hip position for the one without will be left over from whichever of the last two animations you used. Which may throw your pose all off. There is nothing you can do except abandon use of the animation; the problem is in the animation itself, and it's not suitable for use with MLP-like scripts though it may work fine as sold in a static poseball.

=== Balls rez on top of each other, even though you are sure you have positions right. ===
Check for duplicate stored positions. *Any* duplicate stored positions, even those not related to the pose in question, can cause this.

Check for the memory script having blown up during booting. It's easy to miss this, as the error bubble only shows for a short time then goes away. To ensure you don't miss it, you can in Preferences for "Text Chat" turn on "Show script errors and warnings as regular chat." That way, you'll be able to see such script problems even after problem bubble has faded.

=== Balls: not enough rezzing ===
You have a Menu with poses that have 4 animations to them, but only 2 balls are rezzing. ||Check that you didn't tell the pose to only rez 2 balls. Example: <pre>MENU Cuddles | ALL | BLUE | PINK</pre> for 4 animations should be something like <pre>MENU Cuddles | ALL | BLUE | PINK | BLUE | PINK</pre> (or whatever) . Easy mistake for tired eyes to make!

Also, check that you didn't drop the permission parameter. For instance, if you say
<pre>MENU Cuddles | PINK | BLUE </pre>
forgetting to put in there the [ALL | GROUP | OWNER] parameter, MLP will get mixed up, think that PINK is the permission parameter, and only rez the blue ball.

if you say
<pre>MENU Cuddles | PINK </pre>
No balls will rez at all.

Fix: put a permission parameter back in.

===Booting up: MLP starts, gets a bit of the way, then goes no further ===

Check that you have both a .MENUITEMS and .POSITIONS notecard in there.

=== Couldn't find (script)" error ===
If you get a message like this upon first dragging and dropping the MLPv2 scripts into a prim, disregard it. It occurs because a prim contents are very slow to refresh in SL, and one script thinks another one is not there yet. Do nothing; it will sort itself out in a few seconds.

=== llDialog: button labels must be 24 or fewer characters long ===
You have almost certainly forgotten a <pre>|</pre> in a POSE line. Consequently, the scripts were counting the Button name and the first animation name as the button name, making the button name too long.

=== Notecards: I set my notecards to full-perm but customers can't open them to save positions, etc. ===
This happens if the object is no-modify. You can't open notecards in a no-modify object. SL limitation.

=== "No Unused TOMENU" Getting this msg but I know that's not right ===
Check the top of your main MENUITEMS card, referring to the help in this section https://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#.MENUITEMS.2A_NOTECARDS

=== Props don't rez and I have everything right ===
# Make sure you have the ~props script in the MLP object. (Actually, this won't keep the prop from rezzing; it will keep it from saving its position, and keep it from deleting itself when moving to a new pose.)
# MLP is very case sensitive. CHAT 2 in .MENUITEMS does not equal Chat 2 in the props notecard. Check to make sure the case matches.
# Watch the prim count on the parcel where you are working. If the available prim count is going down, then your prop is rezzing -- just not somewhere where you are seeing it.

=== "Script run-time error / Stack-Heap Collision" ===
This is a clue that, sadly, there are too many items in your .menuitems.xxx or .positions.xxx notecards for the script memory to handle. Congratulations, you've just been initiated into the battle-scarred club like the rest of us.

First, make sure the scripts are compiled Mono, not LSL. By default they're Mono and you're better off if you do NOT recompile them.

Second, make sure you have no unused positions stored in any .positions notecards. See tidying tip here https://wiki.secondlife.com/w/index.php?title=MLPV2_Reference_Manual&action=submit#TIP.21_Positions_Notecard_tidying. Tidy, restart and see if that helps.

Third: try optimizing your saved .POSITIONS. If you have old .POSITIONS notecard data with lots of trailing zeros, you can get them trimmed down using this procedure:

# drop .MENUITEMS.reorient (from MLP Tools box) in.
# Menu Reset.
# Use the Reorient menu to move all the poses by 1 cm. This will save all the poses, with only a small change. If you don't want the 1cm change, then just move it back 1cm after it finishes. Wait for both props and pose adjustment to complete! (Be patient!)
# dump pos, dump props, and save to appropriate notecards.
# Delete MENUITEMS.reorient, and restart.

This will strip all the trailing zeros.

Fourth: if your anims are mod, you can change the names. Use short names, which take less memory. Short button names also use less memory.

The last resort is more drastic. You must give up on some poses, and delete their POSE lines from the .MENUITEMS* cards, and their position settings from the .POSITIONS* cards. You may leave the actual animations in the MLPv2 prim, but you might as well remove them as they won't be used anyway.

=== What do I do about balls that are sunk into the mattress? ===
This problem is caused by the animation hip offset being too high. One fix is to redo the animation and set the hip offset lower. If you can't do that, then there are workarounds.

One workaround is to make sure the first pose on every menu has a position where the balls are visible.

The other workaround is to change the sit target in the poseball, so the balls will be higher for the same avatar positions.

'''Note: this will affect all poses, making the balls appear higher for all poses.'''

# Pull out ~ball. Open it, and edit the ~ball script inside.
# For MLPV2.4x and later, near the top of the script:
## Look for this: "vector SitTarget = <0.,0.,.1>"
## Change it to : "vector SitTarget = <0.,0.,-.4>" (Note that .1 changed to -.4: adjust to taste.)
# Versions before MLPV2.4x:
## Look for this: "llSitTarget(<0.0,0.0,0.1>, ZERO_ROTATION);"
## Change it to : "llSitTarget(<0.0,0.0,-.4>, ZERO_ROTATION);" (Note that .1 changed to -.4: adjust to taste.)
# Take the ~ball object into inventory
# Delete ~ball from the MLPV2
# Drag the updated ~ball from inventory into the MLPV2

This will make all the poses .5 M lower than they were, with the balls at the same place. If that's a bigger change than you wanted, try -.2 or -.1 (that is, adjust to taste).

For versions prior to MLPV2.4z6, you will then need to adjust all the positions to compensate. I suggest you use the .MENUITEMS.reorient notecard for this.

=== Sequence just won't run ===
Q: Heres what I have setup in the .sequences notecard:

<pre>SEQUENCE | Romantic
MENU | Romance
POSE | standing
AVWAIT | 0 | Waiting for someone to sit on ball
WAIT | 10
POSE | Kiss
WAIT | 10
POSE | Enter
WAIT | 15...
...REPEAT</pre>

It shows up in the menu selection, but no poseballs are rezzed when you select the sequence. Here's what I have in the .MENUITEMS notecard pertaining to the sequence-

<pre>MENU Romantic
LINKMSG Romantic | 0,-4,-12001,SEQUENCE Romantic
LINKMSG PAUSE | 0,-4,-12001,PAUSE
LINKMSG RESUME | 0,-4,-12001,RESUME
SWAP
STOP
BACK</pre>

A: Your problem is simple: you have two buttons with the same label, which isn't allowed.

=== Sequence just won't run or skips poses in it===
Currently (2011), the sequencer script won't complain to you if the poses you reference actually exist or not. You're on your own for making sure they actually exist and are named exactly the same (in a menu card) as the way you are referring to them. So watch for this.

=== Xcite! features such as tilt / arousal just don't seem to work ===
Make sure you have the latest set of partner scripts (as of Jan 2012, the latest release was I think in 2009.) Make sure your own Xcite! bits aren't horribly out of date -- you need 3.0 bits or higher. Contacting xcite help isn't of much use; as of mid 2011 they became non-responsive to business partners.

That being said, features won't work unless the xcite partner script is set be either no copy or no transfer. They also won't work if the perms were wrong when you rezzed the product, so edit the script and reset it. That will make the script start to run -- it dies upon start up if perms on the script are wrong.

[[Category:MLPV2]]

MLPV2 Sound Effects

2014-05-14T01:58:51Z

Chaz Longstaff:

MLP Sound Effects by Chaz Longstaff

This MLP sound tool will trigger sounds when poses of your choosing are played. You control if the sounds loop or not, how long they play, etc. The script also allows users to turn all sounds off or back on via a button.

You need two things, both provided on this page: A script and a notecard. Make the script (call it "~sounds" or really anything you want) and the notecard (call it .SOUNDS or .SOUNDS.whatever) and drop into your MLPV2 product. Full usage instructions are within the notecard.

PIECE 1: SCRIPT

<lsl>
//MLP Sounds
//v. 1.1 by Chaz Longstaff 2014-03-7
//This script also requires a notecard named .SOUNDS or .SOUNDS.whatever
//lines inside card should read like: posename,sound, delaybeforeinitialstart, howoftentorepeat, volume, #repeatsbeforeanotherdelay, delayduringplay. See sample notecard provided with full usage instructions

list DelayDuringPlay = [""];
list DelayStarts = [""];
list MaxPlays = [""];
list PoseNames = [""];
list Sounds = [""];
list SoundTimes = [""];
list SoundVols = [""];

integer ListLength;
string mysound;
list mysoundlist;
float mystartdelay;
float myplaydelay;
integer mymax;
float mytime;
float myvol;
string playstatus = "On";
integer soundtotal;
integer soundcount;
integer TimesPlayed;
integer x;

float Interval;
integer Debug;

integer PoseCfgCount;
string Pose;

config_init()
{
PoseCfgCount = 0;
DelayStarts = [];
DelayDuringPlay = [];
MaxPlays = [];
PoseNames = [];
Sounds = [];
SoundTimes = [];
SoundVols = [];
Debug = 0;
Interval = 15.;

}

config_parse(string str, string cardName, integer lineNum)
{
str = llStringTrim(str, STRING_TRIM_HEAD); // delete leading spaces

// lines beginning with slash are comments -- ignore them
if ( (llGetSubString(str,0,0) == "/") || (str == "") ) {
return;
}

list ldata = llParseStringKeepNulls(str, [","], [""]);
PoseCfgCount += 1;
string pose = llStringTrim(llList2String(ldata,0), STRING_TRIM);
string mysoundstr = llStringTrim(llList2String(ldata,1), STRING_TRIM);
string mystartdelaystr = llStringTrim(llList2String(ldata,2), STRING_TRIM);
string mytimestr = llStringTrim(llList2String(ldata,3), STRING_TRIM);
string myvolstr = llStringTrim(llList2String(ldata,4), STRING_TRIM);
string mymaxstr = llStringTrim(llList2String(ldata,5), STRING_TRIM);
string myplaydelaystr = llStringTrim(llList2String(ldata,6), STRING_TRIM);

// posename, sound, delay, howoftentorepeat, volume, #repeatsbeforeanotherdelay

addConfig(pose, mysoundstr, mystartdelaystr, mytimestr, myvolstr, mymaxstr, myplaydelaystr);
}

addConfig(string ref, string sound, string delayref, string time, string vol, string maxref, string playdelayref) {
PoseNames += (list)ref;
Sounds += (list)sound;
DelayStarts += (list)delayref;
SoundTimes += (list)time;
SoundVols += (list)vol;
MaxPlays += (list)maxref;
DelayDuringPlay += (list)playdelayref;

}

// Post-process any config, if necessary
config_done() {
announce();
}

announce() {
//integer acount = llGetListLength(AnimNames);

llWhisper(0,
// + plural("anim", "anims", acount)
//+ " and "
(string) PoseCfgCount
+ " pose(s) configured specially for sound ("
+ llGetScriptName()
+ ": "
+ (string)llGetFreeMemory()
+ " bytes free).");
}

togglesound() {
if (playstatus == "On") {
playstatus = "Off";
llSetTimerEvent(0);
}
else {
playstatus = "On";
llSetTimerEvent( mytime );
}
}

// ==== Utilities ====

integer isKey(string str) { //Identifies whether a certain string is a UUID or not. TRUE if it is
return ( (llStringLength(str) == 36) && //UUIDs are always 36 characters
(llGetSubString(str, 8, 8) == "-") && //9th character is always a dash
(llGetSubString(str, 13, 13) == "-") && //14th character is always a dash
(llGetSubString(str, 18, 18) == "-") && //19th character is always a dash
(llGetSubString(str, 23, 23) == "-") ); //24th character is always a dash
}

// Static parameters for reading card config
string ConfigNotecardPrefix = ".SOUNDS"; // string identifying config notecards
float ConfigTimeout = 180.0; // seconds per card to wait for slow server

// Globals for reading card config
integer ConfigLineIndex;
key ConfigRequestID;
list ConfigCards; // list of names of config cards
string ConfigCardName; // name of card being read
integer ConfigCardIndex; // index of next card to read
string ConfigCardKeys; // for detecting config change

// return TRUE if there is a config card

integer next_card()
{
if (ConfigCardIndex >= llGetListLength(ConfigCards)) {
return (FALSE);
}

ConfigLineIndex = 0;
ConfigCardName = llList2String(ConfigCards, ConfigCardIndex);
ConfigCardIndex++;
ConfigRequestID = llGetNotecardLine(ConfigCardName, ConfigLineIndex);
llWhisper(0,"Reading " + ConfigCardName);
return (TRUE);
}

// Get list of config cards, and return list of their keys for use
// in detecting a config change.

string get_cards() {
string item;
string keys;

ConfigCards = [];
integer n = llGetInventoryNumber(INVENTORY_NOTECARD);
while (n-- > 0) {
item = llGetInventoryName(INVENTORY_NOTECARD, n);
if (llSubStringIndex(item, ConfigNotecardPrefix) != -1) {
ConfigCards += [item];
keys += (string) llGetInventoryKey(item);
}
}
return keys;
}

default
{
state_entry() {
state s_config;
}
}

// This state is only used to get into s_config, because going from
// s_config to s_config won't redo it's state_entry. But we might
// not want to redo anything we might have put in default state entry.

state s_reconfig
{
state_entry() {
state s_config;
}
}

// Read card config
// Multiple notecard version - read all cards with the given extension

state s_config
{
state_entry() {
config_init();
ConfigCardKeys = get_cards();
ConfigCardIndex = 0;

if (next_card()) {
llSetTimerEvent(ConfigTimeout);
} else {
state s_unconfigured;
}
}

dataserver(key query_id, string data) {
if (query_id == ConfigRequestID) {
if (data == EOF) {
if (next_card()) {
llSetTimerEvent(ConfigTimeout);
} else {
config_done();
state s_active;
}
} else {
config_parse(data, ConfigCardName, ConfigLineIndex);
ConfigRequestID = llGetNotecardLine(ConfigCardName, ++ConfigLineIndex);
}
}
}

timer() {
llWhisper(0,"Dataserver time out");
state s_unconfigured;
}

on_rez(integer num) { state s_reconfig; }

changed(integer change) {
if (change & CHANGED_OWNER) { llResetScript(); }
if (change & CHANGED_INVENTORY) { state s_reconfig; }
}

state_exit() {
llSetTimerEvent(0);
}
}

state s_unconfigured
{
changed(integer change) {
if (change & CHANGED_INVENTORY) {
if (get_cards() != ConfigCardKeys) {
state s_config;
}
}
}
}

state s_active {

on_rez(integer start) {
llResetScript();

}

state_entry(){
ListLength = llGetListLength(PoseNames);
}

link_message(integer sender_num, integer num, string str, key id) {

// num = 0 and msg = "POSEB": new pose
// id = pose name
if ( (num == 987790) && (str == "togglesound") ) {
togglesound();
}

if (num == 0 && str == "STOP") {
llStopSound();
llSetTimerEvent(0);
} else if (num == 989999) {
if (str == "stopsound") {
llStopSound();
llSetTimerEvent(0);
}
}
else if (num == 0 && str == "POSEB") {
mystartdelay = 0;
mymax = 0;
soundcount = 0;
soundtotal = 0;
TimesPlayed = 0;
mysoundlist = [];
if (playstatus == "Off") {
llSetTimerEvent(0);
return;
}
Pose = llStringTrim( ((string)id) , STRING_TRIM);
// llSay(0, "Pose : " + Pose);
integer ix = llListFindList(PoseNames, (list)Pose);
if ( ix != -1) {
string mysounds = llList2String(Sounds,ix);
integer index = llSubStringIndex(mysounds,"***");
if(index == -1) {
mysound = mysounds;
}
else {
mysoundlist = llParseStringKeepNulls(mysounds, ["***"], [""]);
soundtotal = llGetListLength(mysoundlist);
mysound = llList2String(mysoundlist,soundcount);
}
mystartdelay = (float)llList2String(DelayStarts,ix);
mymax = (integer)llList2String(MaxPlays,ix);
mytime = (float)llList2String(SoundTimes,ix);
myvol = (float)llList2String(SoundVols,ix);
myplaydelay = (float)llList2String(DelayDuringPlay,ix);

// llSay(0,
// "mysound : " + mysound
// + "/ delay : " + (string) mystartdelay
// + " / repeatseconds : " + (string) mytime
// + " / myvol : " + (string) myvol
// + " / maxrepeats : " + (string) mymax
// + " / delayduringplay : " + (string) myplaydelay
// );
if ( mystartdelay > 0 ) llSleep(mystartdelay);
llPlaySound(mysound,myvol);
TimesPlayed = TimesPlayed + 1;
llSetTimerEvent( mytime );
}
else {
// llSay(0, "got a shut off msg");
llSetTimerEvent( 0 );
}
}
} //end linkmsg section

timer() {
//llSay(0, "in timer");
if (mymax == 0) {
//llSay(0, "no max so go ahead and play");
}
else if ( (TimesPlayed + 1) > mymax ) {
TimesPlayed = 0;
llSleep(myplaydelay);
}

if (soundtotal > 1) {
soundcount = soundcount + 1;
if ( (soundcount + 1) > soundtotal ) {
soundcount = 0;
}

mysound = llList2String(mysoundlist,soundcount);
}

if (isKey(mysound) == TRUE) {
//it's a UUID so just play it
llPlaySound(mysound, myvol);
TimesPlayed = TimesPlayed + 1;
}
else {
//it's a sound file, so test to make sure it's present to avoid script errors
if ( llGetInventoryType(mysound) != INVENTORY_NONE ) {
llPlaySound(mysound, myvol);
TimesPlayed = TimesPlayed + 1;
}
}

}

changed(integer change) {
if (change & CHANGED_INVENTORY) {
if (get_cards() != ConfigCardKeys) {
state s_config;
}
}
}

}

</lsl>

PIECE 2: NOTECARD

<lsl>
//name card .SOUNDS
//or .SOUNDS.whatever
//lines inside card should read like: posename,sound, delaybeforeinitialstart, howoftentorepeat, volume, #repeatsbeforeanotherdelay, delayduringplay

//posename: case (and space sensitive inside pose names), make sure you get it right! You can leave spaces in between the commas or not, your choice.
//sound. You have two choices.
//Sound Choice (1) You can put in sound name, but if you do, you must include the sound file inside the prim. You need to have copy / transfer rights to the sound file to include it in products you want to sell to others. You don't need mod rights to the file.
//Sound Choice (2) You can instead supply the UUID of the sound file. You need full perm rights (mod / copy / transfer) to the sound file in order to be able to get the UUID -- right-click over a full-perm sound in your invy. Choose copy UUID, and use that as the sound name. When you list a sound UUID, you don't need to include the sound file inside the MLP product -- makes for tidier contents and less to proof for perms, etc.
//delay: how many seconds to pause initially before starting any sound play. Set to 0 if no delay is wanted. Applies only to initial start.
//howoftentorepeat: how often in seconds the sound should repeat play itself. Enter as a number. Decimal numbers such as 5.5 are fine. 0 equals play only once.
//volume: Enter a number ranging from .1 (lowest) to 1.0 (that being the loudest possible in SL). Instead of 1.0, you can enter just 1
// #repeatsbeforeanotherdelay: no of times to play the sound before once again doing the delay. Example: delay of 10 seconds, 15 repeats: script waits 10 seconds before starting playing. Plays sound 15 times (at the x seconds intervals you specified.)
//delayduringplay: sound plays x number of times, then pauses this long in seconds, then plays x number of times again, then pauses again this long in seconds, etc. Put 0 if no delay.

//MENU BUTTON
//Creating a menu button like this will allow users to toggle the playing of sounds off and on
//LINKMSG buttonname | 0,-4,987790, togglesound
//change the buttonname part to be anything you like (e.g. SND ON/OFF or TOGGLE SOUND). Don't change anything else in this line.
LINKMSG SOUNDON/OFF | 0,-4,987790, togglesound

//SOUND LINE EXAMPLE
//Spanking, LoudSpank, 0, 10, 1.0, 0
//when they are on the Spanking pose, play the sound LoudSpank. No delay in starting. Play every 10 seconds at 1.0 volume (max volume). No limit to repeats.
//Flogging, 98gyt10f-82e4-788c-2a07-1c32d409yhmv, 10, 3, 1, 5
//when they are on the Flogging pose, play the sound represented by the UUID. Wait 10 seconds before starting, then play every 3 seconds at max volume which is 1. When the sound has played 5 times, then pause 10 seconds again, they start play all over again.

BInspect, d3b61629-50a3-9716-7683-8972f2bb631c, 14, 1, 1, 4, 26
BDick, beab335a-c030-0307-0948-c5cc77b3c3ac, 0, 20, 1, 0, 0
BTowel, 59fbf10f-82e4-788c-2a07-1c32d409fafe, 0, 3, 1, 0, 0
BSpank, d71bd292-6d72-a830-68a1-8b4322fb091d, 0, 3, 1, 0, 0
</lsl>

MLPV2 Tutorial

2014-05-13T01:05:17Z

Chaz Longstaff: /* 3. Programming a sequence */

{{Navbox/MLPV2}}

This tutorial is intended for "builders": people adding poses to furniture.

Folks who just want to know how to use their furniture should see [[MLPV2 Users Tutorial]].

== Setting up MLPV2 ==
These instructions look long, but it's easier than it looks. Here's the overview:
# get the scripts and notecards and drop them into a prim (CREATE YOUR OWN PRIM -- so folks know who made it!)
# put your anims in the same prim
# Create and edit one or more .MENUITEMS.* notecards (use whatever you want for "*"). Configure menus and add poses to the menus. Mostly the same as old MLP, with enhancements and no need to edit the main menu.)
# Reset and try the menu
# adust each pose (same way as old MLP)
# dump memory and save positions in notecard (nearly same way as old MLP; sellers may want to use modular .POSITIONS.* files)

These instructions are oriented for someone setting up a new object. However, those who bought one and are adjusting it or adding poses can simply skip the obvious steps that the maker would already have done.

== Get the scripts ==
The latest scripts are available at jPose Island, in the FREEBIES section. It is Adult land, so you will need to either have payment info on file or be adult certified.

MLPV2.3 is available on Marketplace, under Lear Cale as merchant.

Take a good look at the .readme file.

== Install scripts ==
Rez the MLPV2 and copy its contents into inventory and then into your furniture.

Delete the notecards ending in "examples", along with the ~pillow object and any example animations you don't plan to use.

Life is easiest if you use your object's root prim for MLPV2; instructions below for when it's not. For your first try, stick with root prim and keep life simple. (An easy way to add it to an existing bed is to just float it slightly above your mattress and then apply a totally clear texture, available in any freebie depot.) Below, we'll call this prim the "MLP prim".

[Tip: You'll thank yourself later in life if you try to keep the orientation of the MLP prim the same across your products, for example, with rotation 0,0,0. This makes it easier to transfer poses between products. However, with sculpties this isn't always feasible.]

Click the MLP prim so that it starts up for the first time. If you get a menu, fine; you've already done this. If nothing happens, click again -- an SL bug causes the first click to get lost.

== Install animations ==
Drag all the anims you'll use into the prim. (You can pull these out of poseballs you like. If the animations are no-copy, this will render the poseballs useless.)

Note: not all animations will work with MLP. See discussion here: [[MLPV2_Reference_Manual#TIP.21_Animations_Caveat]]

== Create and edit your .MENUITEMS.* file ==

Create a new notecard, named ".MENUITEMS.''mystuff''", where "''mystuff''" can be anything you want. MLPV2 can take any number of these, and bed sellers can make different pose sets for different customers.

[[File:Tutorial1.6.png|100px|thumb|left|Click for graphic view]]

Drop this notecard into the object. [You might want to do most of the editing first; objects with lots of things in inventory react slowly to changes, and you might have a lot of animations. As of Nov/2009, there's also an issue with editing notecards in object inventory. Unless you've heard the "all clear" on this, or know the workaround, it's best to edit in your avatar inventory.]

Create a menu:

MENU ''MyMenu'' | ALL | PINK | BLUE

[Tip! The standard practice is to list the pink ball first, then the blue -- you may do the opposite if you wish, but for what it's worth, that's the convention. This convention was established in 2006 with the release of MLP 1.1, and is practised in XPOSE! as well.]

This creates a menu whose button in the top menu will be labeled ''MyMenu''. '''ALL''' indicates that it will be accessible by everyone (alternatives here are '''GROUP''', only allowing people in the same group as the object, or '''OWNER''', only allowing the owner). After that, list each ball color for the poses in this menu. You can have up to six balls. If you have some solo poses, some couples poses, and some 3some poses, they have to be in different menus.

In this example, a pink and a blue poseball will be rezzed.

For each pose in this menu, add a line like this:

POSE ''pose1'' | ''anim1'' | ''anim2''

where
: ''pose1'' will be the button name for this pose.
: ''anim1'' is the name of the animation for the first poseball (which happens to be pink in our example)
: ''anim2'' is the name of the animation for the second poseball (which happens to be blue in our example)

Zero, one, or two spaces are allowed around the vertical bars. Avoid extra spaces.

For '''facial expressions''', you add a suffix to the animation names indicating the expression. Note that you don't change the actual name of the animation in the inventory, you just add the suffix in this configuration notecard. These are explained in [[MLPV2_Reference_Manual#Animations_.28Facial.29]] . For a simple example, appending "*" will give an astonished open-mouth expression.

The following can also be included in your menu:
STOP
SWAP
BACK
TOMENU ''MyOtherMenu''

: '''STOP''' makes a button labeled STOP that de-rezzes the poseballs and unsits everyone.
: '''SWAP''' makes a button labeled SWAP that exchanges the first two balls, by default. Starting with MLPV2.4, you can configure the swap arrangements for poses with multiple balls, [LINNK TBD].
: '''BACK''' makes a button labeled BACK that goes back to the previous menu. Every menu should have one of these!
: '''TOMENU''' makes a button labeled ''MyOtherMenu'', which goes to the ''MyOtherMenu'' menu (which you must create).

With MLPV2 (assuming you're using the .MENUITEMS that comes with MLPV2 rather than an old MLP configuration), any MENU that is '''not''' found in a previous '''TOMENU''' entry is added to an empty slot in the top menu. I'll talk more about this below, under [[MLPV2 Submenus]].

It's a good convention to end each menu with the following:
SWAP
STOP
BACK

For MLPV2 (again, assuming you're using the .MENUITEMS that comes with MLPV2 rather than an old MLP config), buttons are placed in the menu in the same order they appear in the config notecard. To set old MLP configs to using this new (sane) menu order, see here: [http://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#MENUORDER]

Repeat the above for each menu you want. Poses with different numbers of participants have to be in different menus, since the MENU line gives the number and colors of the balls.

For a menu with 3 or more poses, the POSE line would list that number of animations, separated by vertical bars ("|").

== Continuation menus ==
As we all know, you get at most 12 buttons in an SL menu. However, starting with MLPV2.1, you can have more than 12 buttons in a configured MENU. If there are more than 12, MLPV2.1 and later will automatically add a '''MORE-->''' button after the 11th item, leading to the remaining choices. (And also after the 22nd item, etc.)

If you wish MLPV2 to automatically a '''BACK''' button whenever it adds a '''MORE-->''' button, add the AUTOBACK directive to your .MENUITEMS config card. It doesn't matter where it is, but convention is to put it near the top. Put it alone on a line.

Note that a '''BACK''' button will not be added to the top, main menu (because there is no further back there to go back up to.) Nor will it add it to the last page of a series of sub-menu pages, or to a single-page sub-menu -- you must add the word BACK yourself manually to these if desired.

== Menu Reset ==
Save your changes. (If you're editing a copy in inventory, install it in the MLPV2 prim).

Click the MLPV2 object. If this is the first time since you installed the scripts, it will start up and read the configurations. If you get a menu, select '''OPTIONS -> ShutDown -> Menu Reset'''. This button causes it to re-read all .MENUITEMS* files, including yours.

Watch for warning messages. The most common one is due to an animation being missing or misspelled in the configuration. Fix any mistakes and do another Menu Reset. (A reset is '''not''' required for missing animations; just drop in the anim. If you don't have some of them yet, don't worry, this won't do any harm.

Click to get the menu. You should see the button for your new menu; click it. You should see the menu you configured. Click the first pose. You should see the right number and color balls appear. They may be in odd places.

Tip! Note that "MenuReset" will not re-read positions from the positions card. PosReset and Restart will.

== The default pose ==

The "default pose" is a set of poseball positions and orientations that is used for any new pose, since new poses don't have saved positions yet.

The default pose in the MLPV2 distribution assumes that the MLPV2 prim is essentially an unrotated box, flattened and stretched like a mattress cover. If your prim is rotated (as is likely if you're using a flattened cylinder lying on its side for the mattress, and MLPV2 is in the mattress), you will want to adjust the default pose so none of the balls are underground.

Go to main blue menu and select '''adj-default -> default'''.

Tip! If you don't have this choice, see here: [https://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#TIP.21_Default_Pose]

If the default pose looks fine (6 balls arranged in a hexagon, avs sitting facing each other), skip this step.

If the default pose looks wrong, adjust it following the instructions below, as for any pose you would add. You may have to be clever to get at balls that might end up under the floor or buried in your object.

When saving the default pose as described below, be sure to save it to the .POSITIONS notecard, rather than to your .POSITIONS.''mystuff'' notecard.

== The stand pose ==

MLPV2 uses the '''stand''' pose whenever STOP is used (or on any reset button in the Shutdown menu), just before unseating the avatars. This helps avoid them popping high into the sky, which happens when poseballs are buried inside the object.

I suggest using the default pose for the stand pose. Simply duplicate the "{default} ..." line in .POSITIONS and change "default" to "stand".

== Adjusting poses ==

'''MLPV2.3 and later'''

* Select '''OPTIONS -> Adjust Pos''' at any time. Whenever anyone is sitting on a poseball, it will be long and translucent to be easy to find and select. We call these "beams". Participants can hop on and off balls at any time during adjustment.
* Select the beams (right-click -> Edit) and adjust them as desired. When done with a pose, simply select the next pose. The current pose's position is automatically saved. Also, you can save the current pose's position at any time using '''OPTIONS -> Save Pos'''.
* '''To undo changes''' to the current pose, just select it again. Alternatively, just quit adjusting.
* '''To quit adjusting''', make sure the current pose is saved (if desired), and use either '''STOP''' or '''OPTIONS -> Adjust Pos'''. (Stop will also delete the balls and pop off any participants.)

'''MLPV2.2 and earlier'''

* Use the menu to select whichever pose you want to adjust. If it's a new pose, it will get the default pose. Have avatars sit on the poseballs. Use the menu '''OPTIONS -> Adjust Pos''' to make the poseballs visible and easy to select for editing. (They get long and translucent, so we call them "beams".)
* Select the beams and orient them as desired. When done, use the '''OPTIONS -> SavePos''' button.
* You may continue with the next pose, or re-adjust this one. When someone stands, their poseball will go back to the normal shape. Just click the '''AdjustPos''' button to make it a beam again.
* The '''AdjustPos''' button's only affect is to change the size and appearance of the poseballs. Feel free to adjust positions by selecting the clear tiny sat-upon poseballs and moving them, if you prefer.

== Saving pose positions to notecards ==

'''NOTE WELL''': The '''SavePos''' button saves the position in MLPV2 memory. A reset will cause it to forget. End users will probably want to save the changes to notecards, and sellers will need to.

This is why the .POSITIONS notecard should be ideally released to customers as MODIFY. Note as well, though, that if a notecard is placed in a no modify object, people will not be able to open the notecard at all, regardless of the perms on the notecard. This is a SL system limitation.

'''NOTE''': The ~swap script has to be in and running to save new positions! [for MLPV2.4 and later]

=== Saving pose positions, new object ===

Follow these instructions if this is a new object and you plan to sell it and possibly a line of related objects with MLPV2 poses. There is a simpler way for end users, below.

Create a .POSITIONS.''mystuff'' notecard, where ''mystuff'' matches your .MENUITEMS.''mystuff'' file name. (This isn't absolutely required, but makes life simple and I will assume that convention is followed in this tutorial.)

Use '''OPTIONS -> Dump Pos''' to dump all the positions. Using the chat history window, copy the text between the "-----" lines, which looks something like this:

[xx:xx] : {pose1} <... ''numbers'' ...>

Paste them into your notecard. It isn't necessary to delete the stuff to the left of {pose1}, but you can if you like things tidy.

Delete the {default} line. (Note: if you changed the default pose, save this line in '''.POSITIONS''' notecard.)
Delete the {stand} line. (Note: if you changed the stand pose, save this line in '''.POSITIONS''' notecard.)

Save, and use '''OPTIONS -> ShutDown -> PosReset'''. This causes the .POSITIONS.* files to be re-read, including yours.

That's about it; now you're ready to test your poses. Have fun!

Tip! For those using old MLP .MENUITEMS files: If the PosReset button is not offered, look for the RESTART option. Note that RESET will not re-read positions from the positions card. Only PosReset and RESTART will.

=== Saving a single position that you've updated ===

When you use '''OPTIONS -> SavePos''' for, say, ''pose1'', you'll see a line in chat looking like this:

MLPV2 (empty): {pose1} <... ''numbers'' ...>

There may be a timestamp. You can copy this line and replace it in the corresponding .POSITION.* file (e.g., the one already containing this pose's position).

=== Saving pose positions, simplified version for end users ===

If you're adjusting an object you bought that's already set up, and you've adjusted a lot of poses, this is the easiest way to save all your changes. Note, however, that if your product has pose pack modules and you might want to remove one to make room for other add-on poses, this might not be the best way.

Use '''OPTIONS -> Dump Pos''' to dump all the positions. Using the chat history window, copy the text between the "-----" lines, which looks something like this:

MLPV2 (empty): {pose1} <... ''numbers'' ...>

It may include a timestamp.

Paste them into the .POSITIONS notecard, replacing its previous contents. It is '''not''' necessary to delete the stuff before {pose1}, but you can if you like things tidy.

Delete all other .POSITIONS.* files in the MLPV2 prim's inventory.

If you later decide to delete a pose pack (a .MENUITEMS.* file) with poses you won't use, you can still do that. The positions for those poses will still be in the .POSITIONS notecard, and you can feel free to delete them manually.

== Deleting adj-default menu button ==

Once you're happy with the default pose positions, simply delete .MENUITEMS.zz-default from the MLPV2 prim's inventory. You can always put it back by dragging that file from the MLPV2 distribution.

== PROPS ==

Beginning with MLPV2.1, you can provide prop objects that MLP will rez for specific poses.

When you choose another pose or hit STOP, any rezzed prop disappears. If you delete the MLP object, any prop will disappear in a few minutes.

For any pose, you can have at most '''one''' prop object. If you need more than one prop to rez, you'll have to link them so that they can be treated by MLPV2 as one object.

1) The following lines are required in your MLP menu. Starting with MLPV2.1, they're already in the standard .MENUITEMS, in the OPTIONS menu. Add them if you're starting with an older version.

*LINKMSG DumpProps | 0,-4,1,DUMPPROPS // dump all prop configs
*LINKMSG SaveProp | 0,-4,1,SAVEPROP // save position/rotation for a prop

2) Find the prim prop object that you want MLP to rez, and rez it.

3) Add to this prop object the "~prop" script (you'll find this inside the supplied "~pillow" object). Take your prop object back into inventory and drop it into the MLP prim's inventory. Note: the prop object and everything in it will need to be copiable for next owner -- otherwise, it will only rez once for them!

4) Edit a .PROPS notecard or add a new one (named .PROPS.* where * is whatever you want, for a modular config.) Copy this example line and paste it into your .PROPS file.

| mypose | myobject | <1,1,1>/<0, 0, 0>

(Don't omit the vertical bar ("|") at the left.)

: *Replace "mypose" with the name of the pose that the object should rez for. 
: *Replace "myobject" with the name of the prop object. The object name cannot contain vertical bars. 

Save your work.

5) Use the MLP menu's PosReset or Restart button. When the MLP has restarted, select the pose that the prop goes with. The prop should appear. It might be underneath the MLP object, or some distance away, so look around -- it may be best to do this using a single prim MLP floating in the air, the first time.

6) Edit the prop, and use the editing arrows to move the prop to where you want it. Then, use the MLP menu "SaveProp" button.

To make the change permanent, select the text in the chat line (including the first vertical bar, and optionally any text before it) and replace the corresponding line in your .PROPS* file. Or, do all your props, saving their positions, and then use the DumpProps button. This works the same way as saving positions in .POSITIONS* files.

7) To get MLP to reread .PROPS* files, use PosReset (which resets positions as well as props), or Restart.

Keep in mind that props and positions are saved separately, so if you adjust a pose and its prop, you need to save both pose position and prop. (When using AdjustPos feature with MLPV2.4 or later, both pose and prop positions are saved when you select a new pose.)

'''Worn or Hand-held Props''': For props to be worn by the user, use the ~give script add-on found here [[MLPV2_Give_Item_Add-on]] and have people wear the items.

== SEQUENCES ==

Starting with MLPV2.3, you can create sequences of poses that run automatically once started.

It's a little complicated. You need to:

# set up menus (and often poses as well) for the sequences to use
# set up a control menu for the user to access and control the sequences
# program the sequences

=== 1. Set up the menus (and poses)===

In a .MENUITEMS.* notecard, create menus for the sequences to use. These menus:

(a) tell sequences how many balls to rez, and of what colour; 
(b) are used to set up poses for the sequences

If your sequence will use poses that are already in your menus, you're done here, nothing special to do.

If your sequence will use poses that you don't want to appear in any menu, you need to set up a "hidden menu". To do this, just make a menu the usual way, except use "HIDDEN" rather than "ALL", "GROUP", or "OWNER", like this:

MENU ROMNIGHT | HIDDEN | PINK | BLUE

Add your poses to this menu. Avoid extra spaces, especially between MENU and the menu name.

If you have sequences with different numbers of participants, you'll need to use additional menus with the appropriate number and color poseballs.

=== 2. Create a control menu for the sequence(s) ===

See the .MENUITEMS.example notecard in MLPV2 distribution as an example. This menu has two buttons to start sequences, and two buttons to stop and continue them, along with the usual navigation and swap buttons:

// example menu containing 2 sequences, and sequence controls
MENU Tours... | ALL
LINKMSG *Tour1* | 0,-4,-12001,SEQUENCE Tour1-seq
LINKMSG *Tour2* | 0,-4,-12001,SEQUENCE tour2-seq
LINKMSG PAUSE | 0,-4,-12001,PAUSE
LINKMSG RESUME | 0,-4,-12001,RESUME
LINKMSG NARRATION | 0,-4,-12001,NARRATION
SWAP
STOP
BACK

In the above, "*Tour1*" and "*Tour2*" are button labels -- that's what the user will see in the menu.
The "| 0,-4,-12001,SEQUENCE" part is pure magic, don't mess with that unless you're a magician.
"Tour1-seq" and "tour2-seq" are names of sequences in the .SEQUENCE* notecards.
Be careful: the names need to match exactly.

PAUSE causes the sequence to stop advancing.

RESUME causes the sequence to resume where it left off. Alternatively, if you didn't PAUSE, RESUME advances to the next step. This is handy for quickly testing a sequence with long wait times.

NARRATION allows the user to toggle off and on any WHISPER or SAY messages you might have programmed.

STOP stops the sequence and unrezzes the balls. After a STOP, RESUME and PAUSE have no effect.

'''NOTE WELL''' Avoid having two different buttons in an MLP/MLPV2 menu with the same button name. Only the first of the two will work. Subsequent ones (duplicates) will only cause the first button's effect. (It's OK to have the same button appear in multiple places, if you want them all to do the same thing. BUT:

LINKMSG PLAYALL | 0,-4,-12001,SEQUENCE MASSAGESCENE-seq

and

LINKMSG PLAYALL | 0,-4,-12001,SEQUENCE BJSCENE-seq

in the same menu will cause havok, as the menu will get confused about the duplicate button label of PLAYALL

=== 3. Programming a sequence ===

Create a notecard whose name starts with .SEQUENCES, followed by whatever you wish. In the MLPV2 distribution, this is .SEQUENCES.example. I'll go through an example sequence explaining what each line does.

Start the sequence with the sequence name specified in the control menu in .MENUITEMS file; in this case, "Tour1-seq". The name is arbitrary, it just has to match between the MENUITEMS notecard and the SEQUENCES notecard. For example:

SEQUENCE | Tour1-seq

Next, give it the name of a menu to use to model itself after for setting the number and color of balls. You can change the menu later in the sequence using more MENU lines.

MENU | Example

Note the vertical bar ("|"), unlike in a .MENUITEMS* card. Note as well that all you put is the name of the menu, and not the stuff that would follow it in a .MENUITEMS* card.

Now, program the steps in the sequence as poses followed by timed pauses, and possibly waiting for participants to hop on. (Note the pipe symbol | required, unlike in the .MENUITEMS card. Note as well that you only list the name of the pose -- not any associated animation.)

POSE | standing

The line above starts the "standing" pose.

'''Important''': The sequencer script currently (2011) won't give you any error messages if the Pose you reference doesn't actually exist. You're on your own here, Bernice, to get it right!

AVWAIT | 0 | Waiting for someone to sit on blue ball

The line above causes the sequence to wait for someone to sit on ~ball0. (To see which ball a ball is, pick the pose using the menu and right-click->Edit the ball. The number at the end of the name is the number to put between the "|" characters above.) The text after the final "|" is optional; it's what the object chats if it needs to wait.

You can specify any number of balls here; for example, you can use:

AVWAIT | 0 1 2 3 | Waiting for all participants!

'''Important''': Any looping sequence should have an AVWAIT in the loop. We don't want to disturb the neighborhood with an unused bed running endlessly through a sequence. In a future version, Lear might in fact make it an error to have a loop without an avwait.

WHISPER | 0 | /0 and /1 stand together

The line above causes the object to whisper the given line on channel 0 (the number between the "|" characters). "/0" through "/5" get substituted with the first name of the av on the corresponding ball. If nobody is on the ball, it uses "somebody".

WAIT | 10

The line above causes the sequence to wait for 10 seconds before proceeding.

POSE | pillow-sit | 0 | /0 and /1 sit with a comfy pillow

The line above selects a new pose and whispers the text on channel 0. Note that we omitted this optional chat in the POSE line above. As earlier, /0 and /1 are replaced with the participant's first names. Although you have two poses within the 10m rule, if the next pose in the sequence is 10m+ from the previous pose the balls won't go the distance.

WAIT | 10
POSE | sit2 | 0 | The pillow disappears
WAIT | 10

You should know by now what the lines above do.

=== Programming a loop ===

The next line causes the whole sequence to repeat.

REPEAT

Alternatively, you can use a LABEL line anywhere in the sequence, and end the sequence with a GOTO line, as in the other example provided with the MLPV2 distribution:

LABEL | mylabel
AVWAIT | 0 1| //make sure we're not looping with no one using the balls, so check for people on both ball0 and ball1
...
...
GOTO | mylabel

TIP! Don't re-use a label name twice in the same sequence notecard or funky things may happen.

Or, you can just have the sequence end by not adding any more steps (or, by starting a new sequence). If the sequence doesn't end with GOTO or REPEAT, it simply pauses at the end, leaving the participants in the last pose.

TIP! It doesn't matter whether you leave spaces or not around the | symbol; the sequences script will sort it out.

=== Avoiding the posename chat ===

By default, MLPV2 chats the pose name whenever it starts, either by menu or sequence. If you don't want it chatting pose names during sequence, add "| NOCHAT" to the end of the SEQUENCE line, like this:

SEQUENCE | Tour1-seq | NOCHAT

=== Hiding the poses from the menu ===

You can hide any MENU in the notecards from the user by using "HIDDEN" instead of "ALL", "GROUP", or "OWNER", as below:

MENU | seq1-poses | HIDDEN | PINK | BLUE

Put your sequenced poses in such a menu and they'll be invisible to the user. Just remember to set up the pose positions before hiding the menu they're in! Of course, you can use "Adjust pos", PAUSE in the sequence, and adjust.

=== TIP: Sequence naming rules ===

A sequence has
# a button name
# a sequence name

The button name and sequence name appear in the .MENUITEMS.''myStuff'' notecard:

LINKMSG Cuddle | 0,-4,-12001,SEQUENCE WarmUp

Cuddle is the button name, WarmUp is the sequence name.

The sequence name also appears in the .SEQUENCES.''myStuff'' notecard:

SEQUENCE | WarmUp

This is the fist line of the sequence. WarmUp is the sequence name. '''It must exactly match the sequence name''' (WarmUp) in the LINKMSG line in the .MENUITEMS.''myStuff'' notecard!

The button name does '''not''' need to match the sequence name. It's OK if it does.

== Configurable SWAPs ==

By default, the SWAP button swaps the first two balls, which is appropriate for couples poses. Therefore, there is no need to configure swaps for solo and couples poses.

For poses with 3 or more parties, you may want to configure what the swap button does. In this case, the button will cycle through a set of ball orders for the pose.

It's confusing, but stick with me and we'll muddle through. Here's the big picture. Each line in the .SWAPS.''myStuff'' notecard configures the swaps for one pose. (I would rather have done it per menu, but that just didn't work out, sorry!)

For a pose, we configure a set of ball permutations (arrangements, or orders). When the user hits SWAP, the balls will cycle through the given permutations. The first perumtation is always 0 1 2 3 4 5, meaning that ball0 is first, ball1 is second, ball2 is next, etc. (For a PINK | BLUE | RED menu, ball0 is pink, ball1 is blue, and ball2 is red.)

Since the "0 1 2 3 4 5" permutation is the default, it is NOT configured but is assumed. We only configure the 2nd, 3rd, and subsequent permutation (as many as we like).

Each line of the swap configuration notecard looks like this:

''posename'' | ''permu2'' : ''permu3''

where there can be any number of permutations, separated by a colon (":").

As mentioned above, the orders are given by a list of poseball position numbers.

Let's look at an example, with a 3-ball menu that uses PINK | BLUE | RED balls. Let's say we want the pink and red balls to swap, but leave the blue ball alone.

So, the permutations would be first the implicit 0 1 2 permutation, and then the swapped one, which in this case would be 2 1 0. It would be configured like this:

fmf-cuddle | 2 1 0

where fmf-cuddle is the pose name.

Confused yet? Yeah, me too. Now let's try a 3some pose where we want to rotate all three. For example, they're sitting around a round table, and we just want each one to move one position to the side.

The first permutation is always 0 1 2.

For the next permutation, we want 2 0 1. Balls 0 and 1 move right one place, and ball 2 slips back around to the first position.

For the next permutation, we want 1 2 0. Balls 2 and 0 move right one place, and ball 1 slips back around to the first position.

We'd configure it like this. Remember we omit the first permutation, since it's the default permutation and is implicit:

3-sitting | 2 0 1 : 1 2 0

When we hit SWAP the first time, we get the 2 0 1 permutation. Hit it again, we get 1 2 0. Hit it again and we go back to 0 1 2, the implicit default permutation. And so on, until the avatars get dizzy.

When I configure swaps, I actually write down the default permutation and keep it there to help me think, and then delete it when I create the pose configuration line.

Now let's try a two couples 4some for a PINK BLUE RED GREEN menu (female, male, female, male), where first we want the females to swap, and then we want the males to swap. I'll start out with the default permutation shown because it helps my feeble mind. Then I'll put the subsequent permutations below, in sequence.

0 1 2 3 - default
2 1 0 3 - females swapped

for the next one, let's swap the men but leave the women swapped:

2 3 0 1 - females swapped, males swapped

Are we done? Well, if we stopped here, the next click on SWAP would move all 4 balls. Instead, let's swap the men again, and then moving back to the default will only swap the women.

0 3 2 1 - males swapped

So, putting them all together:

0 1 2 3 - default
2 1 0 3 - females swapped
2 3 0 1 - females swapped, males swapped
0 3 2 1 - males swapped

I hope you're getting the picture by now. If your head hurts, well, mine does too. Just try doing some 6some swaps for real fun!

Here's the resulting configuration line:

Swingers | 2 1 0 3 : 2 3 0 1 : 0 3 2 1

NOTE: I did not test these configs, and I make mistakes. I'll try to find time to test. In the meantime, please feel free to try it out and '''please''' let me know of any mistakes.

Here are some common useful swaps, including the examples above. Delete the comments before using, and of course, replace the name I've given here with the actual pose name.

3somes

mfm-mfm | 2 0 1 : 1 2 0 // swap first & third of 3some
3-swap-other | 0 2 1 // swap 2nd pair of 3some
3-rotate-1 | 2 0 1 : 1 2 0 // rotate three, one direction
3-rotate-2 | 1 2 0 : 2 0 1 // rotate three, other direction
3-all | 0 1 2 : 0 2 1 : 2 0 1 : 2 1 0 : 1 2 0 : 1 0 2 // all permutations

4somes

Swingers | 2 1 0 3 : 2 3 0 1 : 0 3 2 1
fmmm-rotate-m | 0 2 3 1 : 0 3 1 2 // hold 0, rotate others
mfmm-rotate-m | 2 1 3 0 : 3 1 0 2 // hold 1, rotate others

5somes

fmfmf | 2 1 4 3 0 : 2 3 4 1 0 : 4 3 0 1 2 : 4 1 0 3 2 // alternately rotate women, swap men

== Tips ==

=== Expandability ===

For expandability, we recommend that each .MENUITEMS* file contain one "unanchored" menu at the top, with any submenus in the notecard hanging off of that unanchored one. This allows 10 independent modules and only memory limitations on the total number of menus. We also suggest dividing menus & positions into separate notecards making it easy for customers to delete the ones they won't use.

(An "unanchored" menu is one that doesn't have any TOMENU button leading to it.)

MLPV2 loads the notecards in the same order they appear in object inventory. The buttons for the unanchored menus in these notecards are added to the main menu in the same order. So, name your extensions so your notecards sort in the order you want these buttons to appear.

=== Main menu ===

By convention, the top, "main menu" often includes buttons such as OPTIONS, SHUTDOWN, etc, as well as buttons providing access to the sub-menus. By convention, this menu is defined in the .MENUITEMS notecard (note, no suffix).

Don't attempt to put actual poses in the menus found here. They won't work reliably, since these menus don't list the number and color of poseballs.

=== Help button ===

You may wish to add at this top level a HELP button.

The configuration would be something like this:

LINKMSG HELP | 1,-4,987789,-Help for XYZProduct##Here's your help notecard

Put this line at the end of the "TOMENU -" lines below MAIN MENU.

Then drop in the ~give script add-on found here [[MLPV2_Give_Item_Add-on]]

It might be better to name the help notecard something other than just "Help", so that your users can identify it more easily when it ends up in their inventories.

[[Category:MLPV2]]

MLPV2 Tutorial

2014-05-12T22:31:37Z

Chaz Longstaff: /* 3. Programming a sequence */

{{Navbox/MLPV2}}

This tutorial is intended for "builders": people adding poses to furniture.

Folks who just want to know how to use their furniture should see [[MLPV2 Users Tutorial]].

== Setting up MLPV2 ==
These instructions look long, but it's easier than it looks. Here's the overview:
# get the scripts and notecards and drop them into a prim (CREATE YOUR OWN PRIM -- so folks know who made it!)
# put your anims in the same prim
# Create and edit one or more .MENUITEMS.* notecards (use whatever you want for "*"). Configure menus and add poses to the menus. Mostly the same as old MLP, with enhancements and no need to edit the main menu.)
# Reset and try the menu
# adust each pose (same way as old MLP)
# dump memory and save positions in notecard (nearly same way as old MLP; sellers may want to use modular .POSITIONS.* files)

These instructions are oriented for someone setting up a new object. However, those who bought one and are adjusting it or adding poses can simply skip the obvious steps that the maker would already have done.

== Get the scripts ==
The latest scripts are available at jPose Island, in the FREEBIES section. It is Adult land, so you will need to either have payment info on file or be adult certified.

MLPV2.3 is available on Marketplace, under Lear Cale as merchant.

Take a good look at the .readme file.

== Install scripts ==
Rez the MLPV2 and copy its contents into inventory and then into your furniture.

Delete the notecards ending in "examples", along with the ~pillow object and any example animations you don't plan to use.

Life is easiest if you use your object's root prim for MLPV2; instructions below for when it's not. For your first try, stick with root prim and keep life simple. (An easy way to add it to an existing bed is to just float it slightly above your mattress and then apply a totally clear texture, available in any freebie depot.) Below, we'll call this prim the "MLP prim".

[Tip: You'll thank yourself later in life if you try to keep the orientation of the MLP prim the same across your products, for example, with rotation 0,0,0. This makes it easier to transfer poses between products. However, with sculpties this isn't always feasible.]

Click the MLP prim so that it starts up for the first time. If you get a menu, fine; you've already done this. If nothing happens, click again -- an SL bug causes the first click to get lost.

== Install animations ==
Drag all the anims you'll use into the prim. (You can pull these out of poseballs you like. If the animations are no-copy, this will render the poseballs useless.)

Note: not all animations will work with MLP. See discussion here: [[MLPV2_Reference_Manual#TIP.21_Animations_Caveat]]

== Create and edit your .MENUITEMS.* file ==

Create a new notecard, named ".MENUITEMS.''mystuff''", where "''mystuff''" can be anything you want. MLPV2 can take any number of these, and bed sellers can make different pose sets for different customers.

[[File:Tutorial1.6.png|100px|thumb|left|Click for graphic view]]

Drop this notecard into the object. [You might want to do most of the editing first; objects with lots of things in inventory react slowly to changes, and you might have a lot of animations. As of Nov/2009, there's also an issue with editing notecards in object inventory. Unless you've heard the "all clear" on this, or know the workaround, it's best to edit in your avatar inventory.]

Create a menu:

MENU ''MyMenu'' | ALL | PINK | BLUE

[Tip! The standard practice is to list the pink ball first, then the blue -- you may do the opposite if you wish, but for what it's worth, that's the convention. This convention was established in 2006 with the release of MLP 1.1, and is practised in XPOSE! as well.]

This creates a menu whose button in the top menu will be labeled ''MyMenu''. '''ALL''' indicates that it will be accessible by everyone (alternatives here are '''GROUP''', only allowing people in the same group as the object, or '''OWNER''', only allowing the owner). After that, list each ball color for the poses in this menu. You can have up to six balls. If you have some solo poses, some couples poses, and some 3some poses, they have to be in different menus.

In this example, a pink and a blue poseball will be rezzed.

For each pose in this menu, add a line like this:

POSE ''pose1'' | ''anim1'' | ''anim2''

where
: ''pose1'' will be the button name for this pose.
: ''anim1'' is the name of the animation for the first poseball (which happens to be pink in our example)
: ''anim2'' is the name of the animation for the second poseball (which happens to be blue in our example)

Zero, one, or two spaces are allowed around the vertical bars. Avoid extra spaces.

For '''facial expressions''', you add a suffix to the animation names indicating the expression. Note that you don't change the actual name of the animation in the inventory, you just add the suffix in this configuration notecard. These are explained in [[MLPV2_Reference_Manual#Animations_.28Facial.29]] . For a simple example, appending "*" will give an astonished open-mouth expression.

The following can also be included in your menu:
STOP
SWAP
BACK
TOMENU ''MyOtherMenu''

: '''STOP''' makes a button labeled STOP that de-rezzes the poseballs and unsits everyone.
: '''SWAP''' makes a button labeled SWAP that exchanges the first two balls, by default. Starting with MLPV2.4, you can configure the swap arrangements for poses with multiple balls, [LINNK TBD].
: '''BACK''' makes a button labeled BACK that goes back to the previous menu. Every menu should have one of these!
: '''TOMENU''' makes a button labeled ''MyOtherMenu'', which goes to the ''MyOtherMenu'' menu (which you must create).

With MLPV2 (assuming you're using the .MENUITEMS that comes with MLPV2 rather than an old MLP configuration), any MENU that is '''not''' found in a previous '''TOMENU''' entry is added to an empty slot in the top menu. I'll talk more about this below, under [[MLPV2 Submenus]].

It's a good convention to end each menu with the following:
SWAP
STOP
BACK

For MLPV2 (again, assuming you're using the .MENUITEMS that comes with MLPV2 rather than an old MLP config), buttons are placed in the menu in the same order they appear in the config notecard. To set old MLP configs to using this new (sane) menu order, see here: [http://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#MENUORDER]

Repeat the above for each menu you want. Poses with different numbers of participants have to be in different menus, since the MENU line gives the number and colors of the balls.

For a menu with 3 or more poses, the POSE line would list that number of animations, separated by vertical bars ("|").

== Continuation menus ==
As we all know, you get at most 12 buttons in an SL menu. However, starting with MLPV2.1, you can have more than 12 buttons in a configured MENU. If there are more than 12, MLPV2.1 and later will automatically add a '''MORE-->''' button after the 11th item, leading to the remaining choices. (And also after the 22nd item, etc.)

If you wish MLPV2 to automatically a '''BACK''' button whenever it adds a '''MORE-->''' button, add the AUTOBACK directive to your .MENUITEMS config card. It doesn't matter where it is, but convention is to put it near the top. Put it alone on a line.

Note that a '''BACK''' button will not be added to the top, main menu (because there is no further back there to go back up to.) Nor will it add it to the last page of a series of sub-menu pages, or to a single-page sub-menu -- you must add the word BACK yourself manually to these if desired.

== Menu Reset ==
Save your changes. (If you're editing a copy in inventory, install it in the MLPV2 prim).

Click the MLPV2 object. If this is the first time since you installed the scripts, it will start up and read the configurations. If you get a menu, select '''OPTIONS -> ShutDown -> Menu Reset'''. This button causes it to re-read all .MENUITEMS* files, including yours.

Watch for warning messages. The most common one is due to an animation being missing or misspelled in the configuration. Fix any mistakes and do another Menu Reset. (A reset is '''not''' required for missing animations; just drop in the anim. If you don't have some of them yet, don't worry, this won't do any harm.

Click to get the menu. You should see the button for your new menu; click it. You should see the menu you configured. Click the first pose. You should see the right number and color balls appear. They may be in odd places.

Tip! Note that "MenuReset" will not re-read positions from the positions card. PosReset and Restart will.

== The default pose ==

The "default pose" is a set of poseball positions and orientations that is used for any new pose, since new poses don't have saved positions yet.

The default pose in the MLPV2 distribution assumes that the MLPV2 prim is essentially an unrotated box, flattened and stretched like a mattress cover. If your prim is rotated (as is likely if you're using a flattened cylinder lying on its side for the mattress, and MLPV2 is in the mattress), you will want to adjust the default pose so none of the balls are underground.

Go to main blue menu and select '''adj-default -> default'''.

Tip! If you don't have this choice, see here: [https://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#TIP.21_Default_Pose]

If the default pose looks fine (6 balls arranged in a hexagon, avs sitting facing each other), skip this step.

If the default pose looks wrong, adjust it following the instructions below, as for any pose you would add. You may have to be clever to get at balls that might end up under the floor or buried in your object.

When saving the default pose as described below, be sure to save it to the .POSITIONS notecard, rather than to your .POSITIONS.''mystuff'' notecard.

== The stand pose ==

MLPV2 uses the '''stand''' pose whenever STOP is used (or on any reset button in the Shutdown menu), just before unseating the avatars. This helps avoid them popping high into the sky, which happens when poseballs are buried inside the object.

I suggest using the default pose for the stand pose. Simply duplicate the "{default} ..." line in .POSITIONS and change "default" to "stand".

== Adjusting poses ==

'''MLPV2.3 and later'''

* Select '''OPTIONS -> Adjust Pos''' at any time. Whenever anyone is sitting on a poseball, it will be long and translucent to be easy to find and select. We call these "beams". Participants can hop on and off balls at any time during adjustment.
* Select the beams (right-click -> Edit) and adjust them as desired. When done with a pose, simply select the next pose. The current pose's position is automatically saved. Also, you can save the current pose's position at any time using '''OPTIONS -> Save Pos'''.
* '''To undo changes''' to the current pose, just select it again. Alternatively, just quit adjusting.
* '''To quit adjusting''', make sure the current pose is saved (if desired), and use either '''STOP''' or '''OPTIONS -> Adjust Pos'''. (Stop will also delete the balls and pop off any participants.)

'''MLPV2.2 and earlier'''

* Use the menu to select whichever pose you want to adjust. If it's a new pose, it will get the default pose. Have avatars sit on the poseballs. Use the menu '''OPTIONS -> Adjust Pos''' to make the poseballs visible and easy to select for editing. (They get long and translucent, so we call them "beams".)
* Select the beams and orient them as desired. When done, use the '''OPTIONS -> SavePos''' button.
* You may continue with the next pose, or re-adjust this one. When someone stands, their poseball will go back to the normal shape. Just click the '''AdjustPos''' button to make it a beam again.
* The '''AdjustPos''' button's only affect is to change the size and appearance of the poseballs. Feel free to adjust positions by selecting the clear tiny sat-upon poseballs and moving them, if you prefer.

== Saving pose positions to notecards ==

'''NOTE WELL''': The '''SavePos''' button saves the position in MLPV2 memory. A reset will cause it to forget. End users will probably want to save the changes to notecards, and sellers will need to.

This is why the .POSITIONS notecard should be ideally released to customers as MODIFY. Note as well, though, that if a notecard is placed in a no modify object, people will not be able to open the notecard at all, regardless of the perms on the notecard. This is a SL system limitation.

'''NOTE''': The ~swap script has to be in and running to save new positions! [for MLPV2.4 and later]

=== Saving pose positions, new object ===

Follow these instructions if this is a new object and you plan to sell it and possibly a line of related objects with MLPV2 poses. There is a simpler way for end users, below.

Create a .POSITIONS.''mystuff'' notecard, where ''mystuff'' matches your .MENUITEMS.''mystuff'' file name. (This isn't absolutely required, but makes life simple and I will assume that convention is followed in this tutorial.)

Use '''OPTIONS -> Dump Pos''' to dump all the positions. Using the chat history window, copy the text between the "-----" lines, which looks something like this:

[xx:xx] : {pose1} <... ''numbers'' ...>

Paste them into your notecard. It isn't necessary to delete the stuff to the left of {pose1}, but you can if you like things tidy.

Delete the {default} line. (Note: if you changed the default pose, save this line in '''.POSITIONS''' notecard.)
Delete the {stand} line. (Note: if you changed the stand pose, save this line in '''.POSITIONS''' notecard.)

Save, and use '''OPTIONS -> ShutDown -> PosReset'''. This causes the .POSITIONS.* files to be re-read, including yours.

That's about it; now you're ready to test your poses. Have fun!

Tip! For those using old MLP .MENUITEMS files: If the PosReset button is not offered, look for the RESTART option. Note that RESET will not re-read positions from the positions card. Only PosReset and RESTART will.

=== Saving a single position that you've updated ===

When you use '''OPTIONS -> SavePos''' for, say, ''pose1'', you'll see a line in chat looking like this:

MLPV2 (empty): {pose1} <... ''numbers'' ...>

There may be a timestamp. You can copy this line and replace it in the corresponding .POSITION.* file (e.g., the one already containing this pose's position).

=== Saving pose positions, simplified version for end users ===

If you're adjusting an object you bought that's already set up, and you've adjusted a lot of poses, this is the easiest way to save all your changes. Note, however, that if your product has pose pack modules and you might want to remove one to make room for other add-on poses, this might not be the best way.

Use '''OPTIONS -> Dump Pos''' to dump all the positions. Using the chat history window, copy the text between the "-----" lines, which looks something like this:

MLPV2 (empty): {pose1} <... ''numbers'' ...>

It may include a timestamp.

Paste them into the .POSITIONS notecard, replacing its previous contents. It is '''not''' necessary to delete the stuff before {pose1}, but you can if you like things tidy.

Delete all other .POSITIONS.* files in the MLPV2 prim's inventory.

If you later decide to delete a pose pack (a .MENUITEMS.* file) with poses you won't use, you can still do that. The positions for those poses will still be in the .POSITIONS notecard, and you can feel free to delete them manually.

== Deleting adj-default menu button ==

Once you're happy with the default pose positions, simply delete .MENUITEMS.zz-default from the MLPV2 prim's inventory. You can always put it back by dragging that file from the MLPV2 distribution.

== PROPS ==

Beginning with MLPV2.1, you can provide prop objects that MLP will rez for specific poses.

When you choose another pose or hit STOP, any rezzed prop disappears. If you delete the MLP object, any prop will disappear in a few minutes.

For any pose, you can have at most '''one''' prop object. If you need more than one prop to rez, you'll have to link them so that they can be treated by MLPV2 as one object.

1) The following lines are required in your MLP menu. Starting with MLPV2.1, they're already in the standard .MENUITEMS, in the OPTIONS menu. Add them if you're starting with an older version.

*LINKMSG DumpProps | 0,-4,1,DUMPPROPS // dump all prop configs
*LINKMSG SaveProp | 0,-4,1,SAVEPROP // save position/rotation for a prop

2) Find the prim prop object that you want MLP to rez, and rez it.

3) Add to this prop object the "~prop" script (you'll find this inside the supplied "~pillow" object). Take your prop object back into inventory and drop it into the MLP prim's inventory. Note: the prop object and everything in it will need to be copiable for next owner -- otherwise, it will only rez once for them!

4) Edit a .PROPS notecard or add a new one (named .PROPS.* where * is whatever you want, for a modular config.) Copy this example line and paste it into your .PROPS file.

| mypose | myobject | <1,1,1>/<0, 0, 0>

(Don't omit the vertical bar ("|") at the left.)

: *Replace "mypose" with the name of the pose that the object should rez for. 
: *Replace "myobject" with the name of the prop object. The object name cannot contain vertical bars. 

Save your work.

5) Use the MLP menu's PosReset or Restart button. When the MLP has restarted, select the pose that the prop goes with. The prop should appear. It might be underneath the MLP object, or some distance away, so look around -- it may be best to do this using a single prim MLP floating in the air, the first time.

6) Edit the prop, and use the editing arrows to move the prop to where you want it. Then, use the MLP menu "SaveProp" button.

To make the change permanent, select the text in the chat line (including the first vertical bar, and optionally any text before it) and replace the corresponding line in your .PROPS* file. Or, do all your props, saving their positions, and then use the DumpProps button. This works the same way as saving positions in .POSITIONS* files.

7) To get MLP to reread .PROPS* files, use PosReset (which resets positions as well as props), or Restart.

Keep in mind that props and positions are saved separately, so if you adjust a pose and its prop, you need to save both pose position and prop. (When using AdjustPos feature with MLPV2.4 or later, both pose and prop positions are saved when you select a new pose.)

'''Worn or Hand-held Props''': For props to be worn by the user, use the ~give script add-on found here [[MLPV2_Give_Item_Add-on]] and have people wear the items.

== SEQUENCES ==

Starting with MLPV2.3, you can create sequences of poses that run automatically once started.

It's a little complicated. You need to:

# set up menus (and often poses as well) for the sequences to use
# set up a control menu for the user to access and control the sequences
# program the sequences

=== 1. Set up the menus (and poses)===

In a .MENUITEMS.* notecard, create menus for the sequences to use. These menus:

(a) tell sequences how many balls to rez, and of what colour; 
(b) are used to set up poses for the sequences

If your sequence will use poses that are already in your menus, you're done here, nothing special to do.

If your sequence will use poses that you don't want to appear in any menu, you need to set up a "hidden menu". To do this, just make a menu the usual way, except use "HIDDEN" rather than "ALL", "GROUP", or "OWNER", like this:

MENU ROMNIGHT | HIDDEN | PINK | BLUE

Add your poses to this menu. Avoid extra spaces, especially between MENU and the menu name.

If you have sequences with different numbers of participants, you'll need to use additional menus with the appropriate number and color poseballs.

=== 2. Create a control menu for the sequence(s) ===

See the .MENUITEMS.example notecard in MLPV2 distribution as an example. This menu has two buttons to start sequences, and two buttons to stop and continue them, along with the usual navigation and swap buttons:

// example menu containing 2 sequences, and sequence controls
MENU Tours... | ALL
LINKMSG *Tour1* | 0,-4,-12001,SEQUENCE Tour1-seq
LINKMSG *Tour2* | 0,-4,-12001,SEQUENCE tour2-seq
LINKMSG PAUSE | 0,-4,-12001,PAUSE
LINKMSG RESUME | 0,-4,-12001,RESUME
LINKMSG NARRATION | 0,-4,-12001,NARRATION
SWAP
STOP
BACK

In the above, "*Tour1*" and "*Tour2*" are button labels -- that's what the user will see in the menu.
The "| 0,-4,-12001,SEQUENCE" part is pure magic, don't mess with that unless you're a magician.
"Tour1-seq" and "tour2-seq" are names of sequences in the .SEQUENCE* notecards.
Be careful: the names need to match exactly.

PAUSE causes the sequence to stop advancing.

RESUME causes the sequence to resume where it left off. Alternatively, if you didn't PAUSE, RESUME advances to the next step. This is handy for quickly testing a sequence with long wait times.

NARRATION allows the user to toggle off and on any WHISPER or SAY messages you might have programmed.

STOP stops the sequence and unrezzes the balls. After a STOP, RESUME and PAUSE have no effect.

'''NOTE WELL''' Avoid having two different buttons in an MLP/MLPV2 menu with the same button name. Only the first of the two will work. Subsequent ones (duplicates) will only cause the first button's effect. (It's OK to have the same button appear in multiple places, if you want them all to do the same thing. BUT:

LINKMSG PLAYALL | 0,-4,-12001,SEQUENCE MASSAGESCENE-seq

and

LINKMSG PLAYALL | 0,-4,-12001,SEQUENCE BJSCENE-seq

in the same menu will cause havok, as the menu will get confused about the duplicate button label of PLAYALL

=== 3. Programming a sequence ===

Create a notecard whose name starts with .SEQUENCES, followed by whatever you wish. In the MLPV2 distribution, this is .SEQUENCES.example. I'll go through an example sequence explaining what each line does.

Start the sequence with the sequence name specified in the control menu in .MENUITEMS file; in this case, "Tour1-seq". The name is arbitrary, it just has to match between the MENUITEMS notecard and the SEQUENCES notecard. For example:

SEQUENCE | Tour1-seq

Next, give it the name of a menu to use to model itself after for setting the number and color of balls. You can change the menu later in the sequence using more MENU lines.

MENU | Example

Note the vertical bar ("|"), unlike in a .MENUITEMS* card. Note as well that all you put is the name of the menu, and not the stuff that would follow it in a .MENUITEMS* card.

Now, program the steps in the sequence as poses followed by timed pauses, and possibly waiting for participants to hop on. (Note the pipe symbol | required, unlike in the .MENUITEMS card. Note as well that you only list the name of the pose -- not any associated animation.)

POSE | standing

The line above starts the "standing" pose.

'''Important''': The sequencer script currently (2011) won't give you any error messages if the Pose you reference doesn't actually exist. You're on your own here, Bernice, to get it right!

AVWAIT | 0 | Waiting for someone to sit on blue ball

The line above causes the sequence to wait for someone to sit on ~ball0. (To see which ball a ball is, pick the pose using the menu and right-click->Edit the ball. The number at the end of the name is the number to put between the "|" characters above.) The text after the final "|" is optional; it's what the object chats if it needs to wait.

You can specify any number of balls here; for example, you can use:

AVWAIT | 0 1 2 3 | Waiting for all participants!

'''Important''': Any looping sequence should have an AVWAIT in the loop. We don't want to disturb the neighborhood with an unused bed running endlessly through a sequence. In a future version, Lear might in fact make it an error to have a loop without an avwait.

WHISPER | 0 | /0 and /1 stand together

The line above causes the object to whisper the given line on channel 0 (the number between the "|" characters). "/0" through "/5" get substituted with the first name of the av on the corresponding ball. If nobody is on the ball, it uses "somebody".

WAIT | 10

The line above causes the sequence to wait for 10 seconds before proceeding.

POSE | pillow-sit | 0 | /0 and /1 sit with a comfy pillow

The line above selects a new pose and whispers the text on channel 0. Note that we omitted this optional chat in the POSE line above. As earlier, /0 and /1 are replaced with the participant's first names. Although you have two poses within the 10m rule, if the next pose in the sequence is 10m+ from the previous pose the balls won't go the distance.

WAIT | 10
POSE | sit2 | 0 | The pillow disappears
WAIT | 10

You should know by now what the lines above do.

The next line causes the whole sequence to repeat.

REPEAT

Alternatively, you can use a LABEL line anywhere in the sequence, and end the sequence with a GOTO line, as in the other example provided with the MLPV2 distribution:

LABEL | mylabel
AVWAIT | 0 1| //make sure we're not looping with no one using the balls, so check for people on both ball0 and ball1
...
...
GOTO | mylabel

Or, you can just have the sequence end by not adding any more steps (or, by starting a new sequence). If the sequence doesn't end with GOTO or REPEAT, it simply pauses at the end, leaving the participants in the last pose.

TIP! It doesn't matter whether you leave spaces or not around the | symbol; the sequences script will sort it out.

=== Avoiding the posename chat ===

By default, MLPV2 chats the pose name whenever it starts, either by menu or sequence. If you don't want it chatting pose names during sequence, add "| NOCHAT" to the end of the SEQUENCE line, like this:

SEQUENCE | Tour1-seq | NOCHAT

=== Hiding the poses from the menu ===

You can hide any MENU in the notecards from the user by using "HIDDEN" instead of "ALL", "GROUP", or "OWNER", as below:

MENU | seq1-poses | HIDDEN | PINK | BLUE

Put your sequenced poses in such a menu and they'll be invisible to the user. Just remember to set up the pose positions before hiding the menu they're in! Of course, you can use "Adjust pos", PAUSE in the sequence, and adjust.

=== TIP: Sequence naming rules ===

A sequence has
# a button name
# a sequence name

The button name and sequence name appear in the .MENUITEMS.''myStuff'' notecard:

LINKMSG Cuddle | 0,-4,-12001,SEQUENCE WarmUp

Cuddle is the button name, WarmUp is the sequence name.

The sequence name also appears in the .SEQUENCES.''myStuff'' notecard:

SEQUENCE | WarmUp

This is the fist line of the sequence. WarmUp is the sequence name. '''It must exactly match the sequence name''' (WarmUp) in the LINKMSG line in the .MENUITEMS.''myStuff'' notecard!

The button name does '''not''' need to match the sequence name. It's OK if it does.

== Configurable SWAPs ==

By default, the SWAP button swaps the first two balls, which is appropriate for couples poses. Therefore, there is no need to configure swaps for solo and couples poses.

For poses with 3 or more parties, you may want to configure what the swap button does. In this case, the button will cycle through a set of ball orders for the pose.

It's confusing, but stick with me and we'll muddle through. Here's the big picture. Each line in the .SWAPS.''myStuff'' notecard configures the swaps for one pose. (I would rather have done it per menu, but that just didn't work out, sorry!)

For a pose, we configure a set of ball permutations (arrangements, or orders). When the user hits SWAP, the balls will cycle through the given permutations. The first perumtation is always 0 1 2 3 4 5, meaning that ball0 is first, ball1 is second, ball2 is next, etc. (For a PINK | BLUE | RED menu, ball0 is pink, ball1 is blue, and ball2 is red.)

Since the "0 1 2 3 4 5" permutation is the default, it is NOT configured but is assumed. We only configure the 2nd, 3rd, and subsequent permutation (as many as we like).

Each line of the swap configuration notecard looks like this:

''posename'' | ''permu2'' : ''permu3''

where there can be any number of permutations, separated by a colon (":").

As mentioned above, the orders are given by a list of poseball position numbers.

Let's look at an example, with a 3-ball menu that uses PINK | BLUE | RED balls. Let's say we want the pink and red balls to swap, but leave the blue ball alone.

So, the permutations would be first the implicit 0 1 2 permutation, and then the swapped one, which in this case would be 2 1 0. It would be configured like this:

fmf-cuddle | 2 1 0

where fmf-cuddle is the pose name.

Confused yet? Yeah, me too. Now let's try a 3some pose where we want to rotate all three. For example, they're sitting around a round table, and we just want each one to move one position to the side.

The first permutation is always 0 1 2.

For the next permutation, we want 2 0 1. Balls 0 and 1 move right one place, and ball 2 slips back around to the first position.

For the next permutation, we want 1 2 0. Balls 2 and 0 move right one place, and ball 1 slips back around to the first position.

We'd configure it like this. Remember we omit the first permutation, since it's the default permutation and is implicit:

3-sitting | 2 0 1 : 1 2 0

When we hit SWAP the first time, we get the 2 0 1 permutation. Hit it again, we get 1 2 0. Hit it again and we go back to 0 1 2, the implicit default permutation. And so on, until the avatars get dizzy.

When I configure swaps, I actually write down the default permutation and keep it there to help me think, and then delete it when I create the pose configuration line.

Now let's try a two couples 4some for a PINK BLUE RED GREEN menu (female, male, female, male), where first we want the females to swap, and then we want the males to swap. I'll start out with the default permutation shown because it helps my feeble mind. Then I'll put the subsequent permutations below, in sequence.

0 1 2 3 - default
2 1 0 3 - females swapped

for the next one, let's swap the men but leave the women swapped:

2 3 0 1 - females swapped, males swapped

Are we done? Well, if we stopped here, the next click on SWAP would move all 4 balls. Instead, let's swap the men again, and then moving back to the default will only swap the women.

0 3 2 1 - males swapped

So, putting them all together:

0 1 2 3 - default
2 1 0 3 - females swapped
2 3 0 1 - females swapped, males swapped
0 3 2 1 - males swapped

I hope you're getting the picture by now. If your head hurts, well, mine does too. Just try doing some 6some swaps for real fun!

Here's the resulting configuration line:

Swingers | 2 1 0 3 : 2 3 0 1 : 0 3 2 1

NOTE: I did not test these configs, and I make mistakes. I'll try to find time to test. In the meantime, please feel free to try it out and '''please''' let me know of any mistakes.

Here are some common useful swaps, including the examples above. Delete the comments before using, and of course, replace the name I've given here with the actual pose name.

3somes

mfm-mfm | 2 0 1 : 1 2 0 // swap first & third of 3some
3-swap-other | 0 2 1 // swap 2nd pair of 3some
3-rotate-1 | 2 0 1 : 1 2 0 // rotate three, one direction
3-rotate-2 | 1 2 0 : 2 0 1 // rotate three, other direction
3-all | 0 1 2 : 0 2 1 : 2 0 1 : 2 1 0 : 1 2 0 : 1 0 2 // all permutations

4somes

Swingers | 2 1 0 3 : 2 3 0 1 : 0 3 2 1
fmmm-rotate-m | 0 2 3 1 : 0 3 1 2 // hold 0, rotate others
mfmm-rotate-m | 2 1 3 0 : 3 1 0 2 // hold 1, rotate others

5somes

fmfmf | 2 1 4 3 0 : 2 3 4 1 0 : 4 3 0 1 2 : 4 1 0 3 2 // alternately rotate women, swap men

== Tips ==

=== Expandability ===

For expandability, we recommend that each .MENUITEMS* file contain one "unanchored" menu at the top, with any submenus in the notecard hanging off of that unanchored one. This allows 10 independent modules and only memory limitations on the total number of menus. We also suggest dividing menus & positions into separate notecards making it easy for customers to delete the ones they won't use.

(An "unanchored" menu is one that doesn't have any TOMENU button leading to it.)

MLPV2 loads the notecards in the same order they appear in object inventory. The buttons for the unanchored menus in these notecards are added to the main menu in the same order. So, name your extensions so your notecards sort in the order you want these buttons to appear.

=== Main menu ===

By convention, the top, "main menu" often includes buttons such as OPTIONS, SHUTDOWN, etc, as well as buttons providing access to the sub-menus. By convention, this menu is defined in the .MENUITEMS notecard (note, no suffix).

Don't attempt to put actual poses in the menus found here. They won't work reliably, since these menus don't list the number and color of poseballs.

=== Help button ===

You may wish to add at this top level a HELP button.

The configuration would be something like this:

LINKMSG HELP | 1,-4,987789,-Help for XYZProduct##Here's your help notecard

Put this line at the end of the "TOMENU -" lines below MAIN MENU.

Then drop in the ~give script add-on found here [[MLPV2_Give_Item_Add-on]]

It might be better to name the help notecard something other than just "Help", so that your users can identify it more easily when it ends up in their inventories.

[[Category:MLPV2]]

MLPV2 Tutorial

2014-05-12T22:18:18Z

Chaz Longstaff: /* 2. Create a control menu for the sequence(s) */

{{Navbox/MLPV2}}

This tutorial is intended for "builders": people adding poses to furniture.

Folks who just want to know how to use their furniture should see [[MLPV2 Users Tutorial]].

== Setting up MLPV2 ==
These instructions look long, but it's easier than it looks. Here's the overview:
# get the scripts and notecards and drop them into a prim (CREATE YOUR OWN PRIM -- so folks know who made it!)
# put your anims in the same prim
# Create and edit one or more .MENUITEMS.* notecards (use whatever you want for "*"). Configure menus and add poses to the menus. Mostly the same as old MLP, with enhancements and no need to edit the main menu.)
# Reset and try the menu
# adust each pose (same way as old MLP)
# dump memory and save positions in notecard (nearly same way as old MLP; sellers may want to use modular .POSITIONS.* files)

These instructions are oriented for someone setting up a new object. However, those who bought one and are adjusting it or adding poses can simply skip the obvious steps that the maker would already have done.

== Get the scripts ==
The latest scripts are available at jPose Island, in the FREEBIES section. It is Adult land, so you will need to either have payment info on file or be adult certified.

MLPV2.3 is available on Marketplace, under Lear Cale as merchant.

Take a good look at the .readme file.

== Install scripts ==
Rez the MLPV2 and copy its contents into inventory and then into your furniture.

Delete the notecards ending in "examples", along with the ~pillow object and any example animations you don't plan to use.

Life is easiest if you use your object's root prim for MLPV2; instructions below for when it's not. For your first try, stick with root prim and keep life simple. (An easy way to add it to an existing bed is to just float it slightly above your mattress and then apply a totally clear texture, available in any freebie depot.) Below, we'll call this prim the "MLP prim".

[Tip: You'll thank yourself later in life if you try to keep the orientation of the MLP prim the same across your products, for example, with rotation 0,0,0. This makes it easier to transfer poses between products. However, with sculpties this isn't always feasible.]

Click the MLP prim so that it starts up for the first time. If you get a menu, fine; you've already done this. If nothing happens, click again -- an SL bug causes the first click to get lost.

== Install animations ==
Drag all the anims you'll use into the prim. (You can pull these out of poseballs you like. If the animations are no-copy, this will render the poseballs useless.)

Note: not all animations will work with MLP. See discussion here: [[MLPV2_Reference_Manual#TIP.21_Animations_Caveat]]

== Create and edit your .MENUITEMS.* file ==

Create a new notecard, named ".MENUITEMS.''mystuff''", where "''mystuff''" can be anything you want. MLPV2 can take any number of these, and bed sellers can make different pose sets for different customers.

[[File:Tutorial1.6.png|100px|thumb|left|Click for graphic view]]

Drop this notecard into the object. [You might want to do most of the editing first; objects with lots of things in inventory react slowly to changes, and you might have a lot of animations. As of Nov/2009, there's also an issue with editing notecards in object inventory. Unless you've heard the "all clear" on this, or know the workaround, it's best to edit in your avatar inventory.]

Create a menu:

MENU ''MyMenu'' | ALL | PINK | BLUE

[Tip! The standard practice is to list the pink ball first, then the blue -- you may do the opposite if you wish, but for what it's worth, that's the convention. This convention was established in 2006 with the release of MLP 1.1, and is practised in XPOSE! as well.]

This creates a menu whose button in the top menu will be labeled ''MyMenu''. '''ALL''' indicates that it will be accessible by everyone (alternatives here are '''GROUP''', only allowing people in the same group as the object, or '''OWNER''', only allowing the owner). After that, list each ball color for the poses in this menu. You can have up to six balls. If you have some solo poses, some couples poses, and some 3some poses, they have to be in different menus.

In this example, a pink and a blue poseball will be rezzed.

For each pose in this menu, add a line like this:

POSE ''pose1'' | ''anim1'' | ''anim2''

where
: ''pose1'' will be the button name for this pose.
: ''anim1'' is the name of the animation for the first poseball (which happens to be pink in our example)
: ''anim2'' is the name of the animation for the second poseball (which happens to be blue in our example)

Zero, one, or two spaces are allowed around the vertical bars. Avoid extra spaces.

For '''facial expressions''', you add a suffix to the animation names indicating the expression. Note that you don't change the actual name of the animation in the inventory, you just add the suffix in this configuration notecard. These are explained in [[MLPV2_Reference_Manual#Animations_.28Facial.29]] . For a simple example, appending "*" will give an astonished open-mouth expression.

The following can also be included in your menu:
STOP
SWAP
BACK
TOMENU ''MyOtherMenu''

: '''STOP''' makes a button labeled STOP that de-rezzes the poseballs and unsits everyone.
: '''SWAP''' makes a button labeled SWAP that exchanges the first two balls, by default. Starting with MLPV2.4, you can configure the swap arrangements for poses with multiple balls, [LINNK TBD].
: '''BACK''' makes a button labeled BACK that goes back to the previous menu. Every menu should have one of these!
: '''TOMENU''' makes a button labeled ''MyOtherMenu'', which goes to the ''MyOtherMenu'' menu (which you must create).

With MLPV2 (assuming you're using the .MENUITEMS that comes with MLPV2 rather than an old MLP configuration), any MENU that is '''not''' found in a previous '''TOMENU''' entry is added to an empty slot in the top menu. I'll talk more about this below, under [[MLPV2 Submenus]].

It's a good convention to end each menu with the following:
SWAP
STOP
BACK

For MLPV2 (again, assuming you're using the .MENUITEMS that comes with MLPV2 rather than an old MLP config), buttons are placed in the menu in the same order they appear in the config notecard. To set old MLP configs to using this new (sane) menu order, see here: [http://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#MENUORDER]

Repeat the above for each menu you want. Poses with different numbers of participants have to be in different menus, since the MENU line gives the number and colors of the balls.

For a menu with 3 or more poses, the POSE line would list that number of animations, separated by vertical bars ("|").

== Continuation menus ==
As we all know, you get at most 12 buttons in an SL menu. However, starting with MLPV2.1, you can have more than 12 buttons in a configured MENU. If there are more than 12, MLPV2.1 and later will automatically add a '''MORE-->''' button after the 11th item, leading to the remaining choices. (And also after the 22nd item, etc.)

If you wish MLPV2 to automatically a '''BACK''' button whenever it adds a '''MORE-->''' button, add the AUTOBACK directive to your .MENUITEMS config card. It doesn't matter where it is, but convention is to put it near the top. Put it alone on a line.

Note that a '''BACK''' button will not be added to the top, main menu (because there is no further back there to go back up to.) Nor will it add it to the last page of a series of sub-menu pages, or to a single-page sub-menu -- you must add the word BACK yourself manually to these if desired.

== Menu Reset ==
Save your changes. (If you're editing a copy in inventory, install it in the MLPV2 prim).

Click the MLPV2 object. If this is the first time since you installed the scripts, it will start up and read the configurations. If you get a menu, select '''OPTIONS -> ShutDown -> Menu Reset'''. This button causes it to re-read all .MENUITEMS* files, including yours.

Watch for warning messages. The most common one is due to an animation being missing or misspelled in the configuration. Fix any mistakes and do another Menu Reset. (A reset is '''not''' required for missing animations; just drop in the anim. If you don't have some of them yet, don't worry, this won't do any harm.

Click to get the menu. You should see the button for your new menu; click it. You should see the menu you configured. Click the first pose. You should see the right number and color balls appear. They may be in odd places.

Tip! Note that "MenuReset" will not re-read positions from the positions card. PosReset and Restart will.

== The default pose ==

The "default pose" is a set of poseball positions and orientations that is used for any new pose, since new poses don't have saved positions yet.

The default pose in the MLPV2 distribution assumes that the MLPV2 prim is essentially an unrotated box, flattened and stretched like a mattress cover. If your prim is rotated (as is likely if you're using a flattened cylinder lying on its side for the mattress, and MLPV2 is in the mattress), you will want to adjust the default pose so none of the balls are underground.

Go to main blue menu and select '''adj-default -> default'''.

Tip! If you don't have this choice, see here: [https://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#TIP.21_Default_Pose]

If the default pose looks fine (6 balls arranged in a hexagon, avs sitting facing each other), skip this step.

If the default pose looks wrong, adjust it following the instructions below, as for any pose you would add. You may have to be clever to get at balls that might end up under the floor or buried in your object.

When saving the default pose as described below, be sure to save it to the .POSITIONS notecard, rather than to your .POSITIONS.''mystuff'' notecard.

== The stand pose ==

MLPV2 uses the '''stand''' pose whenever STOP is used (or on any reset button in the Shutdown menu), just before unseating the avatars. This helps avoid them popping high into the sky, which happens when poseballs are buried inside the object.

I suggest using the default pose for the stand pose. Simply duplicate the "{default} ..." line in .POSITIONS and change "default" to "stand".

== Adjusting poses ==

'''MLPV2.3 and later'''

* Select '''OPTIONS -> Adjust Pos''' at any time. Whenever anyone is sitting on a poseball, it will be long and translucent to be easy to find and select. We call these "beams". Participants can hop on and off balls at any time during adjustment.
* Select the beams (right-click -> Edit) and adjust them as desired. When done with a pose, simply select the next pose. The current pose's position is automatically saved. Also, you can save the current pose's position at any time using '''OPTIONS -> Save Pos'''.
* '''To undo changes''' to the current pose, just select it again. Alternatively, just quit adjusting.
* '''To quit adjusting''', make sure the current pose is saved (if desired), and use either '''STOP''' or '''OPTIONS -> Adjust Pos'''. (Stop will also delete the balls and pop off any participants.)

'''MLPV2.2 and earlier'''

* Use the menu to select whichever pose you want to adjust. If it's a new pose, it will get the default pose. Have avatars sit on the poseballs. Use the menu '''OPTIONS -> Adjust Pos''' to make the poseballs visible and easy to select for editing. (They get long and translucent, so we call them "beams".)
* Select the beams and orient them as desired. When done, use the '''OPTIONS -> SavePos''' button.
* You may continue with the next pose, or re-adjust this one. When someone stands, their poseball will go back to the normal shape. Just click the '''AdjustPos''' button to make it a beam again.
* The '''AdjustPos''' button's only affect is to change the size and appearance of the poseballs. Feel free to adjust positions by selecting the clear tiny sat-upon poseballs and moving them, if you prefer.

== Saving pose positions to notecards ==

'''NOTE WELL''': The '''SavePos''' button saves the position in MLPV2 memory. A reset will cause it to forget. End users will probably want to save the changes to notecards, and sellers will need to.

This is why the .POSITIONS notecard should be ideally released to customers as MODIFY. Note as well, though, that if a notecard is placed in a no modify object, people will not be able to open the notecard at all, regardless of the perms on the notecard. This is a SL system limitation.

'''NOTE''': The ~swap script has to be in and running to save new positions! [for MLPV2.4 and later]

=== Saving pose positions, new object ===

Follow these instructions if this is a new object and you plan to sell it and possibly a line of related objects with MLPV2 poses. There is a simpler way for end users, below.

Create a .POSITIONS.''mystuff'' notecard, where ''mystuff'' matches your .MENUITEMS.''mystuff'' file name. (This isn't absolutely required, but makes life simple and I will assume that convention is followed in this tutorial.)

Use '''OPTIONS -> Dump Pos''' to dump all the positions. Using the chat history window, copy the text between the "-----" lines, which looks something like this:

[xx:xx] : {pose1} <... ''numbers'' ...>

Paste them into your notecard. It isn't necessary to delete the stuff to the left of {pose1}, but you can if you like things tidy.

Delete the {default} line. (Note: if you changed the default pose, save this line in '''.POSITIONS''' notecard.)
Delete the {stand} line. (Note: if you changed the stand pose, save this line in '''.POSITIONS''' notecard.)

Save, and use '''OPTIONS -> ShutDown -> PosReset'''. This causes the .POSITIONS.* files to be re-read, including yours.

That's about it; now you're ready to test your poses. Have fun!

Tip! For those using old MLP .MENUITEMS files: If the PosReset button is not offered, look for the RESTART option. Note that RESET will not re-read positions from the positions card. Only PosReset and RESTART will.

=== Saving a single position that you've updated ===

When you use '''OPTIONS -> SavePos''' for, say, ''pose1'', you'll see a line in chat looking like this:

MLPV2 (empty): {pose1} <... ''numbers'' ...>

There may be a timestamp. You can copy this line and replace it in the corresponding .POSITION.* file (e.g., the one already containing this pose's position).

=== Saving pose positions, simplified version for end users ===

If you're adjusting an object you bought that's already set up, and you've adjusted a lot of poses, this is the easiest way to save all your changes. Note, however, that if your product has pose pack modules and you might want to remove one to make room for other add-on poses, this might not be the best way.

Use '''OPTIONS -> Dump Pos''' to dump all the positions. Using the chat history window, copy the text between the "-----" lines, which looks something like this:

MLPV2 (empty): {pose1} <... ''numbers'' ...>

It may include a timestamp.

Paste them into the .POSITIONS notecard, replacing its previous contents. It is '''not''' necessary to delete the stuff before {pose1}, but you can if you like things tidy.

Delete all other .POSITIONS.* files in the MLPV2 prim's inventory.

If you later decide to delete a pose pack (a .MENUITEMS.* file) with poses you won't use, you can still do that. The positions for those poses will still be in the .POSITIONS notecard, and you can feel free to delete them manually.

== Deleting adj-default menu button ==

Once you're happy with the default pose positions, simply delete .MENUITEMS.zz-default from the MLPV2 prim's inventory. You can always put it back by dragging that file from the MLPV2 distribution.

== PROPS ==

Beginning with MLPV2.1, you can provide prop objects that MLP will rez for specific poses.

When you choose another pose or hit STOP, any rezzed prop disappears. If you delete the MLP object, any prop will disappear in a few minutes.

For any pose, you can have at most '''one''' prop object. If you need more than one prop to rez, you'll have to link them so that they can be treated by MLPV2 as one object.

1) The following lines are required in your MLP menu. Starting with MLPV2.1, they're already in the standard .MENUITEMS, in the OPTIONS menu. Add them if you're starting with an older version.

*LINKMSG DumpProps | 0,-4,1,DUMPPROPS // dump all prop configs
*LINKMSG SaveProp | 0,-4,1,SAVEPROP // save position/rotation for a prop

2) Find the prim prop object that you want MLP to rez, and rez it.

3) Add to this prop object the "~prop" script (you'll find this inside the supplied "~pillow" object). Take your prop object back into inventory and drop it into the MLP prim's inventory. Note: the prop object and everything in it will need to be copiable for next owner -- otherwise, it will only rez once for them!

4) Edit a .PROPS notecard or add a new one (named .PROPS.* where * is whatever you want, for a modular config.) Copy this example line and paste it into your .PROPS file.

| mypose | myobject | <1,1,1>/<0, 0, 0>

(Don't omit the vertical bar ("|") at the left.)

: *Replace "mypose" with the name of the pose that the object should rez for. 
: *Replace "myobject" with the name of the prop object. The object name cannot contain vertical bars. 

Save your work.

5) Use the MLP menu's PosReset or Restart button. When the MLP has restarted, select the pose that the prop goes with. The prop should appear. It might be underneath the MLP object, or some distance away, so look around -- it may be best to do this using a single prim MLP floating in the air, the first time.

6) Edit the prop, and use the editing arrows to move the prop to where you want it. Then, use the MLP menu "SaveProp" button.

To make the change permanent, select the text in the chat line (including the first vertical bar, and optionally any text before it) and replace the corresponding line in your .PROPS* file. Or, do all your props, saving their positions, and then use the DumpProps button. This works the same way as saving positions in .POSITIONS* files.

7) To get MLP to reread .PROPS* files, use PosReset (which resets positions as well as props), or Restart.

Keep in mind that props and positions are saved separately, so if you adjust a pose and its prop, you need to save both pose position and prop. (When using AdjustPos feature with MLPV2.4 or later, both pose and prop positions are saved when you select a new pose.)

'''Worn or Hand-held Props''': For props to be worn by the user, use the ~give script add-on found here [[MLPV2_Give_Item_Add-on]] and have people wear the items.

== SEQUENCES ==

Starting with MLPV2.3, you can create sequences of poses that run automatically once started.

It's a little complicated. You need to:

# set up menus (and often poses as well) for the sequences to use
# set up a control menu for the user to access and control the sequences
# program the sequences

=== 1. Set up the menus (and poses)===

In a .MENUITEMS.* notecard, create menus for the sequences to use. These menus:

(a) tell sequences how many balls to rez, and of what colour; 
(b) are used to set up poses for the sequences

If your sequence will use poses that are already in your menus, you're done here, nothing special to do.

If your sequence will use poses that you don't want to appear in any menu, you need to set up a "hidden menu". To do this, just make a menu the usual way, except use "HIDDEN" rather than "ALL", "GROUP", or "OWNER", like this:

MENU ROMNIGHT | HIDDEN | PINK | BLUE

Add your poses to this menu. Avoid extra spaces, especially between MENU and the menu name.

If you have sequences with different numbers of participants, you'll need to use additional menus with the appropriate number and color poseballs.

=== 2. Create a control menu for the sequence(s) ===

See the .MENUITEMS.example notecard in MLPV2 distribution as an example. This menu has two buttons to start sequences, and two buttons to stop and continue them, along with the usual navigation and swap buttons:

// example menu containing 2 sequences, and sequence controls
MENU Tours... | ALL
LINKMSG *Tour1* | 0,-4,-12001,SEQUENCE Tour1-seq
LINKMSG *Tour2* | 0,-4,-12001,SEQUENCE tour2-seq
LINKMSG PAUSE | 0,-4,-12001,PAUSE
LINKMSG RESUME | 0,-4,-12001,RESUME
LINKMSG NARRATION | 0,-4,-12001,NARRATION
SWAP
STOP
BACK

In the above, "*Tour1*" and "*Tour2*" are button labels -- that's what the user will see in the menu.
The "| 0,-4,-12001,SEQUENCE" part is pure magic, don't mess with that unless you're a magician.
"Tour1-seq" and "tour2-seq" are names of sequences in the .SEQUENCE* notecards.
Be careful: the names need to match exactly.

PAUSE causes the sequence to stop advancing.

RESUME causes the sequence to resume where it left off. Alternatively, if you didn't PAUSE, RESUME advances to the next step. This is handy for quickly testing a sequence with long wait times.

NARRATION allows the user to toggle off and on any WHISPER or SAY messages you might have programmed.

STOP stops the sequence and unrezzes the balls. After a STOP, RESUME and PAUSE have no effect.

'''NOTE WELL''' Avoid having two different buttons in an MLP/MLPV2 menu with the same button name. Only the first of the two will work. Subsequent ones (duplicates) will only cause the first button's effect. (It's OK to have the same button appear in multiple places, if you want them all to do the same thing. BUT:

LINKMSG PLAYALL | 0,-4,-12001,SEQUENCE MASSAGESCENE-seq

and

LINKMSG PLAYALL | 0,-4,-12001,SEQUENCE BJSCENE-seq

in the same menu will cause havok, as the menu will get confused about the duplicate button label of PLAYALL

=== 3. Programming a sequence ===

Create a notecard whose name starts with .SEQUENCES, followed by whatever you wish. In the MLPV2 distribution, this is .SEQUENCES.example. I'll go through an example sequence explaining what each line does.

Start the sequence with the sequence name specified in the control menu in .MENUITEMS file; in this case, "Tour1-seq". The name is arbitrary, it just has to match between the MENUITEMS notecard and the SEQUENCES notecard. For example:

SEQUENCE | Tour1-seq

Next, tell what menu you'll be using for subsequent poses. Currently, this only sets the number and color of balls, but that might change in the future. You can change the menu later in the sequence using more MENU lines.

MENU | Example

The line above tells us that the following poses are poses in the "Example" menu. Note the vertical bar ("|"), unlike in a .MENUITEMS* card. Note as well that all you put is the name of the menu, and not the stuff that would follow it in a .MENUITEMS* card.)

Now, program the steps in the sequence as poses followed by timed pauses, and possibly waiting for participants to hop on. (Note the pipe symbol | required, unlike in the .MENUITEMS card. Note as well that you only list the name of the pose -- not any associated animation.)

POSE | standing

The line above starts the "standing" pose.

'''Important''': The sequencer script currently (2011) won't give you any error messages if the Pose you reference doesn't actually exist. You're on your own here, Bernice, to get it right!

AVWAIT | 0 | Waiting for someone to sit on blue ball

The line above causes the sequence to wait for someone to sit on ~ball0. (To see which ball a ball is, pick the pose using the menu and right-click->Edit the ball. The number at the end of the name is the number to put between the "|" characters above.) The text after the final "|" is optional; it's what the object chats if it needs to wait.

You can specify any number of balls here; for example, you can use:

AVWAIT | 0 1 2 3 | Waiting for all participants!

'''Important''': Any looping sequence should have an AVWAIT in the loop. We don't want to disturb the neighborhood with an unused bed running endlessly through a sequence. In a future version, I might make it an error to have a loop without an avwait.

WHISPER | 0 | /0 and /1 stand together

The line above causes the object to whisper the given line on channel 0 (the number between the "|" characters). "/0" through "/5" get substituted with the first name of the av on the corresponding ball. If nobody is on the ball, it uses "somebody".

WAIT | 10

The line above causes the sequence to wait for 10 seconds before proceeding.

POSE | pillow-sit | 0 | /0 and /1 sit with a comfy pillow

The line above selects a new pose and whispers the text on channel 0. Note that we omitted this optional chat in the POSE line above. As earlier, /0 and /1 are replaced with the participant's first names. Although you have two poses within the 10m rule, if the next pose in the sequence is 10m+ from the previous pose the balls won't go the distance.

WAIT | 10
POSE | sit2 | 0 | The pillow disappears
WAIT | 10

You should know by now what the lines above do.

The next line causes the whole sequence to repeat.

REPEAT

Alternatively, you can use a LABEL line anywhere in the sequence, and end the sequence with a GOTO line, as in the other example provided with the MLPV2 distribution:

LABEL | mylabel
AVWAIT | 0 1| //make sure we're not looping with no one using the balls, so check for people on both ball0 and ball1
...
...
GOTO | mylabel

Or, you can just have the sequence end by not adding any more steps (or, by starting a new sequence). If the sequence doesn't end with GOTO or REPEAT, it simply pauses at the end, leaving the participants in the last pose.

TIP! It doesn't matter whether you leave spaces or not around the | symbol; the sequences script will sort it out.

=== Avoiding the posename chat ===

By default, MLPV2 chats the pose name whenever it starts, either by menu or sequence. If you don't want it chatting pose names during sequence, add "| NOCHAT" to the end of the SEQUENCE line, like this:

SEQUENCE | Tour1-seq | NOCHAT

=== Hiding the poses from the menu ===

You can hide any MENU in the notecards from the user by using "HIDDEN" instead of "ALL", "GROUP", or "OWNER", as below:

MENU | seq1-poses | HIDDEN | PINK | BLUE

Put your sequenced poses in such a menu and they'll be invisible to the user. Just remember to set up the pose positions before hiding the menu they're in! Of course, you can use "Adjust pos", PAUSE in the sequence, and adjust.

=== TIP: Sequence naming rules ===

A sequence has
# a button name
# a sequence name

The button name and sequence name appear in the .MENUITEMS.''myStuff'' notecard:

LINKMSG Cuddle | 0,-4,-12001,SEQUENCE WarmUp

Cuddle is the button name, WarmUp is the sequence name.

The sequence name also appears in the .SEQUENCES.''myStuff'' notecard:

SEQUENCE | WarmUp

This is the fist line of the sequence. WarmUp is the sequence name. '''It must exactly match the sequence name''' (WarmUp) in the LINKMSG line in the .MENUITEMS.''myStuff'' notecard!

The button name does '''not''' need to match the sequence name. It's OK if it does.

== Configurable SWAPs ==

By default, the SWAP button swaps the first two balls, which is appropriate for couples poses. Therefore, there is no need to configure swaps for solo and couples poses.

For poses with 3 or more parties, you may want to configure what the swap button does. In this case, the button will cycle through a set of ball orders for the pose.

It's confusing, but stick with me and we'll muddle through. Here's the big picture. Each line in the .SWAPS.''myStuff'' notecard configures the swaps for one pose. (I would rather have done it per menu, but that just didn't work out, sorry!)

For a pose, we configure a set of ball permutations (arrangements, or orders). When the user hits SWAP, the balls will cycle through the given permutations. The first perumtation is always 0 1 2 3 4 5, meaning that ball0 is first, ball1 is second, ball2 is next, etc. (For a PINK | BLUE | RED menu, ball0 is pink, ball1 is blue, and ball2 is red.)

Since the "0 1 2 3 4 5" permutation is the default, it is NOT configured but is assumed. We only configure the 2nd, 3rd, and subsequent permutation (as many as we like).

Each line of the swap configuration notecard looks like this:

''posename'' | ''permu2'' : ''permu3''

where there can be any number of permutations, separated by a colon (":").

As mentioned above, the orders are given by a list of poseball position numbers.

Let's look at an example, with a 3-ball menu that uses PINK | BLUE | RED balls. Let's say we want the pink and red balls to swap, but leave the blue ball alone.

So, the permutations would be first the implicit 0 1 2 permutation, and then the swapped one, which in this case would be 2 1 0. It would be configured like this:

fmf-cuddle | 2 1 0

where fmf-cuddle is the pose name.

Confused yet? Yeah, me too. Now let's try a 3some pose where we want to rotate all three. For example, they're sitting around a round table, and we just want each one to move one position to the side.

The first permutation is always 0 1 2.

For the next permutation, we want 2 0 1. Balls 0 and 1 move right one place, and ball 2 slips back around to the first position.

For the next permutation, we want 1 2 0. Balls 2 and 0 move right one place, and ball 1 slips back around to the first position.

We'd configure it like this. Remember we omit the first permutation, since it's the default permutation and is implicit:

3-sitting | 2 0 1 : 1 2 0

When we hit SWAP the first time, we get the 2 0 1 permutation. Hit it again, we get 1 2 0. Hit it again and we go back to 0 1 2, the implicit default permutation. And so on, until the avatars get dizzy.

When I configure swaps, I actually write down the default permutation and keep it there to help me think, and then delete it when I create the pose configuration line.

Now let's try a two couples 4some for a PINK BLUE RED GREEN menu (female, male, female, male), where first we want the females to swap, and then we want the males to swap. I'll start out with the default permutation shown because it helps my feeble mind. Then I'll put the subsequent permutations below, in sequence.

0 1 2 3 - default
2 1 0 3 - females swapped

for the next one, let's swap the men but leave the women swapped:

2 3 0 1 - females swapped, males swapped

Are we done? Well, if we stopped here, the next click on SWAP would move all 4 balls. Instead, let's swap the men again, and then moving back to the default will only swap the women.

0 3 2 1 - males swapped

So, putting them all together:

0 1 2 3 - default
2 1 0 3 - females swapped
2 3 0 1 - females swapped, males swapped
0 3 2 1 - males swapped

I hope you're getting the picture by now. If your head hurts, well, mine does too. Just try doing some 6some swaps for real fun!

Here's the resulting configuration line:

Swingers | 2 1 0 3 : 2 3 0 1 : 0 3 2 1

NOTE: I did not test these configs, and I make mistakes. I'll try to find time to test. In the meantime, please feel free to try it out and '''please''' let me know of any mistakes.

Here are some common useful swaps, including the examples above. Delete the comments before using, and of course, replace the name I've given here with the actual pose name.

3somes

mfm-mfm | 2 0 1 : 1 2 0 // swap first & third of 3some
3-swap-other | 0 2 1 // swap 2nd pair of 3some
3-rotate-1 | 2 0 1 : 1 2 0 // rotate three, one direction
3-rotate-2 | 1 2 0 : 2 0 1 // rotate three, other direction
3-all | 0 1 2 : 0 2 1 : 2 0 1 : 2 1 0 : 1 2 0 : 1 0 2 // all permutations

4somes

Swingers | 2 1 0 3 : 2 3 0 1 : 0 3 2 1
fmmm-rotate-m | 0 2 3 1 : 0 3 1 2 // hold 0, rotate others
mfmm-rotate-m | 2 1 3 0 : 3 1 0 2 // hold 1, rotate others

5somes

fmfmf | 2 1 4 3 0 : 2 3 4 1 0 : 4 3 0 1 2 : 4 1 0 3 2 // alternately rotate women, swap men

== Tips ==

=== Expandability ===

For expandability, we recommend that each .MENUITEMS* file contain one "unanchored" menu at the top, with any submenus in the notecard hanging off of that unanchored one. This allows 10 independent modules and only memory limitations on the total number of menus. We also suggest dividing menus & positions into separate notecards making it easy for customers to delete the ones they won't use.

(An "unanchored" menu is one that doesn't have any TOMENU button leading to it.)

MLPV2 loads the notecards in the same order they appear in object inventory. The buttons for the unanchored menus in these notecards are added to the main menu in the same order. So, name your extensions so your notecards sort in the order you want these buttons to appear.

=== Main menu ===

By convention, the top, "main menu" often includes buttons such as OPTIONS, SHUTDOWN, etc, as well as buttons providing access to the sub-menus. By convention, this menu is defined in the .MENUITEMS notecard (note, no suffix).

Don't attempt to put actual poses in the menus found here. They won't work reliably, since these menus don't list the number and color of poseballs.

=== Help button ===

You may wish to add at this top level a HELP button.

The configuration would be something like this:

LINKMSG HELP | 1,-4,987789,-Help for XYZProduct##Here's your help notecard

Put this line at the end of the "TOMENU -" lines below MAIN MENU.

Then drop in the ~give script add-on found here [[MLPV2_Give_Item_Add-on]]

It might be better to name the help notecard something other than just "Help", so that your users can identify it more easily when it ends up in their inventories.

[[Category:MLPV2]]

MLPV2 Addons

2014-03-08T01:30:02Z

Chaz Longstaff:

{{Navbox/MLPV2}}

*[[MLPV2 Ball Script with more flexible parameters]]
*[[Check Animations Permissions Tool|MLPV2 Check Animations Permissions Tool ]]
*[[Cleaner MLP Say|MLPV2 "Cleaner" MLP Say]]
*[[MLPV2 Color Changer Add-on]]
*[[MLPV2 Give Item Add-on]] (Item or Items, one at a time, NOT in folder)
*[[MLPV2 Give Folder Add-on]] (Item or Items, all at once, in folder)
*[[MLPV2 Give Items in Folder to a Specific Person]]
* [[MLPV2_LockGuard_plugin]]: Add LockGuard support to MLP2
*[[MLPV2 Menu Maker Helper]]
*[[MLPV2_Props_Texture_Changer_Add-on]]
*[[Reset_from_Child_Plugin|MLPV2 Reset_from_Child_Plugin ]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Master | MLPV2 Rez Prop Independent of Pose (Master rezzer script that goes in with other MLP scripts)]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Item|MLPV2 Rez Prop Independent of Pose (Child script that goes into each item)]]
*[[MLPV2_RLV_Plugin]]
*[[MLPV2_RLV_Capture_Plugin]]
*[[MLPV2_Ambiant_Sound_Add-on|MLPV2_Sounds as background music]]
*[[MLPV2_Sound_Effects]] (Triggered by poses)
*[[MLPV2_Texture_Changer_Add-on]]

===Patches===
* [[MLPV2_Balls_Patch]]: Use different balls for ~ball0...5

===Tools===
*[[Script to report on who made which animations in a prim]]

[[Category:MLPV2]]

MLPV2 Sound Effects

2014-03-08T01:26:05Z

Chaz Longstaff: Created page with "MLP Sound Effects by Chaz Longstaff This MLP sound tool will trigger sounds when poses of your choosing are played. You control if the sounds loop or not, how long they play, et…"

MLP Sound Effects by Chaz Longstaff

This MLP sound tool will trigger sounds when poses of your choosing are played. You control if the sounds loop or not, how long they play, etc. The script also allows users to turn all sounds off or back on via a button.

You need two things, both provided on this page: A script and a notecard. Make the script (call it "~sounds" or really anything you want) and the notecard (call it .SOUNDS or .SOUNDS.whatever) and drop into your MLPV2 product. Full usage instructions are within the notecard.

PIECE 1: SCRIPT

<lsl>
//MLP Sounds
//v. 1.1 by Chaz Longstaff 2014-03-7
//This script also requires a notecard named .SOUNDS or .SOUNDS.whatever
//lines inside card should read like: posename,sound, delaybeforeinitialstart, howoftentorepeat, volume, #repeatsbeforeanotherdelay, delayduringplay. See sample notecard provided with full usage instructions

list DelayDuringPlay = [""];
list DelayStarts = [""];
list MaxPlays = [""];
list PoseNames = [""];
list Sounds = [""];
list SoundTimes = [""];
list SoundVols = [""];

integer ListLength;
string mysound;
list mysoundlist;
float mystartdelay;
float myplaydelay;
integer mymax;
float mytime;
float myvol;
string playstatus = "On";
integer soundtotal;
integer soundcount;
integer TimesPlayed;
integer x;

float Interval;
integer Debug;

integer PoseCfgCount;
string Pose;

config_init()
{
PoseCfgCount = 0;
DelayStarts = [];
DelayDuringPlay = [];
MaxPlays = [];
PoseNames = [];
Sounds = [];
SoundTimes = [];
SoundVols = [];
Debug = 0;
Interval = 15.;

}

config_parse(string str, string cardName, integer lineNum)
{
str = llStringTrim(str, STRING_TRIM_HEAD); // delete leading spaces

// lines beginning with slash are comments -- ignore them
if ( (llGetSubString(str,0,0) == "/") || (str == "") ) {
return;
}

list ldata = llParseStringKeepNulls(str, [","], [""]);
PoseCfgCount += 1;
string pose = llStringTrim(llList2String(ldata,0), STRING_TRIM);
string mysoundstr = llStringTrim(llList2String(ldata,1), STRING_TRIM);
string mystartdelaystr = llStringTrim(llList2String(ldata,2), STRING_TRIM);
string mytimestr = llStringTrim(llList2String(ldata,3), STRING_TRIM);
string myvolstr = llStringTrim(llList2String(ldata,4), STRING_TRIM);
string mymaxstr = llStringTrim(llList2String(ldata,5), STRING_TRIM);
string myplaydelaystr = llStringTrim(llList2String(ldata,6), STRING_TRIM);

// posename, sound, delay, howoftentorepeat, volume, #repeatsbeforeanotherdelay

addConfig(pose, mysoundstr, mystartdelaystr, mytimestr, myvolstr, mymaxstr, myplaydelaystr);
}

addConfig(string ref, string sound, string delayref, string time, string vol, string maxref, string playdelayref) {
PoseNames += (list)ref;
Sounds += (list)sound;
DelayStarts += (list)delayref;
SoundTimes += (list)time;
SoundVols += (list)vol;
MaxPlays += (list)maxref;
DelayDuringPlay += (list)playdelayref;

}

// Post-process any config, if necessary
config_done() {
announce();
}

announce() {
//integer acount = llGetListLength(AnimNames);

llWhisper(0,
// + plural("anim", "anims", acount)
//+ " and "
(string) PoseCfgCount
+ " pose(s) configured specially for sound ("
+ llGetScriptName()
+ ": "
+ (string)llGetFreeMemory()
+ " bytes free).");
}

togglesound() {
if (playstatus == "On") {
playstatus = "Off";
llSetTimerEvent(0);
}
else {
playstatus = "On";
llSetTimerEvent( mytime );
}
}

// ==== Utilities ====

integer isKey(string str) { //Identifies whether a certain string is a UUID or not. TRUE if it is
return ( (llStringLength(str) == 36) && //UUIDs are always 36 characters
(llGetSubString(str, 8, 8) == "-") && //9th character is always a dash
(llGetSubString(str, 13, 13) == "-") && //14th character is always a dash
(llGetSubString(str, 18, 18) == "-") && //19th character is always a dash
(llGetSubString(str, 23, 23) == "-") ); //24th character is always a dash
}

// Static parameters for reading card config
string ConfigNotecardPrefix = ".SOUNDS"; // string identifying config notecards
float ConfigTimeout = 180.0; // seconds per card to wait for slow server

// Globals for reading card config
integer ConfigLineIndex;
key ConfigRequestID;
list ConfigCards; // list of names of config cards
string ConfigCardName; // name of card being read
integer ConfigCardIndex; // index of next card to read
string ConfigCardKeys; // for detecting config change

// return TRUE if there is a config card

integer next_card()
{
if (ConfigCardIndex >= llGetListLength(ConfigCards)) {
return (FALSE);
}

ConfigLineIndex = 0;
ConfigCardName = llList2String(ConfigCards, ConfigCardIndex);
ConfigCardIndex++;
ConfigRequestID = llGetNotecardLine(ConfigCardName, ConfigLineIndex);
llWhisper(0,"Reading " + ConfigCardName);
return (TRUE);
}

// Get list of config cards, and return list of their keys for use
// in detecting a config change.

string get_cards() {
string item;
string keys;

ConfigCards = [];
integer n = llGetInventoryNumber(INVENTORY_NOTECARD);
while (n-- > 0) {
item = llGetInventoryName(INVENTORY_NOTECARD, n);
if (llSubStringIndex(item, ConfigNotecardPrefix) != -1) {
ConfigCards += [item];
keys += (string) llGetInventoryKey(item);
}
}
return keys;
}

default
{
state_entry() {
state s_config;
}
}

// This state is only used to get into s_config, because going from
// s_config to s_config won't redo it's state_entry. But we might
// not want to redo anything we might have put in default state entry.

state s_reconfig
{
state_entry() {
state s_config;
}
}

// Read card config
// Multiple notecard version - read all cards with the given extension

state s_config
{
state_entry() {
config_init();
ConfigCardKeys = get_cards();
ConfigCardIndex = 0;

if (next_card()) {
llSetTimerEvent(ConfigTimeout);
} else {
state s_unconfigured;
}
}

dataserver(key query_id, string data) {
if (query_id == ConfigRequestID) {
if (data == EOF) {
if (next_card()) {
llSetTimerEvent(ConfigTimeout);
} else {
config_done();
state s_active;
}
} else {
config_parse(data, ConfigCardName, ConfigLineIndex);
ConfigRequestID = llGetNotecardLine(ConfigCardName, ++ConfigLineIndex);
}
}
}

timer() {
llWhisper(0,"Dataserver time out");
state s_unconfigured;
}

on_rez(integer num) { state s_reconfig; }

changed(integer change) {
if (change & CHANGED_OWNER) { llResetScript(); }
if (change & CHANGED_INVENTORY) { state s_reconfig; }
}

state_exit() {
llSetTimerEvent(0);
}
}

state s_unconfigured
{
changed(integer change) {
if (change & CHANGED_INVENTORY) {
if (get_cards() != ConfigCardKeys) {
state s_config;
}
}
}
}

state s_active {

on_rez(integer start) {
llResetScript();

}

state_entry(){
ListLength = llGetListLength(PoseNames);
}

link_message(integer sender_num, integer num, string str, key id) {

// num = 0 and msg = "POSEB": new pose
// id = pose name
if ( (num == 987790) && (str == "togglesound") ) {
togglesound();
}

if (num == 0 && str == "STOP") {
llStopSound();
llSetTimerEvent(0);
} else if (num == 989999) {
if (str == "stopsound") {
llStopSound();
llSetTimerEvent(0);
}
}
else if (num == 0 && str == "POSEB") {
mystartdelay = 0;
mymax = 0;
soundcount = 0;
soundtotal = 0;
TimesPlayed = 0;
mysoundlist = [];
if (playstatus == "Off") {
llSetTimerEvent(0);
return;
}
Pose = llStringTrim( ((string)id) , STRING_TRIM);
// llSay(0, "Pose : " + Pose);
integer ix = llListFindList(PoseNames, (list)Pose);
if ( ix != -1) {
string mysounds = llList2String(Sounds,ix);
integer index = llSubStringIndex(mysounds,"***");
if(index == -1) {
mysound = mysounds;
}
else {
mysoundlist = llParseStringKeepNulls(mysounds, ["***"], [""]);
soundtotal = llGetListLength(mysoundlist);
mysound = llList2String(mysoundlist,soundcount);
}
mystartdelay = (float)llList2String(DelayStarts,ix);
mymax = (integer)llList2String(MaxPlays,ix);
mytime = (float)llList2String(SoundTimes,ix);
myvol = (float)llList2String(SoundVols,ix);
myplaydelay = (float)llList2String(DelayDuringPlay,ix);

// llSay(0,
// "mysound : " + mysound
// + "/ delay : " + (string) mystartdelay
// + " / repeatseconds : " + (string) mytime
// + " / myvol : " + (string) myvol
// + " / maxrepeats : " + (string) mymax
// + " / delayduringplay : " + (string) myplaydelay
// );
if ( mystartdelay > 0 ) llSleep(mystartdelay);
llPlaySound(mysound,myvol);
TimesPlayed = TimesPlayed + 1;
llSetTimerEvent( mytime );
}
else {
// llSay(0, "got a shut off msg");
llSetTimerEvent( 0 );
}
}
} //end linkmsg section

timer() {
//llSay(0, "in timer");
if (mymax == 0) {
//llSay(0, "no max so go ahead and play");
}
else if ( (TimesPlayed + 1) > mymax ) {
TimesPlayed = 0;
llSleep(myplaydelay);
}

if (soundtotal > 1) {
soundcount = soundcount + 1;
if ( (soundcount + 1) > soundtotal ) {
soundcount = 0;
}

mysound = llList2String(mysoundlist,soundcount);
}

if (isKey(mysound) == TRUE) {
//it's a UUID so just play it
llPlaySound(mysound, myvol);
TimesPlayed = TimesPlayed + 1;
}
else {
//it's a sound file, so test to make sure it's present to avoid script errors
if ( llGetInventoryType(mysound) != INVENTORY_NONE ) {
llPlaySound(mysound, myvol);
TimesPlayed = TimesPlayed + 1;
}
}

}

changed(integer change) {
if (change & CHANGED_INVENTORY) {
if (get_cards() != ConfigCardKeys) {
state s_config;
}
}
}

}

</lsl>

PIECE 2: NOTECARD

//name card .SOUNDS
//or .SOUNDS.whatever
//lines inside card should read like: posename,sound, delaybeforeinitialstart, howoftentorepeat, volume, #repeatsbeforeanotherdelay, delayduringplay

//posename: case (and space sensitive inside pose names), make sure you get it right! You can leave spaces in between the commas or not, your choice.
//sound. You have two choices.
//Sound Choice (1) You can put in sound name, but if you do, you must include the sound file inside the prim. You need to have copy / transfer rights to the sound file to include it in products you want to sell to others. You don't need mod rights to the file.
//Sound Choice (2) You can instead supply the UUID of the sound file. You need full perm rights (mod / copy / transfer) to the sound file in order to be able to get the UUID -- right-click over a full-perm sound in your invy. Choose copy UUID, and use that as the sound name. When you list a sound UUID, you don't need to include the sound file inside the MLP product -- makes for tidier contents and less to proof for perms, etc.
//delay: how many seconds to pause initially before starting any sound play. Set to 0 if no delay is wanted. Applies only to initial start.
//howoftentorepeat: how often in seconds the sound should repeat play itself. Enter as a number. Decimal numbers such as 5.5 are fine. 0 equals play only once.
//volume: Enter a number ranging from .1 (lowest) to 1.0 (that being the loudest possible in SL). Instead of 1.0, you can enter just 1
// #repeatsbeforeanotherdelay: no of times to play the sound before once again doing the delay. Example: delay of 10 seconds, 15 repeats: script waits 10 seconds before starting playing. Plays sound 15 times (at the x seconds intervals you specified.)
//delayduringplay: sound plays x number of times, then pauses this long in seconds, then plays x number of times again, then pauses again this long in seconds, etc. Put 0 if no delay.

//MENU BUTTON
//Creating a menu button like this will allow users to toggle the playing of sounds off and on
//LINKMSG buttonname | 0,-4,987790, togglesound
//change the buttonname part to be anything you like (e.g. SND ON/OFF or TOGGLE SOUND). Don't change anything else in this line.
LINKMSG SOUNDON/OFF | 0,-4,987790, togglesound

//SOUND LINE EXAMPLE
//Spanking, LoudSpank, 0, 10, 1.0, 0
//when they are on the Spanking pose, play the sound LoudSpank. No delay in starting. Play every 10 seconds at 1.0 volume (max volume). No limit to repeats.
//Flogging, 98gyt10f-82e4-788c-2a07-1c32d409yhmv, 10, 3, 1, 5
//when they are on the Flogging pose, play the sound represented by the UUID. Wait 10 seconds before starting, then play every 3 seconds at max volume which is 1. When the sound has played 5 times, then pause 10 seconds again, they start play all over again.

BInspect, d3b61629-50a3-9716-7683-8972f2bb631c, 14, 1, 1, 4, 26
BDick, beab335a-c030-0307-0948-c5cc77b3c3ac, 0, 20, 1, 0, 0
BTowel, 59fbf10f-82e4-788c-2a07-1c32d409fafe, 0, 3, 1, 0, 0
BSpank, d71bd292-6d72-a830-68a1-8b4322fb091d, 0, 3, 1, 0, 0

MLPV2 Addons

2014-03-08T01:18:25Z

Chaz Longstaff:

{{Navbox/MLPV2}}

*[[MLPV2_Ambiant_Sound_Add-on]]
*[[MLPV2 Ball Script with more flexible parameters]]
*[[Check Animations Permissions Tool|MLPV2 Check Animations Permissions Tool ]]
*[[Cleaner MLP Say|MLPV2 "Cleaner" MLP Say]]
*[[MLPV2 Color Changer Add-on]]
*[[MLPV2 Give Item Add-on]] (Item or Items, one at a time, NOT in folder)
*[[MLPV2 Give Folder Add-on]] (Item or Items, all at once, in folder)
*[[MLPV2 Give Items in Folder to a Specific Person]]
* [[MLPV2_LockGuard_plugin]]: Add LockGuard support to MLP2
*[[MLPV2 Menu Maker Helper]]
*[[MLPV2_Props_Texture_Changer_Add-on]]
*[[Reset_from_Child_Plugin|MLPV2 Reset_from_Child_Plugin ]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Master | MLPV2 Rez Prop Independent of Pose (Master rezzer script that goes in with other MLP scripts)]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Item|MLPV2 Rez Prop Independent of Pose (Child script that goes into each item)]]
*[[MLPV2_RLV_Plugin]]
*[[MLPV2_RLV_Capture_Plugin]]
*[[MLPV2_Sound_Effects]]
*[[MLPV2_Texture_Changer_Add-on]]

===Patches===
* [[MLPV2_Balls_Patch]]: Use different balls for ~ball0...5

===Tools===
*[[Script to report on who made which animations in a prim]]

[[Category:MLPV2]]

MLPV2 Rez Prop Independent of Pose Item

2014-02-23T04:06:10Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script to [[MLPV2_Rez_Prop_Independent_of_Pose_Master| ~prop permanent rezzer (MASTER) script]]

<lsl>
//~prop permanent derezzer
//

//put this script in a prop that you have rezzed via the ~prop permanent rezzer (MASTER) script in MLP
//when the ~prop permanent rezzer script in MLP hears a button command to derez, it informs this rezzed object of that command to derez
//so this rezzed object will go away
//version 1.2 by Chaz Longstaff 2014-02-09

integer ch;
integer ListenHandle;

default {

on_rez(integer channel) {
ch = channel;
ListenHandle = llListen(ch,"",NULL_KEY,"");
}

listen(integer channel, string name, key object, string str) {
list TempList2 = llParseStringKeepNulls(str,["##"],[]);
string command = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
string object = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);

if ( (command == "DeRezAll") || ((command == "DeRez")&&(object == llGetObjectName())) ) {
llDie();
}
}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-23T03:54:46Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//PURPOSE
//to rez an item semi-permanently from MLP menu independent of a pose
//with this script, users rez an item by clicking a button (e.g. a Throne, a campfire, etc.)
//when the item is rezzed, it will stay rezzed until it hears a command to go away
//allows multiple props to be rezzed at the same time, the only maximum is how many you allow the user to rez / prim limits on land

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez AThing| 0,-4,987790,Rez##Tiki Torch bb Rezable ##X#.15#.70
//LINKMSG DeRez AThing | 1,-4,987790,DeRez##ItemToRez
//LINKMSG Clear Everything| 1,-4,987790,DeRezAll##dummytext

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ. Separate each of them with a single #
//Yes, that means the rotation is hard coded, so you just need to make your prop something that doesn't need rotational adjustments during rezzing. Sorry about that, rotations do
//my head in so I suck at them! Someone whose head can handle rotations is welcome to mod this to add flexible rotations on if they want...

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Item

2014-02-23T03:53:26Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script to [[MLPV2_Rez_Prop_Independent_of_Pose_Master| ~prop permanent rezzer (MASTER) script]]

<lsl>
//~prop permanent derezzer
//

//put this script in a prop that you have rezzed via the ~prop permanent rezzer (MASTER) script in MLP
//when the ~prop permanent rezzer script in MLP hears a button command to derez, it informs this rezzed object of that command to derez
//so this rezzed object will go away
//version 1.2 by Chaz Longstaff 2014-02-09

integer ch;
integer ListenHandle;

default {

on_rez(integer channel) {
ch = channel;
ListenHandle = llListen(ch,"",NULL_KEY,"");
}

listen(integer channel, string name, key object, string str) {
list TempList2 = llParseStringKeepNulls(str,["##"],[]);
string command = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
string object = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);

if ( (command == "DeRez") && ( object == llGetObjectName() ) ) ( (command == "DeRezAll") ) {
llDie();
}
}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-12T18:18:57Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//PURPOSE
//to rez an item semi-permanently from MLP menu independent of a pose
//with this script, users rez an item by clicking a button (e.g. a Throne, a campfire, etc.)
//when the item is rezzed, it will stay rezzed until it hears a command to go away
//allows multiple props to be rezzed at the same time, the only maximum is how many you allow the user to rez / prim limits on land

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez AThing| 0,-4,987790,Rez##Tiki Torch bb Rezable ##X#.15#.70
//LINKMSG DeRez AThing | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ. Separate each of them with a single #
//Yes, that means the rotation is hard coded, so you just need to make your prop something that doesn't need rotational adjustments during rezzing. Sorry about that, rotations do
//my head in so I suck at them! Someone whose head can handle rotations is welcome to mod this to add flexible rotations on if they want...

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-12T18:12:12Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//PURPOSE
//to rez an item semi-permanently from MLP menu independent of a pose
//when the item is rezzed, it will stay rezzed until it hears a command to go away
//allows multiple props to be rezzed at the same time, the only maximum is how many you allow the user to rez / prim limits on land

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez AThing| 0,-4,987790,Rez##Tiki Torch bb Rezable ##X#.15#.70
//LINKMSG DeRez AThing | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ. Separate each of them with a single #
//Yes, that means the rotation is hard coded, so you just need to make your prop something that doesn't need rotational adjustments during rezzing. Sorry about that, rotations do
//my head in so I suck at them! Someone whose head can handle rotations is welcome to mod this to add flexible rotations on if they want...

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-11T22:38:17Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//PURPOSE
//to rez an item semi-permanently from MLP menu independent of a pose
//when the item is rezzed, it will stay rezzed until it hears a command to go away

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez AThing| 0,-4,987790,Rez##Tiki Torch bb Rezable ##X#.15#.70
//LINKMSG DeRez AThing | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ. Separate each of them with a single #
//Yes, that means the rotation is hard coded, so you just need to make your prop something that doesn't need rotational adjustments during rezzing. Sorry about that, rotations do
//my head in so I suck at them! Someone whose head can handle rotations is welcome to mod this to add flexible rotations on if they want...

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-11T21:47:26Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//PURPOSE
//to rez an item semi-permanently from MLP menu independent of a pose
//when the item is rezzed, it will stay rezzed until it hears a command to go away

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez Sling | 1,-4,987790,Rez##ItemToRez##X|Y|Z
//LINKMSG DeRez Sling | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ
//Yes, that means the rotation is hard coded, so you just need to make your prop something that doesn't need rotational adjustments during rezzing. Sorry about that, rotations do
//my head in so I suck at them! Someone whose head can handle rotations is welcome to mod this to add flexible rotations on if they want...

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Addons

2014-02-11T21:01:20Z

Chaz Longstaff: organized into alpha order

{{Navbox/MLPV2}}

*[[MLPV2_Ambiant_Sound_Add-on]]
*[[MLPV2 Ball Script with more flexible parameters]]
*[[Check Animations Permissions Tool|MLPV2 Check Animations Permissions Tool ]]
*[[Cleaner MLP Say|MLPV2 "Cleaner" MLP Say]]
*[[MLPV2 Color Changer Add-on]]
*[[MLPV2 Give Item Add-on]] (Item or Items, one at a time, NOT in folder)
*[[MLPV2 Give Folder Add-on]] (Item or Items, all at once, in folder)
*[[MLPV2 Give Items in Folder to a Specific Person]]
* [[MLPV2_LockGuard_plugin]]: Add LockGuard support to MLP2
*[[MLPV2 Menu Maker Helper]]
*[[MLPV2_Props_Texture_Changer_Add-on]]
*[[Reset_from_Child_Plugin|MLPV2 Reset_from_Child_Plugin ]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Master | MLPV2 Rez Prop Independent of Pose (Master rezzer script that goes in with other MLP scripts)]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Item|MLPV2 Rez Prop Independent of Pose (Child script that goes into each item)]]
*[[MLPV2_RLV_Plugin]]
*[[MLPV2_RLV_Capture_Plugin]]
*[[MLPV2_Texture_Changer_Add-on]]

===Patches===
* [[MLPV2_Balls_Patch]]: Use different balls for ~ball0...5

===Tools===
*[[Script to report on who made which animations in a prim]]

[[Category:MLPV2]]

MLPV2 Rez Prop Independent of Pose Item

2014-02-11T20:23:08Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script to [[MLPV2_Rez_Prop_Independent_of_Pose_Master| ~prop permanent rezzer (MASTER) script]]

<lsl>
//~prop permanent derezzer
//

//put this script in a prop that you have rezzed via the ~prop permanent rezzer (MASTER) script in MLP
//when the ~prop permanent rezzer script in MLP hears a button command to derez, it informs this rezzed object of that command to derez
//so this rezzed object will go away
//version 1.2 by Chaz Longstaff 2014-02-09

integer ch;
integer ListenHandle;

default {

on_rez(integer channel) {
ch = channel;
ListenHandle = llListen(ch,"",NULL_KEY,"");
}

listen(integer channel, string name, key object, string str) {
list TempList2 = llParseStringKeepNulls(str,["##"],[]);
string command = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
string object = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);

if ( (command == "DeRez") && ( object == llGetObjectName() ) ) {
llDie();
}
}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-11T20:22:54Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//PURPOSE
//to rez an item semi-permanently from MLP menu independent of a pose
//when the item is rezzed, it will stay rezzed until it hears a command to go away

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez Sling | 1,-4,987790,Rez##ItemToRez##X|Y|Z
//LINKMSG DeRez Sling | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Item

2014-02-11T20:22:24Z

Chaz Longstaff: Created page with "Companion script to ~prop permanent rezzer (MASTER) script <lsl> //~prop permanent derezzer // //put this script in a prop that y…"

Companion script to [[MLPV2_Rez_Prop_Independent_of_Pose_Master| ~prop permanent rezzer (MASTER) script]]

<lsl>
//~prop permanent derezzer
//

//put this script in a prop that you have rezzed via the ~prop permanent rezzer (MASTER) script in MLP
//when the ~prop permanent rezzer script in MLP hears a button command to derez, it informs this rezzed object of that command to derez
//so this rezzed object will go away
//version 1.2 by Chaz Longstaff 2014-02-09

integer ch;
integer ListenHandle;

default {

on_rez(integer channel) {
ch = channel;
ListenHandle = llListen(ch,"",NULL_KEY,"");
}

listen(integer channel, string name, key object, string str) {
list TempList2 = llParseStringKeepNulls(str,["##"],[]);
string command = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
string object = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);

if ( (command == "DeRez") && ( object == llGetObjectName() ) ) {
llDie();
}
}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-11T20:22:10Z

Chaz Longstaff:

Companion script: [[MLPV2_Rez_Prop_Independent_of_Pose_Item|~prop permanent derezzer" (ITEM)]]

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//PURPOSE
//to rez an item semi-permanently from MLP menu independent of a pose
//when the item is rezzed, it will stay rezzed until it hears a command to go away

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez Sling | 1,-4,987790,Rez##ItemToRez##X|Y|Z
//LINKMSG DeRez Sling | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-11T20:14:29Z

Chaz Longstaff:

<lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//to rez an item semi-permanently from MLP menu independent of a pose
//when the item is rezzed, it will stay rezzed until it hears a command to go away

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez Sling | 1,-4,987790,Rez##ItemToRez##X|Y|Z
//LINKMSG DeRez Sling | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Rez Prop Independent of Pose Master

2014-02-11T20:14:15Z

Chaz Longstaff: Created page with "</lsl> //MASTER "~prop permanent rezzer" script //version 1.2 by Chaz Longstaff 2014-02-9 //to rez an item semi-permanently from MLP menu independent of a pose //when the item …"

</lsl>
//MASTER "~prop permanent rezzer" script
//version 1.2 by Chaz Longstaff 2014-02-9

//to rez an item semi-permanently from MLP menu independent of a pose
//when the item is rezzed, it will stay rezzed until it hears a command to go away

//there are 3 parts needed:
//1. Your menu commands in the MLP menu notecard;
//2. This script that goes into the MLP along with other MLP scripts -- "~prop permanent rezzer" (MASTER) script;
//3. A small script "~prop permanent derezzer" (ITEM) that you put into each item that you will semi-permanently rez; this listens for the derez command later.
//you can of course name the scripts whatever you want, the name of the scripts doesn't actually matter.

//instructions
//1. put this "~prop permanent rezzer" script inside the MLP product with the other MLP Scripts
//2. put the script "~prop permanent derezzer" in objects you are going to rez "semi-permanently"
//3. add menu buttons to your MLP .MENUITEMS notecard as follows
//
//format of menu buttons:
//
//LINKMSG Rez Sling | 1,-4,987790,Rez##ItemToRez##X|Y|Z
//LINKMSG DeRez Sling | 1,-4,987790,DeRez##ItemToRez

//X Y Z are the coordinates that you have figured out manually by placing an object where you want it, editing it, and making a note of the XYZ

integer ch;
string ObjectName;
vector TargetVector;
integer x;

integer IsVector(string str) {
if ( (vector)str )
return TRUE;
if(llSubStringIndex(str, "<") != -1)
if(llSubStringIndex(str, ">") != -1)
if(llGetListLength(llParseStringKeepNulls(str, [","], [])) == 3)
return TRUE;
return FALSE;
}

default {

on_rez(integer start) {

llResetScript();

}

state_entry() {

}

link_message(integer from, integer num, string str, key id) {

if (num == 987790) {
list TempList1 = llParseStringKeepNulls(str,["##"],[]);
string status = llStringTrim(llList2String(TempList1, 0),STRING_TRIM);
if (status == "DeRez") {
llShout(ch, str);
return;
}

ObjectName = llStringTrim(llList2String(TempList1, 1),STRING_TRIM);
string params = llStringTrim(llList2String(TempList1, 2),STRING_TRIM);
list TempList2 = llParseStringKeepNulls(params,["#"],[]);
string tmpx = llStringTrim(llList2String(TempList2, 0),STRING_TRIM);
if (tmpx == "") tmpx = "0";
string tmpy = llStringTrim(llList2String(TempList2, 1),STRING_TRIM);
if (tmpy == "") tmpy = "0";
string tmpz = llStringTrim(llList2String(TempList2, 2),STRING_TRIM);
if (tmpz == "") tmpz = "0";
TargetVector = <0 + (float)tmpx, 0 + (float)tmpy, 0 + (float)tmpz>;
//TargetVector = llEuler2Rot(TargetVector );
string object = "Object"; // Name of object in inventory
vector relativePosOffset = TargetVector; // "Forward" and a little "above" this prim
vector relativeVel = <0.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.0, 0.0, 0.0, 90>; // Rotated 90 degrees on the x-axis compared to this prim
if (IsVector( (string)TargetVector )) {
"";
//I forget what I wanted to do here!
}

if (status == "Rez") {
vector myPos = llGetPos();
rotation myRot = llGetRot();
vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;
llRezAtRoot(ObjectName, rezPos, rezVel, rezRot, ch);
}
}

}

}
</lsl>

MLPV2 Addons

2014-02-11T20:13:05Z

Chaz Longstaff:

{{Navbox/MLPV2}}

*[[Check Animations Permissions Tool]]
*[[Cleaner MLP Say|"Cleaner" MLP Say]]
*[[MLPV2_Ambiant_Sound_Add-on]]
*[[MLPV2 Ball Script with more flexible parameters]]
*[[MLPV2 Color Changer Add-on]]
*[[MLPV2 Give Item Add-on]] (Item or Items, one at a time, NOT in folder)
*[[MLPV2 Give Folder Add-on]] (Item or Items, all at once, in folder)
*[[MLPV2 Give Items in Folder to a Specific Person]]
*[[MLPV2 Menu Maker Helper]]
*[[MLPV2_Texture_Changer_Add-on]]
*[[MLPV2_Props_Texture_Changer_Add-on]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Master]]
*[[MLPV2_Rez_Prop_Independent_of_Pose_Item]]
*[[MLPV2_RLV_Plugin]]
*[[MLPV2_RLV_Capture_Plugin]]
*[[Reset_from_Child_Plugin]]

===Patches===
* [[MLPV2_Balls_Patch]]: Use different balls for ~ball0...5
* [[MLPV2_LockGuard_plugin]]: Add LockGuard support to MLP2

===Tools===
*[[Script to report on who made which animations in a prim]]

[[Category:MLPV2]]

MLPV2 Addons

2014-02-11T19:58:45Z

Chaz Longstaff:

{{Navbox/MLPV2}}

*[[Check Animations Permissions Tool]]
*[[Cleaner MLP Say|"Cleaner" MLP Say]]
*[[MLPV2_Ambiant_Sound_Add-on]]
*[[MLPV2 Ball Script with more flexible parameters]]
*[[MLPV2 Color Changer Add-on]]
*[[MLPV2 Give Item Add-on]] (Item or Items, one at a time, NOT in folder)
*[[MLPV2 Give Folder Add-on]] (Item or Items, all at once, in folder)
*[[MLPV2 Give Items in Folder to a Specific Person]]
*[[MLPV2 Menu Maker Helper]]
*[[MLPV2_Texture_Changer_Add-on]]
*[[MLPV2_Props_Texture_Changer_Add-on]]
*[[MLPV2_Rez_Prop_Independent_of_Pose]]
*[[MLPV2_RLV_Plugin]]
*[[MLPV2_RLV_Capture_Plugin]]
*[[Reset_from_Child_Plugin]]

===Patches===
* [[MLPV2_Balls_Patch]]: Use different balls for ~ball0...5
* [[MLPV2_LockGuard_plugin]]: Add LockGuard support to MLP2

===Tools===
*[[Script to report on who made which animations in a prim]]

[[Category:MLPV2]]

Timer

2014-02-09T03:38:11Z

Chaz Longstaff:

{{LSL_Event|event_id=11|event_delay|event=timer|event_desc=Repeats the code in the timer(). Result of the [[llSetTimerEvent]] library function call.
|constants
|spec
|caveats=
*The time between timer events can be longer than that specified with [[llSetTimerEvent]], this is caused by:
** '''Time dilation''' - See [[llGetRegionTimeDilation]] for more information;
** '''Default event delay''' - Only so many events can be triggered per second;
** '''Event Execution''' - If the execution of an event takes too long;
** '''llSleep()'''.
*Only one timer can be active at one time.
*The timer survives state changes, but does not survive resets.
|examples=
<lsl>
float gap = 2.0;
float counter = 0.0;

default
{
state_entry()
{
// Activate the timer listener every 2 seconds
llSetTimerEvent(gap);
}

timer()
{
counter = counter + gap;
llSay(0, (string)counter+" seconds have passed");
}
}
</lsl>
|helpers
|also_header
|also_events
|also_functions={{LSL DefineRow||[[llSetTimerEvent]]|}}
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Script
|cat2=Time
|cat3
|cat4
}}

MLPV2

2014-02-08T02:34:43Z

Chaz Longstaff:

{{multi-lang}}
{{Navbox/MLPV2}}
* Back to [[Using MLP or MLPV2]].

'''MLPV2 - Multi-Love-Pose, Version 2'''

MLPV2 is a set of scripts and configuration files that enable you to put multiple poses, with different animations and avatar positions for each pose, into an object such as furniture or a HUD. Poses are selected by menu. MLPV2 is freeware based on Miffy Fluffy's MLP; MLP is gnu-licenced.

MLPV2 is commonly used for sex beds, but can be used for a variety of purposes. It is relatively easy to set up new poses once you have the animations you need and sufficient building skills to move and orient objects where you want them. In this case, you're orienting the avatars in the poses. If the object is sold, as long as the seller allows full permissions on certain configuration files, ends user can adjust the poses to suit their own avatars or add new poses of their own. All this is possible without modifying any scripts.

The MLP 2.x line was developed by Lear Cale over a period of three years ranging from early spring 2008 until December 2010. There have been no additional versions since then, with the latest version being 2.5c. The 2.4 versions tend to be more used by older builders owing to possibly memory issues in the nascent 2.5x line.

See the navigation box at the right for tutorials and reference information.

== Availability ==

Currently available for free, copy/mod/xfer, at:
* [http://marketplace.secondlife.com/p/MLPV2-Pose-Menu-script-system-FULL-PERM/470710 MLPV2.3] - at Marketplace
* Inworld at jPose Villa (use Search or see Lear Cale's profile pics for FREEBIES).

== New Features in MLPV2.5 ==

* MLPV2 now reduces its memory limits after reading the configuration, to reduce parcel memory usage. This happens by default without any change to notecards.
* MEMORY commands for all notecards
* The "Adjust" menu button now prints free memory.
* During "Adjust" mode, ~memory script's limit is set to max, to allow storing new pose positions. Its limit goes back down when you leave Adjust mode.

NOTE from Chaz in 2014: some builders have reported that MLP 2.5x may be too aggressive in trying to limit memory and cause unexpected memory stack heap crashes in scripts such as sequences which aren't overloaded at all. In this case, using the MEMORY [[MLPV2_Reference_Manual#DIRECTIVES|directive]] in the SEQUENCES notecard (and maybe others), and maxing it to 65535 seems to help. Otherwise, if you're not concerned about memory management overly, you may want to stick to the highest 2.4 version, which is MLPV 2.4z9.

== New Features in MLPV2.4 ==

* Each sitter can adjust his or her position
* SWAP behavior is configurable, per-pose
* HIDDEN attribute for menus, for hiding poses used only by sequences
* NOCHAT attribute for sequences (so they don't chat pose name at each change)
* Elimination of trailing zeros in POSITIONS (on "save pos") to reduce memory usage.

== Feature Summary, as of MLPV2.3 ==

* Notecard configured (.MENUITEMS* and .POSITIONS* files)
* Backwards-compatible with MLP V1.2 configurations.
* Up to 6 avatars per pose. When you select a pose, poseballs appear in the colors configured in the notecards.
* Supports over 200 couples poses, limited by script memory.
* Poses can be added by the end user, without scripting (but only if notecards are modifiable)
* Poses can be adjusted by the end user (but only if notecards are modifiable)
* Configurable facial expressions per pose. All standard built-in SL expressions, plus "sleeping" which is emulated using a combination of two built-in expressions.
* Extended menus: if a menu has more than 9 buttons, a "More-->" button is automatically appended, leading to subsequent buttons.
* Modular configurations: Put a menu and position file along with all the necessary animations in a folder; drop the folder into an MLPV2 object, and use its menu to reset it, and the new poses are instantly available. (Of course, they may need to be adjusted to fit the size and orientation of the object.)
* Menu buttons are ordered as they appear in the configuration files, rather than the odd default LSL style (optional; the default is to work the same way as MLP1.2)
* Poseball hovertext is configurable via the inventory poseball's description
* Warnings for duplicate .POSITIONS* file entries
* Option to check configuration for missing or unused position entries
* Can rez a prop object from inventory, configurable per-pose
* Compatibility with Xcite, Sensations, and chains scripts, without modifying standard MLPV2 scripts. (You do need adaptor scripts; examples are provided.)
* Sequences: configure sequences of poses and chats (including participants' names) to play automatically on using one menu button.
* Reorientation -- drop in this menu module to re-orient all the poses for a new item. Allows you to change the rotation and offset on all 3 axes.
* MLP bug fix: if you rez a copy, it uses the same channel as the original, and on MLP V1.2 you'd get crosstalk. The menu channel is now reset on rez. This does not reset positions; saved positions are not lost.
* MLP bug fix: Avoid reanimating a non-sitting avatar! This happened in these cases that I'm aware of:
** Avatar is posed and STOP button is hit and then a new pose is selected. The avatar (no longer sitting) would get animated.
** Same as above, but instead of STOP button, avatar teleports or relogs

[[Category:MLPV2]]

MLPV2 Reference Manual

2014-02-08T02:14:32Z

Chaz Longstaff: /* DIRECTIVES */ expanded memory documentation

{{Multi-lang}}
{{Navbox/MLPV2}}

== .MENUITEMS* NOTECARDS ==

Menu notecards create menus.

When MLP2 starts up, it reads all *.MENUITEMS* notecards ("*" can be anything), in the same order as they're shown in object contents. You can have as many MENUITEMS notecards as you wish, or just one. MLP2 essentially reads all MENUITEMS notecards as though they've been concatenated into one big file.

The first two things (other than comments) MLPV2 reads from the first *.MENUITEMS* notecard MUST be two POSE statements, first for "default" and second for "stand" -- even if you don't use the STAND button anywhere. Note that these must not be repeated in subsequent *.MENUITEMS* notecards. See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.)

After the first two POSE statements, it expects directives and then MENU commands to build menus.

An example, to be clear:

POSE stand | stand | stand | stand | stand | stand | stand
POSE default | sit_ground | sit_ground | sit_ground

MENUORDER
// NORELOAD

MENU MAIN MENU | ALL
(etc)

Don't insert anything else at the top of the main MENUITEMS notecard, or you may experience strange errors such as "No Unused TOMENU"

The first MENU created is the main menu, which a user gets on touching the MLP2 object. The remaining menus are reached via buttons configured using TOMENU.

There are several built-in commands that you use to build your menu, as well as several options.

Most commands cause buttons to be added to menus. In this case, the command format is usually like this:

COMMAND ''ButtonLabel''

Replace ''ButtonLabel'' with whatever you want to appear as the button label. In many cases, this is optional, and the button label will match the command name. (Whenever something in a command format is in ''italics'', it means that you replace that text with what you want.)

=== COMMENTS ===
Comments in MENUITEMS notecards must be preceded by "//".

Any subsequent text on that line is ignored by the scripts.

Example 1:
//all this text is ignored

Example 2:
STOP // STOP is read by the scripts; but this part of the line is ignored.

=== DEFAULT / STAND ===

Place these are the very top of the first *.MENUITEMS* notecard, which is usually the one named ".MENUITEMS". (You may insert commented lines before this; commented lines don't count.)

Example:
POSE stand | stand | stand | stand //pose before starting and when stopping
POSE default | sit_ground | sit_ground | sit_ground //default pose when no animation entered

You may use other animations; the ones in the example are standard ones built into the SL, and don't need to appear in object inventory. {{Footnote|For a list of other built-in animations, see here: [https://wiki.secondlife.com/wiki/Internal_Animations#User-playable_animations].}}

See [[#TIP.21_Default_Pose| the default pose tip]] for help on setting coordinates for the default pose.

=== DIRECTIVES ===

Directives affect the overall behavior of MLP2. It usually doesn't matter where in the .MENUITEMS* files they are, but by convention, they appear after the default and stand poses. Directives do not cause a menu button to appear.

All are case-sensitive and so therefore you must use them in upper case as shown here.

If you want a directive to be acted upon, type its name into your menu card. If you don't, either just leave it out, or comment it out.

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| AUTOBACK ||

(MLPV2.1)
Automatically inserts BACK before any MORE--> automatically added by the AUTOMORE feature (see below). This does not add a BACK to every menu page, only those with "MORE-->" inserted by the AUTOMORE feature.

|-
|| AUTOMORE ||

Automatically inserts "More-->" button for menus with more than 12 buttons *except* for the main menu. If you need a "More-->" on the Main Menu, you must add one manually.

You would add a manual one like this:

MORE More-->

"MORE" is the command; "More-->" is the button label.

|-
|| MEMORY ||

(MLPV2.5)
This directive changes the maximum memory limit for the ~menu script.

MEMORY ''MemoryLimit''

Sets the limit to ''MemoryLimit'' in Byte on the ~menu script if encoutered in .MENUITEMS notecards.

MLPV2.5c and up reduce their memory limits after reading the configuration, to reduce parcel memory usage. This happens by default without any change to notecards.
MEMORY commands for all notecards set the amount of free memory to reserve after reading configuration. Lower numbers use less region (sim) script memory but also increase risk of
stack-heap errors. Set MEMORY to 65536 to get max permissible memory. If MEMORY commands are omitted, defaults are used.

When MLPV2 prints memory for a script as "(~scriptname: 10000 bytes free, 40000 byte limit)" 10000 bytes are available for the script's use. If it gets stack-heap errors, configure a higher MEMORY limit for that script's notecard. 40000 bytes is the limit: if this number is below 65535, you can configure more MEMORY for that script. If it's at 65535, you're maxxed out; you might have to reduce (remove poses, shorten pose names, etc -- see wiki for tips)

The "Adjust" menu button now prints free memory. During "Adjust" mode, ~memory script's limit is set to max, to allow storing new pose positions. Its limit goes back down when you leave Adjust mode.

Some scripts have hard-coded limits that can't be changed by notecard. If you get stack-heap errors for these, you can try modifying the script, increasing the number passed to llSetMemoryLimit().

<nowiki>|</nowiki>MEMORY|''MemoryLimit''|

Sets memory limit of ~props script in .PROPS notecards.

MEMORY | ''MemoryLimit''

Sets memory limit of ~swap script in .SWAP notecards.

|-
|| MENUORDER ||

This directive causes all menu buttons to appear in menus in the same order as they appear in the .MENUITEMS* files. If absent, menus are in the group-by-3-backwards order typical of SL menus, like original MLP. If present *anywhere* in any of the .MENUITEMS notecards, it affects all menus regardless of what .MENUITEM notecard they are in.

|-
|| NORELOAD ||

This directive causes MLP2 not to do a menu reset when rezzed. MLPV2.1 does not autoreload on rez, and this directive has no effect with MLPV2.1. (Automatic reset on rez was added to fix a problem where multiple copies of the same MLP object responded to each others' menus. A better fix was found in MLPV2.1.)

|-
|}

=== MENU COMMANDS ===

These will cause buttons to appear on menus.

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| ADJUST||

Adds a button to make the balls turn into long, translucent beams for easy editing to manoeuvre them into their proper positions for each pose.

ADJUST ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "AdjustPos".

See [[#TIP.21_ADJUST_Beams| tip on adjusting beams.]]

|-
|| BACK ||

Creates a button labelled "BACK" that, when pressed, displays the menu one level up in the menu hierarchy.

BACK ''ButtonLabel''

''ButtonLabel'' is optional.

If you use the AUTOMORE and AUTOBACK, you will only need to manually enter this on the last page of a submenu (including the only page of a menu with 12 or fewer buttons).

|-
||BALLUSERS ||

Creates a button to cycle through the access levels governing who can sit on the poseballs.

The levels are OWNER, GROUP and ALL

BALLUSERS ''ButtonLabel'' | ''Level''

''ButtonLabel'' is the optional button label.
''Level'' is ALL, GROUP, or OWNER.

If it is set to GROUP, avatars with the same active group tag as the MLP object can use the balls. The group for the MLPv2 product can set by right-clicking the product and selecting Edit, More >> General tab - Group: Set.

|-
||CHAT||

Adds a button to toggle on/off whether the MLP object will chat the name of each pose as it is selected.

CHAT ''ButtonLabel'' | ''OnOff''

''ButtonLabel'' is the optional button label.
''OnOff'' is the default, either ON or OFF.

|-
||CHECK ||

Adds a button that find poses with no positions and vice versa.

CHECK ''ButtonLabel''

''ButtonLabel'' is the optional button label. Typically, it's "CheckPos".

'''Note!''' This will reload all .POSITIONS.* files, so first backup any positions that have been saved using SAVEPOS but not manually entered into a *.POSITIONS* notecard!

|-
|| DUMP ||

Adds a button to dump the saved pose positions, suitable for saving into *.POSITIONS.* notecards.

DUMP ''ButtonLabel''

''ButtonLabel'' is the optional button label. Typically, it's "Dump Pos".

The positions are chatted to owner only. Positions for all poses are dumped. The user may then copy/paste this into *.POSITIONS* notecards so that the positions will be retained across a position reset, or a full restart or shutdown.

NOTE! *.POSITIONS* notecards should be released to customers with full permissions, to allow them to save positions that they've adjusted to fit their avatars.

If the MLP product has several *.POSITIONS* notecards, the end user may copy/paste all the info into the main .POSITIONS notecard, and delete all the other *.POSITIONS* notecards in the prim. They are no longer needed; all their information has now been amalgamated into .POSITIONS. However, builders may want to keep modules separate; they can do so by manually sorting the entries into their respective *.POSITIONS* files.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
|| (DUMPPROPS) ||

(MLPV2.1)
To add a button that will save prop configurations, use the following line:

LINKMSG Dump Props | 0,-4,1,DUMPPROPS // dump all prop configs

This adds a button named "Dump Props" (or whatever you prefer) that causes all the prop positions to be printed to the screen. They are visible to the MLP product owner only. The user may then copy/paste this text to *.PROPS* notecards for permanent storage.

If the MLP product has several *.PROPS* notecards, the end user may copy/paste all the info into the main .PROPS notecard, and delete all the other *.PROPS* notecards in the prim. They are no longer needed; all their information has now been amalgamated into .PROPS. However, builders may want to keep modules separate; they can do so by manually sorting the entries into their respective *.PROPS* files.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
|| HIDE ||

Adds a button that causes any MLP pose balls rezzed to become invisible. Not many MLP product makers bother with offering this button. The opposite is the SHOW command.

HIDE ''ButtonLabel''

''ButtonLabel'' is optional.

|-
|| INVISIBLE ||

Adds a button to toggle visibility for the prim that the MLP scripts are in. Note: this does not apply to the balls or any other prims, even linked ones.

INVISIBLE ''ButtonLabel''

''ButtonLabel'' is optional.

|-
|| LINKMSG ||

Adds a button that will send a specified link message to other scripts in the object when the button is pressed. This is useful for adding scripted features to MLP2 without having to modify MLP2 scripts.

LINKMSG ''ButtonLabel'' | ''menu'',''primnum'',''lm-num-arg'',''lm-str-arg''

{|{{Prettytable}}
|+
|-{{Hl2}}
!Parameter
!Explanation
|-
|| ''ButtonLabel'' || What you want the button to be called on the menu.
|-
|| ''menu'' || Set to 1 if the script receiving the button will pop up a menu. It causes MLP2 not to repost its menu, to avoid menus stacking up. Set to 0 otherwise -- (note: this doesn't inhibit MLP2's redo menu feature.)
|-
|| ''primnum'' ||
Set to -1 to send the link message to all prims

Set to -4 for just the prim the script is actually in
|-
|| ''lm-num-arg'' || 'num' arg for llMessageLinked()
|-
|| ''lm-str-arg'' || 'str' arg for llMessageLinked()
|-
|}

The menu user's UUID key is passed automatically as the 'key' argument for llMessageLinked().

|-
|| MENU ||

Creates a menu that can be reached from other menus. The first MENU configured becomes the main menu, which the user gets on 'touch'.

A menu's buttons are configured following the MENU statement.

MENU ''ButtonLabel'' | ''who''
or
MENU ''ButtonLabel'' | ''who'' | ''ballcolors''

This creates a menu named ''name1'', and a button named the same on the main menu.

Those who can access it are specified by ''who'', one of the following:

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| ALL || Anyone can use it
|-
|| GROUP || Only those who are wearing a group tag that matches the object's group can use it
|-
|| OWNER || Only the object owner can use it
|-
|}

''ballcolors'' is a list of zero to four ball color names, separated by vertical bars ("|"). The color name MUST be in UPPER-CASE. The following ball color names are supported:
{|{{Prettytable}}
|+
|-{{Hl2}}
!Version
!Colors
|-
|| MLPV2 || BLUE PINK
|-
|| MLPV2.1 || PINK, BLUE, PINK2, BLUE2, GREEN, MAGENTA, RED, ORANGE, WHITE, BLACK, YELLOW, CYAN, RED2, TEAL, GREEN2
|-
|}

See under Menu Parameters section for greater details.

For example:

MENU MyMenu | ALL | PINK | BLUE

Creates a menu named Mymenu. Poses in this menu will have 2 balls, a pink and a blue one.

Subsequent menu configuration lines add buttons to this menu, until the next MENU command. There is a limit of 12 buttons to a menu, unless AUTOMORE is used.

Note that, unless you use the MENUORDER directive, these menu items will be offered to users in the usual SL ass-backwards-by-three manner.

How do we get a button to get to this menu? There are two ways.

The first way is the same as with original MLP: use the TOMENU command to create a button to get to this menu:

TOMENU ''MenuName''

The button label must match the menu name. Menu names are case-sensitive.

The second way requires "TOMENU -" configuration lines in the main menu. For any MENU statement where no preceeding TOMENU matches the menu name, a menu button is automatically added to the main menu. (For this to work, the main menu must be filled with "TOMENU -" statements, which create blank spaces for this purpose. When MONO comes out and memory is less of an issue, we will try to make this simpler!)

|-
||MENUUSERS ||

Adds a button that cycles through the access levels governing who can use the menu.

MENUUSERS ''ButtonLabel'' | ''Level''

''ButtonLabel'' is optional.

''Level'' specifies the default, and must be one of the following: OWNER, GROUP, or ALL

If it is set to GROUP, avatars with active group tag amtching the MLP object's group can use the main menu. (You can restrict access to sub-menus on a per menu basis. See MENU above for more info.) The group for the MLPv2 product can set by right-clicking the product and selecting Edit, More >> General tab - Group: Set.

|-
|| OFF ||

Adds a button to turn the MLP system off.

OFF ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "Shutdown!"

When turned off, MLP deletes any balls, turns off all the scripts except for one that will turn it back on again when the owner touches it.

This reduces any contribution the MLP might be making to lag.

Any saved poses or prop configurations that have not been saved to *.POSITIONS* and *.PROPS* files are irrevocably lost.

|-
|| POSE ||

Adds a button for a pose.

POSE ''PoseName'' | ''AnimList''

''PoseName'' is the button label, and also the pose name (found in the *.POSITIONS* and *.PROPS* notecards).
''AnimList'' is a list of animation names, separated by vertical bars ("|").

The number of animations must match the number of ball colors listed in the corresponding MENU configuration.
That is, if the MENU has 3 poseballs, you must provide 3 animation names.

The animations are applied to the balls specified, in order. That is, if the ball colors are "PINK BLUE PINK", three animations should be listed. The first applies to the first pink ball, the second to the blue ball, and the third animation applies to the third ball, which is pink. (See also "Ball Colors" option below for more information.)

The ball positions are specified in a .POSITIONS* file, discussed below. If there is no .POSITIONS entry for a pose, the default pose is used. It's a good idea to always set up the default pose first for a new MLP product, to avoid balls rezzing underground or in other inconvenient locations.

Each animation name must have a corresponding animation in the object's contents, unless it is a built-in animation. Yyou cannot refer to animations by UUID.

|-
|| REDO ||

Adds a button to enable/disable popping the menu back up after making a selection.

REDO ''ButtonName''

''ButtonName'' is optional.

By default, when a user makes a choice on an MLP menu, the menu re-presents itself for further use.

If you offer this command button to users, and they click it, it will toggle this feature off and on.

Few MLP product makers offer this button to users, because turning off the menu coming back can create the perception that something is broken.

|-

|| RELOAD ||

Adds a button to reload *.POSITIONS* and *.PROPS* notecards.

RELOAD ''ButtonName''

''ButtonName'' is optional. Typically, it's "Reset Pos".

This button is useful after changing *.POSITIONS* or *.PROPS* notecards, to verify that you did what you intended. It's considerably faster than a complete reset since the menu isn't reread.

General rule: if you changed a .MENUITEMS card, do Menu reset. If you changed a .POSITIONS or .PROPS card, do Pos Reset.

|-
|| RESET ||

Adds a button to reload *.MENUITEMS* notecards.

RESET ''ButtonName''

''ButtonName'' is optional. Typically, it's "Reset Menu".

In addition to re-reading the notecards, it resets most of the MLPV2 scripts.

|-
|| RESTART ||

Adds a button to do what both RESET and RELOAD do, combined.

RESTART ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "Reload".

RESTART is therefore the most thorough command to use for a complete reboot.

|-
|| SAVE ||

Adds a button to save ball positions for the current pose.

SAVE ''ButtonName''

''ButtonName'' is typically "Save Pos".

Immediately after adjusting a pose, always, '''''ALWAYS''''' click this button! You will no doubt, like all of us, lose a few adjustments that you make when you first start out with MLP before this gets scarred into your habits.

'''Caution!''' This is not permanent. Anything that causes the *.POSITIONS* cards to be re-read will wipe these settings out from script memory. A pose is permanent only if it's saved in a *.POSITIONS* card.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

Note: the poseballs cannot be more than 10 metres from the MLP item for this to work.

|-
|| (SAVEPROP) ||

To add a button to save the prop location for the current pose, use the following command:

LINKMSG Save Prop | 0,-4,1,SAVEPROP // save position/rotation for a prop

where "Save Prop" is the button name (and can be whatever you choose).

You use this button after you have adjusted a prop. This stores information about the position, etc, to script memory.

This information will also be printed to the screen (only the owner can see it.) This information should be copied to the .PROPS notecard for permanent storage. You can either do this right on the spot, or arrange and save a whole bunch of prop positions, and then use the DUMPPROPS command to print out all the prop info at once for copying and pasting to the .PROPS notecard.

'''Note:''' a prop cannot be more than 10 metres from the MLP item for this to work.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
||SHOW ||

Adds a button that causes any MLP pose balls rezzed to become visible.

SHOW ''ButtonName''

Not many MLP product makers bother with offering this command. The opposite is the HIDE command.

|-
|| STOP ||

Adds a button to delete any balls and unseat any participants.

STOP ''ButtonName''

''ButtonName'' is optional.

Note though that, unlike OFF (covered above) it does not significantly reduce any contribution the MLP system might be making to lag.

|-
|| SWAP ||

Adds a button to swap positions between the first and second balls for any pose.

SWAP ''ButtonName''

''ButtonName'' is optional.

It has no effect on any third or fourth balls in a pose. However, this behavior may change in future versions.

Note: In some animation menuing systems such as XPOSE (as of summer 2008), hitting the SWAP button only swaps the current pose; the swap is lost at the next pose. In MLP, the SWAP is maintained until a user chooses to SWAP back.

IMHO, the XPOSE behavior is better, and I might change this in a future version. [Lear Cale]

|-
|| TOMENU ||

Adds a button to get to another menu.

TOMENU ''MenuName''

''MenuName'' is used as the button label, and must exactly match the name of the menu (case-sensitive).

If a menu (say, "Foo") exists, and there is no "TOMENU Foo" statement on a preceeding menu, and if there are unused "TOMENU -" statements for the main menu, a button for "Foo" is added to the main menu, using up a "TOMENU -" line.

Don't worry about supplying lots of TOMENU - slots on your main menu. If MLPv2 doesn't need them, it will just ignore them!

Note that if you are offering [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| modules]], you must provide some "TOMENU -" slots on your main menu for the module menu buttons to appear.

|-
|| Z* ||

The Z command adds a button that allows end users to easily adjust for themselves the height of the poseballs.

Z ''sign'' ''number''

For this command (and only for this command!), no spaces are allowed between the items (Z, ''sign'', and ''number). For example:

Z+1
Z+5
Z+25
Z-1
Z-5
Z-25

The numbers are treated by MLP as being a measurement in centimetres. Each time a user clicks a button, say Z+5, the height will be increased by 5 centimetres. If they have previously clicked the Z+5 button, then the height will be increased by an additional 5 centimetres.

A Z-5 button, if offered, would decrease the height by 5 cm.

Z adjustments chosen by users apply to all the poses, not just the one currently being used.

Note: the ongoing tally of these adjustments are stored in the Object Description of the prim that holds the MLP scripts, so any descriptions you put there will be replaced.

To clear them, you need to either use the Z buttons to set the offset back to 0, or, edit the object, select the MLP prim if it's not the root prim, and clear the description.

Traditionally, MLP product makers have put these Z commands under the OPTIONS menu.
These were recently moved to a HEIGHT submenu, to make room for the Props commands.

See the [[#TIP.21_OPTIONS_Menu_2| Tip! Options Menu]] for more info on how exactly to do this.

|-
|}

See the [[#TIP.21_OPTIONS_Menu_2| Tip! Options Menu]] table at the end of this page for helpful advice on arranging many of these menu commands into a tidy sub-menu.

=== MENU PARAMETERS ===

Info that you can add to MENU statement lines.

==== Ball Colors ====

If a MENU has no pose ball colors listed, it should have no POSE buttons.

When, however, a particular MENU will contain POSE statements in it, then the MENU statement must be followed by a set of ball colors to be used for all poses in this particular menu.

One to four balls can be specified, supporting poses for up to four participants. The balls are rezzed as necessary when a pose in the menu is selected.

Supported colors as of summer 2008 are:

{|{{Prettytable}}
|+
|-{{Hl2}}
!
!
!
!
!
|-
|| PINK || PINK2 || BLUE || BLUE2 || WHITE
|-
|| GREEN || GREEN2 || RED || RED2 || BLACK
|-
|| MAGENTA || ORANGE || YELLOW ||CYAN ||TEAL
|-
|}

PINK2, BLUE2, RED2, and GREEN2 are darker their respective colors with no number after them.

Note: The colors must be given in uppercase as shown above.

Examples:

MENU boy-girl | ALL | BLUE | PINK

MENU Boy Only | ALL | BLUE | HIDE

MENU Girl Only | ALL | PINK

MENU Anyone | ALL | GREEN

MENU 3Some | ALL | PINK | BLUE | PINK

MENU 4Some | ALL | PINK | BLUE | PINK | BLUE

=== POSE PARAMETERS ===

Info that you can add to POSE statement lines.

==== Animations (Facial) ====

In the POSE line, add the suffixes listed below to the animation names to cause facial expressions. (You don't change the animation name in inventory, just add the suffix to the anim name in the POSE line.)

NOTE: There is currently (April 2011) no menu button to allow MLP users to turn facial expressions off and on.

{|{{Prettytable}}
|+
|-{{Hl2}}
!suffix
!expression
|-
|| * || mouth open
|-
|| ::1 || mouth open
|-
|| ::2 || surprise
|-
|| ::3 || tongue out
|-
|| ::4 || smile
|-
|| ::5 || toothsmile
|-
|| ::6 || wink
|-
|| ::7 || cry
|-
|| ::8 || kiss
|-
|| ::9 || laugh
|-
|| ::10 || disdain
|-
|| ::11 || repulsed
|-
|| ::12 || anger
|-
|| ::13 || bored
|-
|| ::14 || sad
|-
|| ::15 || embarrassed
|-
|| ::16 || frown
|-
|| ::17 || shrug
|-
|| ::18 || afraid
|-
|| ::19 || worry
|-
|| ::20 || sleep
|-
|| ::21 || random (for MLPv2.4v or higher, produces random surprise / pleasure expressions)
|-
|}

''Note: 20 is a combination of disdain and smile, the closest that could be found for sleep.''

There must be NO SPACE between the animation name, and the suffix. Example:

POSE Sleep 01 | Sleep 01 femalesleep::20 | Sleep 01 malesleep::20

To make the expression happen periodically rather than constantly, add another extension and the length of the repetition cycle (in seconds).

For example, to use MyAnim with open mouth every 5.5 seconds:

POSE Mypose | MyAnim::1::5.5

If during menu boot you get an error that says "animation xyx not found", but you know that animation xyx really is in there, check to see that you didn't put a space before the expression suffix after all.

Note that this suffix appears only in the POSE line of a MENU; the actual name of the animation in the object's contents folder should *not* be changed to have this suffix. (Many animations are sold no mod; so you wouldn't be able to, anyway.)

== .POSITIONS* NOTECARDS ==

The .positions notecards, as their name implies, provide a place for storing information about positions of the poses in the menu.

As long as any position adjustments you have made have only been saved via the SavePos buttons, assume them to be temporary. They are only saved in script memory, and script memory is volatile. If you hand the MLP v 2.0 object to someone else, or if your sim crashes really terribly or if the script blows up with a stack-heap error, etc ... you may lose all the work you'd thought you'd saved.

The *.POSITIONS* notecards provide a safety against losing your work.

You create *.POSITIONS* notecards by your manually copying and pasting in information from the "Save Pos" or "Dump Pos" buttons (SAVE and DUMP commands described above). SL does not allow scripts to write data to notecards, so you must do this yourself.

NOTE: If the .POSITIONS notecard is no modify, or is placed in a no modify prim, people will not be able to open the notecard at all. This is a SL system limitation.

The lines in the .positions notecard look something like this:

{LieHold1} <-0.253,0.157,0.285> <0.0,0.0,0.0> <-0.146,0.000,0.177> <0.0,0.0,90.0>

where "LieHold1" is the name of a pose (from the POSE statement in a *.MENUITEMS* file).

The 4 vectors in the above example represent in order:
first ball position, first ball rotation, second ball position, second ball rotation

If there are 3 and / or 4 balls also involved in a given pose, then the pattern repeats on for them as well.

If you rename a pose in the menu that you have already stored a position in the notecard for, be sure to edit the .positions card, locate that pose in it, and give it the new name as well to match.

Be sure to purge out position lines for which menu items no longer exist. This is one instance in which tidiness really does pay off: all that old, unneeded position information is read into the scripts' memory, which can make you think that your MLP product is "full" (that fatal stack-heap message) and can't hold any of the other poses you had planned to add.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on .positions cards when using modules.

Note: Comparing positions to menu items is easier and the work of seconds as opposed to minutes if you keep the positions information cleaned up. See [[#TIP.21_Positions_Notecard_tidying| the tip on tidying .POSITIONS notecards]], if you wish to do this extra (not-required) work.

Remember that purchasers of your MLP2 product should be able to adjust poses to fine-tune them to their own heights, sizes, etc. All *.POSITIONS* notecards should be supplied to end-users with MODIFY rights so that they too can permanently save all their hard work. {{Footnote|Some furniture makers prefer to sell their furniture no mod so that others can't just disassemble it and copy the dimensions of the pieces and thereby duplicate the furniture -- fair enough. However, if the .positions notecard is in a no-mod prim, notecards inside it will also be no mod.

There doesn't seem to yet be a way around this. While llAllowInventoryDrop in a small add-on script might seem promising (and the change event could be set to delete the old .positions card), the problem remains that by then, a fresh positions card the user had dropped in would already be named .positions 1, an invalid file name. Because you can't rename objects inside a prim, you'd have to then have your script delete that .positions 1 card as well, and then invite the user to drop his/her fresh .positions notecard in a second time, which would be very confusing. Or, using the LINKMSG feature, create a button that tells a script to delete the .positions notecard, and then invites the user to drop a new one in. But you'd want that script to ask the user if s/he really knew what they were doing.

Note as well that a no-mod prim prevents the option of allowing customers to purchase add-on modules for you -- unless provision is made for an llAllowInventoryDrop.}}

(MLPV2.5) to set a memory limit on the ~memory script, use a line like this:
{MEMORY} <''MemoryLimit''>

== SEQUENCE NOTECARDS ==

SEQUENCE | seqence-name | NOCHAT 
use NOCHAT to inhibit chatting of poses 

MENU | menu-name 
set number & colors of balls 

POSE | pose-name | chat-chan | chat-message 
start a pose (chan & message are optional; message is whispered). 

AVWAIT | 0 1 2 3 | chat-message-if-waiting 
pause the entire sequence set until the balls listed are sat on (0 1 2 3 in this example) 
 
examples: 
to wait for two people: AVWAIT | 0 1 | Waiting for both people to get on the balls 
to wait for three people: AVWAIT | 0 1 2| Waiting for three people to get on the balls 
to wait for four people: AVWAIT | 0 1 2 3| Waiting for four people to get on the balls 
 
Only have one (1) AVWAIT line per sequence set, or you may get stack-heap blow-ups. 
 

WAIT | wait-seconds 
pause before executing next command 

GOTO | label-name 
go to a label, to loop a portion of a sequence 

LABEL | label-name 
set a target for GOTO 

REPEAT 
repeat the whole sequence 

SAY | chat-chan | chat-message 
say the given text on the given chat chan 

WHISPER | chat-chan | chat-message 
whisper the given text on the given chat chan 

SOUND | sound-name | 0 to 1.0 
plays sound from '''prim contents''' at volume 0 to maximum 

MEMORY | ''MemoryLimit''

(MLPV2.5) Sets memory limit of the ~sequencer script.

NOTE: The chat messages can include the first names of participants using /0 for avatar on first ball, /1 for av on 2nd ball, etc.

=== Sequence scripting debugging ===

(very advanced) 

Put any one of these are the very top of your sequences notecard, outside of any defined sequence, in order to turn on debugging for the sequences script:

debug | 1 
sequence start/stop 

debug | 2 
echo each command as executed 

debug | 4 
avatar hop on/off 

debug | -1 
all debugging 

=== Sequences and Props ===
Yes, props will still work for items used in sequences.

== TIPS ==

{{box|TIP! ADJUST Beams |Finding the ADJUST beams hard to see? First, make sure that you have set world to noon. If you still find them difficult to edit, haul the ~ball out of your prim.

Edit the ~ball script in it, and look for this part of the script in the listen event:
<lsl>
} else if (str == "ADJUST") {
llSetAlpha(0.2,ALL_SIDES);
llSetText("Adjust",<1.0,1.0,1.0>,1.0);
llSetScale(<0.1,0.1,5.0>);
</lsl>
It's the llSetAlpha setting it to only .2 that makes it hard to see. Try it at .4, or .6, or higher.

Save, take the ball into inventory, then delete the old one in the prim and replace it with your adjusted one.}}

{{box|TIP! Animations Caveat|
Though all animations will work with MLPv2, not every single one you come across will work reliably.

Some animations, if they happen to have been made by the creator in a certain way, will work as expected after certain other animations, but not after others. You'll get different results depending on which pose you ran last.

The problem is animations that have their hip position the same in their T frame and first animation frame. They just won't work with MLP.

Example: if you have 3 anims, 2 with hip positions set and one without, the hip position for the one without will be the hip position left over from whichever of the last two anims you used. It's the way SL animations work. If there's no change in any joint between the "T" frame (first frame in bvh file) and the first animation frame (second frame in bvh file), SL ignores that joint for the whole animation. And when all other animations are turned off, this means that these joints are left free to do whatever SL does with them. It leaves them as they were from the previous anim, or overrides them with SL builtin motions like typing, head movement, arm pointing while editing, etc.

The values in the hip joint aren't important; what's important is that that they *be* different between T frame and 1st animation frame. For MLP, you want every joint in the animation to have been moved (except head, if you want it to be able to move with the mouse.)

This problem can be avoided when making animations if you move the hip even just 1 degree, and normally the stomach 1 degree in the opposite direction.

So sadly, in the course of things, odds are, you're just going to buy some animations that just ain't going to work with MLP. And there is no way of knowing in advance.

When creating animations for MLP, Lear Cale highly recommends using priority 3. This disallows the typing while chatting animation, but allows head movement (if the head joint is not moved in the beginning of the animation). It also allows someone to create a priority 4 animation and run it to override MLP animation behavior (until the next pose is selected). }}

{{box|TIP! Animations Permission|
The ball user, upon first sitting on a ball, will be asked permission to animate them. S/he must say yes to yes, or they will end up just "hovering" on the poseball.

The "permission pls" menu often gets hidden behind the MLP main menu (if you are the one who called up the menu.) You need to click the ">>>" to cycle through the menus on your screen to find the permissions prompt. This is SL behaviour and there's no way to fix it, other than turning "redo" menu off in MLP.

NOTE: in their great wisdom, SL modified the 1.20 viewer to show something other than ">>>" for this button. Damn them.

If you are wondering why permission must be asked, when normally sitting on something is taken as implying permission to be animated, it's because it's not actually the balls that are doing the animating -- it's a script in the MLP. Because one script is not allowed (for security reasons) to pass permission to another script, the scripts in the MLP itself can't take advantage of any permissions the poseballs have acquired.}}

{{box|TIP! Animation Synchronization |Animations appear to start separately per ball once an avatar sits on it. Thus, they're not in sync.

In fact, the animations are started at the same time. However, it takes time for the animations to get sent between SL and the client, so as a result they don't look synchronized.

There is no simple feature in MLPV2 to automatically synchronize poses as such. You can manually synchronize by shifting to another pose and then shifting back again. (Starting with

There is no built-in feature to automatically synchronize, as there is with couples danceballs. Prior to MLPV2.4z4, you can manually synchronize by changing to another pose and then back. Starting with MLPV2.4, you can manually resynchronize by selecting the same pose again.

There is an advanced feature of MLPV2 that you could use to get automatic periodic synchronization: Sequences.

A sequence is simply a list of poses that MLPV2 will play at the touch of a button, with the option to repeat the sequence or a portion of the sequence. See the example sequence in the distribution. You could set up a simple sequence that plays one pose, waits some time that's at least as long as the animations, and repeats, like this, which goes in .SEQUENCES notecard:
<pre>
SEQUENCE | snuggle-seq | NOCHAT
MENU | couples
POSE | snuggle
AVWAIT | 0 1
POSE | snuggle
WAIT | 30
REPEAT
</pre>

}}

{{Box|TIP! Animations and balls|
Animations remain in the main MLP object; they are never placed in the poseballs. The animations are played from within the main MLP product; the poseball is just the delivery vehicle. Consequently, poseballs can be deleted or lost without the main product being affected. And, the poseballs themselves are just copies of the one inside the MLP product.

A ball will commit suicide if left behind somewhere (the MLP object needs to be within 20 metres.)}}

{{Box|TIP! Ball text|
By default, both the poseball floating text and the right-click menu 'sit' choice text is the word "LOVE". You can set these to whatever you want by editing the description of ~ball in object contents. If you type in that field the word "none" (without the quotes), or just type in a space or two, there will be no floating text, and the right-click menu 'sit' choice text becomes the system default of just "Sit Here" (for English viewers).}}

{{Box|TIP! Phantom Balls|
To make your balls rez as phantom, put an asterisk in the ~ball description line.}}

{{Box|TIP! More than 6 balls|
There are no plans to expand beyond 6 balls active at once. If this is totally necessary for you, you'd be better off just going with a product that actually supports the number of avatars you want, such as XPOSE. You'll save yourself and your customers time and confusion by going with a product that was designed to handle larger numbers from the ground up.}}

{{Box|TIP! Balls are buried in furniture|
Sometimes when you position the balls correctly for an animation, the balls end up buried in furniture.

This is a property of the animation: the hip position in the animation is too high. While it is in theory possible to fix this in MLP scripts, it would be hard to do, especially without using up lots of memory for poses.

Most people know that when this happens they can select another pose first, jump on, and then change to the pose they want. Consequently, the simplest workaround is to make sure the first pose in each menu has all balls visible.

Alternatively, you could ask the creator of the animation to adjust it, but the chances of them doing this just for your piece of furniture are not high.

If someone stands up while on balls that are buried in furniture, they will get ejected from the furniture unceremoniously. This won't happen if they use the STOP button on the menu instead.

Vesta Martynov suggests another workaround -- changing the offset that the ball is rezzed at. (Note that this will apply to all poses, not just the problem ones.) Her work-around is, before you start on a MLP product, to take the ball out and rez it on the ground. Edit the script in the ball, and search for this SitTarget line:

llSitTarget(<0.0,0.0,0.1>,ZERO_ROTATION);

The .01 there is the vertical offset. She changes it to something like this:

llSitTarget(<0.0,0.0,-0.25>,ZERO_ROTATION);

Save your changes, take the ball back into your inventory, and use it to replace the one that was inside the MLP.

After you do this, all the balls and animations will be lifted, so you can go in and lower the animations, but you will no longer have balls sinking into your furniture.

(Vesta Martynov, conversation in MLP group, 2009-06-11 19:46)
}}

{{Box|TIP! Ball scripts|
When updating your version of MLPv2 scripts, make sure you update the script in ~ball as well.
}}

{{Box|TIP! Changing the number of active Balls|
When going from a pose in a menu with 4 ball colors to a pose in a menu with 2 balls, the 2 balls are deleted. Assuming you're not using phantom balls, if the balls rez again (say you go back to a pose in a menu with 4 balls), the balls should bump anyone standing in their way out of the way. People wanting to use the newly re-rezzed balls and be animated by them will have to hop back on them. When changing the number of balls active, bear in mind that the number of animations in a POSE line must match the number of ball colors in the MENU line above. You can't mix poses with 2 anims and poses with 4 anims in the same menu section. This is not supported.}}

{{box|TIP! Default Pose |
You need to set position coordinates for the default pose. To do this, on the MLPV2 main menu click the "adj-default" button, then ADJUST the default pose position, save, and copy the coordinates to the .positions notecard as per normal. When you have finished, delete the .menuitems.zz-default notecard from the prim.

If on the main blue menu you do not see a button called "adj-default", do the following steps:

1) Create a notecard with the file name of: 

.Menuitems.zz-default

Paste the following in as content:

<pre>
// The "default" pose below is for adjusting "default" position.
// Since there are currently no other items in this menu, you can comment out the whole menu 
// or simply delete this file when you've done that.

MENU adj-default | ALL | BLUE | PINK | BLUE | PINK
POSE default | sit_ground | sit_ground | sit_ground | sit_ground
SWAP
ADJUST
SAVE Save Pos
DUMP Mem Dump
BACK
</pre>

Tip! If the product you are making is only for 1 or 2 people, then you don't need to include all 4 balls that are listed in the menu above. For a solo product, you can just do instead:
<pre> MENU adj-default | ALL | BLUE
POSE default | sit_ground
ADJUST
SAVE Save Pos
DUMP Mem Dump
BACK
</pre>

Drop this notecard into the prim where you are working with MLPV2.

2) Make sure the main menu notecard has a spare TOMENU slot to fit the adj-default choice into:

TOMENU -

3) restart the MLPV2 product.

4) ADJUST the default pose position, save, and copy the coordinates to the .positions notecard as per normal.

5) When you have finished, delete the .menuitems.zz-default notecard from the prim.}}

{{box|TIP! Notecard Editing|
If the MLP prim contains many animations, access to a notecards contents can be PAINFULLY slow.

First, make sure the prim is ready to let you open the notecard. Right-click on the notecard that you see in the contents folder. If you get a big menu of choices, rather than just the standard 4 of Open, Properties, Rename, Delete, then the prim isn't ready to let you open the notecard. You simply have to wait. Sometimes, you may need to wait up to 2 to 4 minutes. Yes, ridiculous -- but that's SL.

Make all your changes before saving. Once you save, the notecard you have open may no longer be the notecard that is inside the prim (sic.) Once you have saved, even if you did so by accident out of habit, leave the notecard opened for a few seconds, then close it, and wait until the prim is ready to let you open it again if you need to do further edits.

Note: as of summer 2008, the wait time for notecards to open from inside prim folder contents seems to be getting increasingly worse, and the system seems to be getting increasingly intolerant of allowing repeated saves on the same opened notecard. Thus, the advice to close and re-open after a save.}}

{{box|TIP! Modules -- multiple .menuitems and .positions notecards|
There can be several *.MENUITEMS* and *.POSITIONS* notecards in an MLP product (where "*" is any text that's allowed in a notecard name). This is to allow the addition of modules to the product. This allows you the option, for example, of letting customers purchase an MLP product for couples, and then coming back later to purchase an odd-on for 3Somes. Customers then pad home, edit the contents folder of their MLP product, plop in the add-on stuff, and restart their MLP.

'''Note:''' a module's menu appears as a button on the MLP product's main menu. For this to actually happen, you *must* provide a blank slot for it by supplying a TOMENU - parameter on the main menu. Normally, there should be a bunch of these in the main menu.

The add-on will consist of a .menuitems card, a .positions card, and the associated animations (with permissions set correctly.)

For you as a vendor to make a module, you create a .MENUITEMS.xxx notecard, and a corresponding .POSITIONS.xxx notecard (where xxx can be anbything and is normally thought of as the name of the module.) If this module uses props, you also create a .PROPS.xxx notecard.

A *.MENUITEMS* card for a module should have no default or stand pose, etc. It normally has only the actual menus being added and the associated poses.

Example:

<pre>MENU myAddOns
TOMENU myAddOn1
TOMENU myAddOn2

MENU MyAddOn1 | ALL | PINK | BLUE
POSE Whoohoo! | Bump1 | Bump2
POSE Zowee | Grind1 | Grind2

MENU MyAddOn2 | ALL | PINK | BLUE | PINK
POSE Fubar | Dance1 | Dance2 | Dance3</pre>

To test, you would then drop all associated notecards (.menuitems.xxx, .positions.xxx and .props.xxx if using) into the MLP product, along with the necessary animations and props, of course, and restart the MLP product. (Of course, if you were selling it as a separate add-on, you would after remove the above components from the main product, and package them separately.) Remember if you make any pose position adjustments during testing that the position information should be copied and pasted to the relevant .positions.xxx notecard -- not the main .positions notecard, because you are preparing a sold-separately module. Ditto for any prop adjustments, which go into the .props.xxx notecard.

Purchasers of an add-on need to always keep that .menuitems.xxx notecard in their product. However, the .positions.xxx and the .props.xxx notecards have, in a way, a limited lifespan. When you do a DUMP command, you copy / paste all that info into the notecard named simply .positions -- that is the main .positions notecard. Or, into .props notecard, in the case of a DUMPPROPS command. All the info that the subsidiary .positions.xxx and .props.xxx notecards hold is now amalgamated into the main notecard, and the subsidiary ones are no longer needed. They can be deleted. But to be clear, do not delete their corresponding .menuitems.xxx notecards.

Multiple .positions notecards are read by the script in the same order they appear in object inventory.

Note: it is best to be using the MENUORDER directive when offering modules.}}

{{box|TIP! Sub-Menus|Can you add a module menu ie: .MENUITEMS.myposes and have it show as a top menu item with sub menus? Something that would give a My Poses button that when clicked would open a sub menu dialog with buttons for my poses 1, my poses 2 etc.

Abolutely, and that's the best way to do it.

Start your .MENUITEMS.mystuff with the parent menu. Fill it with "TOMENU" statements like this:

<pre>
MENU WhizBangInc | ALL
TOMENU WBI-cuddles
TOMENU WBI-fun
TOMENU WBI-freaky
TOMENU WBI-illegalin42states</pre>}}

{{box|TIP! Options Menu|
By tradition, most of the common functionality command buttons are stored under a MENU called "OPTIONS".

Such commands include ADJUST, SAVE, DUMP, Show/Hide (aka INVISIBLE), MenuUsers, BallUsers, Chat, Dump Props, Save Prop, etc.

As well, the z commands for height adjustment were traditionally offered there as well.

With the rapidly-increasing number of functions available within MLPv2, however, the OPTIONS submenu is becoming very crowded.

Consequently, consider taking all the z height adjustment options out from under OPTIONS and put them in a sub-menu like this:

<pre>MENU HEIGHT | ALL
Z+1 //adjust Z = height offset in cm - use any integer to set the step size
Z+5
Z+25
Z-1
Z-5
Z-25
BACK
</pre>

Then, in the OPTIONS menu, just make this button linking to the HEIGHT submenu:

TOMENU HEIGHT}}

{{box|TIP! Positions Notecard tidying|
The lines in the .positions notecard look like this when copied and pasted in directly from chat:

[7:46] Animated Living Sofa Combo Couple & Solo 2.1e: {Lie&Hold} <-0.413,0.130,0.245> <1.0,-9.0,-0.9> <-0.539,0.207,0.155> <-0.1,-8.9,-1.1>

The extraneous chatter before the {LieHold1} parameter in the curly brackets (aka braces) is ignored by the scripts, so there is no need to delete it.

Still, if you as an MLP professional wish cleaner, easier to read content (which is a boon for easier maintenance and troubleshooting), then copy the contents of the .positions card in question into a simple text programme (such as Notepad on a Windows PC), and using the example above, you would search for:

[7:46] Animated Living Sofa Combo Couple & Solo 2.1e: [including the final space at the end of it]

and just replace it with nothing, and then paste the cleaned up text back into the .positions card.

The cleaned up text then looks like this.

{LieHold1} <-0.253,0.157,0.285> <0.0,0.0,0.0> <-0.146,0.000,0.177> <0.0,0.0,90.0>

You may wish to also to SORT the positions in alpha order to make it easier to find them.

So that instead of:

{Massage} <-0.230,-0.133,-0.287> <0.0,0.0,-86.0> <-0.287,0.259,0.161> <0.0,0.0,-82.0> 
{Sprawl 1} <0.960,0.000,-0.190> <0.0,0.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 
{Lie 01} <-0.115,-0.069,0.694> <0.0,0.0,-90.0> <-32.417,-199.035,-518.585> <0.0,0.0,0.0> 
{Couch 1} <-0.179,0.001,0.143> <0.0,-19.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 

You have 

{Couch 1} <-0.179,0.001,0.143> <0.0,-19.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 
{Lie 01} <-0.115,-0.069,0.694> <0.0,0.0,-90.0> <-32.417,-199.035,-518.585> <0.0,0.0,0.0> 
{Massage} <-0.230,-0.133,-0.287> <0.0,0.0,-86.0> <-0.287,0.259,0.161> <0.0,0.0,-82.0> 
{Sprawl 1} <0.960,0.000,-0.190> <0.0,0.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 

You can do this sorting in seconds by copying & pasting the (cleaned-up position chatter) into something such as Microsoft Word, or a spreadsheet, and telling it to sort, and then copying & pasting the sorted positions back into the .positions notecard. (This really works best though if you have stripped the initial chatter info from them.) }}

{{box|TIP! Notecard reading order|
Q: I have a question about animation packs. I know the readme notecard says that the scripts read the notecards in alpha order. If I were to name the notecards as A, B, and C would the buttons on the menu then be in that order as well? I'm picky--I like my buttons in a certain order.

A: Yes.}}

{{Box|TIP! Portable use of an MLPv2 product|
Attach the MLPv2 object to your HUD. You can use its default shape and color for a clickable bar on one of the edges of your screen (to move HUD position: Right-click and Edit it and use the arrows). While in edit mode, you can also edit color/transparency/size/position.

Note that the balls will appear relative to the initial MLPv2 position. Adjust the height offset with a (Z) command.}}

{{Box|TIP! Props|
Props are objects the MLP product will rez for poses. When you choose another pose or hit STOP, any rezzed prop disappears. If you delete the MLP object, any prop will disappear within 3 minutes.

Props support starts with MLPV2.1.

To add a prop, edit a .PROPS notecard or add a new one (named .props.xxx where xxx is the name of the module, for a modular config). Copy the following example line and paste it into your .PROPS notecard.

<pre>| mypose | myobject | <1,1,1>/<0, 0, 0></pre>

Then: 
*Replace "mypose" with the pose name;
*Replace "myobject" with the name of the prop object. The object name cannot contain vertical bars;
*Add the "~prop" script (from inside the "~pillow" object that comes with the standard distribution) to your prop object, and drop your prop object into the MLP prim's inventory. The prop and everything in it will need to be copiable for next owner;
*Make sure your menu has the SAVEPROP and DUMPPROPS command on it.

Restart the MLP, and then select the pose. The prop should appear. It might be underneath the MLP object, so look around -- it may be best to do this using a single prim MLP floating in the air, the first time so that it doesn't rez in the ground!

Move the prop to where you want it, and use MLP menu command "SAVEPROP". To make the change permanent, select the chat information that is printed out on your screen (including the first vertical bar, and optionally any text before it) and replace the corresponding line in your .props.xxx file. Or, do all your props and use DUMPPROPS. (This procedure is similar to that for saving positions in .positions.xxx notecards.)

To get MLP to reread .props.xxx files, restart the product (which resets positions as well as props).

Keep in mind that props and positions are saved as two separate steps. If you adjust a pose and its prop, you need to save both pose position and prop.

Tip: We are all so used to hitting the button to save positions. If you find that a prop position isn't saving, check your chat history to make sure you didn't hit the save position button instead of save prop just out of habit!

 '''Hand-held Props''' For props to be used as hand-held items, use the ~give script add-on found here [[MLPV2_Give_Item_Add-on]] and have people wear the items. 

'''Number of Props''' 
For any pose, you can have at most one prop. If you need more than one prop to rez, you'll have to link the items so that they can be treated by MLP as one object. Alternatively, if you have a scripter friend to help you, you might try having the rezzed object rez another object from its contents. Your scripter friend would need to make the rezzed child object listen for the same die command as the main object that was rezzed.

Or, you *might* perhaps try the rezzed object as a coalesced object, making sure that each item has in it a script (created custom for you by a scripter friend) so they can die when required to -- experiment with that somewhere in the open at first in case it goes all over the place. 
}}

{{Box|TIP! STOP in every menu|
STOP and BACK buttons should be on every menu.

Why STOP on every menu? It solves so many problems. For example, if you use STOP, you don't get ejected like a James Bond villain if the poseball happens to be buried in the furniture. After moving or rotating a bed, STOP resets the position (Lear put in code to do this automatically, but there's no event that tells you when rotation stops.) And no doubt, SL and MLPV2 have bugs, and I've seen funky and unrepeatable oddness that STOP fixes in a jiffy. Plus it makes the poseballs go away.}}

{{box|TIP! Scripting -- call on MLP Menu from another script via linked msgs|
If you just want the MLP menu to come up from another script in the object (same prim or different one), simply do what the ~touch_passer script does (the llMessageLinked() call). If your script is in the same prim as MLP scripts, change LINK_ALL_OTHERS to LINK_THIS.
}}

{{box|TIP! Scripting -- call on MLP Menu from another script via chat|MLP listens for menu responses on this channel, minus one:

<pre>
// Return a channel number that's based on the prim's key -- unique per object
integer channel() {
return (integer)("0x"+llGetSubString((string)llGetKey(),-4,-1));
}</pre>

Note that the key here is the key of the MLP object.

Oh, warning: it also checks to see if the chat came from the same user as whoever used the menu recently. If they don't match, it sends a menu (dialog) -- in this case, to your object, which won't do anything. So, I suspect that this will work only if you keep users from getting access to the MLPV2 menu directly.}}

== API ==

When the MLP is ready for use, it sends out a linked message on channel -11003 saying "READY"

llMessageLinked(LINK_SET, -11003, "READY", NullKey);

{{Footnotes}}

== Illegal Pirated Animation Kit FYI ==
http://wiki.secondlife.com/w/index.php?title=62_Animation_MLP_Set

For "free" status of Sexgen animation kit released October 2011 by Stroker Serpentine, see here: https://wiki.secondlife.com/wiki/Stroker_Serpentine_Sexgen_Animation_Set

[[Category:MLPV2]]

MLPV2 Users Reference

2014-02-03T01:43:06Z

Chaz Longstaff: /* Chat button */

{{multi-lang}}
{{Navbox/MLPV2}}

= Introduction =

This document describes what standard MLPV2 menu buttons do. Note that this applies only if the builder used the standard OPTIONS menu without modifications and followed common conventions.

= Buttons found in pose menus =
== STAND button ==
'''STAND''' brings up a standing pose, suitable for use when beginning or quitting.

== STOP button ==
'''STOP''' causes the STAND pose to happen momentarily, and then unseats all avatars and deletes the poseballs. It also shuts down any scripts that are not needed while the product isn't active. The product remains ready for immediate use.

== SWAP button ==
'''SWAP''' exchanges the participants' roles in the pose. It has no effect with solo poses. For couples, it exchanges the two participants. For poses with more than two poseballs, the default is to swap the first two, but more sophisticated swaps can be configured in the notecards.

== BACK button ==
'''BACK''' returns to the previous menu in the menu hierarchy.

= OPTIONS menu =
== Chat button ==
'''Chat''' turns menu action chatting on and off. Typically, MLPV2 chats the pose name when a pose is selected. This button alternately enables and disables that, along with other chat messages that MLPV2 issues. That means that if you happen to be toggling options such as "MenuUsers" and "BallUsers", which normally chat to you what setting you have just selected... that means that you won't hear that. You need to have Chat on to hear what setting you have just selected.

== Adjust Pos button ==
'''Adjust Pos''' turns pose adjustment mode on or off.

Normally, adjustment mode is off.

When adjustment mode is on, poseballs that are sat upon turn into semi-transparent beams that are easy to select and reposition.

In adjustment mode, whenever a new pose is selected, the current pose's position (including props, as of MLPV2.4TBD ) is saved before starting the new pose. Selecting the ''same'' pose abandons any changes to the current pose and returns it to the last saved position.

== Save Pos button ==

This button saves the curren't pose's position to MLPV2 memory (but not to notecards).

== Dump Pos button ==

This button dumps all pose positions from MLPV2 memory, suitable for saving to .POSITIONS notecards.

== Save Prop button ==

This button saves the curren't pose's position to MLPV2 memory (but not to notecards).

== Dump Prop button ==

This button dumps all prop positions from MLPV2 memory, suitable for saving to .PROPS notecards.

== Ball Users button ==

This button cycles through three settings for who can use the poseballs

* OWNER - only the owner can sit
* GROUP - avatars other than the owner must wear group tag to sit (matching the MLPV2 object's group)
* ALL - any avatar can sit

== Show/Hide button ==

This buttons alternately shows and hides the MLPV2 prim. It does not affect other prims.

== Menu Users button ==

This button cycles through three settings for who can use the MLPV2 menus:

* OWNER - only the owner can use the menus
* GROUP - avatars other than the owner must wear group tag to use the menus (matching the MLPV2 object's group)
* ALL - any avatar can use the menus

However, specific menus may be further restricted to OWNER or GROUP based on notecard configuration, regardless of this setting.

== Height button ==

This button presents a menu for adjusting the height of all poses.

= Shutdown... Menu =

Typically, only the owner can use this menu. However, for rental land, it may be wise to set this menu to GROUP (in the .MENUITEMS notecard).

== Pos Reset button ==

This button causes MLPV2 to re-read the .POSITIONS and .PROPS notecards.

== Menu Reset button ==

This button causes MLPV2 to re-read the .MENUITEMS notecards.

== Restart button ==

This button does a full restart of MLPV2, including re-reading .MENUITEMS, .POSITIONS, and .PROPS notecards.

== Shutdown! button ==

This button stops all MLPV2 scripts except one which remains running to allow restart on owner-click.
Only the owner can use this button, regardless of other settings, because only the owner can click to restart MLPV2.

= Sequence control buttons =
These buttons are commonly found in menus that contain sequences. (Sequences are series of poses with optional sounds and chat.)

== PAUSE button ==
The sequence pauses, staying in the current pose.

== RESUME button ==
The sequence resumes with the next pose. If the sequence was not paused, this advances to the next pose rather than waiting for the timeout.

[[Category:MLPV2]]

MLPV2 Reference Manual

2014-01-28T04:41:49Z

Chaz Longstaff: Chaz updated AVWAIT directions.

{{Multi-lang}}
{{Navbox/MLPV2}}

== .MENUITEMS* NOTECARDS ==

Menu notecards create menus.

When MLP2 starts up, it reads all *.MENUITEMS* notecards ("*" can be anything), in the same order as they're shown in object contents. You can have as many MENUITEMS notecards as you wish, or just one. MLP2 essentially reads all MENUITEMS notecards as though they've been concatenated into one big file.

The first two things (other than comments) MLPV2 reads from the first *.MENUITEMS* notecard MUST be two POSE statements, first for "default" and second for "stand" -- even if you don't use the STAND button anywhere. Note that these must not be repeated in subsequent *.MENUITEMS* notecards. See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.)

After the first two POSE statements, it expects directives and then MENU commands to build menus.

An example, to be clear:

POSE stand | stand | stand | stand | stand | stand | stand
POSE default | sit_ground | sit_ground | sit_ground

MENUORDER
// NORELOAD

MENU MAIN MENU | ALL
(etc)

Don't insert anything else at the top of the main MENUITEMS notecard, or you may experience strange errors such as "No Unused TOMENU"

The first MENU created is the main menu, which a user gets on touching the MLP2 object. The remaining menus are reached via buttons configured using TOMENU.

There are several built-in commands that you use to build your menu, as well as several options.

Most commands cause buttons to be added to menus. In this case, the command format is usually like this:

COMMAND ''ButtonLabel''

Replace ''ButtonLabel'' with whatever you want to appear as the button label. In many cases, this is optional, and the button label will match the command name. (Whenever something in a command format is in ''italics'', it means that you replace that text with what you want.)

=== COMMENTS ===
Comments in MENUITEMS notecards must be preceded by "//".

Any subsequent text on that line is ignored by the scripts.

Example 1:
//all this text is ignored

Example 2:
STOP // STOP is read by the scripts; but this part of the line is ignored.

=== DEFAULT / STAND ===

Place these are the very top of the first *.MENUITEMS* notecard, which is usually the one named ".MENUITEMS". (You may insert commented lines before this; commented lines don't count.)

Example:
POSE stand | stand | stand | stand //pose before starting and when stopping
POSE default | sit_ground | sit_ground | sit_ground //default pose when no animation entered

You may use other animations; the ones in the example are standard ones built into the SL, and don't need to appear in object inventory. {{Footnote|For a list of other built-in animations, see here: [https://wiki.secondlife.com/wiki/Internal_Animations#User-playable_animations].}}

See [[#TIP.21_Default_Pose| the default pose tip]] for help on setting coordinates for the default pose.

=== DIRECTIVES ===

Directives affect the overall behavior of MLP2. It usually doesn't matter where in the .MENUITEMS* files they are, but by convention, they appear after the default and stand poses. Directives do not cause a menu button to appear.

All are case-sensitive and so therefore you must use them in upper case as shown here.

If you want a directive to be acted upon, type its name into your menu card. If you don't, either just leave it out, or comment it out.

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| AUTOBACK ||

(MLPV2.1)
Automatically inserts BACK before any MORE--> automatically added by the AUTOMORE feature (see below). This does not add a BACK to every menu page, only those with "MORE-->" inserted by the AUTOMORE feature.

|-
|| AUTOMORE ||

Automatically inserts "More-->" button for menus with more than 12 buttons *except* for the main menu. If you need a "More-->" on the Main Menu, you must add one manually.

You would add a manual one like this:

MORE More-->

"MORE" is the command; "More-->" is the button label.

|-
|| MEMORY ||

(MLPV2.5)
This directive changes the maximum memory limit for the ~menu script.

MEMORY ''MemoryLimit''

Sets the limit to ''MemoryLimit'' in Byte on the ~menu script if encoutered in .MENUITEMS notecards.

<nowiki>|</nowiki>MEMORY|''MemoryLimit''|

Sets memory limit of ~props script in .PROPS notecards.

MEMORY | ''MemoryLimit''

Sets memory limit of ~swap script in .SWAP notecards.

|-
|| MENUORDER ||

This directive causes all menu buttons to appear in menus in the same order as they appear in the .MENUITEMS* files. If absent, menus are in the group-by-3-backwards order typical of SL menus, like original MLP. If present *anywhere* in any of the .MENUITEMS notecards, it affects all menus regardless of what .MENUITEM notecard they are in.

|-
|| NORELOAD ||

This directive causes MLP2 not to do a menu reset when rezzed. MLPV2.1 does not autoreload on rez, and this directive has no effect with MLPV2.1. (Automatic reset on rez was added to fix a problem where multiple copies of the same MLP object responded to each others' menus. A better fix was found in MLPV2.1.)

|-
|}

=== MENU COMMANDS ===

These will cause buttons to appear on menus.

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| ADJUST||

Adds a button to make the balls turn into long, translucent beams for easy editing to manoeuvre them into their proper positions for each pose.

ADJUST ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "AdjustPos".

See [[#TIP.21_ADJUST_Beams| tip on adjusting beams.]]

|-
|| BACK ||

Creates a button labelled "BACK" that, when pressed, displays the menu one level up in the menu hierarchy.

BACK ''ButtonLabel''

''ButtonLabel'' is optional.

If you use the AUTOMORE and AUTOBACK, you will only need to manually enter this on the last page of a submenu (including the only page of a menu with 12 or fewer buttons).

|-
||BALLUSERS ||

Creates a button to cycle through the access levels governing who can sit on the poseballs.

The levels are OWNER, GROUP and ALL

BALLUSERS ''ButtonLabel'' | ''Level''

''ButtonLabel'' is the optional button label.
''Level'' is ALL, GROUP, or OWNER.

If it is set to GROUP, avatars with the same active group tag as the MLP object can use the balls. The group for the MLPv2 product can set by right-clicking the product and selecting Edit, More >> General tab - Group: Set.

|-
||CHAT||

Adds a button to toggle on/off whether the MLP object will chat the name of each pose as it is selected.

CHAT ''ButtonLabel'' | ''OnOff''

''ButtonLabel'' is the optional button label.
''OnOff'' is the default, either ON or OFF.

|-
||CHECK ||

Adds a button that find poses with no positions and vice versa.

CHECK ''ButtonLabel''

''ButtonLabel'' is the optional button label. Typically, it's "CheckPos".

'''Note!''' This will reload all .POSITIONS.* files, so first backup any positions that have been saved using SAVEPOS but not manually entered into a *.POSITIONS* notecard!

|-
|| DUMP ||

Adds a button to dump the saved pose positions, suitable for saving into *.POSITIONS.* notecards.

DUMP ''ButtonLabel''

''ButtonLabel'' is the optional button label. Typically, it's "Dump Pos".

The positions are chatted to owner only. Positions for all poses are dumped. The user may then copy/paste this into *.POSITIONS* notecards so that the positions will be retained across a position reset, or a full restart or shutdown.

NOTE! *.POSITIONS* notecards should be released to customers with full permissions, to allow them to save positions that they've adjusted to fit their avatars.

If the MLP product has several *.POSITIONS* notecards, the end user may copy/paste all the info into the main .POSITIONS notecard, and delete all the other *.POSITIONS* notecards in the prim. They are no longer needed; all their information has now been amalgamated into .POSITIONS. However, builders may want to keep modules separate; they can do so by manually sorting the entries into their respective *.POSITIONS* files.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
|| (DUMPPROPS) ||

(MLPV2.1)
To add a button that will save prop configurations, use the following line:

LINKMSG Dump Props | 0,-4,1,DUMPPROPS // dump all prop configs

This adds a button named "Dump Props" (or whatever you prefer) that causes all the prop positions to be printed to the screen. They are visible to the MLP product owner only. The user may then copy/paste this text to *.PROPS* notecards for permanent storage.

If the MLP product has several *.PROPS* notecards, the end user may copy/paste all the info into the main .PROPS notecard, and delete all the other *.PROPS* notecards in the prim. They are no longer needed; all their information has now been amalgamated into .PROPS. However, builders may want to keep modules separate; they can do so by manually sorting the entries into their respective *.PROPS* files.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
|| HIDE ||

Adds a button that causes any MLP pose balls rezzed to become invisible. Not many MLP product makers bother with offering this button. The opposite is the SHOW command.

HIDE ''ButtonLabel''

''ButtonLabel'' is optional.

|-
|| INVISIBLE ||

Adds a button to toggle visibility for the prim that the MLP scripts are in. Note: this does not apply to the balls or any other prims, even linked ones.

INVISIBLE ''ButtonLabel''

''ButtonLabel'' is optional.

|-
|| LINKMSG ||

Adds a button that will send a specified link message to other scripts in the object when the button is pressed. This is useful for adding scripted features to MLP2 without having to modify MLP2 scripts.

LINKMSG ''ButtonLabel'' | ''menu'',''primnum'',''lm-num-arg'',''lm-str-arg''

{|{{Prettytable}}
|+
|-{{Hl2}}
!Parameter
!Explanation
|-
|| ''ButtonLabel'' || What you want the button to be called on the menu.
|-
|| ''menu'' || Set to 1 if the script receiving the button will pop up a menu. It causes MLP2 not to repost its menu, to avoid menus stacking up. Set to 0 otherwise -- (note: this doesn't inhibit MLP2's redo menu feature.)
|-
|| ''primnum'' ||
Set to -1 to send the link message to all prims

Set to -4 for just the prim the script is actually in
|-
|| ''lm-num-arg'' || 'num' arg for llMessageLinked()
|-
|| ''lm-str-arg'' || 'str' arg for llMessageLinked()
|-
|}

The menu user's UUID key is passed automatically as the 'key' argument for llMessageLinked().

|-
|| MENU ||

Creates a menu that can be reached from other menus. The first MENU configured becomes the main menu, which the user gets on 'touch'.

A menu's buttons are configured following the MENU statement.

MENU ''ButtonLabel'' | ''who''
or
MENU ''ButtonLabel'' | ''who'' | ''ballcolors''

This creates a menu named ''name1'', and a button named the same on the main menu.

Those who can access it are specified by ''who'', one of the following:

{|{{Prettytable}}
|+
|-{{Hl2}}
!Keyword
!Explanation
|-
|| ALL || Anyone can use it
|-
|| GROUP || Only those who are wearing a group tag that matches the object's group can use it
|-
|| OWNER || Only the object owner can use it
|-
|}

''ballcolors'' is a list of zero to four ball color names, separated by vertical bars ("|"). The color name MUST be in UPPER-CASE. The following ball color names are supported:
{|{{Prettytable}}
|+
|-{{Hl2}}
!Version
!Colors
|-
|| MLPV2 || BLUE PINK
|-
|| MLPV2.1 || PINK, BLUE, PINK2, BLUE2, GREEN, MAGENTA, RED, ORANGE, WHITE, BLACK, YELLOW, CYAN, RED2, TEAL, GREEN2
|-
|}

See under Menu Parameters section for greater details.

For example:

MENU MyMenu | ALL | PINK | BLUE

Creates a menu named Mymenu. Poses in this menu will have 2 balls, a pink and a blue one.

Subsequent menu configuration lines add buttons to this menu, until the next MENU command. There is a limit of 12 buttons to a menu, unless AUTOMORE is used.

Note that, unless you use the MENUORDER directive, these menu items will be offered to users in the usual SL ass-backwards-by-three manner.

How do we get a button to get to this menu? There are two ways.

The first way is the same as with original MLP: use the TOMENU command to create a button to get to this menu:

TOMENU ''MenuName''

The button label must match the menu name. Menu names are case-sensitive.

The second way requires "TOMENU -" configuration lines in the main menu. For any MENU statement where no preceeding TOMENU matches the menu name, a menu button is automatically added to the main menu. (For this to work, the main menu must be filled with "TOMENU -" statements, which create blank spaces for this purpose. When MONO comes out and memory is less of an issue, we will try to make this simpler!)

|-
||MENUUSERS ||

Adds a button that cycles through the access levels governing who can use the menu.

MENUUSERS ''ButtonLabel'' | ''Level''

''ButtonLabel'' is optional.

''Level'' specifies the default, and must be one of the following: OWNER, GROUP, or ALL

If it is set to GROUP, avatars with active group tag amtching the MLP object's group can use the main menu. (You can restrict access to sub-menus on a per menu basis. See MENU above for more info.) The group for the MLPv2 product can set by right-clicking the product and selecting Edit, More >> General tab - Group: Set.

|-
|| OFF ||

Adds a button to turn the MLP system off.

OFF ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "Shutdown!"

When turned off, MLP deletes any balls, turns off all the scripts except for one that will turn it back on again when the owner touches it.

This reduces any contribution the MLP might be making to lag.

Any saved poses or prop configurations that have not been saved to *.POSITIONS* and *.PROPS* files are irrevocably lost.

|-
|| POSE ||

Adds a button for a pose.

POSE ''PoseName'' | ''AnimList''

''PoseName'' is the button label, and also the pose name (found in the *.POSITIONS* and *.PROPS* notecards).
''AnimList'' is a list of animation names, separated by vertical bars ("|").

The number of animations must match the number of ball colors listed in the corresponding MENU configuration.
That is, if the MENU has 3 poseballs, you must provide 3 animation names.

The animations are applied to the balls specified, in order. That is, if the ball colors are "PINK BLUE PINK", three animations should be listed. The first applies to the first pink ball, the second to the blue ball, and the third animation applies to the third ball, which is pink. (See also "Ball Colors" option below for more information.)

The ball positions are specified in a .POSITIONS* file, discussed below. If there is no .POSITIONS entry for a pose, the default pose is used. It's a good idea to always set up the default pose first for a new MLP product, to avoid balls rezzing underground or in other inconvenient locations.

Each animation name must have a corresponding animation in the object's contents, unless it is a built-in animation. Yyou cannot refer to animations by UUID.

|-
|| REDO ||

Adds a button to enable/disable popping the menu back up after making a selection.

REDO ''ButtonName''

''ButtonName'' is optional.

By default, when a user makes a choice on an MLP menu, the menu re-presents itself for further use.

If you offer this command button to users, and they click it, it will toggle this feature off and on.

Few MLP product makers offer this button to users, because turning off the menu coming back can create the perception that something is broken.

|-

|| RELOAD ||

Adds a button to reload *.POSITIONS* and *.PROPS* notecards.

RELOAD ''ButtonName''

''ButtonName'' is optional. Typically, it's "Reset Pos".

This button is useful after changing *.POSITIONS* or *.PROPS* notecards, to verify that you did what you intended. It's considerably faster than a complete reset since the menu isn't reread.

General rule: if you changed a .MENUITEMS card, do Menu reset. If you changed a .POSITIONS or .PROPS card, do Pos Reset.

|-
|| RESET ||

Adds a button to reload *.MENUITEMS* notecards.

RESET ''ButtonName''

''ButtonName'' is optional. Typically, it's "Reset Menu".

In addition to re-reading the notecards, it resets most of the MLPV2 scripts.

|-
|| RESTART ||

Adds a button to do what both RESET and RELOAD do, combined.

RESTART ''ButtonLabel''

''ButtonLabel'' is optional. Typically, it's "Reload".

RESTART is therefore the most thorough command to use for a complete reboot.

|-
|| SAVE ||

Adds a button to save ball positions for the current pose.

SAVE ''ButtonName''

''ButtonName'' is typically "Save Pos".

Immediately after adjusting a pose, always, '''''ALWAYS''''' click this button! You will no doubt, like all of us, lose a few adjustments that you make when you first start out with MLP before this gets scarred into your habits.

'''Caution!''' This is not permanent. Anything that causes the *.POSITIONS* cards to be re-read will wipe these settings out from script memory. A pose is permanent only if it's saved in a *.POSITIONS* card.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

Note: the poseballs cannot be more than 10 metres from the MLP item for this to work.

|-
|| (SAVEPROP) ||

To add a button to save the prop location for the current pose, use the following command:

LINKMSG Save Prop | 0,-4,1,SAVEPROP // save position/rotation for a prop

where "Save Prop" is the button name (and can be whatever you choose).

You use this button after you have adjusted a prop. This stores information about the position, etc, to script memory.

This information will also be printed to the screen (only the owner can see it.) This information should be copied to the .PROPS notecard for permanent storage. You can either do this right on the spot, or arrange and save a whole bunch of prop positions, and then use the DUMPPROPS command to print out all the prop info at once for copying and pasting to the .PROPS notecard.

'''Note:''' a prop cannot be more than 10 metres from the MLP item for this to work.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on this when using modules.

|-
||SHOW ||

Adds a button that causes any MLP pose balls rezzed to become visible.

SHOW ''ButtonName''

Not many MLP product makers bother with offering this command. The opposite is the HIDE command.

|-
|| STOP ||

Adds a button to delete any balls and unseat any participants.

STOP ''ButtonName''

''ButtonName'' is optional.

Note though that, unlike OFF (covered above) it does not significantly reduce any contribution the MLP system might be making to lag.

|-
|| SWAP ||

Adds a button to swap positions between the first and second balls for any pose.

SWAP ''ButtonName''

''ButtonName'' is optional.

It has no effect on any third or fourth balls in a pose. However, this behavior may change in future versions.

Note: In some animation menuing systems such as XPOSE (as of summer 2008), hitting the SWAP button only swaps the current pose; the swap is lost at the next pose. In MLP, the SWAP is maintained until a user chooses to SWAP back.

IMHO, the XPOSE behavior is better, and I might change this in a future version. [Lear Cale]

|-
|| TOMENU ||

Adds a button to get to another menu.

TOMENU ''MenuName''

''MenuName'' is used as the button label, and must exactly match the name of the menu (case-sensitive).

If a menu (say, "Foo") exists, and there is no "TOMENU Foo" statement on a preceeding menu, and if there are unused "TOMENU -" statements for the main menu, a button for "Foo" is added to the main menu, using up a "TOMENU -" line.

Don't worry about supplying lots of TOMENU - slots on your main menu. If MLPv2 doesn't need them, it will just ignore them!

Note that if you are offering [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| modules]], you must provide some "TOMENU -" slots on your main menu for the module menu buttons to appear.

|-
|| Z* ||

The Z command adds a button that allows end users to easily adjust for themselves the height of the poseballs.

Z ''sign'' ''number''

For this command (and only for this command!), no spaces are allowed between the items (Z, ''sign'', and ''number). For example:

Z+1
Z+5
Z+25
Z-1
Z-5
Z-25

The numbers are treated by MLP as being a measurement in centimetres. Each time a user clicks a button, say Z+5, the height will be increased by 5 centimetres. If they have previously clicked the Z+5 button, then the height will be increased by an additional 5 centimetres.

A Z-5 button, if offered, would decrease the height by 5 cm.

Z adjustments chosen by users apply to all the poses, not just the one currently being used.

Note: the ongoing tally of these adjustments are stored in the Object Description of the prim that holds the MLP scripts, so any descriptions you put there will be replaced.

To clear them, you need to either use the Z buttons to set the offset back to 0, or, edit the object, select the MLP prim if it's not the root prim, and clear the description.

Traditionally, MLP product makers have put these Z commands under the OPTIONS menu.
These were recently moved to a HEIGHT submenu, to make room for the Props commands.

See the [[#TIP.21_OPTIONS_Menu_2| Tip! Options Menu]] for more info on how exactly to do this.

|-
|}

See the [[#TIP.21_OPTIONS_Menu_2| Tip! Options Menu]] table at the end of this page for helpful advice on arranging many of these menu commands into a tidy sub-menu.

=== MENU PARAMETERS ===

Info that you can add to MENU statement lines.

==== Ball Colors ====

If a MENU has no pose ball colors listed, it should have no POSE buttons.

When, however, a particular MENU will contain POSE statements in it, then the MENU statement must be followed by a set of ball colors to be used for all poses in this particular menu.

One to four balls can be specified, supporting poses for up to four participants. The balls are rezzed as necessary when a pose in the menu is selected.

Supported colors as of summer 2008 are:

{|{{Prettytable}}
|+
|-{{Hl2}}
!
!
!
!
!
|-
|| PINK || PINK2 || BLUE || BLUE2 || WHITE
|-
|| GREEN || GREEN2 || RED || RED2 || BLACK
|-
|| MAGENTA || ORANGE || YELLOW ||CYAN ||TEAL
|-
|}

PINK2, BLUE2, RED2, and GREEN2 are darker their respective colors with no number after them.

Note: The colors must be given in uppercase as shown above.

Examples:

MENU boy-girl | ALL | BLUE | PINK

MENU Boy Only | ALL | BLUE | HIDE

MENU Girl Only | ALL | PINK

MENU Anyone | ALL | GREEN

MENU 3Some | ALL | PINK | BLUE | PINK

MENU 4Some | ALL | PINK | BLUE | PINK | BLUE

=== POSE PARAMETERS ===

Info that you can add to POSE statement lines.

==== Animations (Facial) ====

In the POSE line, add the suffixes listed below to the animation names to cause facial expressions. (You don't change the animation name in inventory, just add the suffix to the anim name in the POSE line.)

NOTE: There is currently (April 2011) no menu button to allow MLP users to turn facial expressions off and on.

{|{{Prettytable}}
|+
|-{{Hl2}}
!suffix
!expression
|-
|| * || mouth open
|-
|| ::1 || mouth open
|-
|| ::2 || surprise
|-
|| ::3 || tongue out
|-
|| ::4 || smile
|-
|| ::5 || toothsmile
|-
|| ::6 || wink
|-
|| ::7 || cry
|-
|| ::8 || kiss
|-
|| ::9 || laugh
|-
|| ::10 || disdain
|-
|| ::11 || repulsed
|-
|| ::12 || anger
|-
|| ::13 || bored
|-
|| ::14 || sad
|-
|| ::15 || embarrassed
|-
|| ::16 || frown
|-
|| ::17 || shrug
|-
|| ::18 || afraid
|-
|| ::19 || worry
|-
|| ::20 || sleep
|-
|| ::21 || random (for MLPv2.4v or higher, produces random surprise / pleasure expressions)
|-
|}

''Note: 20 is a combination of disdain and smile, the closest that could be found for sleep.''

There must be NO SPACE between the animation name, and the suffix. Example:

POSE Sleep 01 | Sleep 01 femalesleep::20 | Sleep 01 malesleep::20

To make the expression happen periodically rather than constantly, add another extension and the length of the repetition cycle (in seconds).

For example, to use MyAnim with open mouth every 5.5 seconds:

POSE Mypose | MyAnim::1::5.5

If during menu boot you get an error that says "animation xyx not found", but you know that animation xyx really is in there, check to see that you didn't put a space before the expression suffix after all.

Note that this suffix appears only in the POSE line of a MENU; the actual name of the animation in the object's contents folder should *not* be changed to have this suffix. (Many animations are sold no mod; so you wouldn't be able to, anyway.)

== .POSITIONS* NOTECARDS ==

The .positions notecards, as their name implies, provide a place for storing information about positions of the poses in the menu.

As long as any position adjustments you have made have only been saved via the SavePos buttons, assume them to be temporary. They are only saved in script memory, and script memory is volatile. If you hand the MLP v 2.0 object to someone else, or if your sim crashes really terribly or if the script blows up with a stack-heap error, etc ... you may lose all the work you'd thought you'd saved.

The *.POSITIONS* notecards provide a safety against losing your work.

You create *.POSITIONS* notecards by your manually copying and pasting in information from the "Save Pos" or "Dump Pos" buttons (SAVE and DUMP commands described above). SL does not allow scripts to write data to notecards, so you must do this yourself.

NOTE: If the .POSITIONS notecard is no modify, or is placed in a no modify prim, people will not be able to open the notecard at all. This is a SL system limitation.

The lines in the .positions notecard look something like this:

{LieHold1} <-0.253,0.157,0.285> <0.0,0.0,0.0> <-0.146,0.000,0.177> <0.0,0.0,90.0>

where "LieHold1" is the name of a pose (from the POSE statement in a *.MENUITEMS* file).

The 4 vectors in the above example represent in order:
first ball position, first ball rotation, second ball position, second ball rotation

If there are 3 and / or 4 balls also involved in a given pose, then the pattern repeats on for them as well.

If you rename a pose in the menu that you have already stored a position in the notecard for, be sure to edit the .positions card, locate that pose in it, and give it the new name as well to match.

Be sure to purge out position lines for which menu items no longer exist. This is one instance in which tidiness really does pay off: all that old, unneeded position information is read into the scripts' memory, which can make you think that your MLP product is "full" (that fatal stack-heap message) and can't hold any of the other poses you had planned to add.

See [[#TIP.21_TIP.21_Modules_--_multiple_.menuitems_and_.positions_notecards| Modules]] for help and more information on .positions cards when using modules.

Note: Comparing positions to menu items is easier and the work of seconds as opposed to minutes if you keep the positions information cleaned up. See [[#TIP.21_Positions_Notecard_tidying| the tip on tidying .POSITIONS notecards]], if you wish to do this extra (not-required) work.

Remember that purchasers of your MLP2 product should be able to adjust poses to fine-tune them to their own heights, sizes, etc. All *.POSITIONS* notecards should be supplied to end-users with MODIFY rights so that they too can permanently save all their hard work. {{Footnote|Some furniture makers prefer to sell their furniture no mod so that others can't just disassemble it and copy the dimensions of the pieces and thereby duplicate the furniture -- fair enough. However, if the .positions notecard is in a no-mod prim, notecards inside it will also be no mod.

There doesn't seem to yet be a way around this. While llAllowInventoryDrop in a small add-on script might seem promising (and the change event could be set to delete the old .positions card), the problem remains that by then, a fresh positions card the user had dropped in would already be named .positions 1, an invalid file name. Because you can't rename objects inside a prim, you'd have to then have your script delete that .positions 1 card as well, and then invite the user to drop his/her fresh .positions notecard in a second time, which would be very confusing. Or, using the LINKMSG feature, create a button that tells a script to delete the .positions notecard, and then invites the user to drop a new one in. But you'd want that script to ask the user if s/he really knew what they were doing.

Note as well that a no-mod prim prevents the option of allowing customers to purchase add-on modules for you -- unless provision is made for an llAllowInventoryDrop.}}

(MLPV2.5) to set a memory limit on the ~memory script, use a line like this:
{MEMORY} <''MemoryLimit''>

== SEQUENCE NOTECARDS ==

SEQUENCE | seqence-name | NOCHAT 
use NOCHAT to inhibit chatting of poses 

MENU | menu-name 
set number & colors of balls 

POSE | pose-name | chat-chan | chat-message 
start a pose (chan & message are optional; message is whispered). 

AVWAIT | 0 1 2 3 | chat-message-if-waiting 
pause the entire sequence set until the balls listed are sat on (0 1 2 3 in this example) 
 
examples: 
to wait for two people: AVWAIT | 0 1 | Waiting for both people to get on the balls 
to wait for three people: AVWAIT | 0 1 2| Waiting for three people to get on the balls 
to wait for four people: AVWAIT | 0 1 2 3| Waiting for four people to get on the balls 
 
Only have one (1) AVWAIT line per sequence set, or you may get stack-heap blow-ups. 
 

WAIT | wait-seconds 
pause before executing next command 

GOTO | label-name 
go to a label, to loop a portion of a sequence 

LABEL | label-name 
set a target for GOTO 

REPEAT 
repeat the whole sequence 

SAY | chat-chan | chat-message 
say the given text on the given chat chan 

WHISPER | chat-chan | chat-message 
whisper the given text on the given chat chan 

SOUND | sound-name | 0 to 1.0 
plays sound from '''prim contents''' at volume 0 to maximum 

MEMORY | ''MemoryLimit''

(MLPV2.5) Sets memory limit of the ~sequencer script.

NOTE: The chat messages can include the first names of participants using /0 for avatar on first ball, /1 for av on 2nd ball, etc.

=== Sequence scripting debugging ===

(very advanced) 

Put any one of these are the very top of your sequences notecard, outside of any defined sequence, in order to turn on debugging for the sequences script:

debug | 1 
sequence start/stop 

debug | 2 
echo each command as executed 

debug | 4 
avatar hop on/off 

debug | -1 
all debugging 

=== Sequences and Props ===
Yes, props will still work for items used in sequences.

== TIPS ==

{{box|TIP! ADJUST Beams |Finding the ADJUST beams hard to see? First, make sure that you have set world to noon. If you still find them difficult to edit, haul the ~ball out of your prim.

Edit the ~ball script in it, and look for this part of the script in the listen event:
<lsl>
} else if (str == "ADJUST") {
llSetAlpha(0.2,ALL_SIDES);
llSetText("Adjust",<1.0,1.0,1.0>,1.0);
llSetScale(<0.1,0.1,5.0>);
</lsl>
It's the llSetAlpha setting it to only .2 that makes it hard to see. Try it at .4, or .6, or higher.

Save, take the ball into inventory, then delete the old one in the prim and replace it with your adjusted one.}}

{{box|TIP! Animations Caveat|
Though all animations will work with MLPv2, not every single one you come across will work reliably.

Some animations, if they happen to have been made by the creator in a certain way, will work as expected after certain other animations, but not after others. You'll get different results depending on which pose you ran last.

The problem is animations that have their hip position the same in their T frame and first animation frame. They just won't work with MLP.

Example: if you have 3 anims, 2 with hip positions set and one without, the hip position for the one without will be the hip position left over from whichever of the last two anims you used. It's the way SL animations work. If there's no change in any joint between the "T" frame (first frame in bvh file) and the first animation frame (second frame in bvh file), SL ignores that joint for the whole animation. And when all other animations are turned off, this means that these joints are left free to do whatever SL does with them. It leaves them as they were from the previous anim, or overrides them with SL builtin motions like typing, head movement, arm pointing while editing, etc.

The values in the hip joint aren't important; what's important is that that they *be* different between T frame and 1st animation frame. For MLP, you want every joint in the animation to have been moved (except head, if you want it to be able to move with the mouse.)

This problem can be avoided when making animations if you move the hip even just 1 degree, and normally the stomach 1 degree in the opposite direction.

So sadly, in the course of things, odds are, you're just going to buy some animations that just ain't going to work with MLP. And there is no way of knowing in advance.

When creating animations for MLP, Lear Cale highly recommends using priority 3. This disallows the typing while chatting animation, but allows head movement (if the head joint is not moved in the beginning of the animation). It also allows someone to create a priority 4 animation and run it to override MLP animation behavior (until the next pose is selected). }}

{{box|TIP! Animations Permission|
The ball user, upon first sitting on a ball, will be asked permission to animate them. S/he must say yes to yes, or they will end up just "hovering" on the poseball.

The "permission pls" menu often gets hidden behind the MLP main menu (if you are the one who called up the menu.) You need to click the ">>>" to cycle through the menus on your screen to find the permissions prompt. This is SL behaviour and there's no way to fix it, other than turning "redo" menu off in MLP.

NOTE: in their great wisdom, SL modified the 1.20 viewer to show something other than ">>>" for this button. Damn them.

If you are wondering why permission must be asked, when normally sitting on something is taken as implying permission to be animated, it's because it's not actually the balls that are doing the animating -- it's a script in the MLP. Because one script is not allowed (for security reasons) to pass permission to another script, the scripts in the MLP itself can't take advantage of any permissions the poseballs have acquired.}}

{{box|TIP! Animation Synchronization |Animations appear to start separately per ball once an avatar sits on it. Thus, they're not in sync.

In fact, the animations are started at the same time. However, it takes time for the animations to get sent between SL and the client, so as a result they don't look synchronized.

There is no simple feature in MLPV2 to automatically synchronize poses as such. You can manually synchronize by shifting to another pose and then shifting back again. (Starting with

There is no built-in feature to automatically synchronize, as there is with couples danceballs. Prior to MLPV2.4z4, you can manually synchronize by changing to another pose and then back. Starting with MLPV2.4, you can manually resynchronize by selecting the same pose again.

There is an advanced feature of MLPV2 that you could use to get automatic periodic synchronization: Sequences.

A sequence is simply a list of poses that MLPV2 will play at the touch of a button, with the option to repeat the sequence or a portion of the sequence. See the example sequence in the distribution. You could set up a simple sequence that plays one pose, waits some time that's at least as long as the animations, and repeats, like this, which goes in .SEQUENCES notecard:
<pre>
SEQUENCE | snuggle-seq | NOCHAT
MENU | couples
POSE | snuggle
AVWAIT | 0 1
POSE | snuggle
WAIT | 30
REPEAT
</pre>

}}

{{Box|TIP! Animations and balls|
Animations remain in the main MLP object; they are never placed in the poseballs. The animations are played from within the main MLP product; the poseball is just the delivery vehicle. Consequently, poseballs can be deleted or lost without the main product being affected. And, the poseballs themselves are just copies of the one inside the MLP product.

A ball will commit suicide if left behind somewhere (the MLP object needs to be within 20 metres.)}}

{{Box|TIP! Ball text|
By default, both the poseball floating text and the right-click menu 'sit' choice text is the word "LOVE". You can set these to whatever you want by editing the description of ~ball in object contents. If you type in that field the word "none" (without the quotes), or just type in a space or two, there will be no floating text, and the right-click menu 'sit' choice text becomes the system default of just "Sit Here" (for English viewers).}}

{{Box|TIP! Phantom Balls|
To make your balls rez as phantom, put an asterisk in the ~ball description line.}}

{{Box|TIP! More than 6 balls|
There are no plans to expand beyond 6 balls active at once. If this is totally necessary for you, you'd be better off just going with a product that actually supports the number of avatars you want, such as XPOSE. You'll save yourself and your customers time and confusion by going with a product that was designed to handle larger numbers from the ground up.}}

{{Box|TIP! Balls are buried in furniture|
Sometimes when you position the balls correctly for an animation, the balls end up buried in furniture.

This is a property of the animation: the hip position in the animation is too high. While it is in theory possible to fix this in MLP scripts, it would be hard to do, especially without using up lots of memory for poses.

Most people know that when this happens they can select another pose first, jump on, and then change to the pose they want. Consequently, the simplest workaround is to make sure the first pose in each menu has all balls visible.

Alternatively, you could ask the creator of the animation to adjust it, but the chances of them doing this just for your piece of furniture are not high.

If someone stands up while on balls that are buried in furniture, they will get ejected from the furniture unceremoniously. This won't happen if they use the STOP button on the menu instead.

Vesta Martynov suggests another workaround -- changing the offset that the ball is rezzed at. (Note that this will apply to all poses, not just the problem ones.) Her work-around is, before you start on a MLP product, to take the ball out and rez it on the ground. Edit the script in the ball, and search for this SitTarget line:

llSitTarget(<0.0,0.0,0.1>,ZERO_ROTATION);

The .01 there is the vertical offset. She changes it to something like this:

llSitTarget(<0.0,0.0,-0.25>,ZERO_ROTATION);

Save your changes, take the ball back into your inventory, and use it to replace the one that was inside the MLP.

After you do this, all the balls and animations will be lifted, so you can go in and lower the animations, but you will no longer have balls sinking into your furniture.

(Vesta Martynov, conversation in MLP group, 2009-06-11 19:46)
}}

{{Box|TIP! Ball scripts|
When updating your version of MLPv2 scripts, make sure you update the script in ~ball as well.
}}

{{Box|TIP! Changing the number of active Balls|
When going from a pose in a menu with 4 ball colors to a pose in a menu with 2 balls, the 2 balls are deleted. Assuming you're not using phantom balls, if the balls rez again (say you go back to a pose in a menu with 4 balls), the balls should bump anyone standing in their way out of the way. People wanting to use the newly re-rezzed balls and be animated by them will have to hop back on them. When changing the number of balls active, bear in mind that the number of animations in a POSE line must match the number of ball colors in the MENU line above. You can't mix poses with 2 anims and poses with 4 anims in the same menu section. This is not supported.}}

{{box|TIP! Default Pose |
You need to set position coordinates for the default pose. To do this, on the MLPV2 main menu click the "adj-default" button, then ADJUST the default pose position, save, and copy the coordinates to the .positions notecard as per normal. When you have finished, delete the .menuitems.zz-default notecard from the prim.

If on the main blue menu you do not see a button called "adj-default", do the following steps:

1) Create a notecard with the file name of: 

.Menuitems.zz-default

Paste the following in as content:

<pre>
// The "default" pose below is for adjusting "default" position.
// Since there are currently no other items in this menu, you can comment out the whole menu 
// or simply delete this file when you've done that.

MENU adj-default | ALL | BLUE | PINK | BLUE | PINK
POSE default | sit_ground | sit_ground | sit_ground | sit_ground
SWAP
ADJUST
SAVE Save Pos
DUMP Mem Dump
BACK
</pre>

Tip! If the product you are making is only for 1 or 2 people, then you don't need to include all 4 balls that are listed in the menu above. For a solo product, you can just do instead:
<pre> MENU adj-default | ALL | BLUE
POSE default | sit_ground
ADJUST
SAVE Save Pos
DUMP Mem Dump
BACK
</pre>

Drop this notecard into the prim where you are working with MLPV2.

2) Make sure the main menu notecard has a spare TOMENU slot to fit the adj-default choice into:

TOMENU -

3) restart the MLPV2 product.

4) ADJUST the default pose position, save, and copy the coordinates to the .positions notecard as per normal.

5) When you have finished, delete the .menuitems.zz-default notecard from the prim.}}

{{box|TIP! Notecard Editing|
If the MLP prim contains many animations, access to a notecards contents can be PAINFULLY slow.

First, make sure the prim is ready to let you open the notecard. Right-click on the notecard that you see in the contents folder. If you get a big menu of choices, rather than just the standard 4 of Open, Properties, Rename, Delete, then the prim isn't ready to let you open the notecard. You simply have to wait. Sometimes, you may need to wait up to 2 to 4 minutes. Yes, ridiculous -- but that's SL.

Make all your changes before saving. Once you save, the notecard you have open may no longer be the notecard that is inside the prim (sic.) Once you have saved, even if you did so by accident out of habit, leave the notecard opened for a few seconds, then close it, and wait until the prim is ready to let you open it again if you need to do further edits.

Note: as of summer 2008, the wait time for notecards to open from inside prim folder contents seems to be getting increasingly worse, and the system seems to be getting increasingly intolerant of allowing repeated saves on the same opened notecard. Thus, the advice to close and re-open after a save.}}

{{box|TIP! Modules -- multiple .menuitems and .positions notecards|
There can be several *.MENUITEMS* and *.POSITIONS* notecards in an MLP product (where "*" is any text that's allowed in a notecard name). This is to allow the addition of modules to the product. This allows you the option, for example, of letting customers purchase an MLP product for couples, and then coming back later to purchase an odd-on for 3Somes. Customers then pad home, edit the contents folder of their MLP product, plop in the add-on stuff, and restart their MLP.

'''Note:''' a module's menu appears as a button on the MLP product's main menu. For this to actually happen, you *must* provide a blank slot for it by supplying a TOMENU - parameter on the main menu. Normally, there should be a bunch of these in the main menu.

The add-on will consist of a .menuitems card, a .positions card, and the associated animations (with permissions set correctly.)

For you as a vendor to make a module, you create a .MENUITEMS.xxx notecard, and a corresponding .POSITIONS.xxx notecard (where xxx can be anbything and is normally thought of as the name of the module.) If this module uses props, you also create a .PROPS.xxx notecard.

A *.MENUITEMS* card for a module should have no default or stand pose, etc. It normally has only the actual menus being added and the associated poses.

Example:

<pre>MENU myAddOns
TOMENU myAddOn1
TOMENU myAddOn2

MENU MyAddOn1 | ALL | PINK | BLUE
POSE Whoohoo! | Bump1 | Bump2
POSE Zowee | Grind1 | Grind2

MENU MyAddOn2 | ALL | PINK | BLUE | PINK
POSE Fubar | Dance1 | Dance2 | Dance3</pre>

To test, you would then drop all associated notecards (.menuitems.xxx, .positions.xxx and .props.xxx if using) into the MLP product, along with the necessary animations and props, of course, and restart the MLP product. (Of course, if you were selling it as a separate add-on, you would after remove the above components from the main product, and package them separately.) Remember if you make any pose position adjustments during testing that the position information should be copied and pasted to the relevant .positions.xxx notecard -- not the main .positions notecard, because you are preparing a sold-separately module. Ditto for any prop adjustments, which go into the .props.xxx notecard.

Purchasers of an add-on need to always keep that .menuitems.xxx notecard in their product. However, the .positions.xxx and the .props.xxx notecards have, in a way, a limited lifespan. When you do a DUMP command, you copy / paste all that info into the notecard named simply .positions -- that is the main .positions notecard. Or, into .props notecard, in the case of a DUMPPROPS command. All the info that the subsidiary .positions.xxx and .props.xxx notecards hold is now amalgamated into the main notecard, and the subsidiary ones are no longer needed. They can be deleted. But to be clear, do not delete their corresponding .menuitems.xxx notecards.

Multiple .positions notecards are read by the script in the same order they appear in object inventory.

Note: it is best to be using the MENUORDER directive when offering modules.}}

{{box|TIP! Sub-Menus|Can you add a module menu ie: .MENUITEMS.myposes and have it show as a top menu item with sub menus? Something that would give a My Poses button that when clicked would open a sub menu dialog with buttons for my poses 1, my poses 2 etc.

Abolutely, and that's the best way to do it.

Start your .MENUITEMS.mystuff with the parent menu. Fill it with "TOMENU" statements like this:

<pre>
MENU WhizBangInc | ALL
TOMENU WBI-cuddles
TOMENU WBI-fun
TOMENU WBI-freaky
TOMENU WBI-illegalin42states</pre>}}

{{box|TIP! Options Menu|
By tradition, most of the common functionality command buttons are stored under a MENU called "OPTIONS".

Such commands include ADJUST, SAVE, DUMP, Show/Hide (aka INVISIBLE), MenuUsers, BallUsers, Chat, Dump Props, Save Prop, etc.

As well, the z commands for height adjustment were traditionally offered there as well.

With the rapidly-increasing number of functions available within MLPv2, however, the OPTIONS submenu is becoming very crowded.

Consequently, consider taking all the z height adjustment options out from under OPTIONS and put them in a sub-menu like this:

<pre>MENU HEIGHT | ALL
Z+1 //adjust Z = height offset in cm - use any integer to set the step size
Z+5
Z+25
Z-1
Z-5
Z-25
BACK
</pre>

Then, in the OPTIONS menu, just make this button linking to the HEIGHT submenu:

TOMENU HEIGHT}}

{{box|TIP! Positions Notecard tidying|
The lines in the .positions notecard look like this when copied and pasted in directly from chat:

[7:46] Animated Living Sofa Combo Couple & Solo 2.1e: {Lie&Hold} <-0.413,0.130,0.245> <1.0,-9.0,-0.9> <-0.539,0.207,0.155> <-0.1,-8.9,-1.1>

The extraneous chatter before the {LieHold1} parameter in the curly brackets (aka braces) is ignored by the scripts, so there is no need to delete it.

Still, if you as an MLP professional wish cleaner, easier to read content (which is a boon for easier maintenance and troubleshooting), then copy the contents of the .positions card in question into a simple text programme (such as Notepad on a Windows PC), and using the example above, you would search for:

[7:46] Animated Living Sofa Combo Couple & Solo 2.1e: [including the final space at the end of it]

and just replace it with nothing, and then paste the cleaned up text back into the .positions card.

The cleaned up text then looks like this.

{LieHold1} <-0.253,0.157,0.285> <0.0,0.0,0.0> <-0.146,0.000,0.177> <0.0,0.0,90.0>

You may wish to also to SORT the positions in alpha order to make it easier to find them.

So that instead of:

{Massage} <-0.230,-0.133,-0.287> <0.0,0.0,-86.0> <-0.287,0.259,0.161> <0.0,0.0,-82.0> 
{Sprawl 1} <0.960,0.000,-0.190> <0.0,0.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 
{Lie 01} <-0.115,-0.069,0.694> <0.0,0.0,-90.0> <-32.417,-199.035,-518.585> <0.0,0.0,0.0> 
{Couch 1} <-0.179,0.001,0.143> <0.0,-19.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 

You have 

{Couch 1} <-0.179,0.001,0.143> <0.0,-19.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 
{Lie 01} <-0.115,-0.069,0.694> <0.0,0.0,-90.0> <-32.417,-199.035,-518.585> <0.0,0.0,0.0> 
{Massage} <-0.230,-0.133,-0.287> <0.0,0.0,-86.0> <-0.287,0.259,0.161> <0.0,0.0,-82.0> 
{Sprawl 1} <0.960,0.000,-0.190> <0.0,0.0,0.0> <0.700,0.000,0.700> <0.0,0.0,-180.0> 

You can do this sorting in seconds by copying & pasting the (cleaned-up position chatter) into something such as Microsoft Word, or a spreadsheet, and telling it to sort, and then copying & pasting the sorted positions back into the .positions notecard. (This really works best though if you have stripped the initial chatter info from them.) }}

{{box|TIP! Notecard reading order|
Q: I have a question about animation packs. I know the readme notecard says that the scripts read the notecards in alpha order. If I were to name the notecards as A, B, and C would the buttons on the menu then be in that order as well? I'm picky--I like my buttons in a certain order.

A: Yes.}}

{{Box|TIP! Portable use of an MLPv2 product|
Attach the MLPv2 object to your HUD. You can use its default shape and color for a clickable bar on one of the edges of your screen (to move HUD position: Right-click and Edit it and use the arrows). While in edit mode, you can also edit color/transparency/size/position.

Note that the balls will appear relative to the initial MLPv2 position. Adjust the height offset with a (Z) command.}}

{{Box|TIP! Props|
Props are objects the MLP product will rez for poses. When you choose another pose or hit STOP, any rezzed prop disappears. If you delete the MLP object, any prop will disappear within 3 minutes.

Props support starts with MLPV2.1.

To add a prop, edit a .PROPS notecard or add a new one (named .props.xxx where xxx is the name of the module, for a modular config). Copy the following example line and paste it into your .PROPS notecard.

<pre>| mypose | myobject | <1,1,1>/<0, 0, 0></pre>

Then: 
*Replace "mypose" with the pose name;
*Replace "myobject" with the name of the prop object. The object name cannot contain vertical bars;
*Add the "~prop" script (from inside the "~pillow" object that comes with the standard distribution) to your prop object, and drop your prop object into the MLP prim's inventory. The prop and everything in it will need to be copiable for next owner;
*Make sure your menu has the SAVEPROP and DUMPPROPS command on it.

Restart the MLP, and then select the pose. The prop should appear. It might be underneath the MLP object, so look around -- it may be best to do this using a single prim MLP floating in the air, the first time so that it doesn't rez in the ground!

Move the prop to where you want it, and use MLP menu command "SAVEPROP". To make the change permanent, select the chat information that is printed out on your screen (including the first vertical bar, and optionally any text before it) and replace the corresponding line in your .props.xxx file. Or, do all your props and use DUMPPROPS. (This procedure is similar to that for saving positions in .positions.xxx notecards.)

To get MLP to reread .props.xxx files, restart the product (which resets positions as well as props).

Keep in mind that props and positions are saved as two separate steps. If you adjust a pose and its prop, you need to save both pose position and prop.

Tip: We are all so used to hitting the button to save positions. If you find that a prop position isn't saving, check your chat history to make sure you didn't hit the save position button instead of save prop just out of habit!

 '''Hand-held Props''' For props to be used as hand-held items, use the ~give script add-on found here [[MLPV2_Give_Item_Add-on]] and have people wear the items. 

'''Number of Props''' 
For any pose, you can have at most one prop. If you need more than one prop to rez, you'll have to link the items so that they can be treated by MLP as one object. Alternatively, if you have a scripter friend to help you, you might try having the rezzed object rez another object from its contents. Your scripter friend would need to make the rezzed child object listen for the same die command as the main object that was rezzed.

Or, you *might* perhaps try the rezzed object as a coalesced object, making sure that each item has in it a script (created custom for you by a scripter friend) so they can die when required to -- experiment with that somewhere in the open at first in case it goes all over the place. 
}}

{{Box|TIP! STOP in every menu|
STOP and BACK buttons should be on every menu.

Why STOP on every menu? It solves so many problems. For example, if you use STOP, you don't get ejected like a James Bond villain if the poseball happens to be buried in the furniture. After moving or rotating a bed, STOP resets the position (Lear put in code to do this automatically, but there's no event that tells you when rotation stops.) And no doubt, SL and MLPV2 have bugs, and I've seen funky and unrepeatable oddness that STOP fixes in a jiffy. Plus it makes the poseballs go away.}}

{{box|TIP! Scripting -- call on MLP Menu from another script via linked msgs|
If you just want the MLP menu to come up from another script in the object (same prim or different one), simply do what the ~touch_passer script does (the llMessageLinked() call). If your script is in the same prim as MLP scripts, change LINK_ALL_OTHERS to LINK_THIS.
}}

{{box|TIP! Scripting -- call on MLP Menu from another script via chat|MLP listens for menu responses on this channel, minus one:

<pre>
// Return a channel number that's based on the prim's key -- unique per object
integer channel() {
return (integer)("0x"+llGetSubString((string)llGetKey(),-4,-1));
}</pre>

Note that the key here is the key of the MLP object.

Oh, warning: it also checks to see if the chat came from the same user as whoever used the menu recently. If they don't match, it sends a menu (dialog) -- in this case, to your object, which won't do anything. So, I suspect that this will work only if you keep users from getting access to the MLPV2 menu directly.}}

== API ==

When the MLP is ready for use, it sends out a linked message on channel -11003 saying "READY"

llMessageLinked(LINK_SET, -11003, "READY", NullKey);

{{Footnotes}}

== Illegal Pirated Animation Kit FYI ==
http://wiki.secondlife.com/w/index.php?title=62_Animation_MLP_Set

For "free" status of Sexgen animation kit released October 2011 by Stroker Serpentine, see here: https://wiki.secondlife.com/wiki/Stroker_Serpentine_Sexgen_Animation_Set

[[Category:MLPV2]]

MLPV2 Addons

2014-01-08T00:00:11Z

Chaz Longstaff:

{{Navbox/MLPV2}}

*[[MLPV2 Give Item Add-on]] (Item or Items, one at a time, NOT in folder)
*[[MLPV2 Give Folder Add-on]] (Item or Items, all at once, in folder)
*[[MLPV2 Give Items in Folder to a Specific Person]]
*[[Check Animations Permissions Tool]]
*[[Cleaner MLP Say|"Cleaner" MLP Say]]
*[[MLPV2_Texture_Changer_Add-on]]
*[[MLPV2 Color Changer Add-on]]
*[[MLPV2_Props_Texture_Changer_Add-on]]
*[[MLPV2_Ambiant_Sound_Add-on]]
*[[MLPV2_RLV_Plugin]]
*[[MLPV2_RLV_Capture_Plugin]]
*[[Reset_from_Child_Plugin]]
*[[MLPV2 Ball Script with more flexible parameters]]
*[[MLPV2 Menu Maker Helper]]

===Patches===
* [[MLPV2_Balls_Patch]]: Use different balls for ~ball0...5
* [[MLPV2_LockGuard_plugin]]: Add LockGuard support to MLP2

===Tools===
*[[Script to report on who made which animations in a prim]]

[[Category:MLPV2]]

MLPV2 Give Item Add-on

2014-01-07T23:58:00Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

Add on tool for MLPV2 that puts a button on the MLPV2 menu that, when clicked, gives a user an object (or multiple objects) that you wish them to use with an animation. If you are giving multiple items, they are giving in succession one after the other -- that is, each is given separately, rather than all being given at once in a folder.

By Chaz Longstaff, June 2008.

Example:
LINKMSG TieMeUp | 1,-4,987789,Cuff1#Cuff2#Cuff3#Cuff4##Wear these four cuffs. 

Steps to use: 
#Copy and paste everything below the double-line on this page into a script called, for the sake of argument, "~give" (the script name is actually irrelevant; you may call it kumquat if you wish;) 
#Drop the script into the prim where you have the rest of the MLPV2 scripts; 
#Add the object that you wish to give out. Usually, it is either a prim object, or clothing. Note that this object to be given out needs to have both copy and transfer permissions set on it; 
#Add to the menu in an MLPV2 menu notecard the following line: 

LINKMSG MyButtonName | 1,-4,987789,NamesOfObjectToOffer##MsgToPerson 

In the above line, there are three elements for you to customize:
*MyButtonName -- the wording that you want to appear for the button on the blue menu
*NamesOfObjectToOffer -- the name(s) (case and spacing sensitive) of the object(s) you are offering. If you are offering more than one, separate them with a hash mark (aka number sign, pound sign) # . Example: Item01#Item02#Item03 . If you are not offering more than one, don't use a # separator here.
*MsgToPerson -- A message to be instant messaged to the person being offered the item, so they know what it is for, and don't think it's a random spammer or griefer passing by, etc.

Note that NamesOfObjectToOffer and MsgToPerson are separated by a ## separator (two hash marks.)

What you don't need to change in the above sample line:
* 1 -- makes it so the MLPV2 menu doesn't reappear, so the user can see the accept-object menu
* -4 -- the value of LINK_THIS, meaning, send this message to this prim only. (Use -2 if the ~give script is in a different prim.)
* 987789 -- This is the number the ~give script looks for to detect a message to it.

<lsl>
// Add-on by Chaz Longstff for MLPV2 by Lear Cale. June 2008.
// Function: gives object to someone on an MLPV2 ball
// MLP button: LINKMSG MyButtonName | 1,-4,987789,NamesOfObjectToOffer##MsgToPerson

// In a menu card, format a menu button like this, for example:
// LINKMSG TieMeUp | 1,-4,987789,Cuff1#Cuff2#Cuff3#Cuff4##Wear these four cuffs.
// In this example, TieMeUp is the button name
// 1 means whether to make the MLPV2 menu go away or not.
// Generally set it to 1 as per the example, as otherwise the user
// might not see the accept prompt for the inventory being given.
// -4 is the value of LINK_THIS, meaning, send this message to this prim only.
// (Use -1 if the ~give script is in a different prim.)
// 987789 -- don't change this, this is the link message number
// Cuff1#Cuff2#Cuff3#Cuff4##Wear these four cuffs.
// The items separated by # are the items to give,
// followed by a message to be instant messaged to the recipient
// of the object. It's good to include a msg, so that they don't think
// it's a griefer trying to hand them something. Notice that the list
// of objects to give and the accompanying msg, are separated by ##

default{
link_message(integer from, integer num, string str, key id) {
if (num == 987789) {
list TempList = llParseStringKeepNulls(str,["##"],[]);
string message = llStringTrim(llList2String(TempList, 1),STRING_TRIM);
string Objects = llStringTrim(llList2String(TempList, 0),STRING_TRIM);
list ObjectsToGive = llParseStringKeepNulls(Objects,["#"],[]);
integer GiveLength = llGetListLength(ObjectsToGive);
if (GiveLength != 0) {
if (message != "") {
llInstantMessage(id,message + " " + llList2CSV(ObjectsToGive));
}
integer x;
for (x = 0; x < GiveLength; x++) {
string ObjectToGive = llStringTrim(llList2String(ObjectsToGive, x),STRING_TRIM);
if ( ( llGetInventoryType(ObjectToGive) != INVENTORY_NONE)
&& ( llGetInventoryPermMask(ObjectToGive, MASK_NEXT) & PERM_COPY) ) {
llGiveInventory(id,ObjectToGive);
}
}//end of for
}//end of checking GiveLength
} //end of if check for the right channel
} //end link_message event
} //end default state
</lsl>

[[Category:MLPV2]]

MLPV2 Troubleshooting Tips

2014-01-06T03:47:21Z

Chaz Longstaff: added: Could not find animation '00000000-0000-0000-0000-000000000000'

{{Navbox/MLPV2}}
These MLPV2 troubleshooting tips are for normal end users and builders.

== User issues ==

These issues can be seen by any MLPV2 user even when the furniture is reasonably set up.

=== Why am I not being animated? ===
Try turning off your Animation Overrider, if you have one. Whether this is an issue for you depends on a techical detail: the priority of the animations in your AO and the priority of the animations in the MLP/MLPV2 product.

=== Why am I floating? ===
Sometimes we can be using a pose and suddenly we rise about 1 meter higher and stay there. Sometimes this happens in everyone's view, and other times it only appears for some. This is an SL bug and happens with any animation system, not just MLP/MLPV2. The problem usually goes away if you select the pose again, or stand and sit again. Sometimes it may be necessary to relog.

=== Balls won't rez when I choose a pose! ===
First, try STOP. If the balls got deleted for any reason, they won't rez when you pick a pose and the MLP still thinks the balls are there. STOP fixes this. (The timeout in many MLP objects also help avoid this, by doing a STOP if nobody's used it for a while.)

Second (if first doesn't work), try resetting via the MLPV2 menu: "OPTIONS -> Shutdown... -> Restart".

Consider if maybe they *are* rezzing, but way below you or way above you -- check the description line of the MLP object to see if there is a number in there, in which case set it to 0.

=== Menu doesn't come up ===
Make sure you're on land where you are allowed to run scripts. There is a "no scripting" icon at the top of the viewer screen if you can't.

If you can't, try setting your group to the land's group. If that makes the no-scripting icon go away, set the MLP object to the land's group. (Do this in the Edit tab, or be wearing the group tag when you rez the object.)

If that isn't the problem, most likely it had a stack/heap error when you were away.

If the object permissions allow it, select the object and use "Reset Scripts". (In original style viewers, this is SL menu "Tools -> Reset Scripts in Selection". For SL2, I have no idea where it is. Naughty LL for goofing everything up.)

If this is a recurring problem, there is an MLPV2 recovery script; ask the MLPV2 group for more info. Alternatively, delete some of the poses, to allow more room.

=== "Animate me" permission popup not happening===

You won't get the animate permission popup if you were the last person on a particular poseball. It keeps your permission. You also don't get animate permission for yourself when MLP is used as a HUD, because worn items give permission automatically. (So do sat-upon items, but in the case of MLP, the script that takes permission is in the furniture, not the ball.)

=== avatar != perm key ===
This is some debugging code that Lear had left exposed by mistake in some versions. It can be ignored; it is not really an error.

If it is annoying, just update to the latest script set. (Users can do this if the item is modifiable, but users should ask the maker first in case the maker has made custom modifications or is using add-on scripts.)

=== OPTIONS menu doesn't work after deeding to group ===
If you deed an MLP, you lose the OPTIONS menu unless you remember to change all the OWNER menus to GROUP menus, and even then you won't be able to use full shutdown.

=== Could not find animation '00000000-0000-0000-0000-000000000000' ===
Often one user will get this, and not another. Some have speculated it could be AO issues (even if the AO is turned off) or something indeterminate related to the avi. The speculation comes from forums where users have reported the issue and said that it went away as inexplicably as it started, by either a relog, clearing network cache, tping away and back, taking AO off completely for a bit, etc. Or went away over night.

It could also be the asset server playing silly buggers, and a sim reboot (if possible) might solve it.

In any event, what's certain is that there is nothing wrong with the actual MLP product.

== Builder issues ==

=== Animation xyx not found ===
* Check that the animation is indeed in the prim
* Check the spelling
* If you are using expression suffixes, check that you didn't put a space before the expression suffix
* Check that as a separator in POSE lines you have used only <pre>|</pre> or <pre>space|space</pre> You can also use two spaces on each side of the vertical bar, but you cannot use three spaces: the superfluous space is not stripped away while reading the notecard; instead, it gets treated as part of the animation name, and thus the animation name can't be found.
* Also check for invisible soft-returns that may have come in if you were doing your work in another program such as Microsoft Word.

=== Animation won't remember its position ===
This can occur that even though you've triple-checked all your work; there will be an animation that sometimes will come out in the right position, sometimes not. After a bit of head-banging, you realize it all depends on which animation you played just before it. If the creator of that animation did not set a hip position for it, you will get different results depending on which pose you ran last. That is, if you have 3 animations, 2 with hip positions and one without, the hip position for the one without will be left over from whichever of the last two animations you used. Which may throw your pose all off. There is nothing you can do except abandon use of the animation; the problem is in the animation itself, and it's not suitable for use with MLP-like scripts though it may work fine as sold in a static poseball.

=== Balls rez on top of each other, even though you are sure you have positions right. ===
Check for duplicate stored positions. *Any* duplicate stored positions, even those not related to the pose in question, can cause this.

Check for the memory script having blown up during booting. It's easy to miss this, as the error bubble only shows for a short time then goes away. To ensure you don't miss it, you can in Preferences for "Text Chat" turn on "Show script errors and warnings as regular chat." That way, you'll be able to see such script problems even after problem bubble has faded.

=== Balls: not enough rezzing ===
You have a Menu with poses that have 4 animations to them, but only 2 balls are rezzing. ||Check that you didn't tell the pose to only rez 2 balls. Example: <pre>MENU Cuddles | ALL | BLUE | PINK</pre> for 4 animations should be something like <pre>MENU Cuddles | ALL | BLUE | PINK | BLUE | PINK</pre> (or whatever) . Easy mistake for tired eyes to make!

Also, check that you didn't drop the permission parameter. For instance, if you say
<pre>MENU Cuddles | PINK | BLUE </pre>
forgetting to put in there the [ALL | GROUP | OWNER] parameter, MLP will get mixed up, think that PINK is the permission parameter, and only rez the blue ball.

if you say
<pre>MENU Cuddles | PINK </pre>
No balls will rez at all.

Fix: put a permission parameter back in.

===Booting up: MLP starts, gets a bit of the way, then goes no further ===

Check that you have both a .MENUITEMS and .POSITIONS notecard in there.

=== Couldn't find (script)" error ===
If you get a message like this upon first dragging and dropping the MLPv2 scripts into a prim, disregard it. It occurs because a prim contents are very slow to refresh in SL, and one script thinks another one is not there yet. Do nothing; it will sort itself out in a few seconds.

=== llDialog: button labels must be 24 or fewer characters long ===
You have almost certainly forgotten a <pre>|</pre> in a POSE line. Consequently, the scripts were counting the Button name and the first animation name as the button name, making the button name too long.

=== Notecards: I set my notecards to full-perm but customers can't open them to save positions, etc. ===
This happens if the object is no-modify. You can't open notecards in a no-modify object. SL limitation.

=== "No Unused TOMENU" Getting this msg but I know that's not right ===
Check the top of your main MENUITEMS card, referring to the help in this section https://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#.MENUITEMS.2A_NOTECARDS

=== Props don't rez and I have everything right ===
# Make sure you have the ~props script in the MLP object. (Actually, this won't keep the prop from rezzing; it will keep it from saving its position, and keep it from deleting itself when moving to a new pose.)
# MLP is very case sensitive. CHAT 2 in .MENUITEMS does not equal Chat 2 in the props notecard. Check to make sure the case matches.
# Watch the prim count on the parcel where you are working. If the available prim count is going down, then your prop is rezzing -- just not somewhere where you are seeing it.

=== "Script run-time error / Stack-Heap Collision" ===
This is a clue that, sadly, there are too many items in your .menuitems.xxx or .positions.xxx notecards for the script memory to handle. Congratulations, you've just been initiated into the battle-scarred club like the rest of us.

First, make sure the scripts are compiled Mono, not LSL. By default they're Mono and you're better off if you do NOT recompile them.

Second, make sure you have no unused positions stored in any .positions notecards. See tidying tip here https://wiki.secondlife.com/w/index.php?title=MLPV2_Reference_Manual&action=submit#TIP.21_Positions_Notecard_tidying. Tidy, restart and see if that helps.

Third: try optimizing your saved .POSITIONS. If you have old .POSITIONS notecard data with lots of trailing zeros, you can get them trimmed down using this procedure:

# drop .MENUITEMS.reorient (from MLP Tools box) in.
# Menu Reset.
# Use the Reorient menu to move all the poses by 1 cm. This will save all the poses, with only a small change. If you don't want the 1cm change, then just move it back 1cm after it finishes. Wait for both props and pose adjustment to complete! (Be patient!)
# dump pos, dump props, and save to appropriate notecards.
# Delete MENUITEMS.reorient, and restart.

This will strip all the trailing zeros.

Fourth: if your anims are mod, you can change the names. Use short names, which take less memory. Short button names also use less memory.

The last resort is more drastic. You must give up on some poses, and delete their POSE lines from the .MENUITEMS* cards, and their position settings from the .POSITIONS* cards. You may leave the actual animations in the MLPv2 prim, but you might as well remove them as they won't be used anyway.

=== What do I do about balls that are sunk into the mattress? ===
This problem is caused by the animation hip offset being too high. One fix is to redo the animation and set the hip offset lower. If you can't do that, then there are workarounds.

One workaround is to make sure the first pose on every menu has a position where the balls are visible.

The other workaround is to change the sit target in the poseball, so the balls will be higher for the same avatar positions.

'''Note: this will affect all poses, making the balls appear higher for all poses.'''

# Pull out ~ball. Open it, and edit the ~ball script inside.
# For MLPV2.4x and later, near the top of the script:
## Look for this: "vector SitTarget = <0.,0.,.1>"
## Change it to : "vector SitTarget = <0.,0.,-.4>" (Note that .1 changed to -.4: adjust to taste.)
# Versions before MLPV2.4x:
## Look for this: "llSitTarget(<0.0,0.0,0.1>, ZERO_ROTATION);"
## Change it to : "llSitTarget(<0.0,0.0,-.4>, ZERO_ROTATION);" (Note that .1 changed to -.4: adjust to taste.)
# Take the ~ball object into inventory
# Delete ~ball from the MLPV2
# Drag the updated ~ball from inventory into the MLPV2

This will make all the poses .5 M lower than they were, with the balls at the same place. If that's a bigger change than you wanted, try -.2 or -.1 (that is, adjust to taste).

For versions prior to MLPV2.4z6, you will then need to adjust all the positions to compensate. I suggest you use the .MENUITEMS.reorient notecard for this.

=== Sequence just won't run ===
Q: Heres what I have setup in the .sequences notecard:

<pre>SEQUENCE | Romantic
MENU | Romance
POSE | standing
AVWAIT | 0 | Waiting for someone to sit on ball
WAIT | 10
POSE | Kiss
WAIT | 10
POSE | Enter
WAIT | 15...
...REPEAT</pre>

It shows up in the menu selection, but no poseballs are rezzed when you select the sequence. Here's what I have in the .MENUITEMS notecard pertaining to the sequence-

<pre>MENU Romantic
LINKMSG Romantic | 0,-4,-12001,SEQUENCE Romantic
LINKMSG PAUSE | 0,-4,-12001,PAUSE
LINKMSG RESUME | 0,-4,-12001,RESUME
SWAP
STOP
BACK</pre>

A: Your problem is simple: you have two buttons with the same label, which isn't allowed.

=== Sequence just won't run or skips poses in it===
Currently (2011), the sequencer script won't complain to you if the poses you reference actually exist or not. You're on your own for making sure they actually exist and are named exactly the same (in a menu card) as the way you are referring to them. So watch for this.

=== Xcite! features such as tilt / arousal just don't seem to work ===
Make sure you have the latest set of partner scripts (as of Jan 2012, the latest release was I think in 2009.) Make sure your own Xcite! bits aren't horribly out of date -- you need 3.0 bits or higher. Contacting xcite help isn't of much use; as of mid 2011 they became non-responsive to business partners.

That being said, features won't work unless the xcite partner script is set be either no copy or no transfer. They also won't work if the perms were wrong when you rezzed the product, so edit the script and reset it. That will make the script start to run -- it dies upon start up if perms on the script are wrong.

[[Category:MLPV2]]

MLPV2 Menu Maker Helper

2013-11-16T14:13:18Z

Chaz Longstaff:

<lsl>
//won't make your MLP menu for you completely but will save you some typing time by giving you an outline of your menu based on a set of animations
//drop in a box of animations that are paired by name logically so that they will appear in alpha order in an inventory list.
//it will make an MLP menu giving POSE name to first animation in the set of two
//you may need to re-order M and F anims in the pose line depending on your style of creating MLP menu lines
//to use, copy this into a script, save, add script to a box which holds the animations you want to use, then click the box to run the script.
//WON'T be useful with all animations because of course how animations are named varies wildly from animator to animator, and not even animators are consistent with their own styles and if such inconsistently named anims are also no mod, you're beat....
//Chaz Longstaff November 2013
//
//Sample of what this can produce for you
//[05:58] POSE Cuddle 1 B|Cuddle 1 B|Cuddle 1 T
//[05:58] POSE Kiss His Neck B|Kiss His Neck B|Kiss His Neck T
//[05:58] POSE Relax Hug1 B|Relax Hug1 B|Relax Hug1 T
//[05:58] POSE Sex Neck Kiss 01 B|Sex Neck Kiss 01 B|Sex Neck Kiss 01 T
//[05:58] POSE Sex1 B|Sex1 B|Sex1 T
//[05:58] POSE Sex1Brut B|Sex1Brut B|Sex1Brut T
//[05:58] POSE Sex1BrutFast B|Sex1BrutFast B|Sex1BrutFast T
//[05:58] POSE Sex1Fast B|Sex1Fast B|Sex1Fast T
//[05:58] POSE SexLickTit B|SexLickTit B|SexLickTit T

mySay(string objectName, string msg) {
string name = llGetObjectName();
llSetObjectName(objectName);
llSay(0, "/me " + msg);
llSetObjectName(name);
}

list printObjectList(integer type) {
list result = [];
integer n = llGetInventoryNumber(INVENTORY_ANIMATION);
integer i = 0;
integer count = 1;
string myitem;
string myitem1;
string myitem2;
integer type;
mySay("", "__________________________________________");
while(i < n) {

string itemName = llGetInventoryName(INVENTORY_ANIMATION, i);
type = llGetInventoryType(itemName);

if (type == INVENTORY_ANIMATION) {

string myitem = llGetInventoryName(type, i);
if (count == 1) {
myitem1 = myitem;
// llSay(0, (string)count + " " + myitem1);
}
else myitem2 = myitem;

if (count == 2) {
// llSay(0, (string)count + " " + myitem2);
mySay("","POSE " + myitem1 + "|" + myitem1 + "|" + myitem2 );
count = 1;
myitem = "";
myitem1 = "";
myitem2 = "";
}
else {
count = count + 1;
}

}

++i;
}
mySay("", "__________________________________________");
return result;
}

//__________________________

default
{
on_rez(integer start_param) {
llResetScript();
}

state_entry() {

}

changed(integer change) {
if (change & CHANGED_INVENTORY) {
llResetScript();
}
}

touch_start(integer total_number) {
string tmp = "all";
integer type;

type = INVENTORY_ALL;

printObjectList(type);

}

}

</lsl>

MLPV2 Menu Maker Helper

2013-11-16T14:11:07Z

Chaz Longstaff:

<lsl>
//won't make your MLP menu for you completely but will save you some typing time by giving you an outline of your menu based on a set of animations
//drop in a box of animations that are paired by name logically so that they will appear in alpha order in an inventory list.
//it will make an MLP menu giving POSE name to first animation in the set of two
//you may need to re-order M and F anims in the pose line depending on your style of creating MLP menu lines
//to use, copy this into a script, save, add script to a box which holds the animations you want to use, then click the box to run the script.
//Chaz Longstaff November 2013
//
//Sample of what this can produce for you
//[05:58] POSE Cuddle 1 B|Cuddle 1 B|Cuddle 1 T
//[05:58] POSE Kiss His Neck B|Kiss His Neck B|Kiss His Neck T
//[05:58] POSE Relax Hug1 B|Relax Hug1 B|Relax Hug1 T
//[05:58] POSE Sex Neck Kiss 01 B|Sex Neck Kiss 01 B|Sex Neck Kiss 01 T
//[05:58] POSE Sex1 B|Sex1 B|Sex1 T
//[05:58] POSE Sex1Brut B|Sex1Brut B|Sex1Brut T
//[05:58] POSE Sex1BrutFast B|Sex1BrutFast B|Sex1BrutFast T
//[05:58] POSE Sex1Fast B|Sex1Fast B|Sex1Fast T
//[05:58] POSE SexLickTit B|SexLickTit B|SexLickTit T

mySay(string objectName, string msg) {
string name = llGetObjectName();
llSetObjectName(objectName);
llSay(0, "/me " + msg);
llSetObjectName(name);
}

list printObjectList(integer type) {
list result = [];
integer n = llGetInventoryNumber(INVENTORY_ANIMATION);
integer i = 0;
integer count = 1;
string myitem;
string myitem1;
string myitem2;
integer type;
mySay("", "__________________________________________");
while(i < n) {

string itemName = llGetInventoryName(INVENTORY_ANIMATION, i);
type = llGetInventoryType(itemName);

if (type == INVENTORY_ANIMATION) {

string myitem = llGetInventoryName(type, i);
if (count == 1) {
myitem1 = myitem;
// llSay(0, (string)count + " " + myitem1);
}
else myitem2 = myitem;

if (count == 2) {
// llSay(0, (string)count + " " + myitem2);
mySay("","POSE " + myitem1 + "|" + myitem1 + "|" + myitem2 );
count = 1;
myitem = "";
myitem1 = "";
myitem2 = "";
}
else {
count = count + 1;
}

}

++i;
}
mySay("", "__________________________________________");
return result;
}

//__________________________

default
{
on_rez(integer start_param) {
llResetScript();
}

state_entry() {

}

changed(integer change) {
if (change & CHANGED_INVENTORY) {
llResetScript();
}
}

touch_start(integer total_number) {
string tmp = "all";
integer type;

type = INVENTORY_ALL;

printObjectList(type);

}

}

</lsl>

MLPV2 Menu Maker Helper

2013-11-16T14:08:46Z

Chaz Longstaff:

<lsl>
//won't make your MLP menu for you completely but will save you some typing time by giving you an outline of your menu based on a set of animations
//drop in a box of animations that are paired by name logically so that they will appear in alpha order in an inventory list.
//it will make an MLP menu giving POSE name to first animation in the set of two
//you may need to re-order M and F anims in the pose line depending on your style of creating MLP menu lines
//to use, copy this into a script, save, add script to a box which holds the animations you want to use, then click the box to run the script.
//Chaz Longstaff November 2013
//
//Sample of what this can produce for you
//[05:58] POSE Cuddle 1 B|Cuddle 1 B|Cuddle 1 T
//[05:58] POSE Kiss His Neck B|Kiss His Neck B|Kiss His Neck T
//[05:58] POSE Relax Hug1 B|Relax Hug1 B|Relax Hug1 T
//[05:58] POSE Sex Neck Kiss 01 B|Sex Neck Kiss 01 B|Sex Neck Kiss 01 T
//[05:58] POSE Sex1 B|Sex1 B|Sex1 T
//[05:58] POSE Sex1Brut B|Sex1Brut B|Sex1Brut T
//[05:58] POSE Sex1BrutFast F|Sex1BrutFast F|Sex1BrutFast T
//[05:58] POSE Sex1Fast B|Sex1Fast B|Sex1Fast T
//[05:58] POSE SexLickTit B|SexLickTit B|SexLickTit T

mySay(string objectName, string msg) {
string name = llGetObjectName();
llSetObjectName(objectName);
llSay(0, "/me " + msg);
llSetObjectName(name);
}

list printObjectList(integer type) {
list result = [];
integer n = llGetInventoryNumber(INVENTORY_ANIMATION);
integer i = 0;
integer count = 1;
string myitem;
string myitem1;
string myitem2;
integer type;
mySay("", "__________________________________________");
while(i < n) {

string itemName = llGetInventoryName(INVENTORY_ANIMATION, i);
type = llGetInventoryType(itemName);

if (type == INVENTORY_ANIMATION) {

string myitem = llGetInventoryName(type, i);
if (count == 1) {
myitem1 = myitem;
// llSay(0, (string)count + " " + myitem1);
}
else myitem2 = myitem;

if (count == 2) {
// llSay(0, (string)count + " " + myitem2);
mySay("","POSE " + myitem1 + "|" + myitem1 + "|" + myitem2 );
count = 1;
myitem = "";
myitem1 = "";
myitem2 = "";
}
else {
count = count + 1;
}

}

++i;
}
mySay("", "__________________________________________");
return result;
}

//__________________________

default
{
on_rez(integer start_param) {
llResetScript();
}

state_entry() {

}

changed(integer change) {
if (change & CHANGED_INVENTORY) {
llResetScript();
}
}

touch_start(integer total_number) {
string tmp = "all";
integer type;

type = INVENTORY_ALL;

printObjectList(type);

}

}

</lsl>

MLPV2 Menu Maker Helper

2013-11-16T14:02:12Z

Chaz Longstaff:

<lsl>
//won't make your MLP menu for you completely but will save you some typing time by giving you an outline of your menu based on a set of animations
//drop in a box of animations that are paired by name logically so that they will appear in alpha order in an inventory list.
//it will make an MLP menu giving POSE name to first animation in the set of two
//you may need to re-order M and F anims in the pose line depending on your style of creating MLP menu lines
//Chaz Longstaff November 2013
//
//Sample of what this can produce for you
//[05:58] POSE Cuddle 1 B|Cuddle 1 B|Cuddle 1 T
//[05:58] POSE Kiss His Neck B|Kiss His Neck B|Kiss His Neck T
//[05:58] POSE Relax Hug1 B|Relax Hug1 B|Relax Hug1 T
//[05:58] POSE Sex Neck Kiss 01 B|Sex Neck Kiss 01 B|Sex Neck Kiss 01 T
//[05:58] POSE Sex1 B|Sex1 B|Sex1 T
//[05:58] POSE Sex1Brut B|Sex1Brut B|Sex1Brut T
//[05:58] POSE Sex1BrutFast F|Sex1BrutFast F|Sex1BrutFast T
//[05:58] POSE Sex1Fast B|Sex1Fast B|Sex1Fast T
//[05:58] POSE SexLickTit B|SexLickTit B|SexLickTit T

mySay(string objectName, string msg) {
string name = llGetObjectName();
llSetObjectName(objectName);
llSay(0, "/me " + msg);
llSetObjectName(name);
}

list printObjectList(integer type) {
list result = [];
integer n = llGetInventoryNumber(INVENTORY_ANIMATION);
integer i = 0;
integer count = 1;
string myitem;
string myitem1;
string myitem2;
integer type;
mySay("", "__________________________________________");
while(i < n) {

string itemName = llGetInventoryName(INVENTORY_ANIMATION, i);
type = llGetInventoryType(itemName);

if (type == INVENTORY_ANIMATION) {

string myitem = llGetInventoryName(type, i);
if (count == 1) {
myitem1 = myitem;
// llSay(0, (string)count + " " + myitem1);
}
else myitem2 = myitem;

if (count == 2) {
// llSay(0, (string)count + " " + myitem2);
mySay("","POSE " + myitem1 + "|" + myitem1 + "|" + myitem2 );
count = 1;
myitem = "";
myitem1 = "";
myitem2 = "";
}
else {
count = count + 1;
}

}

++i;
}
mySay("", "__________________________________________");
return result;
}

//__________________________

default
{
on_rez(integer start_param) {
llResetScript();
}

state_entry() {

}

changed(integer change) {
if (change & CHANGED_INVENTORY) {
llResetScript();
}
}

touch_start(integer total_number) {
string tmp = "all";
integer type;

type = INVENTORY_ALL;

printObjectList(type);

}

}

</lsl>

MLPV2 Menu Maker Helper

2013-11-16T13:40:05Z

Chaz Longstaff: Created page with "<lsl> //won't make your MLP menu for you completely but will save you some typing time //drop in a box of animations that are paired by name logically so that they will appear in…"

<lsl>
//won't make your MLP menu for you completely but will save you some typing time
//drop in a box of animations that are paired by name logically so that they will appear in alpha order in an inventory list
//it will make an MLP menu giving POSE name to first animation in the set of two
//you may need to re-order M and F anims in the pose line
//Chaz Longstaff November 2013
//
//Sample of what this can produce for you
//[05:26] POSE Cuddle 1 M|Cuddle 1 M|Kiss His Neck F
//[05:26] POSE Relax Hug1 M|Relax Hug1 M|Sex Neck Kiss 01 F
//[05:26] POSE Sex1 M|Sex1 M|Sex1 F
//[05:26] POSE Sex1Brut M|Sex1Brut M|Sex1Brut F
//[05:26] POSE Sex1BrutFast M|Sex1BrutFast M|Sex1BrutFast F
//[05:26] POSE Sex1Fast M|Sex1Fast M|SexLickTit F

mySay(string objectName, string msg) {
string name = llGetObjectName();
llSetObjectName(objectName);
llSay(0, "/me " + msg);
llSetObjectName(name);
}

list printObjectList(integer type) {
list result = [];
integer n = llGetInventoryNumber(type);
integer i = 0;
integer count = 0;
string myitem;
string myitem1;
string myitem2;
integer type;
mySay("", "__________________________________________");
while(i < n) {

string itemName = llGetInventoryName(INVENTORY_ALL, i);
type = llGetInventoryType(itemName);

if (type != INVENTORY_ANIMATION) {
jump gonext;
}

string myitem = llGetInventoryName(type, i);
if (count == 1) {
myitem1 = myitem;
}
else myitem2 = myitem;

if (count == 2) {
mySay("","POSE " + myitem1 + "|" + myitem1 + "|" + myitem2 );
count = 0;
myitem = "";
myitem1 = "";
myitem2 = "";
}
else {
count = count + 1;
}

@gonext;

++i;
}
mySay("", "__________________________________________");
return result;
}

//__________________________

default
{
on_rez(integer start_param) {
llResetScript();
}

state_entry() {

}

changed(integer change) {
if (change & CHANGED_INVENTORY) {
llResetScript();
}
}

touch_start(integer total_number) {
string tmp = "all";
integer type;

type = INVENTORY_ALL;

printObjectList(type);

}

}

</lsl>

MLPV2 Addons

2013-11-16T13:38:37Z

Chaz Longstaff:

{{Navbox/MLPV2}}

*[[MLPV2 Give Item Add-on]]
*[[MLPV2 Give Folder Add-on]]
*[[MLPV2 Give Items in Folder to a Specific Person]]
*[[Check Animations Permissions Tool]]
*[[Cleaner MLP Say|"Cleaner" MLP Say]]
*[[MLPV2_Texture_Changer_Add-on]]
*[[MLPV2 Color Changer Add-on]]
*[[MLPV2_Props_Texture_Changer_Add-on]]
*[[MLPV2_Ambiant_Sound_Add-on]]
*[[MLPV2_RLV_Plugin]]
*[[MLPV2_RLV_Capture_Plugin]]
*[[Reset_from_Child_Plugin]]
*[[MLPV2 Ball Script with more flexible parameters]]
*[[MLPV2 Menu Maker Helper]]

===Patches===
* [[MLPV2_Balls_Patch]]: Use different balls for ~ball0...5
* [[MLPV2_LockGuard_plugin]]: Add LockGuard support to MLP2

===Tools===
*[[Script to report on who made which animations in a prim]]

[[Category:MLPV2]]

MLPV2 Give Items in Folder to a Specific Person

2013-03-29T20:00:13Z

Chaz Longstaff:

* Back to [[MLPV2_Addons]]

<lsl>
//add-on by Chaz Longstff for MLPV2 by Lear Cale. August 2011. Give 2 v.001
//Function: gives object to a specific person on an MLPV2 ball
//
//in a menu card, format a menu button like this, for example:
//LINKMSG MyButtonName | 0,-4,987789,Cuff1#Cuff2#Cuff3#Cuff4##FolderName##0##Wear these four cuffs.
//In this example, MyButtonName is the button name
//0 means whether to make the MLPV2 menu go away or not. Generally set it to 0 as per the example, so the menu comes back (taking advantage of new 2.x and higher viewers). To make the MLPV2 menu go away, use 1 instead.
//-4 -- the value of LINK_THIS, meaning, send this message to this prim only. (Use -1 if the ~give2 script is in a different prim.)
//987789 -- don't change this, this is the communication channel
//Cuff1#Cuff2#Cuff3#Cuff4 -- (The items to give are separated by a single #
//##FolderName: the name of the folder to put the stuff in. Note that it needs to be preceded by a double ##.
//##0 -- (offer to person on which ball? 0, 1, 2, 3, 4, 5 . You can leave blank if the person to receive is the person who is operating the menu, this is default behaviour.)
//##Wear these four cuffs -- Msg to receiver. (Note that it needs to be preceded by a double ##. It's good to include a msg, so that they don't think it's a griefer trying to hand them something. However, you can leave this param blank if you wish.
//Caution: There is a linden script limit of 255 bytes of info that can be read from a notecard line. Practically speaking, that means you are limited to say maybe 225, 230 characters in total that you can have in this LINKMSG line. So if you are giving several items to wear in one folder, keep the items names short and sweet, or your whole line will get truncated randomly, just cut right off.

//parameters
string ObjectToGive;
string message;
integer x;
list Avnames = ["", "", "", "", "", ""];
key GiveToID;
string FolderName;

addAv(string id, integer ballIx) {
Avnames = llListReplaceList(Avnames, (list)id, ballIx, ballIx);
}

removeAv(integer ballIx) {
addAv("", ballIx);
}

myMsg() {
string name = llGetObjectName();
llSetObjectName("Blue Balls");
//change the text "Blue Balls" to anything you like, such as your own Brand Name
llInstantMessage(GiveToID,message + " " + FolderName);
if (name != "") llSetObjectName(name);
}
//_________________________
default{
link_message(integer from, integer num, string str, key id) {

if (num == -11000) {
// av hopped on
list parms = llParseStringKeepNulls(str, ["|"], []);
integer ballnum = (integer)llList2String(parms, 0);
// string anim = llList2String(parms, 1); // anim name parameter, if desired
//debug(4, llKey2Name(dkey) + ": on ball " + (string)ballnum);
addAv((string)id, ballnum);
return;

} else if (num == -11001) {
// av hopped off
//debug(4, llKey2Name(dkey) + ": off ball " + str);
removeAv((integer)str);
return;
}
else if (num == 987789) {
//llSay(0, "test:" + str);
string idtogiveto = "";
list TempList = llParseStringKeepNulls(str,["##"],[]);
string Objects = llStringTrim(llList2String(TempList, 0),STRING_TRIM);
list ObjectsToGive = llParseStringKeepNulls(Objects,["#"],[]);
integer GiveLength = llGetListLength(ObjectsToGive);
FolderName = llStringTrim(llList2String(TempList, 1),STRING_TRIM);
string ball = llStringTrim(llList2String(TempList, 2),STRING_TRIM);
message = llStringTrim(llList2String(TempList, 3),STRING_TRIM);

if (ball != "") {
idtogiveto = llStringTrim(llList2String(Avnames,(integer)ball),STRING_TRIM);
}
//llSay(0, idtogiveto);
if (idtogiveto == "") {
GiveToID = id;
//llSay(0, (string)GiveToID);
}

else GiveToID = (key)idtogiveto;
if (GiveLength != 0) {
if (message != "") {
myMsg();
}
llGiveInventoryList(GiveToID, FolderName, ObjectsToGive);

}//end of checking GiveLength
} //end of if check for the right channel
} //end link_message event
} //end default state

</lsl>

[[Category:MLPV2]]

StMatthewsByTheSea

2012-01-28T11:50:22Z

Chaz Longstaff:

== St Matthew's by-the-Sea Episcopal Chapel ==

'''Find Us in Second Life'''

[http://slurl.com/secondlife/Divine%20Forest/85/234/22 St Matthew's Chapel]

'''About Us'''

St. Matthew's by-the-Sea is an inclusive and affirming Episcopal /Anglican chapel.

We are one of the most active, ongoing "church" groups in SL.

We are an LGBT friendly community but that is just one facet of us; we are broadly-based and focus on people as people. You do not have to be an Episcopalian, Anglican or even Christian to be part of our community.

We gather regularly for Compline Mon-Thu at 8pm SLT. Please join us! The service is short, normally lasting only 20 to 25 minutes. We just read a service together from the Book of Common Prayer; there is no sermon to endure, etc, etc.

'''In World Groups'''

Join the Friends of St. Matthew's group if you would like to know what is going on at the Chapel and get Group Notices of services.

We also send notices and group IM's through the Inclusive Anglicans of Second Life, the LGBT Christian Community and the Episcopalians of Second Life.

'''For More Information Contact'''

Caoilin Galthie at caoilingalthie@gmail.com

Visit our [http://stmattsinsl.wordpress.com/ St. Matthew's by-the-Sea blog].

StMatthewsByTheSea

2012-01-28T11:49:43Z

Chaz Longstaff:

== St Matthew's by-the-Sea Episcopal Chapel ==

'''Find Us in Second Life'''

[http://slurl.com/secondlife/Divine%20Forest/85/234/22 St Matthew's Chapel]

'''About Us'''

St. Matthew's by-the-Sea is an inclusive and affirming Episcopal /Anglican chapel.

We are one of the most active, ongoing "church" groups in SL.

We are an LGBT friendly community but that is just once facet of us; we are broadly-based and focus on people as people. You do not have to be an Episcopalian, Anglican or even Christian to be part of our community.

We gather regularly for Compline Mon-Thu at 8pm SLT. Please join us! The service is short, normally lasting only 20 to 25 minutes. We just read a service together from the Book of Common Prayer; there is no sermon to endure, etc, etc.

'''In World Groups'''

Join the Friends of St. Matthew's group if you would like to know what is going on at the Chapel and get Group Notices of services.

We also send notices and group IM's through the Inclusive Anglicans of Second Life, the LGBT Christian Community and the Episcopalians of Second Life.

'''For More Information Contact'''

Caoilin Galthie at caoilingalthie@gmail.com

Visit our [http://stmattsinsl.wordpress.com/ St. Matthew's by-the-Sea blog].

MLPV2 Public Domain Animations

2012-01-19T09:10:37Z

Chaz Longstaff:

{{Navbox/MLPV2}}

==Animations: Which are public-domain, which are not?==

Note: If you want to be added to one of the lists below and don't know how to edit a wiki page, just IM Chaz Longstaff and indicate in your IM the section to add you to.

Beginning furniture makers or experimenters often don’t have the money and / or confidence yet to invest in buying licenced animations.

Here's a list of the status of animations from various animators. It's to help you determine which animations you can safely regard as being in the public domain (i.e. "freebies"), versus which ones might be illegally floating around as pirated animations. Using pirated animations -- knowingly or unknowingly, it's the same -- can cause your creations to be deleted by LL and get you a bad reputation just when you are starting out and trying to get known.

Now, just because the animations are in the public domain doesn't always make them "good quality" -- they can be dated, and show their age, which can be why they were released at a certain point for free. But when you are just started out and practising, or want to make a few things just for friends, they can be very useful.

In the lists below, "confirmed in conversation with CL" -- the CL stands for Chaz Longstaff.

===Genuine freebies (last updated 19 Jan 2012)===
* Ayla Holt [5]
* Betray Resident [5]
* Butcher Cassidy (confirmed in conversation with CL)
* Chip Midnight (confirmed in conversation with CL)
* Damien Fate (confirmed in conversation with CL)
* Emma Thorn (confirmed in conversation with CL 3 August 2008)
* Fleabite Beach (confirmed in conversation with CL 5 June 2008)
* Jayce Tearfall [5]
* Kammie Rayna [5]
* Linda Kellie [5]
* linkin Slate (confirmed in conversation with CL)
* Sin Delight [5]
* Ulrika Zugzwang (from her profile, noted by CL)
* YadNi Monde (confirmed in conversation with CL)
* Yuriko Nishi (confirmed in conversation with CL 5 June 2008)

===Animators whose stuff always requires a licence (last updated September 15th, 2008)===
* Animator Ragu
* Beau Perkins
* Bella Beleza
* Ben Stravinsky
* Cita Boa
* Craig Altman
* Damen Gorilla
* Dylan Rickenbacker
* fana dechou
* Furr Burt
* Johan Durant
* loufa Shilova
* Medhue Simoni
* mikeD Streeter
* Natalie Oe (confirmed in conversation with CL 13 Aug 2008)
* Nya Raymaker / Jolly Lovenkraft (confirmed in conversation with CL 13 Aug 2008)
* Nytemyst Grace
* Owain Raymaker (confirmed in conversation with CL 13 Aug 2008)
* Parsalin Gullwing
* Sandy Clymer
* Sin Toshi
* Siryn Rosse (confirmed here in this thread in old SL forums 13 Aug 2008)
* store Allen
* suzi sohmers
* Tara Bournemouth
* trebbort subagja
* Varon Kappler
* Zoe Biggles

===Animators who never licence their stuff [1] (last updated September 15th, 2008)===
* Abramelin Wolfe
* Cheree Bury (confirmed here in this thread in old SL forums 13 Aug 2008)
* Darkness Anubis
* Desiree Bisiani (and Cheewha Palen)
* Flip Fitzsimmons
* Hol ALexander
* jamie Cheeky
* Jennifer Brennon
* Lizz Silverstar
* niknak Bugaboo
* Paul Llewelyn
* Paul Lobo
* Phil Deakins
* Ravanne Sullivan
* Renee Irwin
* Riann Maltese

===Animators who produce both licenced and freebie stuff [2] (last updated September 15th, 2008)===
* Darien Caldwell (confirmed in conversation)
* Deira Llanfair (confirmed here in this thread in old SL forums 13 Aug 2008)
* Ferran Brodsky (confirmed in conversation with CL)
* Indika Herbst (confirmed in conversation with CL)
* Lear Cale (confirmed in conversation with CL)
* LordJason Kiesler (confirmed in conversation with CL)
* Starlight Kiesler (confirmed in conversation with CL)

===Animators who released some freebies in the past but now never licence their stuff [3] (last updated September 15th, 2008)===
* Neo Virgo (confirmed in conversation with CL 5 July 2008)
* Owain Raymaker (confirmed in conversation with CL 13 Aug 2008)
* Shukran Fahid (confirmed in conversation with CL 24 Aug 2008. Please do not contact him about these freebies as he is no longer in possession of them; you must obtain them from somewhere else. And, they are not supported.)

===Creator no longer exists [4] (last updated September 15th, 2008)===
* Cid Jacob
* Eva Capalini

===Status Uncertain===
(IM’ed / emailed a minimum of 3 times, but no response. Attempts to contact them have been abandoned. Last updated September 15th, 2008)
* Cristiano Midnight
* Dyonis Blanc
* Gwinivere Grayson
* Kiari LeFay
* Kris Gullwing
* Launa Fauna
* Michael Firefly
* Princess Medici
* Remo Yossarian
* stephenpaul Bliss (reportedly no longer active in SL; status of his animations uncertain.)

* Sine Wave (various creators). Released the following genuine freebies: Lime Jelly, Hipster, We love you girl, and We love you boy. There is a full-perm version of Caramel circulating, but its release was accidental.

===FOOTNOTES===

[1] if you see these animations being used by anyone but them, they are likely pirated.

[2] You need to check with these animators when free stuff created by them comes into your hands.

[3] These people released some stuff as freebies in the distant past, but now only produce animations for their own use, and never licence any of these current ones out.

[4] An effort was made at clarification but no real determination of status was possible owing to the accounts having been deleted from SL. Use at your own risk.

[5] Ayla Holt and Kammie Rayna were avatars used by Linda Kellie. Public domain status in all OpenSim or SL grids was confirmed on 17 January 2012 in conversation with Reven Rosca. Also confirmed on Linda's website, http://www.lindakellie.com/ (link valid as of 19 January 2012), from where the source files for her animations can be downloaded.

MLPV2 Public Domain Animations

2012-01-19T09:09:19Z

Chaz Longstaff:

{{Navbox/MLPV2}}

==Animations: Which are public-domain, which are not?==

Note: this list has generally been maintained by Chaz Longstaff. If you want to be added to one of the lists below and don't know how to edit a wiki page, just IM him and he will add you to the appropriate section that you indicate (please indicate in your IM the section.)

Beginning furniture makers or experimenters often don’t have the money and / or confidence yet to invest in buying licenced animations.

Here's a list of the status of animations from various animators. It's to help you determine which animations you can safely regard as being in the public domain (i.e. "freebies"), versus which ones might be illegally floating around as pirated animations. Using pirated animations -- knowingly or unknowingly, it's the same -- can cause your creations to be deleted by LL and get you a bad reputation just when you are starting out and trying to get known.

Now, just because the animations are in the public domain doesn't always make them "good quality" -- they can be dated, and show their age, which can be why they were released at a certain point for free. But when you are just started out and practising, or want to make a few things just for friends, they can be very useful.

In the lists below, "confirmed in conversation with CL" -- the CL stands for Chaz Longstaff.

===Genuine freebies (last updated 19 Jan 2012)===
* Ayla Holt [5]
* Betray Resident [5]
* Butcher Cassidy (confirmed in conversation with CL)
* Chip Midnight (confirmed in conversation with CL)
* Damien Fate (confirmed in conversation with CL)
* Emma Thorn (confirmed in conversation with CL 3 August 2008)
* Fleabite Beach (confirmed in conversation with CL 5 June 2008)
* Jayce Tearfall [5]
* Kammie Rayna [5]
* Linda Kellie [5]
* linkin Slate (confirmed in conversation with CL)
* Sin Delight [5]
* Ulrika Zugzwang (from her profile, noted by CL)
* YadNi Monde (confirmed in conversation with CL)
* Yuriko Nishi (confirmed in conversation with CL 5 June 2008)

===Animators whose stuff always requires a licence (last updated September 15th, 2008)===
* Animator Ragu
* Beau Perkins
* Bella Beleza
* Ben Stravinsky
* Cita Boa
* Craig Altman
* Damen Gorilla
* Dylan Rickenbacker
* fana dechou
* Furr Burt
* Johan Durant
* loufa Shilova
* Medhue Simoni
* mikeD Streeter
* Natalie Oe (confirmed in conversation with CL 13 Aug 2008)
* Nya Raymaker / Jolly Lovenkraft (confirmed in conversation with CL 13 Aug 2008)
* Nytemyst Grace
* Owain Raymaker (confirmed in conversation with CL 13 Aug 2008)
* Parsalin Gullwing
* Sandy Clymer
* Sin Toshi
* Siryn Rosse (confirmed here in this thread in old SL forums 13 Aug 2008)
* store Allen
* suzi sohmers
* Tara Bournemouth
* trebbort subagja
* Varon Kappler
* Zoe Biggles

===Animators who never licence their stuff [1] (last updated September 15th, 2008)===
* Abramelin Wolfe
* Cheree Bury (confirmed here in this thread in old SL forums 13 Aug 2008)
* Darkness Anubis
* Desiree Bisiani (and Cheewha Palen)
* Flip Fitzsimmons
* Hol ALexander
* jamie Cheeky
* Jennifer Brennon
* Lizz Silverstar
* niknak Bugaboo
* Paul Llewelyn
* Paul Lobo
* Phil Deakins
* Ravanne Sullivan
* Renee Irwin
* Riann Maltese

===Animators who produce both licenced and freebie stuff [2] (last updated September 15th, 2008)===
* Darien Caldwell (confirmed in conversation)
* Deira Llanfair (confirmed here in this thread in old SL forums 13 Aug 2008)
* Ferran Brodsky (confirmed in conversation with CL)
* Indika Herbst (confirmed in conversation with CL)
* Lear Cale (confirmed in conversation with CL)
* LordJason Kiesler (confirmed in conversation with CL)
* Starlight Kiesler (confirmed in conversation with CL)

===Animators who released some freebies in the past but now never licence their stuff [3] (last updated September 15th, 2008)===
* Neo Virgo (confirmed in conversation with CL 5 July 2008)
* Owain Raymaker (confirmed in conversation with CL 13 Aug 2008)
* Shukran Fahid (confirmed in conversation with CL 24 Aug 2008. Please do not contact him about these freebies as he is no longer in possession of them; you must obtain them from somewhere else. And, they are not supported.)

===Creator no longer exists [4] (last updated September 15th, 2008)===
* Cid Jacob
* Eva Capalini

===Status Uncertain===
(IM’ed / emailed a minimum of 3 times, but no response. Attempts to contact them have been abandoned. Last updated September 15th, 2008)
* Cristiano Midnight
* Dyonis Blanc
* Gwinivere Grayson
* Kiari LeFay
* Kris Gullwing
* Launa Fauna
* Michael Firefly
* Princess Medici
* Remo Yossarian
* stephenpaul Bliss (reportedly no longer active in SL; status of his animations uncertain.)

* Sine Wave (various creators). Released the following genuine freebies: Lime Jelly, Hipster, We love you girl, and We love you boy. There is a full-perm version of Caramel circulating, but its release was accidental.

===FOOTNOTES===

[1] if you see these animations being used by anyone but them, they are likely pirated.

[2] You need to check with these animators when free stuff created by them comes into your hands.

[3] These people released some stuff as freebies in the distant past, but now only produce animations for their own use, and never licence any of these current ones out.

[4] An effort was made at clarification but no real determination of status was possible owing to the accounts having been deleted from SL. Use at your own risk.

[5] Ayla Holt and Kammie Rayna were avatars used by Linda Kellie. Public domain status in all OpenSim or SL grids was confirmed on 17 January 2012 in conversation with Reven Rosca. Also confirmed on Linda's website, http://www.lindakellie.com/ (link valid as of 19 January 2012), from where the source files for her animations can be downloaded.

MLPV2 Version Tracking

2012-01-19T02:20:09Z

Chaz Longstaff:

{{Navbox/MLPV2}}

== MLPV2 Version Tracking ==

MLPV2.5a

This is a first cut at memory reduction for MLPV2. The goal is to reduce memory usage stats.

* ~menucfg: deleted state exit handler, moved code to entry handler.
* ~menucfg sets memory limit to usage + 100 and shuts off
* MEMORY commands for .MENUITEMS and .POSITIONS (see xxxx.example for examples)
* prints ~menu memory usage on Adjust. What about ~positions? ~pose?
* reduced memory in ~run
* "Adjust" menu button now prints current memory usage in ~menu. (Need something for ~positions as well.)

TODO in subsequent release(s):

* have posers set their memory limit low -- NOPE, leave as LSL, because they take 17K in Mono.
* have posers shut themselves down? (Currently ~menu stops them when not in use.)
* check for other scripts to lower memory.
* memory limit for ~pos? use same as ~menu, or that minus a constant?
* find out whether lists can be further optimized
* MEMORY commands for ~sequencer and ~swap

2.4z9

* sequences: omit objname in chat
* xcite: allow multiple /x in chat strings
* Changed scripts: ~sequences, ~MLPT-Xcite-adaptor4, and ~menu (version number only)

2.4z5,6,7
* Use version 2.4z7 (5 and 6 releases were replaced within hours owing to permission issues, etc.)
* Moved the "check config" feature to a separate script in MLP tools, freeing up a bit of memory in ~menu and ~memory.
* The config check is for when you think it's done: it checks for poses without positions and vice versa, or missing sounds.
* Change to ~ball that allows changing sit target without having to adjust .POSITIONS

2.4z4
* Resync when starting same anim (e.g., new pose using same anim, or choosing same pose again)

2.4z3
* BUG FIX - Since MLPV2.4w, if you change to a pose with fewer balls, avs popped off are not de-animated, and partner scripts (like xcite) are not told that the avatar stood.
* Only changed script is ~menu.

2.4 z
* Adds SOUND for sequences

2.4 y
* With this version, you may now delete unnecessary "~poser n" scripts (e.g. ~poser 5). Delete the unnecessary high-numbered ones. For couples, you need "~poser" and "~poser 1" but not the others.

2.4 w
* Should fit about 50 more couples poses (assuming button and anim names aren't long).

2.4 v
* added random expressions via ::21 (change in all ~poser scripts)
* fixed: the "build-in" typo;
* fixed: example SEQUENCES nc had debug turned on

2.4u2
* same as 2.4u, but with a 'fullstop timeout' script in the tools box

2.4u
* allow STAND as first pose chosen in a menu. Previously, rezzed no balls for STAND (used whatever balls from last menu chosen)
* provide a button for adjusting STAND in zz-adjDefault
* free up some memory in ~menu (about 2K)
* Changes to: ~menu, .readme only, .POSITIONS.zz-default

2.4t2
* Forgot to update vers # in 2.4t, please use this one.
* Changed: ~menu, ~swap.

2.4t
* Minor bug fixed: if SWAP used after reset before any pose selected, ~swap fails; reset required.
* ~MLPT-timeout added to MLP Tools box. Drop this script in so MLP will STOP when unused for one hour (editable). See MLPT readme for details.
* NOTE: In this distribution to the MLPV2 group, ~MLPT-timeout is included directly, not just in the MLP Tools box. Please give it a try and let me know if there are any problems.

2.4s
* Sequences turned "chat" off; this update fixes that. I thought I'd fixed that before, but evidently not.
* Changed scripts are ~menu (version string only), and ~sequence.
* No other changes.

2.4q
* MLPV2.4p was borked in reading positions. This fixes it. It also backs out the ~memory changes, which don't work well with the new server code (1.30.2) (as I'd suspected).

2.4p1
* fixed OFF for "CHAT Chat Info OFF" and "REDO RedoMenu OFF" configs. (Buttons worked; default settings didn't.) 
* removed object name from pose chats 
* reduced probability of "*" prefix in ~ball desc causing it to miss color change message 
* eliminated sliced arrays in ~memory, dramatically increasing free mem (but perhaps running afoul of upcoming changes, stay tuned). followed Liz's suggestion to use one list rather than multiple. I don't know why multiple had the severe overhead. When I tested it earlier, the two methods worked the same in Mono, whereas multiple lists worked much better for LSL. However, there's an issue here, and I expect this subject will come up again, related to memory handling differences for per-parcel script memory limits. 
* sitter: Instead of arrow keys adjusting, you now press both page-up and page-down to enable the arrow keys (shift left/right, up/down, and page up/down). Push page-up and page-down to disable again. This way, folks trying to adjust their view won't move their avvies.
* updated scripts: ~menu, ~memory, ~ball 
* Added "ready" linked message. Uses -11003, "READY"

2.4p
* same as for 2.4p1 above, except linked message "ready" used channel 0.

2.4n4
* fixes to address some sequencing issues such as NOCHAT turning off all chat, etc. 
Changes made to the following scripts: ~sequencer

2.4n3
* fixes to turning off scripts (lag reduction). Should no longer fail after sim reset. Should also fix a reanimation problem. 
* Leave ~timeout running so it'll delete itself when bought 
* ~timeout moved to MLP Tools kit 
* Changes made to the following scripts: ~menu and and all ~poser* scripts (~poser, ~poser1, etc.)

2.4n2
* by this version, the MATURE directive was partially retired by being commented out

2.4n
* fix warning when multiple people using menu at same time (popups go to wrong people)

2.4m - add warning and truncate for pose button label too big (usually, missing "|")
- sitter adjustable poseball (start ~ball description with plus sign to activate)

v2.4l
* avoid "animating without permission" script errors (when sitter doesn't accept) -- partially solved (error gone, but something's still wrong if MLP bought when someone's on a ball.) 
* MATURE directive (skip rest of card if not MATURE sim). (might ditch this) 
* stop poser# scripts when corresponding ball isn't rezzed 
* stop several other scripts when no balls are rezzed 

v4.2k
* fix ~prop: don't jump on double-save

v4.2j
* fix ~ball: don't listen if rez-arg is zero; cancel old listen on rez.

v4.2i
* fix getrefpos issue on save

v4.2h
* warn if props aren't copiable (check for current and for next owner)

v4.2g
* Adjust mode auto-saves props too; delete trailing zeros on save

v4.2f
* STOP resets swap

v2.4e
* restarter button in MLP Tools, xcite double-stim for per-anim fixed

2.4 d
* Bug fix: SAVE after SWAP should now work correctly. Note: don't SWAP while editing a pose; it'll reset it to the previously saved position. Instead, save and then swap, after which you can save and it'll do the right thing. I should put this in the wiki!
* ~timeout put back in

2.4
* HIDDEN attribute for menus (instead of "ALL/GROUP/OWNER") for menus used only by sequences.
* NOCHAT option for sequences (use "SEQUENCE | seqname | NOCHAT") -- disables bed chatting pose name during sequence.
* SWAP behavior configurable per-pose (for poses with more than 2 balls). See "CONFIGURING SWAP FEATURE" above.

2.3k
* fixed startup race condition (stopping before reading MENUITEMS), fixed sequence labels not found

2.3j
* height menu bug fix (probably broken since 2.3's reorient menu added)

2.3i
* bug fix (remenu broken in 2.3h)

2.3h
* sequences: rez balls on sequence start

2.3g
* reset fixes:
* kill balls on reset in ~menu startup
* don't say "click to start" until ready, in ~run

----

CHANGES in MLPV2 Version 2.3:

- Supports sounds

- Supports up to 6 avatars (poseballs)

- Sequences (tours) -- set up a menu button that plays a sequence of poses and chats. You configure the sequences in a new .SEQUENCE type of notecard. More info on that here:

- When rezzed, balls are now named ~ball0 .. ~ball5, to support easy sitting for bot clients (used for machinima, not camping!) The object name in inventory has not changed.

- "Adjust Pos" is now a toggle. Try it and see! Avs can hop on and off and balls return to the 'adjusting' shape. You can also use STOP to return to normal mode.

- EZ-Adust! Now, when you're in adjust mode and you change poses, it saves the current pose before swithcing to new pose. To abandon changes, quit adjust mode, STOP, or just re-select the current pose.

- TOOLS PACK:

- "Reorient" menu for more easily adapting an existing pose set to a new furniture item

- script to check anim permissions

- script to check for unused animations

- Three different example xcite adaptor scripts (requires Xcite! Partner script from Xcite)
- AutoZhao adaptor script

- touch passer moved here, since it's never required in the MLP prim

----

CHANGES in MLPV2 Version 2.2 (unreleased other than to MLPV2 group)

- Added LMs when avs sit or unsit, to make it possible to add support for things like xcite and cuffs without modifying MLP scripts. Read more here:

- Cleaner chat on DUMP (omits object name)

----

CHANGES in MLPV2 Version 2.1:

- Props! Rez an object per pose. Object is deleted when changing to new pose, or after 3 minutes if bed is deleted.

- 15 ball colors supported!

- AUTOBACK - automatically inserts BACK before MORE--> button (optional, off by default)

- Bug fix for AUTOMORE on main menus with too many buttons. AUTOMORE no longer supported for main menu. Might be fixed some day.

- Bug fix for AUTOMORE menues with more than one extra page.

- Expression control code removed -- didn't work out. MLPV2 no longer takes controls. Of course, still compatible with all MLP and MLPV2.0 scripts.

----

CHANGES in MLPV2, Version 2.0:

- Now supports Solo, 3some, and 4some menus.

- Memory optimized: now holds over 70 couples poses.

- Expressions supported (20 expressions, constant or periodic). See "TO ADD POSES" above.

- Extended menus. (Automatic "More-->" button for menus with more than 12 buttons.)

- Menu buttons now appear in menus in the same order as in the configuration
but only if the new MENUORDER config item appears -- otherwise order is same as before, for backwards compatibility).

- Modular configuration: reads all *.MENUITEMS* and *.POSITIONS* files, in sort order (same as in object contents).

MENU config lines with no corresponding TOMENU lines get added to the main menu (replacing a blank "TOMENU -" line).

This allows makers to easily provide add-on packs, each being folder containing .MENUITEMS*, .POSITIONS*, and animations files. Customer simply drops the folder in and resets.

- Backwards-compatible with MLP V1.2 configurations.

- Ball timeouts have been disabled. This should make MLPV2 a little more efficient. However, if you move a bed with balls rezzed, you'll need to delete the balls manually.

- Set poseball's floating text and pie menu sit text by changing its description.
Also, if the ball's description begins with an asterisk ("*"), the poseball is phantom.
After changing ball's description, STOP to delete any balls and then select any pose.

- New LM button type, to pass LMs to other scripts/prims. This allows adding features to furniture, with buttons in the MLP menus, without changing any MLP scripts.

- Warning for duplicate entries in .POSITIONS* files.

- Configuration consistency checker: try "ConfigCheck" in Shutdown menu
NOTE: this will reload .POSITIONS.* files, so backup any saved positions first! It will find buttons with no positions and vice versa.

- AutoZhao support

- Restart menu reorganized:

Use "Pos Reset" button after changing *.POSITIONS* files.

Use "Menu Reset" button after changing *.MENUITEMS* files.

Use "Restart" button to restart all. This used to do only a menu reset.

- MLP bug fix: if you rez a copy, it uses the same channel as the original, and on MLP V1.2 you'd get crosstalk.

The menu script is now reset on rez. This does not reset positions; saved positions are not lost.

- MLP bug fix: Avoid reanimating a non-sitting avatar! This happened in these cases that I'm aware of:

A) Avatar is posed and STOP button is hit and then a new pose is selected. The avatar (no longer sitting) would get animated.

B) Same as above, but instead of STOP button, avatar teleports or relogs

[[Category:MLPV2]]

MLPV2 Public Domain Animations

2012-01-18T01:29:40Z

Chaz Longstaff: Created page with "{{Navbox/MLPV2}} ==Animations: Which are public-domain, which are not?== Note: this list has generally been maintained by Chaz Longstaff. If you want to be added to one of t…"

{{Navbox/MLPV2}}

==Animations: Which are public-domain, which are not?==

Note: this list has generally been maintained by Chaz Longstaff. If you want to be added to one of the lists below and don't know how to edit a wiki page, just IM him and he will add you to the appropriate section that you indicate (please indicate in your IM the section.)

Beginning furniture makers or experimenters often don’t have the money and / or confidence yet to invest in buying licenced animations.

Here's a list of the status of animations from various animators. It's to help you determine which animations you can safely regard as being in the public domain (i.e. "freebies"), versus which ones might be illegally floating around as pirated animations. Using pirated animations -- knowingly or unknowingly, it's the same -- can cause your creations to be deleted by LL and get you a bad reputation just when you are starting out and trying to get known.

Now, just because the animations are in the public domain doesn't always make them "good quality" -- they can be dated, and show their age, which can be why they were released at a certain point for free. But when you are just started out and practising, or want to make a few things just for friends, they can be very useful.

In the lists below, "confirmed in conversation with CL" -- the CL stands for Chaz Longstaff.

===Genuine freebies (last updated 17 Jan 2012)===
* Ayla Holt [5]
* Butcher Cassidy (confirmed in conversation with CL)
* Chip Midnight (confirmed in conversation with CL)
* Damien Fate (confirmed in conversation with CL)
* Emma Thorn (confirmed in conversation with CL 3 August 2008)
* Fleabite Beach (confirmed in conversation with CL 5 June 2008)
* Kammie Rayna [5]
* Linda Kellie [5]
* linkin Slate (confirmed in conversation with CL)
* Ulrika Zugzwang (from her profile, noted by CL)
* YadNi Monde (confirmed in conversation with CL)
* Yuriko Nishi (confirmed in conversation with CL 5 June 2008)

===Animators whose stuff always requires a licence (last updated September 15th, 2008)===
* Animator Ragu
* Beau Perkins
* Bella Beleza
* Ben Stravinsky
* Cita Boa
* Craig Altman
* Damen Gorilla
* Dylan Rickenbacker
* fana dechou
* Furr Burt
* Johan Durant
* loufa Shilova
* Medhue Simoni
* mikeD Streeter
* Natalie Oe (confirmed in conversation with CL 13 Aug 2008)
* Nya Raymaker / Jolly Lovenkraft (confirmed in conversation with CL 13 Aug 2008)
* Nytemyst Grace
* Owain Raymaker (confirmed in conversation with CL 13 Aug 2008)
* Parsalin Gullwing
* Sandy Clymer
* Sin Toshi
* Siryn Rosse (confirmed here in this thread in old SL forums 13 Aug 2008)
* store Allen
* suzi sohmers
* Tara Bournemouth
* trebbort subagja
* Varon Kappler
* Zoe Biggles

===Animators who never licence their stuff [1] (last updated September 15th, 2008)===
* Abramelin Wolfe
* Cheree Bury (confirmed here in this thread in old SL forums 13 Aug 2008)
* Darkness Anubis
* Desiree Bisiani (and Cheewha Palen)
* Flip Fitzsimmons
* Hol ALexander
* jamie Cheeky
* Jennifer Brennon
* Lizz Silverstar
* niknak Bugaboo
* Paul Llewelyn
* Paul Lobo
* Phil Deakins
* Ravanne Sullivan
* Renee Irwin
* Riann Maltese

===Animators who produce both licenced and freebie stuff [2] (last updated September 15th, 2008)===
* Darien Caldwell (confirmed in conversation)
* Deira Llanfair (confirmed here in this thread in old SL forums 13 Aug 2008)
* Ferran Brodsky (confirmed in conversation with CL)
* Indika Herbst (confirmed in conversation with CL)
* Lear Cale (confirmed in conversation with CL)
* LordJason Kiesler (confirmed in conversation with CL)
* Starlight Kiesler (confirmed in conversation with CL)

===Animators who released some freebies in the past but now never licence their stuff [3] (last updated September 15th, 2008)===
* Neo Virgo (confirmed in conversation with CL 5 July 2008)
* Owain Raymaker (confirmed in conversation with CL 13 Aug 2008)
* Shukran Fahid (confirmed in conversation with CL 24 Aug 2008. Please do not contact him about these freebies as he is no longer in possession of them; you must obtain them from somewhere else. And, they are not supported.)

===Creator no longer exists [4] (last updated September 15th, 2008)===
* Cid Jacob
* Eva Capalini

===Status Uncertain===
(IM’ed / emailed a minimum of 3 times, but no response. Attempts to contact them have been abandoned. Last updated September 15th, 2008)
* Cristiano Midnight
* Dyonis Blanc
* Gwinivere Grayson
* Kiari LeFay
* Kris Gullwing
* Launa Fauna
* Michael Firefly
* Princess Medici
* Remo Yossarian
* stephenpaul Bliss (reportedly no longer active in SL; status of his animations uncertain.)

* Sine Wave (various creators). Released the following genuine freebies: Lime Jelly, Hipster, We love you girl, and We love you boy. There is a full-perm version of Caramel circulating, but its release was accidental.

===FOOTNOTES===

[1] if you see these animations being used by anyone but them, they are likely pirated.

[2] You need to check with these animators when free stuff created by them comes into your hands.

[3] These people released some stuff as freebies in the distant past, but now only produce animations for their own use, and never licence any of these current ones out.

[4] An effort was made at clarification but no real determination of status was possible owing to the accounts having been deleted from SL. Use at your own risk.

[5] Ayla Holt and Kammie Rayna were avatars used by Linda Kellie. Public domain status confirmed on 17 January 2012 in conversation with Reven Rosca.

Template:Navbox/MLPV2

2012-01-18T01:05:14Z

Chaz Longstaff:

{{Navbox
|float={{{float|right}}}
|width={{{width|30%}}}
|1={{{1|}}}
|title=[[MLPV2]]
|content=For users:
*[[MLPV2_Users_Tutorial | MLPV2 User's Tutorial]]
*[[MLPV2 Users Reference | MLPV2 User's Reference]]
For users and builders:
*[[MLPV2 FAQ | MLPV2 FAQ]]
*[[MLPV2 Troubleshooting Tips | MLPV2 Troubleshooting Tips]]
For builders:
*[[MLPV2 Tutorial | MLPV2 Tutorial]]
*[[MLPV2 Reference Manual | MLPV2 Reference Manual]]
*[[MLPV2 Addons | MLPV2 Addons]]
*[[MLPV2 and Chains TUTORIAL | MLPV2 and Chains Tutorial]]
*[[MLPV2 Link Message Numbers | MLPV2 Link Message Numbers]]
*[[MLPV2 Public Domain Animations | MLPV2 Public Domain Animations]]
*[[MLPV2 Version Tracking]]
}}

<noinclude>
[[Category:MLPV2]]
</noinclude>

MLPV2 Troubleshooting Tips

2011-12-23T23:50:59Z

Chaz Longstaff:

{{Navbox/MLPV2}}
These MLPV2 troubleshooting tips are for normal end users and builders.

== User issues ==

These issues can be seen by any MLPV2 user even when the furniture is reasonably set up.

=== Why am I not being animated? ===
Try turning off your Animation Overrider, if you have one. Whether this is an issue for you depends on a techical detail: the priority of the animations in your AO and the priority of the animations in the MLP/MLPV2 product.

=== Why am I floating? ===
Sometimes we can be using a pose and suddenly we rise about 1 meter higher and stay there. Sometimes this happens in everyone's view, and other times it only appears for some. This is an SL bug and happens with any animation system, not just MLP/MLPV2. The problem usually goes away if you select the pose again, or stand and sit again. Sometimes it may be necessary to relog.

=== Balls won't rez when I choose a pose! ===
First, try STOP. If the balls got deleted for any reason, they won't rez when you pick a pose and the MLP still thinks the balls are there. STOP fixes this. (The timeout in many MLP objects also help avoid this, by doing a STOP if nobody's used it for a while.)

Second (if first doesn't work), try resetting via the MLPV2 menu: "OPTIONS -> Shutdown... -> Restart".

Consider if maybe they *are* rezzing, but way below you or way above you -- check the description line of the MLP object to see if there is a number in there, in which case set it to 0.

=== Menu doesn't come up ===
Make sure you're on land where you are allowed to run scripts. There is a "no scripting" icon at the top of the viewer screen if you can't.

If you can't, try setting your group to the land's group. If that makes the no-scripting icon go away, set the MLP object to the land's group. (Do this in the Edit tab, or be wearing the group tag when you rez the object.)

If that isn't the problem, most likely it had a stack/heap error when you were away.

If the object permissions allow it, select the object and use "Reset Scripts". (In original style viewers, this is SL menu "Tools -> Reset Scripts in Selection". For SL2, I have no idea where it is. Naughty LL for goofing everything up.)

If this is a recurring problem, there is an MLPV2 recovery script; ask the MLPV2 group for more info. Alternatively, delete some of the poses, to allow more room.

=== "Animate me" permission popup not happening===

You won't get the animate permission popup if you were the last person on a particular poseball. It keeps your permission. You also don't get animate permission for yourself when MLP is used as a HUD, because worn items give permission automatically. (So do sat-upon items, but in the case of MLP, the script that takes permission is in the furniture, not the ball.)

=== avatar != perm key ===
This is some debugging code that Lear had left exposed by mistake in some versions. It can be ignored; it is not really an error.

If it is annoying, just update to the latest script set. (Users can do this if the item is modifiable, but users should ask the maker first in case the maker has made custom modifications or is using add-on scripts.)

=== OPTIONS menu doesn't work after deeding to group ===
If you deed an MLP, you lose the OPTIONS menu unless you remember to change all the OWNER menus to GROUP menus, and even then you won't be able to use full shutdown.

== Builder issues ==

=== Animation xyx not found ===
* Check that the animation is indeed in the prim
* Check the spelling
* If you are using expression suffixes, check that you didn't put a space before the expression suffix
* Check that as a separator in POSE lines you have used only <pre>|</pre> or <pre>space|space</pre> You can also use two spaces on each side of the vertical bar, but you cannot use three spaces: the superfluous space is not stripped away while reading the notecard; instead, it gets treated as part of the animation name, and thus the animation name can't be found.
* Also check for invisible soft-returns that may have come in if you were doing your work in another program such as Microsoft Word.

=== Animation won't remember its position ===
This can occur that even though you've triple-checked all your work; there will be an animation that sometimes will come out in the right position, sometimes not. After a bit of head-banging, you realize it all depends on which animation you played just before it. If the creator of that animation did not set a hip position for it, you will get different results depending on which pose you ran last. That is, if you have 3 animations, 2 with hip positions and one without, the hip position for the one without will be left over from whichever of the last two animations you used. Which may throw your pose all off. There is nothing you can do except abandon use of the animation; the problem is in the animation itself, and it's not suitable for use with MLP-like scripts though it may work fine as sold in a static poseball.

=== Balls rez on top of each other, even though you are sure you have positions right. ===
Check for duplicate stored positions. *Any* duplicate stored positions, even those not related to the pose in question, can cause this.

Check for the memory script having blown up during booting. It's easy to miss this, as the error bubble only shows for a short time then goes away. To ensure you don't miss it, you can in Preferences for "Text Chat" turn on "Show script errors and warnings as regular chat." That way, you'll be able to see such script problems even after problem bubble has faded.

=== Balls: not enough rezzing ===
You have a Menu with poses that have 4 animations to them, but only 2 balls are rezzing. ||Check that you didn't tell the pose to only rez 2 balls. Example: <pre>MENU Cuddles | ALL | BLUE | PINK</pre> for 4 animations should be something like <pre>MENU Cuddles | ALL | BLUE | PINK | BLUE | PINK</pre> (or whatever) . Easy mistake for tired eyes to make!

Also, check that you didn't drop the permission parameter. For instance, if you say
<pre>MENU Cuddles | PINK | BLUE </pre>
forgetting to put in there the [ALL | GROUP | OWNER] parameter, MLP will get mixed up, think that PINK is the permission parameter, and only rez the blue ball.

if you say
<pre>MENU Cuddles | PINK </pre>
No balls will rez at all.

Fix: put a permission parameter back in.

===Booting up: MLP starts, gets a bit of the way, then goes no further ===

Check that you have both a .MENUITEMS and .POSITIONS notecard in there.

=== Couldn't find (script)" error ===
If you get a message like this upon first dragging and dropping the MLPv2 scripts into a prim, disregard it. It occurs because a prim contents are very slow to refresh in SL, and one script thinks another one is not there yet. Do nothing; it will sort itself out in a few seconds.

=== llDialog: button labels must be 24 or fewer characters long ===
You have almost certainly forgotten a <pre>|</pre> in a POSE line. Consequently, the scripts were counting the Button name and the first animation name as the button name, making the button name too long.

=== Notecards: I set my notecards to full-perm but customers can't open them to save positions, etc. ===
This happens if the object is no-modify. You can't open notecards in a no-modify object. SL limitation.

=== "No Unused TOMENU" Getting this msg but I know that's not right ===
Check the top of your main MENUITEMS card, referring to the help in this section https://wiki.secondlife.com/wiki/MLPV2_Reference_Manual#.MENUITEMS.2A_NOTECARDS

=== Props don't rez and I have everything right ===
# Make sure you have the ~props script in the MLP object. (Actually, this won't keep the prop from rezzing; it will keep it from saving its position, and keep it from deleting itself when moving to a new pose.)
# MLP is very case sensitive. CHAT 2 in .MENUITEMS does not equal Chat 2 in the props notecard. Check to make sure the case matches.
# Watch the prim count on the parcel where you are working. If the available prim count is going down, then your prop is rezzing -- just not somewhere where you are seeing it.

=== "Script run-time error / Stack-Heap Collision" ===
This is a clue that, sadly, there are too many items in your .menuitems.xxx or .positions.xxx notecards for the script memory to handle. Congratulations, you've just been initiated into the battle-scarred club like the rest of us.

First, make sure the scripts are compiled Mono, not LSL. By default they're Mono and you're better off if you do NOT recompile them.

Second, make sure you have no unused positions stored in any .positions notecards. See tidying tip here https://wiki.secondlife.com/w/index.php?title=MLPV2_Reference_Manual&action=submit#TIP.21_Positions_Notecard_tidying. Tidy, restart and see if that helps.

Third: try optimizing your saved .POSITIONS. If you have old .POSITIONS notecard data with lots of trailing zeros, you can get them trimmed down using this procedure:

# drop .MENUITEMS.reorient (from MLP Tools box) in.
# Menu Reset.
# Use the Reorient menu to move all the poses by 1 cm. This will save all the poses, with only a small change. If you don't want the 1cm change, then just move it back 1cm after it finishes. Wait for both props and pose adjustment to complete! (Be patient!)
# dump pos, dump props, and save to appropriate notecards.
# Delete MENUITEMS.reorient, and restart.

This will strip all the trailing zeros.

Fourth: if your anims are mod, you can change the names. Use short names, which take less memory. Short button names also use less memory.

The last resort is more drastic. You must give up on some poses, and delete their POSE lines from the .MENUITEMS* cards, and their position settings from the .POSITIONS* cards. You may leave the actual animations in the MLPv2 prim, but you might as well remove them as they won't be used anyway.

=== What do I do about balls that are sunk into the mattress? ===
This problem is caused by the animation hip offset being too high. One fix is to redo the animation and set the hip offset lower. If you can't do that, then there are workarounds.

One workaround is to make sure the first pose on every menu has a position where the balls are visible.

The other workaround is to change the sit target in the poseball, so the balls will be higher for the same avatar positions.

'''Note: this will affect all poses, making the balls appear higher for all poses.'''

# Pull out ~ball. Open it, and edit the ~ball script inside.
# For MLPV2.4x and later, near the top of the script:
## Look for this: "vector SitTarget = <0.,0.,.1>"
## Change it to : "vector SitTarget = <0.,0.,-.4>" (Note that .1 changed to -.4: adjust to taste.)
# Versions before MLPV2.4x:
## Look for this: "llSitTarget(<0.0,0.0,0.1>, ZERO_ROTATION);"
## Change it to : "llSitTarget(<0.0,0.0,-.4>, ZERO_ROTATION);" (Note that .1 changed to -.4: adjust to taste.)
# Take the ~ball object into inventory
# Delete ~ball from the MLPV2
# Drag the updated ~ball from inventory into the MLPV2

This will make all the poses .5 M lower than they were, with the balls at the same place. If that's a bigger change than you wanted, try -.2 or -.1 (that is, adjust to taste).

For versions prior to MLPV2.4z6, you will then need to adjust all the positions to compensate. I suggest you use the .MENUITEMS.reorient notecard for this.

=== Sequence just won't run ===
Q: Heres what I have setup in the .sequences notecard:

<pre>SEQUENCE | Romantic
MENU | Romance
POSE | standing
AVWAIT | 0 | Waiting for someone to sit on ball
WAIT | 10
POSE | Kiss
WAIT | 10
POSE | Enter
WAIT | 15...
...REPEAT</pre>

It shows up in the menu selection, but no poseballs are rezzed when you select the sequence. Here's what I have in the .MENUITEMS notecard pertaining to the sequence-

<pre>MENU Romantic
LINKMSG Romantic | 0,-4,-12001,SEQUENCE Romantic
LINKMSG PAUSE | 0,-4,-12001,PAUSE
LINKMSG RESUME | 0,-4,-12001,RESUME
SWAP
STOP
BACK</pre>

A: Your problem is simple: you have two buttons with the same label, which isn't allowed.

=== Sequence just won't run or skips poses in it===
Currently (2011), the sequencer script won't complain to you if the poses you reference actually exist or not. You're on your own for making sure they actually exist and are named exactly the same (in a menu card) as the way you are referring to them. So watch for this.

=== Xcite! features such as tilt / arousal just don't seem to work ===
Make sure you have the latest set of partner scripts (as of Jan 2012, the latest release was I think in 2009.) Make sure your own Xcite! bits aren't horribly out of date -- you need 3.0 bits or higher. Contacting xcite help isn't of much use; as of mid 2011 they became non-responsive to business partners.

That being said, features won't work unless the xcite partner script is set be either no copy or no transfer. They also won't work if the perms were wrong when you rezzed the product, so edit the script and reset it. That will make the script start to run -- it dies upon start up if perms on the script are wrong.