Monster Maker - Revision history

Songbird: /* Bodypart Sizes */

2022-03-15T08:35:12Z

Bodypart Sizes

← Older revision		Revision as of 08:35, 15 March 2022
Line 45:		Line 45:
	::'''3rd Person Say''': This is what you see when you use the say command or don't use poses while communicating on channels. For example, if you put ''snarls'', people on the channel will see when you type ''pub Hi!'': [Public] Player snarls, "Hi!"		::'''3rd Person Say''': This is what you see when you use the say command or don't use poses while communicating on channels. For example, if you put ''snarls'', people on the channel will see when you type ''pub Hi!'': [Public] Player snarls, "Hi!"

	::'''Breasts, Cocks, Cunts''': This is the number of breasts, cocks, and cunts that the infection has for its base. Remember, this does not mean all players will have it, due to ~~Male Preferred~~, ~~Female Only~~ and ~~like~~ merits.		::'''Breasts, Cocks, Cunts''': This is the number of breasts, cocks, and cunts that the infection has for its base. Remember, this does not mean all players will have it due to No Vagina, No Penis, and similar merits.

	::'''Breast Size, Cock Length, Cunt Length''': This is the size of the parts the monster infection has. Remember that all these numbers represent proportionately to size 5. So, if you have size 12 for cock length, that's size 12 for size 5. If your monster's size is 1, it'll still have a cock size ''proportionately'' equivalent to 12, meaning something closer to size 2 or so, but you still input it as 12.		::'''Breast Size, Cock Length, Cunt Length''': This is the size of the parts the monster infection has. Remember that all these numbers represent proportionately to size 5. So, if you have size 12 for cock length, that's size 12 for size 5. If your monster's size is 1, it'll still have a cock size ''proportionately'' equivalent to 12, meaning something closer to size 2 or so, but you still input it as 12.

Songbird: /* Tips and Hints */

2017-10-20T06:19:17Z

Tips and Hints

← Older revision		Revision as of 06:19, 20 October 2017
Line 131:		Line 131:
	::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.		::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.
	::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.		::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.
	::* Local stats refer to stats that you the player can change with ~~either @set me=<stat>:~~<~~value~~> ~~or &~~<~~stat~~> me=<value>.		::* Local stats refer to stats that you the player can change with lset <Form Name>/<statname>=<value>
	::* Case statements can be used in lieu of messy [if ][else if ][end if] statements. For example: [case stat cocks of [player] >][when (target) 10]many[end when][when (target) 6]several[end when][when (target) 3]a few[end when][when (target) 2]a couple[end when][when (target) 0]a[end when][when 1]no[end when][end case] cock[if stat cocks of [player] > 1]s[end if]. For more information, check out +help string parsing/case on the MUCK.		::* Case statements can be used in lieu of messy [if ][else if ][end if] statements. For example: [case stat cocks of [player] >][when (target) 10]many[end when][when (target) 6]several[end when][when (target) 3]a few[end when][when (target) 2]a couple[end when][when (target) 0]a[end when][when 1]no[end when][end case] cock[if stat cocks of [player] > 1]s[end if]. For more information, check out +help string parsing/case on the MUCK.

Songbird at 18:06, 15 August 2017

2017-08-15T18:06:08Z

← Older revision		Revision as of 18:06, 15 August 2017
Line 203:		Line 203:
	:: You can type @nviewparse followed by a string of code or description portion to get it checked for common errors and look at it in an organized fashion. For @formparse, you can look over your submitted (not yet approved) forms' portions as well as approved forms to look over String Parsing. Just type the @formparse command for the syntax. Using this, you can see what parsing might've been used on some of your favorite forms!		:: You can type @nviewparse followed by a string of code or description portion to get it checked for common errors and look at it in an organized fashion. For @formparse, you can look over your submitted (not yet approved) forms' portions as well as approved forms to look over String Parsing. Just type the @formparse command for the syntax. Using this, you can see what parsing might've been used on some of your favorite forms!

	''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch and ~~Songbird~~ or post a +request under 'Building' to get it added here!''		''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch and Song or post a +request under 'Building' to get it added here!''

	[[Category:Monster Making]]		[[Category:Monster Making]]

Cyrus: /* Templates */

2017-02-11T21:28:28Z

Templates

← Older revision		Revision as of 21:28, 11 February 2017
Line 172:		Line 172:

	::''Color''		::''Color''
	:[if color present in [player]][~~local stat~~ color of [player]][else]<default>[end if]		:[if color present in [player]][lstat color of [player]][else]<default>[end if]
	::''Color2''		::''Color2''
	:[if color2 present in [player]][~~local stat~~ color2 of [player]][else]<default>[end if]		:[if color2 present in [player]][lstat color2 of [player]][else]<default>[end if]
	::''Color3''		::''Color3''
	:[if color3 present in [player]][~~local stat~~ color3 of [player]][else]<default>[end if]		:[if color3 present in [player]][lstat color3 of [player]][else]<default>[end if]
	::''Example:''		::''Example:''
	::Skin Description: a sleek coat of [if color present in [player]][~~local stat~~ color of [player]][else]tawny orange[end if] fur all over their body with [if color2 present in [player]][~~local stat~~ color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.		::Skin Description: a sleek coat of [if color present in [player]][lstat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 present in [player]][lstat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.

	:'''Arm/Tail Divider Support''': The String Parsing used in order to add in alternative descriptions for Arm Divider and Tail Divider usage.		:'''Arm/Tail Divider Support''': The String Parsing used in order to add in alternative descriptions for Arm Divider and Tail Divider usage.

Songbird at 02:42, 15 April 2015

2015-04-15T02:42:03Z

← Older revision		Revision as of 02:42, 15 April 2015
Line 50:		Line 50:

	=== Descriptions and Transformations ===		=== Descriptions and Transformations ===
	::This section can be one of the trickier portions. Here, you input the descriptions for each body part -- how they look when you view their description. Transformations are what is viewed, ~~first~~-person, by the player who's being infected by this monster. String parsing and use of ''they'', ''their'', and ''them'' are all key in the Description fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.		::This section can be one of the trickier portions. Here, you input the descriptions for each body part -- how they look when you view their description. Transformations are what is viewed, second-person, by the player who's being infected by this monster. String parsing and use of ''they'', ''their'', and ''them'' are all key in the Description fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.

	::Here is the list of fields:		::Here is the list of fields:
Line 76:		Line 76:
	::'''Short Skin Description''': This is the less-often used description. Mainly for heat messages and the like, it is also displayed when the [skin] string parsing is used. Using only two or three adjectives. For example, if you were wishing to describe a rabbit's fur, you could describe it as: ''soft, silky'' for the short description.		::'''Short Skin Description''': This is the less-often used description. Mainly for heat messages and the like, it is also displayed when the [skin] string parsing is used. Using only two or three adjectives. For example, if you were wishing to describe a rabbit's fur, you could describe it as: ''soft, silky'' for the short description.

	::'''Skin Transformation''': This is the ~~first~~-person transformation message you see when you transform into this monster. For example: ''Your skin shudders and itches as many minute fibers spring from your flesh into a thick coat of soft, silky fur.'' would display as just that when you transform your skin to this monster.		::'''Skin Transformation''': This is the second-person transformation message you see when you transform into this monster. For example: ''Your skin shudders and itches as many minute fibers spring from your flesh into a thick coat of soft, silky fur.'' would display as just that when you transform your skin to this monster.

	::'''Head, Torso, Arms, and Legs Description''': Like the Long Skin Description, these are what will be displayed. They will also be following ''Their head is'', ''Their body is'', ''Their arms are'', and ''Their legs are'', so remember not to include that in the description. For example, let's say you want "Their arms are long and lean." to appear in the description. You would enter into the field: ''long and lean''.		::'''Head, Torso, Arms, and Legs Description''': Like the Long Skin Description, these are what will be displayed. They will also be following ''Their head is'', ''Their body is'', ''Their arms are'', and ''Their legs are'', so remember not to include that in the description. For example, let's say you want "Their arms are long and lean." to appear in the description. You would enter into the field: ''long and lean''.

Songbird: Changed instances of 1st person to 2nd person

2015-04-15T02:40:53Z

Changed instances of 1st person to 2nd person

← Older revision		Revision as of 02:40, 15 April 2015
Line 28:		Line 28:
	:: The Bodypart Sizes section is divided into several fields. These are as follows:		:: The Bodypart Sizes section is divided into several fields. These are as follows:
	::* Size		::* Size
	::* ~~1st~~ Person Say		::* 2nd Person Say
	::* 3rd Person Say		::* 3rd Person Say
	::* Breasts		::* Breasts
Line 41:		Line 41:
	::'''Size''': This refers to the overall size of the monster. Human is size 5 (ranges from 5'-6'6", generally with some leeway.) Body size is fairly ambiguous and purposely so, but 5 is the starting point. It goes up and down from there, from 1 to 30 (35 for special forms like privately purchased forms).		::'''Size''': This refers to the overall size of the monster. Human is size 5 (ranges from 5'-6'6", generally with some leeway.) Body size is fairly ambiguous and purposely so, but 5 is the starting point. It goes up and down from there, from 1 to 30 (35 for special forms like privately purchased forms).

	::'''~~1st~~ Person Say''': This is what you see when you use the say command or don't use poses while communicating on channels. For example, if you put ''snarl'', you will see when you type ''pub Hi!'': [Public] You snarl, "Hi!"		::'''2nd Person Say''': This is what you see when you use the say command or don't use poses while communicating on channels. For example, if you put ''snarl'', you will see when you type ''pub Hi!'': [Public] You snarl, "Hi!"

	::'''3rd Person Say''': This is what you see when you use the say command or don't use poses while communicating on channels. For example, if you put ''snarls'', people on the channel will see when you type ''pub Hi!'': [Public] Player snarls, "Hi!"		::'''3rd Person Say''': This is what you see when you use the say command or don't use poses while communicating on channels. For example, if you put ''snarls'', people on the channel will see when you type ''pub Hi!'': [Public] Player snarls, "Hi!"
Line 109:		Line 109:
	=== Victory and Defeat Messages ===		=== Victory and Defeat Messages ===
	::One of the more complicated parts of monster making is this. Fortunately, there are only a few fields that you have to actually worry about. They are:		::One of the more complicated parts of monster making is this. Fortunately, there are only a few fields that you have to actually worry about. They are:
	::*Monster Defeats Player, ~~1st~~ Person Defeat		::*Monster Defeats Player, 2nd Person Defeat
	::*Player Defeats Monster, ~~1st~~ Person Victory		::*Player Defeats Monster, 2nd Person Victory
	::*Player Defeats Monster, 3rd Person Victory		::*Player Defeats Monster, 3rd Person Victory
	::*Misc. Notes		::*Misc. Notes
Line 116:		Line 116:
	::'''Monster Defeats Player''': This is the easiest of the three defeat fields to fill out. Since the monster is usually a solid specimen of just that infection, you don't have to worry about infection mixes when writing this one up. It is from the player's point of view and being defeated by the monster. For example: ''The goblin looms over you, a leer cracking his lips. Raising a meaty fist, he brings it down over your head again and again until you black completely out.'' You can, of course, put string parsing in and have actions based on the defeated player's statistics, such as the presence of a cock or vagina with [if [player] is male] or [if [player] is female]. Just be sure to review over it and follow String Parsing syntax.		::'''Monster Defeats Player''': This is the easiest of the three defeat fields to fill out. Since the monster is usually a solid specimen of just that infection, you don't have to worry about infection mixes when writing this one up. It is from the player's point of view and being defeated by the monster. For example: ''The goblin looms over you, a leer cracking his lips. Raising a meaty fist, he brings it down over your head again and again until you black completely out.'' You can, of course, put string parsing in and have actions based on the defeated player's statistics, such as the presence of a cock or vagina with [if [player] is male] or [if [player] is female]. Just be sure to review over it and follow String Parsing syntax.

	::'''Player Defeats Monster, ~~1st~~ Person''': The tricky part with this field is accounting for infection parts the player ''doesn't'' have. A victory message triggers based on the Groin infection of the player, and not its other mutations. If you want to incorporate unique aspects of the monster into the victory message, be sure to put a check in for that part existing. This can be accomplished with [if stat mutation/<body part> of [victor] = <monster>]<message if body part has correct infection>[else]<message if that body part isn't present>[end if]. For example: ''You gloat over your fallen opponent before [if stat mutation/ass of [victor] = Scorpion]striking down with your stinger[if stat misc/Tail Divider of [victor] == 1]s[end if][else]beating down with your fist[end if].''		::'''Player Defeats Monster, 2nd Person''': The tricky part with this field is accounting for infection parts the player ''doesn't'' have. A victory message triggers based on the Groin infection of the player, and not its other mutations. If you want to incorporate unique aspects of the monster into the victory message, be sure to put a check in for that part existing. This can be accomplished with [if stat mutation/<body part> of [victor] = <monster>]<message if body part has correct infection>[else]<message if that body part isn't present>[end if]. For example: ''You gloat over your fallen opponent before [if stat mutation/ass of [victor] = Scorpion]striking down with your stinger[if stat misc/Tail Divider of [victor] == 1]s[end if][else]beating down with your fist[end if].''

	::'''Player Defeats Monster, 3rd Person''': Same here as with ~~1st~~ person for difficulties and methods, save you're writing it from an observer's point of view. With the above example, you'd instead have: ''As [victor] gloats over [%p of [victor]] fallen opponent, [%s of [victor]] [if stat mutation/ass of [victor] = Scorpion]strikes down with [%p of [victor]] stinger-tipped tail[if stat misc/Tail Divider of [victor] == 1]s[end if][else]beats down over [%p of [victor]] enemy with [%p of [victor]] fists[end if].'' Your victory messages are as comprehensive as you make them.		::'''Player Defeats Monster, 3rd Person''': Same here as with 2nd person for difficulties and methods, save you're writing it from an observer's point of view. With the above example, you'd instead have: ''As [victor] gloats over [%p of [victor]] fallen opponent, [%s of [victor]] [if stat mutation/ass of [victor] = Scorpion]strikes down with [%p of [victor]] stinger-tipped tail[if stat misc/Tail Divider of [victor] == 1]s[end if][else]beats down over [%p of [victor]] enemy with [%p of [victor]] fists[end if].'' Your victory messages are as comprehensive as you make them.

	::'''Misc. Notes''': This is the area where you would note some of your ideas for monster placement and potential monster powers. Final discretion still lies in the park of staff, but it's always good to voice your ideas, as the creator of the form. Remember that no Dedication or Private powers will be available for usage. For a list of powers that exist, ''list powers'' can be used, and you can ''+rpinfo'' any power to get details about it. Try to match what would be themely for the monster, not just what does the most damage or the like.		::'''Misc. Notes''': This is the area where you would note some of your ideas for monster placement and potential monster powers. Final discretion still lies in the park of staff, but it's always good to voice your ideas, as the creator of the form. Remember that no Dedication or Private powers will be available for usage. For a list of powers that exist, ''list powers'' can be used, and you can ''+rpinfo'' any power to get details about it. Try to match what would be themely for the monster, not just what does the most damage or the like.

Cyrus: /* Templates */

2015-02-10T04:16:00Z

Templates

← Older revision		Revision as of 04:16, 10 February 2015
Line 169:		Line 169:
	::With this, you can see that if the Kitsune/quad variable is blank, the arms will show up anthro, but if any value is in it, the arms will show up like a quadruped's. The 'Quad' naming was arbitrary, and the form is Kitsune. It's a good way to organize variables.		::With this, you can see that if the Kitsune/quad variable is blank, the arms will show up anthro, but if any value is in it, the arms will show up like a quadruped's. The 'Quad' naming was arbitrary, and the form is Kitsune. It's a good way to organize variables.

	:'''Color Chooser Support''': This bit of parsing will allow for folks with a Color Chooser item to have different colors for parts of your form. Remember, there are ~~tree~~ colors supported, Color, Color2 and Color3.		:'''Color Chooser Support''': This bit of parsing will allow for folks with a Color Chooser item to have different colors for parts of your form. Remember, there are three colors supported, Color, Color2 and Color3.

	::''Color''		::''Color''

Songbird: Made parsing examples more comprehensive.

2014-12-05T00:12:14Z

Made parsing examples more comprehensive.

← Older revision		Revision as of 00:12, 5 December 2014
Line 116:		Line 116:
	::'''Monster Defeats Player''': This is the easiest of the three defeat fields to fill out. Since the monster is usually a solid specimen of just that infection, you don't have to worry about infection mixes when writing this one up. It is from the player's point of view and being defeated by the monster. For example: ''The goblin looms over you, a leer cracking his lips. Raising a meaty fist, he brings it down over your head again and again until you black completely out.'' You can, of course, put string parsing in and have actions based on the defeated player's statistics, such as the presence of a cock or vagina with [if [player] is male] or [if [player] is female]. Just be sure to review over it and follow String Parsing syntax.		::'''Monster Defeats Player''': This is the easiest of the three defeat fields to fill out. Since the monster is usually a solid specimen of just that infection, you don't have to worry about infection mixes when writing this one up. It is from the player's point of view and being defeated by the monster. For example: ''The goblin looms over you, a leer cracking his lips. Raising a meaty fist, he brings it down over your head again and again until you black completely out.'' You can, of course, put string parsing in and have actions based on the defeated player's statistics, such as the presence of a cock or vagina with [if [player] is male] or [if [player] is female]. Just be sure to review over it and follow String Parsing syntax.

	::'''Player Defeats Monster, 1st Person''': The tricky part with this field is accounting for infection parts the player ''doesn't'' have. A victory message triggers based on the Groin infection of the player, and not its other mutations. If you want to incorporate unique aspects of the monster into the victory message, be sure to put a check in for that part existing. This can be accomplished with [if stat mutation/<body part> of [victor] = <monster>]<message if body part has correct infection>[else]<message if that body part isn't present>[end if]. For example: ''You gloat over ~~the~~ fallen ~~[loser]~~ before [if stat mutation/ass of [victor] = Scorpion]striking down with your stinger.[else]beating down with your fist.[end if]''		::'''Player Defeats Monster, 1st Person''': The tricky part with this field is accounting for infection parts the player ''doesn't'' have. A victory message triggers based on the Groin infection of the player, and not its other mutations. If you want to incorporate unique aspects of the monster into the victory message, be sure to put a check in for that part existing. This can be accomplished with [if stat mutation/<body part> of [victor] = <monster>]<message if body part has correct infection>[else]<message if that body part isn't present>[end if]. For example: ''You gloat over your fallen opponent before [if stat mutation/ass of [victor] = Scorpion]striking down with your stinger[if stat misc/Tail Divider of [victor] == 1]s[end if][else]beating down with your fist[end if].''

	::'''Player Defeats Monster, 3rd Person''': Same here as with 1st person for difficulties and methods, save you're writing it from an observer's point of view. With the above example, you'd instead have: ''As [victor] gloats over ~~the~~ fallen [~~loser~~]~~, they~~ [if stat mutation/ass of [victor] = Scorpion]~~strike~~ down with ~~their~~ stinger-tipped tail.[else]~~beat~~ down over ~~their~~ enemy with ~~their~~ fists.[end if]'' Your victory messages are as comprehensive as you make them.		::'''Player Defeats Monster, 3rd Person''': Same here as with 1st person for difficulties and methods, save you're writing it from an observer's point of view. With the above example, you'd instead have: ''As [victor] gloats over [%p of [victor]] fallen opponent, [%s of [victor]] [if stat mutation/ass of [victor] = Scorpion]strikes down with [%p of [victor]] stinger-tipped tail[if stat misc/Tail Divider of [victor] == 1]s[end if][else]beats down over [%p of [victor]] enemy with [%p of [victor]] fists[end if].'' Your victory messages are as comprehensive as you make them.

	::'''Misc. Notes''': This is the area where you would note some of your ideas for monster placement and potential monster powers. Final discretion still lies in the park of staff, but it's always good to voice your ideas, as the creator of the form. Remember that no Dedication or Private powers will be available for usage. For a list of powers that exist, ''list powers'' can be used, and you can ''+rpinfo'' any power to get details about it. Try to match what would be themely for the monster, not just what does the most damage or the like.		::'''Misc. Notes''': This is the area where you would note some of your ideas for monster placement and potential monster powers. Final discretion still lies in the park of staff, but it's always good to voice your ideas, as the creator of the form. Remember that no Dedication or Private powers will be available for usage. For a list of powers that exist, ''list powers'' can be used, and you can ''+rpinfo'' any power to get details about it. Try to match what would be themely for the monster, not just what does the most damage or the like.

Cyrus: /* Templates */ updated leg splitter support with proper code.

2014-11-21T03:42:35Z

Templates: updated leg splitter support with proper code.

← Older revision		Revision as of 03:42, 21 November 2014
Line 190:		Line 190:

	:'''Leg Splitter Support''': Similar to Arm/Tail Dividers, adding in an alternate tauric description.		:'''Leg Splitter Support''': Similar to Arm/Tail Dividers, adding in an alternate tauric description.
	:[if ~~stat misc/Leg Splitter of~~ [player] ~~== 1~~]<Leg Splitter active description[else]<normal description>[end if]		:[if taur present in [player]]<Leg Splitter active description[else]<normal description>[end if]
	::Like taurs, this should go in at least the Ass mutation. [legs] can be used for the current legs description.		::Like taurs, this should go in at least the Ass mutation. [legs] can be used for the current legs description.

Cyrus: /* Templates */

2014-11-16T22:57:14Z

Templates

← Older revision		Revision as of 22:57, 16 November 2014
Line 185:		Line 185:
	:[if stat misc/Arm Divider of [player] == 1]<Arm Divider active description>[else]<normal description>[end if]		:[if stat misc/Arm Divider of [player] == 1]<Arm Divider active description>[else]<normal description>[end if]
	::''Tail Divider''		::''Tail Divider''
	:[if stat misc/Tail Divider of [player] == 1]<~~Arm~~ Divider active description>[else]<normal description>[end if]		:[if stat misc/Tail Divider of [player] == 1]<Tail Divider active description>[else]<normal description>[end if]
	::''Example:''		::''Example:''
	::Arm Description: powerfully built with st[if stat misc/Arm Divider of [player] == 1]acked shoulders leading to three pairs of[else]urdy shoulders leading down to their powerful[end if] arms. Each terminates in dexterous hands capped in wicked talons.		::Arm Description: powerfully built with st[if stat misc/Arm Divider of [player] == 1]acked shoulders leading to three pairs of[else]urdy shoulders leading down to their powerful[end if] arms. Each terminates in dexterous hands capped in wicked talons.