MLPV2 Tutorial - Revision history

Andrea Ildor at 22:28, 25 September 2015

2015-09-25T22:28:36Z

← Older revision		Revision as of 15:28, 25 September 2015
Line 1:		Line 1:
	{{Navbox/MLPV2}}		{{Navbox/MLPV2}}

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

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

Andrea Ildor at 22:28, 25 September 2015

2015-09-25T22:28:14Z

← Older revision		Revision as of 15:28, 25 September 2015
Line 1:		Line 1:
	{{Navbox/MLPV2}}		{{Navbox/MLPV2}}

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

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

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

2014-05-13T01:05:17Z

3. Programming a sequence

← Older revision		Revision as of 18:05, 12 May 2014
Line 375:		Line 375:

	You should know by now what the lines above do.		You should know by now what the lines above do.

			=== Programming a loop ===

	The next line causes the whole sequence to repeat.		The next line causes the whole sequence to repeat.
Line 387:		Line 389:
	...		...
	GOTO \| mylabel		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.		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.

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

2014-05-12T22:31:37Z

3. Programming a sequence

← Older revision		Revision as of 15:31, 12 May 2014
Line 332:		Line 332:
	SEQUENCE \| Tour1-seq		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.		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		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.)		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.)		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.)
Line 356:		Line 356:
	AVWAIT \| 0 1 2 3 \| Waiting for all participants!		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.		'''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		WHISPER \| 0 \| /0 and /1 stand together

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

2014-05-12T22:18:18Z

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

← Older revision		Revision as of 15:18, 12 May 2014
Line 290:		Line 290:
	// example menu containing 2 sequences, and sequence controls		// example menu containing 2 sequences, and sequence controls
	MENU Tours... \| ALL		MENU Tours... \| ALL
	LINKMSG ~~Tour~~ \| 0,-4,-12001,SEQUENCE Tour1-seq		LINKMSG Tour1 \| 0,-4,-12001,SEQUENCE Tour1-seq
	LINKMSG Tour2 \| 0,-4,-12001,SEQUENCE tour2-seq		LINKMSG Tour2 \| 0,-4,-12001,SEQUENCE tour2-seq
	LINKMSG PAUSE \| 0,-4,-12001,PAUSE		LINKMSG PAUSE \| 0,-4,-12001,PAUSE

Gianinni Babenco: /* Help button */ +Category:MLPV2

2011-12-25T16:19:04Z

Help button: +Category:MLPV2

← Older revision		Revision as of 09:19, 25 December 2011
Line 549:		Line 549:
	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.		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]]
	[[~~User~~:~~Lear Cale\|Lear Cale~~]] ~~10:31, 14 May 2008 (PDT)~~

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

2011-12-06T20:15:39Z

3. Programming a sequence

← Older revision		Revision as of 13:15, 6 December 2011
Line 343:		Line 343:

	The line above starts the "standing" pose.		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		AVWAIT \| 0 \| Waiting for someone to sit on blue ball

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

2011-12-05T03:17:03Z

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

← Older revision		Revision as of 20:17, 4 December 2011
Line 312:		Line 312:
	STOP stops the sequence and unrezzes the balls. After a STOP, RESUME and PAUSE have no effect.		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.)		'''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 ===		=== 3. Programming a sequence ===

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

2011-08-29T06:35:44Z

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

← Older revision		Revision as of 23:35, 28 August 2011
Line 294:		Line 294:
	LINKMSG PAUSE \| 0,-4,-12001,PAUSE		LINKMSG PAUSE \| 0,-4,-12001,PAUSE
	LINKMSG RESUME \| 0,-4,-12001,RESUME		LINKMSG RESUME \| 0,-4,-12001,RESUME
			LINKMSG NARRATION \| 0,-4,-12001,NARRATION
	SWAP		SWAP
	STOP		STOP
Line 306:		Line 307:

	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.		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.		STOP stops the sequence and unrezzes the balls. After a STOP, RESUME and PAUSE have no effect.

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

2011-08-27T22:16:37Z

3. Programming a sequence

← Older revision		Revision as of 15:16, 27 August 2011
Line 373:		Line 373:
	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.		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.

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

	TIP! Don't repeat the use of label name in a .SEQUENCES card. For example, if you use LABEL\|here in the first sequence you define, don't reuse "here" as a label name in any other subsequent sequences. Come up with a different label name, or you will confuse the script and when sequences are playing, you'll get the message: No such sequence label: 'here' -- even though it is there. The problem is actually that there are too many labels named that, confusing the script.

	=== Avoiding the posename chat ===		=== Avoiding the posename chat ===

← Older revision		Revision as of 15:31, 12 May 2014
Line 332:		Line 332:
	SEQUENCE \| Tour1-seq		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.		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		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.)		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.)		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.)
Line 356:		Line 356:
	AVWAIT \| 0 1 2 3 \| Waiting for all participants!		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.		'''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		WHISPER \| 0 \| /0 and /1 stand together

← Older revision		Revision as of 15:18, 12 May 2014
Line 290:		Line 290:
	// example menu containing 2 sequences, and sequence controls		// example menu containing 2 sequences, and sequence controls
	MENU Tours... \| ALL		MENU Tours... \| ALL
	LINKMSG ~~Tour~~ \| 0,-4,-12001,SEQUENCE Tour1-seq		LINKMSG Tour1 \| 0,-4,-12001,SEQUENCE Tour1-seq
	LINKMSG Tour2 \| 0,-4,-12001,SEQUENCE tour2-seq		LINKMSG Tour2 \| 0,-4,-12001,SEQUENCE tour2-seq
	LINKMSG PAUSE \| 0,-4,-12001,PAUSE		LINKMSG PAUSE \| 0,-4,-12001,PAUSE