https://wiki.flexiblesurvival.com/api.php?action=feedcontributions&feedformat=atom&user=GlitchFlexible Survival - User contributions [en]2026-07-02T03:34:16ZUser contributionsMediaWiki 1.43.1https://wiki.flexiblesurvival.com/index.php?title=Organ_sizes&diff=1574315Organ sizes2021-11-12T05:33:18Z<p>Glitch: </p>
<hr />
<div>The values between asterisks are what to target when using a Nanite Carnal Equalizer to adjust a specific body part. Examples: 'shift breasts=margay' or 'shift cock length=lion beast'.<br />
<br />
The 'Missing' column lists any mutation locations that don't exist for that creature, reducing the number of mutations <br />
required to acquire the Total badge, and carrying forward any previous mutations when Shifted to by a Nanite Adept. For <br />
instance, If a NA shifts to Cat Girl, then to Zombie, she will still have the cat tail in her description. &gt;&lt;&gt; <br />
and Rubber Balls each only have a single mutation location, thus they are listed as missing "all but..."<br />
<br />
NEUT means that the mutation does not carry any inherent sexual characteristics. This means that you will maintain the <br />
organs and sizes you had previously, allowing for Cat Bois, Otter girls, and so on. Currently, this also means that any <br />
child with this mutation on their groin will be born Neuter.<br />
<br />
A note on body size/mass: the numbers are, like the rest of the organ sizes, not in any absolute terms. "5" is human average. Sizes smaller than 5 are smaller than average. Sizes above 5 are larger than average. If the form is more or less humanoid, this translates to taller or shorter, but some forms are dense or differently arranged, such as a tauric form. Currently, the largest size a player can get normally is hardcapped at 20 ('''roughly''' two to three times human average in height, about three to four times human average in mass), while the Kaiju and Quetzalcoatl supernatural dedications allow a larger size bounded by two softcaps. The largest possible height commonly obtainable is 95 for a Tall Giant Kaiju with a Tormunga torso, Giant Size toggle on, and the Overblown and Large Tendencies perks. Any time you look at a player, the first few words of the autodesc will tell you if they are shorter or taller than you are, and roughly by how much.<br />
<br />
{{:Organ_Sizes_Table}}<br />
{| border="1" align="center" class="wikitable"<br />
|}<br />
<br />
= Supplementary Tables =<br />
<br />
== Organ Descriptions ==<br />
<br />
The following table is a list of organ sizes, and how they get described in descriptions of players and monsters. Please take note that multiple breast pairs do not match this table as the individual breasts tend to be smaller than the set breast size, with exceptions made for those with a [[Mammary Magnifier]] and/or a [[Breast Consolidator]]<br />
<br><br />
<br><br />
'''Note that the descriptions of organs are meant to be relative to the body size. Hand filling breasts on a giant are hand filling. For a giant.'''<br />
<br><br />
<br><br />
<br />
=== Cock Length ===<br />
<br />
They have X (description) cock(s)/penis(es)/shaft(s)/maleness(es).<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
! Transformation (Growing)<br />
! Transformation (Shrinking)<br />
|-<br />
| 0-1<br />
| finger sized/minuscule<br />
| You yelp in surprise as a puny organ erupts from the flesh of your nethers- A minuscule penis, no bigger than your index finger.<br />
| You shudder as your manflesh shrinks, eventually becoming something no bigger than your index finger.<br />
|-<br />
| 2-3<br />
| small<br />
| Your groin feels a tad heavy as it fills out, leaving you with a maleness slightly longer than the width of your hand.<br />
| You shiver as your manhood retracts, leaving you with an organ only slightly longer than the width of your hand.<br />
|-<br />
| 4-5<br />
| average<br />
| Your manhood engorges as it begins filling out, leaving you with average organs an average organ, roughly two hand-widths in length.<br />
| Your maleness shrinks until it is about the length of two widths of your hand.<br />
|-<br />
| 6-7<br />
| above average<br />
| Your manhood engorges as it gains in length, eventually being more than two hands can hold.<br />
| Your maleness retracts until it is at a state where it would take a little more than two of your hands to hold.<br />
|-<br />
| 8-9<br />
| large<br />
| Your male organ engorges as it fills out, the organ thick, about half the length of your thigh.<br />
| Your male organ engorges, retracting as it shrinks to about half the length of your thigh.<br />
|-<br />
| 10-11<br />
| thick/heavy<br />
| Your manhood engorges as it seems to gain weight and girth, the organ just shy of your knees.<br />
| Your manhood retracts and eventually comes to rest a short distance above the knee.<br />
|-<br />
| 12-13<br />
| forearm length<br />
| Your manhood engorges, gaining in length until its dimensions become quite comparable to your forearm, fist and all. You can no longer fully wrap a hand around any of your rod.<br />
| Your manhood swells, retracting until its dimensions are similar to your forearm with a clenched fist.<br />
|-<br />
| 14-15<br />
| torso length<br />
| Your manhood engorges, surging in girth and length, and eventually it seems to be as long as your torso. On the plus side you can have a handy chin rest. The downside? You may poke your eye or throat if you sleep in the fetal position.<br />
| Your manhood pulses, shrinking until it is as long as your torso, its tip at your collarbone.<br />
|-<br />
| 16-17<br />
| shin bumping<br />
| Your manhood engorges until its dimensions leave it almost as long as your leg, the fleshy pillar roughly halfway between knee and ankle.<br />
| Your manhood swells, retracting until its length is somewhere between ankle and shin.<br />
|-<br />
| 18-19<br />
| leg length<br />
| Your manhood engorges until you seem to have another leg. It is a struggle to wrap both hands around the thick girth of your meat.<br />
| Your manhood swells as it shrinks down to a size roughly equal to your legs.<br />
|-<br />
| 20-21<br />
| unwieldly<br />
| Your manhood engorges, eventually reaching a point where you may risk tripping over these absurd dimensions.<br />
| Your manhood swells, shrinking down to a slightly more reasonable dimension. However, it seems to have the annoying tendency of being the perfect length to trip over and tangle with your legs.<br />
|-<br />
| 22-23<br />
| body length<br />
| Your manhood engorges until it is as long as you are tall, easily towering above your head. It is rather hard to keep your balance at this point.<br />
| Your manhood swells, and then begins to shrink until the massive rod is as long as you are tall.<br />
|-<br />
| 24+<br />
| body overshadowing/bigger than themself<br />
| Your manhood engorges past all sense of reason and logic, the abomination ridiculously thick, and easily far taller and heavier than you. You wonder how you will remain conscious if you ever get an erection... wait, scratch that. You wonder how you will survive.<br />
| <br />
|-<br />
|}<br />
<br />
=== Ball Size ===<br />
They have (description) balls.<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
! Transformation (Growing)<br />
! Transformation (Shrinking)<br />
|-<br />
| 1-2<br />
| tiny<br />
| You feel some internal shifting as the nanites alter your biology, leaving you with two tiny balls.<br />
| Scrotal flesh dwindles, balls shrinking until you are left with two orbs that could hardly be called balls.<br />
|-<br />
| 3-5<br />
| small<br />
| Scrotal flesh grows taut for a moment as your balls expand to form small, rounded balls.<br />
| Scrotal flesh dwindles as your balls shrink to small rounded balls.<br />
|-<br />
| 6-8<br />
| average<br />
| Scrotal flesh grows taut for a moment as your balls expand to two average sized balls.<br />
| Scrotal flesh dwindles as your balls shrink to two average sized balls.<br />
|-<br />
| 9-11<br />
| large<br />
| Scrotal flesh grows taut for a moment as your balls expand to roughly twice their previous size, your scrotum ending up quite the handful.<br />
| Scrotal flesh dwindles as your balls shrink to roughly half their previous size, your scrotum a literal handful.<br />
|-<br />
| 12-14<br />
| fist sized<br />
| Scrotal flesh grows taut for a moment as your balls expand until each is roughly the size of your clenched fist.<br />
| Scrotal flesh dwindles as your balls shrink until they are about as big as your clenched fist.<br />
|-<br />
| 15-17<br />
| hand filling<br />
| Scrotal flesh grows taut for a moment as your balls expand, surging as each becomes a literal handful- larger than a clenched fist. You cannot even wrap your paw/hand around one.<br />
| Scrotal flesh dwindles as your balls shrink, the spheres eventually a literal handful.<br />
|-<br />
| 18-19<br />
| head sized<br />
| Scrotal flesh grows taut for a moment as your balls expand and swell, your balls only seeming to halt when they are as big as your own head!<br />
| Scrotal flesh dwindles as your balls shrink, eventually coming to a stop at around the size of your head.<br />
|-<br />
| 20-25<br />
| lap filling<br />
| Scrotal flesh grows taut for a moment as your balls expand, each ball of flesh stretching far beyond its normal limits. When all is said and done, both take up a good deal of space between your thighs, becoming a literal lapful.<br />
| Scrotal flesh dwindles as your balls shrink, both eventually large enough to make a literal lapful as they dominate the space between your thighs.<br />
|-<br />
| 26-31<br />
| knee knocking<br />
| Scrotal flesh grows taut for a moment as your balls expand and surge, each nut becoming large enough to dominate a lap, and to make matters worse, they bump against your knees if you walk the wrong way.<br />
| Scrotal flesh dwindles as your balls shrink until they reach a point where either could dominate a lap. At least walking is easier, if still awkward- the damn things bump your knees if you don't stroll along properly.<br />
|-<br />
| 32-37<br />
| shin bumping/seat worthy<br />
| Scrotal flesh grows taut for a moment as your balls expand, each eventually reaching such huge proportions that they are about halfway down to your shins. On the plus side you have a handy seat. On the downside? You have one hell of a problem walking.<br />
| Scrotal flesh dwindles as your balls shrink. Sure, they no longer brush the ground, but you're more liable to trip than ever due to their ungainly size.<br />
|-<br />
| 38-42<br />
| ground brushing<br />
| Scrotal flesh grows taut for a moment as your balls expand, testes literally large enough to brush the ground. On the plus, walking is a little easier, but on the downside that scraping makes stealth a hassle.<br />
| Scrotal flesh dwindles as your balls shrink, testes becoming slightly more manageable, but stealth harder. Giant orbs dragging along the ground have their downsides.<br />
|-<br />
| 43-48<br />
| unwieldly sized<br />
| Scrotal flesh grows taut for a moment as your balls expand until each is large enough to comfortably fit in to the crook of your back. Still ungainly, but at least you will always have something to lean on.<br />
| Scrotal flesh dwindles as your balls shrink, becoming a little more manageable, but by no means easy. A convenient thing to lean on, as either could fit comfortably against your mid-back.<br />
|-<br />
| 49-54<br />
| body sized<br />
| Scrotal flesh grows taut for a moment as your balls expand, each nut as large as you are tall, and probably wider to boot.<br />
| Scrotal flesh dwindles as your balls shrink to something slightly less inconvenient, but strangely more comical. Trouble with doorways, halls, and seating abound!<br />
|-<br />
| 55+<br />
| unfathomably over sized<br />
| Scrotal flesh grows taut for a moment as your balls expand to simply ridiculous proportions. Far larger than you, these grand balls could probably get caught in a door or hallway that you would normally be able to pass easily in to.<br />
|-<br />
|}<br />
<br />
=== Breast Size ===<br />
<br />
It is important to note again, that for the description and the shifting message that your breast individually might not match up with the number. Please make sure to reference your character such that your description and shifting message match up, as these are more important than the actual stat number.<br />
<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Size<br />
! Description<br />
! Transforming (Growing)<br />
! Transforming (Shrinking)<br />
|-<br />
| 0<br />
| nipples<br />
|<br />
| You shudder as you become flatter than FlatsVille. Your chest could pass as a billboard save for the nipples. This could be good or bad depending on your views.<br />
|-<br />
| 1-3<br />
| flat<br />
| You shudder as your bust expands, leaving you slightly less flat than the billboard you were before, two slight mounds giving the impression of bust.<br />
| You shudder as you become flatter than FlatsVille. Your chest could pass as a billboard save for the nipples. This could be good or bad depending on your views.<br />
|-<br />
| 4-7<br />
| small/petite<br />
| You shudder as your breasts expand, leaving you with two perky mounds.<br />
| You shiver as your breasts retract, but you still seem to retain some semblance of a chest, your breasts pert mounds upon your chest.<br />
|-<br />
| 8-11<br />
| average<br />
| You shudder as your breasts expand to a rather average size.<br />
| You shiver as your breasts retract to a rather average looking size.<br />
|-<br />
| 12-15<br />
| large/hand filling<br />
| You shudder as your breasts expand, each bulge of flesh easily able to fill the palm of your hand. Literal handfuls indeed.<br />
| You shiver as your breasts shrink to a smaller size. Still, they are quite generous, each being a rather pleasant handful.<br />
|-<br />
| 16-19<br />
| hefty<br />
| You shudder as your breasts expand a bit beyond the scope of one hand, two now required to grasp the jiggly flesh. Your quite the handful now, and you seem to have a little heft to your chest now.<br />
| You shiver as your breasts shrink down to being two handfuls apiece. You still got quite a bit of jiggle, if slightly less of a handful than you were before.<br />
|-<br />
| 20-23<br />
| grand<br />
| You shudder as your breasts expand and are now quite large and plush, a few cup sizes short of something that could hold your head. Crossing your arms could support these puppies quite nicely.<br />
|You shiver as your breasts shrink down to a rather generous and impressive size, smaller than your head at least. If you crossed your arms, you could support them quite nicely.<br />
|-<br />
| 24-27<br />
| head sized<br />
| You shudder as your breasts expand to a point that each pliant mound is as large as your head. (If have Normal Physics) You are also greeted with a growing soreness in your back. (If you don't have Normal Physics) You are also greeted with a surprising lack of back pain.<br />
| You shiver as your breasts shrink down until they are about as large as your head.<br />
|-<br />
| 28-31<br />
| chest filling<br />
| You shudder as your breasts expand, each impressive easily covering each half of your chest, far larger than your head. The soft fleshy orbs jiggle and bounce quite a bit as you walk, occasionally bumping in to the side of your arms.<br />
| You shudder as your breasts shrink down to a more manageable size, though they are by no means small, each breast far larger than your head. (If you have Normal Physics) Your back does not hurt quite as much. (End if) Your balance improves a little.<br />
|-<br />
| 32-35<br />
| arm filling<br />
| You shudder as your bust expands further, your chest reaching such proportions as they begin to bottom out near the top of your stomach. You have barely enough room to clasp your fingers together if you were to reach around your mammaries. You notice some problems with balance, and you are carrying quite a bit of weight.<br />
| You gasp as your breasts shrink to a point where you can actually reach your fingers if you were to wrap your arms around your titflesh.<br />
|-<br />
| 36-39<br />
| waist bumping<br />
| You shudder as your breasts expand to such immense proportions that the fleshy spheres bump and brush against your waist as you walk. You are really beginning to have balance problems.<br />
| You shiver as your breasts shrink down to around your waist, greatly alleviating balancing issues. Still, they bounce and jiggle against your waist, so that is not saying much.<br />
|-<br />
| 40-43<br />
| knee bouncing<br />
| You shudder as your breasts expand to even greater proportions, the rounded mammaries knocking against your knees as you walk, greatly contributing to bounce and jiggle.<br />
| You sigh as your breasts shrink to a far more reasonable proportion, greatly solving many problems that you were plagued with. Still, your knees bounce those breasts as you walk, and it can be a rather odd sensation.<br />
|-<br />
| 44-47<br />
| body-sized<br />
| You shudder as your breasts expand expand further, billowing out until they are as large as you are. Unsupported they would drag upon the ground, (if you have Normal Physics) but at least the growing back pain is gone, (end if) and if supported, your balance is significantly compromised. How can you even manage to move? That is a mystery only you can answer, considering others will have to deal with all the extra space you take up.<br />
| You shiver as your breasts shrink to far less insane proportions. Still, it is quite maddening, taking up all that space- breasts as large as you are. Balance issues are still abound, but at least you are mobile.<br />
|-<br />
| 48+<br />
| impossibly huge<br />
| You shudder as your breasts expand expand to completely unreasonable proportions. Good luck moving, as these puppies are now larger than you are. It is doubtful you may be able to walk forwards, so you may have to deal with going backwards, if you can even move.<br />
|<br />
|-<br />
|}<br />
<br />
=== Cunt Length ===<br />
They have X (description) vagina(s)/cunt(s)/puss(y/ies)/cleft(s).<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
! Transformation (Growing)<br />
! Transformation (Shrinking)<br />
|-<br />
| 1-2<br />
| minuscule<br />
| You tremble as the nanites rework your anatomy, eventually leaving you with a small mound of flesh between your legs- a small vagina. It is little more than a small hole capable of housing a finger.<br />
| You shudder, in each pussy feeling wet as it shrinks down to minuscule proportions- almost nothing more than a mound of flesh and accompanying hole to go with it. Barely enough room for a finger.<br />
|-<br />
| 3-4<br />
| small<br />
| Your pussy feels wet as it seems to grow deeper, mound growing more prominent. It is not too terribly deep.<br />
| Your pussy feels wet as it shrinks, growing tighter and tighter. It can now only house a few fingers comfortably.<br />
|-<br />
| 5-6<br />
| standard<br />
| Your pussy feels wet as it becomes more prominent, finally resembling something normal. It seems to be fairly standard in size, nothing overly large or small.<br />
| Your pussy feels wet as it shrinks, eventually becoming something more average in size.<br />
|-<br />
| 7-8<br />
| moderately large<br />
| Your pussy feels wet as a shudder runs through your form. Nothing really seems to change outwardly, but a private check reveals your sex to be more able to stretch, and a bit deeper.<br />
| Your pussy feels wet as it seems to tighten, though still above the average depth, retaining a bit of stretch, your hips narrowing a little as well.<br />
|-<br />
| 9-10<br />
| large<br />
| Your pussy feels wet and you squirm uncomfortably, nanites making a few more changes, deepening your sex your hips growing a little wider, as if to allow larger things inside you more comfortably.<br />
| Your pussy feels wet as it shrinks, nanites making changes until it is tighter, your feminine lips becoming a little less pronounced in the process.<br />
|-<br />
| 11-12<br />
| wide<br />
| Your cleft feels wet as it thickens a little, cleft becoming a little more pronounced and defined, the familiar tingle of deepening accompanying such a transformation.<br />
| Your pussy feels wet as it tightens, internals shifting as it reworks itself. You cannot easily take something the size of your forearm anymore.<br />
|-<br />
| 13-15<br />
| thick-lipped<br />
| Your pussy feels wet as it seems to deepen further. There is almost no outward change, but you could comfortably fit something the size of your forearm in there if you had the dexterity to do so.<br />
| Your pussy feels wet as it tightens, shrinking in size, your hips narrowing as well. You're still quite deep, you just cannot cram as much in, only really able to manage something the size of your arm down to your elbow.<br />
|-<br />
| 16-17<br />
| elbow-deep<br />
| Your pussy feels wet as your hips seem to widen a more, greatly enhancing your figure along with giving some much needed room to fit some larger things in. You could easily squeeze a good two thirds of your arm in there.<br />
| Your pussy feels wet as that literal hollow feeling fades, sex tightening as some previous elasticity vanishes.<br />
|-<br />
| 18-19<br />
| arm deep<br />
| Your pussy feels wet as it deepens even more. You begin to wonder a few things, and seem to feel a little hollow in the literal sense. You could easily fit something as long and thick as your entire arm in there.<br />
| Your pussy feels wet as an odd feeling overtakes you. You can take something the size of your arm with ease, but you are not quite as stretchy as you once were.<br />
|-<br />
| 20-21<br />
| cavernous<br />
| Your pussy feels wet as it becomes little more elastic. You cannot help but feel slightly odd as things shift around. You could swear that your sex take takes up a good deal of your body at this point.<br />
| Your pussy feels wet as much of your elasticity fades. You still got something as deep as your torso, but your hips are not as insane as they were, and your bones and internals are now much more normal than they were.<br />
|-<br />
| 22-23<br />
| body length<br />
| Your pussy feels wet as your internals shift drastically. You feel odd- although you cannot pinpoint why. The outward appearance of your vagina seems fine- much the same as it was before, except that it seems to stretch through your entire torso.<br />
|<br />
|-<br />
| 24+<br />
| impossibly elastic<br />
| Your feel pussy feels wet with a familiar sensation as your female parts shift yet again. It is hard to say exactly what happened, aside from some rather impressive hips and an altered bone structure, but you are highly elastic at this point- A torso has its limits, but you might just be able to cram a portion of things larger than that within you.<br />
|<br />
|-<br />
|}<br />
<br />
=== Clit Length ===<br />
<br />
They have X (description) clits(s)/buzzers(es)/buttons(s).<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
|-<br />
| 0-1<br />
| non-existent/always hidden <br />
|-<br />
| 2-3<br />
| nubby/insignificant<br />
|-<br />
| 4-5<br />
| average<br />
|-<br />
| 6-7<br />
| large/plump<br />
|-<br />
| 8-9<br />
| finger length/prominent<br />
|-<br />
| 10-11<br />
| grippable/exposed<br />
|-<br />
| 12-13<br />
| hand length/cock-like<br />
|-<br />
| 14-15<br />
| lengthy <br />
|-<br />
| 16-17<br />
| belly slapping<br />
|-<br />
| 18-19<br />
| awkwardly oversized<br />
|-<br />
| 20-21<br />
| thigh slapping <br />
|-<br />
| 22-23<br />
| forearm sized/thigh length<br />
|-<br />
| 24+<br />
| unspeakably huge<br />
|-<br />
|}<br />
<br />
=== Udder Size ===<br />
<br />
Udder size is tied directly to your breast size, but has a different description. If you want to change your udder size, assuming you have one, you need to change your breast sizes.<br />
<br />
They have an udder, it seems (description) and has (number of breasts) teats.<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
|-<br />
| 0-1<br />
| flat<br />
|-<br />
| 2-4<br />
| small<br />
|-<br />
| 5-7<br />
| average<br />
|-<br />
| 8-10<br />
| large<br />
|-<br />
| 11-13<br />
| bloated<br />
|-<br />
| 14-18<br />
| lap filling<br />
|-<br />
| 19-21<br />
| amazingly huge<br />
|-<br />
| 22-26<br />
| impossibly huge<br />
|-<br />
<br />
|}<br />
<br />
== Size shifting guides ==<br />
<br />
The following tables are the main table's information, a little reworked and sorted into certain categories of <br />
interest.<br><br />
This is mostly done to supply [[Nanite Adepts]] with the [[Nanite Carnal Equalizer]] or [[Nanite Fine Tuner]], or people who like to <br />
use [[Nanite Hypo]]s and [[Sexual Fixative]]s to change their organ sizes. ''This is also good for monster creators who want to <br />
see what has and hasn't been done when it comes to scale tendencies''<br />
<br />
<br><br />
<br><br />
The following table has the following categories:<br />
* Female<br />
* Single organs<br />
* Boob size is the primary factor<br />
* Cunt lengths were selected to start at 8, with a medium and large value supplemented with each available boob size, where <br />
possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Cunt Length<br />
|----<br />
|[[Banshee]]<br />
|1<br />
|8<br />
|----<br />
|[[Squid Girl]]<br />
|1<br />
|8<br />
|----<br />
|[[Lollipop Lady]]<br />
|2<br />
|9<br />
|----<br />
|[[Eagle Girl]]<br />
|2<br />
|16<br />
|----<br />
|[[Valkyrie]]<br />
|3<br />
|8<br />
|----<br />
|[[Female Commando]]<br />
|3<br />
|9<br />
|----<br />
|[[Leech]]<br />
|3<br />
|15<br />
|----<br />
|[[Latex Snow Leopard]]<br />
|4<br />
|8<br />
|----<br />
|[[Female Widow Convert]]<br />
|4<br />
|10<br />
|----<br />
|[[Farm Hen]]<br />
|4<br />
|14<br />
|----<br />
|[[Slurry Girl]]<br />
|4<br />
|28<br />
|----<br />
|[[Hair-bound Woman]]<br />
|5<br />
|8<br />
|----<br />
|[[Knockout Mouse]]<br />
|5<br />
|16<br />
|----<br />
|[[Snow Leopardtaur|Female Snow Leopardtaur]]<br />
|5<br />
|18<br />
|----<br />
|[[Peregrine Girl]]<br />
|6<br />
|7<br />
|----<br />
|[[Fire Elemental]]<br />
|6<br />
|16<br />
|----<br />
|[[Evil Nurse]]<br />
|7<br />
|9<br />
|----<br />
|[[Cherry Cordial]]<br />
|7<br />
|10<br />
|----<br />
|[[Liquid Panthress]]<br />
|7<br />
|24<br />
|----<br />
|[[F15 Girl]]<br />
|8<br />
|8<br />
|----<br />
|[[Busty Succubus]]<br />
|8<br />
|20<br />
|----<br />
|[[Anime Babe]]<br />
|9<br />
|8<br />
|----<br />
|[[Icy Phoenix]]<br />
|9<br />
|10<br />
|----<br />
|[[Busty Cow]]<br />
|10<br />
|8<br />
|----<br />
|[[Cowgirl]]<br />
|10<br />
|15<br />
|----<br />
|[[VTOL Lady]]<br />
|10<br />
|20<br />
|----<br />
|[[Dark Elf Female]]<br />
|14<br />
|18<br />
|----<br />
|[[Wolf Spider]]<br />
|8<br />
|10<br />
|----<br />
|----<br />
|[[Arachne]]<br />
|10<br />
|80<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Female<br />
* Single organs<br />
* Cunt length is the primary factor<br />
* Small, medium and large Boob sizes were included with each cunt length, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Cunt Length<br />
!Cup Sizes<br />
|----<br />
|[[Chocolate Bunny]]<br />
|4<br />
|2<br />
|----<br />
|[[Honey Bee]]<br />
|6<br />
|2<br />
|----<br />
|[[Bearded Dragon Recruit]]<br />
|6<br />
|4<br />
|----<br />
|[[Giant]]<br />
|6<br />
|6<br />
|----<br />
|[[Peregrine Girl]]<br />
|7<br />
|6<br />
|----<br />
|[[Banshee]]<br />
|8<br />
|1<br />
|----<br />
|[[Latex Snow Leopard]]<br />
|8<br />
|4<br />
|----<br />
|[[Anime Babe]]<br />
|8<br />
|9<br />
|----<br />
|[[Busty Cow]]<br />
|8<br />
|10<br />
|----<br />
|[[Lollipop Lady]]<br />
|9<br />
|2<br />
|----<br />
|[[Female Commando]]<br />
|9<br />
|3<br />
|----<br />
|[[Evil Nurse]]<br />
|9<br />
|7<br />
|----<br />
|[[Bunny Girl]]<br />
|10<br />
|3<br />
|----<br />
|[[Leather Mistress]]<br />
|10<br />
|4<br />
|----<br />
|[[Cherry Cordial]]<br />
|10<br />
|7<br />
|----<br />
|[[Icy Phoenix]]<br />
|10<br />
|9<br />
|----<br />
|[[Palmetto Roach]]<br />
|11<br />
|0<br />
|----<br />
|[[Skunk Girl]]<br />
|12<br />
|3<br />
|----<br />
|[[Corota]]<br />
|12<br />
|4<br />
|----<br />
|[[Sexy Dragoness]]<br />
|12<br />
|8<br />
|----<br />
|[[Furie]]<br />
|13<br />
|5<br />
|----<br />
|[[Farm Hen]]<br />
|14<br />
|4<br />
|----<br />
|[[Leech]]<br />
|15<br />
|3<br />
|----<br />
|[[Cowgirl]]<br />
|15<br />
|10<br />
|----<br />
|[[Eagle Girl]]<br />
|16<br />
|2<br />
|----<br />
|[[Knockout Mouse]]<br />
|16<br />
|5<br />
|----<br />
|[[Lizard Girl]]<br />
|17<br />
|3<br />
|----<br />
|[[Snow Leopardtaur|Female Snow Leopardtaur]]<br />
|18<br />
|5<br />
|----<br />
|[[Dark Elf Female]]<br />
|18<br />
|14<br />
|----<br />
|[[Shadow Dragon]]<br />
|19<br />
|4<br />
|----<br />
|[[Goo Girl]]<br />
|20<br />
|3<br />
|----<br />
|[[Busty Succubus]]<br />
|20<br />
|8<br />
|----<br />
|[[VTOL Lady]]<br />
|20<br />
|10<br />
|----<br />
|[[Female Lamia]]<br />
|24<br />
|3<br />
|----<br />
|[[Liquid Panthress]]<br />
|24<br />
|7<br />
|----<br />
|[[Slurry Girl]]<br />
|28<br />
|4<br />
|----<br />
|[[Centaur Mare]]<br />
|30<br />
|3<br />
|----<br />
|[[Wolf Spider]]<br />
|10<br />
|8<br />
|----<br />
|----<br />
|[[Arachne]]<br />
|80<br />
|10<br />
|----<br />
|}<br />
<br />
<br />
The following table has the following categories:<br />
* Male<br />
* Single organs<br />
* Cock length is the primary factor<br />
* Small, and large ball sizes, as well as nipple and nippleless were included with each cock length, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Cock Length<br />
!Ball Size<br />
!Nipples?<br />
|----<br />
|[[Mountain Man]]<br />
|5<br />
|4<br />
|*<br />
|----<br />
|[[Male Alley Cat]]<br />
|6<br />
|1<br />
|<br />
|----<br />
|[[Anole]]<br />
|6<br />
|2<br />
|<br />
|----<br />
|[[Fey Folke]]<br />
|6<br />
|4<br />
|<br />
|----<br />
||[[Water Moccasin|Male Water Moccasin]]<br />
|6<br />
|4<br />
|<br />
|----<br />
||[[Villainous Gnome]]<br />
|6<br />
|6<br />
|<br />
|----<br />
|[[Horseshoe Crab]]<br />
|6<br />
|13<br />
|<br />
|----<br />
|[[Raptorian]]<br />
|7<br />
|4<br />
|<br />
|----<br />
|[[Aassahke Male]]<br />
|8<br />
|3<br />
|<br />
|----<br />
|[[Fox Boy]]<br />
|8<br />
|3<br />
|<br />
|----<br />
|[[Ebony Raven]]<br />
|8<br />
|4<br />
|<br />
|----<br />
|[[Pangolin]]<br />
|8<br />
|4<br />
|<br />
|----<br />
|[[German Shepherd]]<br />
|8<br />
|4<br />
|*<br />
|----<br />
|[[Quilled Tousky]]<br />
|8<br />
|5<br />
|<br />
|----<br />
|[[Latex Fox]]<br />
|8<br />
|6<br />
|<br />
|----<br />
|[[Treant]]<br />
|8<br />
|8<br />
|<br />
|----<br />
|[[Circus Clown]]<br />
|8<br />
|10<br />
|<br />
|----<br />
|[[Orthom Brute]]<br />
|8<br />
|12<br />
|<br />
|----<br />
|[[Orc]]<br />
|9<br />
|5<br />
|<br />
|----<br />
|[[Gladiator]]<br />
|10<br />
|4<br />
|<br />
|----<br />
|[[Half-Lizard]]<br />
|10<br />
|4<br />
|<br />
|----<br />
|[[Stegosaurian]]<br />
|10<br />
|7<br />
|<br />
|----<br />
|[[Honey Bear]]<br />
|10<br />
|10<br />
|<br />
|----<br />
|[[Nephilim]]<br />
|10<br />
|16<br />
|*<br />
|----<br />
|[[Skunk Beast]]<br />
|11<br />
|7<br />
|<br />
|----<br />
|[[Wolf Boy]]<br />
|12<br />
|4<br />
|<br />
|----<br />
|[[Porcupine]]<br />
|12<br />
|6<br />
|<br />
|----<br />
|[[Wolf Beast]]<br />
|12<br />
|6<br />
|<br />
|----<br />
|[[Gargoyle Sentinel]]<br />
|12<br />
|12<br />
|<br />
|----<br />
|[[White Siberian Tiger]]<br />
|12<br />
|16<br />
|<br />
|----<br />
|[[Male Rex]]<br />
|13<br />
|6<br />
|<br />
|----<br />
|[[Clockwork Fox Guy]]<br />
|13<br />
|6<br />
|<br />
|----<br />
|[[Troll]]<br />
|14<br />
|7<br />
|<br />
|----<br />
|[[Killer Whale]]<br />
|14<br />
|10<br />
|<br />
|----<br />
|[[Fox Taur]]<br />
|14<br />
|16<br />
|<br />
|----<br />
|[[Dandy Peacock]]<br />
|15<br />
|15<br />
|<br />
|----<br />
|[[Lion Beast]]<br />
|16<br />
|6<br />
|<br />
|----<br />
|[[Clydesdale Stud]]<br />
|16<br />
|10<br />
|<br />
|----<br />
|[[Anthro Dolphin]]<br />
|16<br />
|15<br />
|<br />
|----<br />
|[[Arctic Fox]]<br />
|16<br />
|20<br />
|<br />
|----<br />
|[[Muscle Hulk]]<br />
|16<br />
|26<br />
|<br />
|----<br />
|[[Dark Elf Male]]<br />
|18<br />
|10<br />
|<br />
|----<br />
|[[Tarragon]]<br />
|18<br />
|13<br />
|<br />
|----<br />
|[[Clownfish]]<br />
|18<br />
|19<br />
|<br />
|----<br />
|[[Donkey Boy]]<br />
|18<br />
|30<br />
|*<br />
|----<br />
|[[Horned Wyvern]]<br />
|20<br />
|9<br />
|<br />
|----<br />
|[[Friesian Stallion]]<br />
|20<br />
|14<br />
|<br />
|----<br />
|[[Ogre]]<br />
|24<br />
|24<br />
|<br />
|----<br />
|[[Centaur Stallion]]<br />
|28<br />
|20<br />
|<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Herm<br />
* Single organs<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Cunt Length<br />
!Cock Length<br />
!Ball Size<br />
|----<br />
|[[Magma Wurm]]<br />
|0<br />
|10<br />
|12<br />
|0<br />
|----<br />
|[[Palmetto Roach]]<br />
|0<br />
|11<br />
|12<br />
|0<br />
|----<br />
|[[Priapan Orca]]<br />
|0<br />
|12<br />
|12<br />
|6<br />
|----<br />
|[[Water Hydra]]<br />
|0<br />
|14<br />
|14<br />
|8<br />
|----<br />
|[[Ancient Tortoise]]<br />
|2<br />
|5<br />
|4<br />
|0<br />
|----<br />
|[[Kobold Herm]]<br />
|2<br />
|6<br />
|5<br />
|1<br />
|----<br />
|[[Math Teacher]]<br />
|4<br />
|2<br />
|8<br />
|0<br />
|----<br />
|[[Jorogumo]]<br />
|4<br />
|12<br />
|12<br />
|0<br />
|----<br />
||[[Deer Herm]]<br />
|4<br />
|12<br />
|12<br />
|12<br />
|----<br />
|[[Vampire Herm]]<br />
|4<br />
|18<br />
|14<br />
|0<br />
|----<br />
|[[Water Dragon]]<br />
|5<br />
|6<br />
|6<br />
|5<br />
|----<br />
|[[Genetically Superior Human]]<br />
|5<br />
|15<br />
|16<br />
|5<br />
|----<br />
|[[Kangaroo]]<br />
|5<br />
|36<br />
|36<br />
|14<br />
|----<br />
|[[Ember Breeder]]<br />
|6<br />
|6<br />
|6<br />
|2<br />
|----<br />
|[[Striped Snake Beast]]<br />
|6<br />
|13<br />
|13<br />
|6<br />
|----<br />
|[[M1A1H]]<br />
|6<br />
|16<br />
|16<br />
|0<br />
|----<br />
|[[Amazonian]]<br />
|6<br />
|16<br />
|16<br />
|6<br />
|----<br />
|[[Blue Gryphon]]<br />
|8<br />
|13<br />
|13<br />
|7<br />
|----<br />
|[[Blue Sphinx]]<br />
|8<br />
|18<br />
|18<br />
|19<br />
|----<br />
|[[Hugely Hung Happy Hyper Herm Horse]]<br />
|20<br />
|60<br />
|60<br />
|20<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Female<br />
* Single organs, as many boobs as possible<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Breasts<br />
!Cunt Length<br />
|----<br />
|[[Feral Wolfess]]<br />
|3<br />
|8<br />
|9<br />
|----<br />
|[[Shadow Vixen]]<br />
|3<br />
|6<br />
|8<br />
|----<br />
|[[Fox Girl]]<br />
|4<br />
|6<br />
|12<br />
|----<br />
|[[Female Alley Cat]]<br />
|4<br />
|6<br />
|6<br />
|----<br />
|[[Female Husky]]<br />
|6<br />
|4<br />
|10<br />
|----<br />
|[[MSPA Series 6]]<br />
||8<br />
|8<br />
|8<br />
|----<br />
|[[Pink Panda]]<br />
|9<br />
|8<br />
|10<br />
|----<br />
|[[Chocolate Cow]]<br />
|12<br />
|4<br />
|28<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Herm<br />
* Single organs, as many boobs as possible<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Breasts<br />
!Cunt Length<br />
!Cock Length<br />
!Ball Size<br />
|----<br />
||[[Hyena|Hyena Herm]]<br />
|2<br />
|6<br />
|8<br />
|14<br />
|6<br />
|----<br />
||[[Wolfen Predator]]<br />
|3<br />
|6<br />
|24<br />
|18<br />
|13<br />
|----<br />
|[[Cerberus Herm]]<br />
|5<br />
|12<br />
|18<br />
|18<br />
|0<br />
|----<br />
|[[Painted Wolf Herm]]<br />
|7<br />
|4<br />
|10<br />
|10<br />
|10<br />
|----<br />
|[[Panther Taur]]<br />
|8<br />
|6<br />
|14<br />
|14<br />
|15<br />
|----<br />
|[[Collie Herm]]<br />
|10<br />
|6<br />
|13<br />
|12<br />
|4<br />
|----<br />
|[[Ember Render]]<br />
|12<br />
|4<br />
|18<br />
|12<br />
|18<br />
|----<br />
|[[Ember Matriarch]]<br />
|14<br />
|14<br />
|20<br />
|20<br />
|18<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Male<br />
* Multiple organs<br />
* Cock length is the primary factor<br />
(Siren is techincally not even male, but it does not matter for organ scaling)<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Cock Length<br />
!Ball Size<br />
!Cocks<br />
|----<br />
|[[King Cobra]]<br />
|16<br />
|12<br />
|2<br />
|----<br />
|[[Crimson Wyrm]]<br />
|12<br />
|6<br />
|2<br />
|----<br />
|[[Siren]]<br />
|18<br />
|19<br />
|2<br />
|----<br />
|[[Octopus Guy]]<br />
|18<br />
|10<br />
|3<br />
|----<br />
|[[Komodo Dragon]]<br />
|20<br />
|15<br />
|2<br />
|----<br />
|}<br />
<br />
Fhe following table has the following categories:<br />
* Herm<br />
* Multiple organs, single boobs<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Cunt Length<br />
!Cock Length<br />
!Ball Size<br />
!Cocks<br />
!Cunts<br />
|----<br />
|[[Giant Bat]]<br />
|2<br />
|8<br />
|9<br />
|3<br />
|2<br />
|1<br />
|----<br />
|[[Cuddlefish]]<br />
|3<br />
|18<br />
|18<br />
|0<br />
|2<br />
|2<br />
|----<br />
|[[Bull Shark]]<br />
|5<br />
|11<br />
|11<br />
|8<br />
|2<br />
|1<br />
|----<br />
|[[Anglerfish]]<br />
|6<br />
|12<br />
|10<br />
|20<br />
|3<br />
|1<br />
|----<br />
|[[Quicksilver Serpent]]<br />
|24<br />
|48<br />
|48<br />
|32<br />
|2<br />
|1<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Herm<br />
* Multiple organs, multiboobs<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Breasts<br />
!Cunts<br />
!Cunt Length<br />
!Cocks<br />
!Cock Length<br />
!Ball Size<br />
|----<br />
|[[Parasitic Plant]]<br />
|6<br />
|4<br />
|3<br />
|20<br />
|4<br />
|12<br />
|5<br />
|----<br />
|[[Manticore]]<br />
|6<br />
|6<br />
|1<br />
|7<br />
|2<br />
|7<br />
|16<br />
|----<br />
|[[Margay Taur]]<br />
|6<br />
|12<br />
|2<br />
|15<br />
|2<br />
|8<br />
|6<br />
|----<br />
|[[Parade Dragon]]<br />
|7<br />
|42<br />
|7<br />
|6<br />
|14<br />
|6<br />
|4<br />
|----<br />
|[[Rept-Taur]]<br />
|8<br />
|6<br />
|2<br />
|20<br />
|2<br />
|20<br />
|0<br />
|----<br />
|[[Mutant Hyena]]<br />
|12<br />
|4<br />
|1<br />
|10<br />
|2<br />
|10<br />
|32<br />
|----<br />
|[[Green Hydra]]<br />
|15<br />
|4<br />
|1<br />
|15<br />
|3<br />
|15<br />
|4<br />
|----<br />
|}<br />
<br />
<br />
[[Category:Guides]] [[Category:Theme]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Organ_sizes&diff=1573689Organ sizes2021-11-12T05:21:17Z<p>Glitch: </p>
<hr />
<div>The values between asterisks are what to target when using a Nanite Carnal Equalizer to adjust a specific body part. Examples: 'shift breasts=margay' or 'shift cock length=lion beast'.<br />
<br />
The 'Missing' column lists any mutation locations that don't exist for that creature, reducing the number of mutations <br />
required to acquire the Total badge, and carrying forward any previous mutations when Shifted to by a Nanite Adept. For <br />
instance, If a NA shifts to Cat Girl, then to Zombie, she will still have the cat tail in her description. &gt;&lt;&gt; <br />
and Rubber Balls each only have a single mutation location, thus they are listed as missing "all but..."<br />
<br />
NEUT means that the mutation does not carry any inherent sexual characteristics. This means that you will maintain the <br />
organs and sizes you had previously, allowing for Cat Bois, Otter girls, and so on. Currently, this also means that any <br />
child with this mutation on their groin will be born Neuter.<br />
<br />
A note on body size/mass: the numbers are, like the rest of the organ sizes, not in any absolute terms. "5" is human average. Sizes smaller than 5 are smaller than average. Sizes above 5 are larger than average. If the form is more or less humanoid, this translates to taller or shorter, but some forms are dense or differently arranged, such as a tauric form. Currently, the largest size a player can get normally is hardcapped at 20 ('''roughly''' two to three times human average in height, about three to four times human average in mass), while the Kaiju and Quetzalcoatl supernatural dedications allow a larger size bounded by two softcaps. The largest possible height commonly obtainable is 95 for a Tall Giant Kaiju with a Tormunga torso, Giant Size toggle on, and the Overblown and Large Tendencies perks. Any time you look at a player, the first few words of the autodesc will tell you if they are shorter or taller than you are, and roughly by how much.<br />
<br />
{{:Organ_Sizes_table}}<br />
{| border="1" align="center" class="wikitable"<br />
|}<br />
<br />
= Supplementary Tables =<br />
<br />
== Organ Descriptions ==<br />
<br />
The following table is a list of organ sizes, and how they get described in descriptions of players and monsters. Please take note that multiple breast pairs do not match this table as the individual breasts tend to be smaller than the set breast size, with exceptions made for those with a [[Mammary Magnifier]] and/or a [[Breast Consolidator]]<br />
<br><br />
<br><br />
'''Note that the descriptions of organs are meant to be relative to the body size. Hand filling breasts on a giant are hand filling. For a giant.'''<br />
<br><br />
<br><br />
<br />
=== Cock Length ===<br />
<br />
They have X (description) cock(s)/penis(es)/shaft(s)/maleness(es).<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
! Transformation (Growing)<br />
! Transformation (Shrinking)<br />
|-<br />
| 0-1<br />
| finger sized/minuscule<br />
| You yelp in surprise as a puny organ erupts from the flesh of your nethers- A minuscule penis, no bigger than your index finger.<br />
| You shudder as your manflesh shrinks, eventually becoming something no bigger than your index finger.<br />
|-<br />
| 2-3<br />
| small<br />
| Your groin feels a tad heavy as it fills out, leaving you with a maleness slightly longer than the width of your hand.<br />
| You shiver as your manhood retracts, leaving you with an organ only slightly longer than the width of your hand.<br />
|-<br />
| 4-5<br />
| average<br />
| Your manhood engorges as it begins filling out, leaving you with average organs an average organ, roughly two hand-widths in length.<br />
| Your maleness shrinks until it is about the length of two widths of your hand.<br />
|-<br />
| 6-7<br />
| above average<br />
| Your manhood engorges as it gains in length, eventually being more than two hands can hold.<br />
| Your maleness retracts until it is at a state where it would take a little more than two of your hands to hold.<br />
|-<br />
| 8-9<br />
| large<br />
| Your male organ engorges as it fills out, the organ thick, about half the length of your thigh.<br />
| Your male organ engorges, retracting as it shrinks to about half the length of your thigh.<br />
|-<br />
| 10-11<br />
| thick/heavy<br />
| Your manhood engorges as it seems to gain weight and girth, the organ just shy of your knees.<br />
| Your manhood retracts and eventually comes to rest a short distance above the knee.<br />
|-<br />
| 12-13<br />
| forearm length<br />
| Your manhood engorges, gaining in length until its dimensions become quite comparable to your forearm, fist and all. You can no longer fully wrap a hand around any of your rod.<br />
| Your manhood swells, retracting until its dimensions are similar to your forearm with a clenched fist.<br />
|-<br />
| 14-15<br />
| torso length<br />
| Your manhood engorges, surging in girth and length, and eventually it seems to be as long as your torso. On the plus side you can have a handy chin rest. The downside? You may poke your eye or throat if you sleep in the fetal position.<br />
| Your manhood pulses, shrinking until it is as long as your torso, its tip at your collarbone.<br />
|-<br />
| 16-17<br />
| shin bumping<br />
| Your manhood engorges until its dimensions leave it almost as long as your leg, the fleshy pillar roughly halfway between knee and ankle.<br />
| Your manhood swells, retracting until its length is somewhere between ankle and shin.<br />
|-<br />
| 18-19<br />
| leg length<br />
| Your manhood engorges until you seem to have another leg. It is a struggle to wrap both hands around the thick girth of your meat.<br />
| Your manhood swells as it shrinks down to a size roughly equal to your legs.<br />
|-<br />
| 20-21<br />
| unwieldly<br />
| Your manhood engorges, eventually reaching a point where you may risk tripping over these absurd dimensions.<br />
| Your manhood swells, shrinking down to a slightly more reasonable dimension. However, it seems to have the annoying tendency of being the perfect length to trip over and tangle with your legs.<br />
|-<br />
| 22-23<br />
| body length<br />
| Your manhood engorges until it is as long as you are tall, easily towering above your head. It is rather hard to keep your balance at this point.<br />
| Your manhood swells, and then begins to shrink until the massive rod is as long as you are tall.<br />
|-<br />
| 24+<br />
| body overshadowing/bigger than themself<br />
| Your manhood engorges past all sense of reason and logic, the abomination ridiculously thick, and easily far taller and heavier than you. You wonder how you will remain conscious if you ever get an erection... wait, scratch that. You wonder how you will survive.<br />
| <br />
|-<br />
|}<br />
<br />
=== Ball Size ===<br />
They have (description) balls.<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
! Transformation (Growing)<br />
! Transformation (Shrinking)<br />
|-<br />
| 1-2<br />
| tiny<br />
| You feel some internal shifting as the nanites alter your biology, leaving you with two tiny balls.<br />
| Scrotal flesh dwindles, balls shrinking until you are left with two orbs that could hardly be called balls.<br />
|-<br />
| 3-5<br />
| small<br />
| Scrotal flesh grows taut for a moment as your balls expand to form small, rounded balls.<br />
| Scrotal flesh dwindles as your balls shrink to small rounded balls.<br />
|-<br />
| 6-8<br />
| average<br />
| Scrotal flesh grows taut for a moment as your balls expand to two average sized balls.<br />
| Scrotal flesh dwindles as your balls shrink to two average sized balls.<br />
|-<br />
| 9-11<br />
| large<br />
| Scrotal flesh grows taut for a moment as your balls expand to roughly twice their previous size, your scrotum ending up quite the handful.<br />
| Scrotal flesh dwindles as your balls shrink to roughly half their previous size, your scrotum a literal handful.<br />
|-<br />
| 12-14<br />
| fist sized<br />
| Scrotal flesh grows taut for a moment as your balls expand until each is roughly the size of your clenched fist.<br />
| Scrotal flesh dwindles as your balls shrink until they are about as big as your clenched fist.<br />
|-<br />
| 15-17<br />
| hand filling<br />
| Scrotal flesh grows taut for a moment as your balls expand, surging as each becomes a literal handful- larger than a clenched fist. You cannot even wrap your paw/hand around one.<br />
| Scrotal flesh dwindles as your balls shrink, the spheres eventually a literal handful.<br />
|-<br />
| 18-19<br />
| head sized<br />
| Scrotal flesh grows taut for a moment as your balls expand and swell, your balls only seeming to halt when they are as big as your own head!<br />
| Scrotal flesh dwindles as your balls shrink, eventually coming to a stop at around the size of your head.<br />
|-<br />
| 20-25<br />
| lap filling<br />
| Scrotal flesh grows taut for a moment as your balls expand, each ball of flesh stretching far beyond its normal limits. When all is said and done, both take up a good deal of space between your thighs, becoming a literal lapful.<br />
| Scrotal flesh dwindles as your balls shrink, both eventually large enough to make a literal lapful as they dominate the space between your thighs.<br />
|-<br />
| 26-31<br />
| knee knocking<br />
| Scrotal flesh grows taut for a moment as your balls expand and surge, each nut becoming large enough to dominate a lap, and to make matters worse, they bump against your knees if you walk the wrong way.<br />
| Scrotal flesh dwindles as your balls shrink until they reach a point where either could dominate a lap. At least walking is easier, if still awkward- the damn things bump your knees if you don't stroll along properly.<br />
|-<br />
| 32-37<br />
| shin bumping/seat worthy<br />
| Scrotal flesh grows taut for a moment as your balls expand, each eventually reaching such huge proportions that they are about halfway down to your shins. On the plus side you have a handy seat. On the downside? You have one hell of a problem walking.<br />
| Scrotal flesh dwindles as your balls shrink. Sure, they no longer brush the ground, but you're more liable to trip than ever due to their ungainly size.<br />
|-<br />
| 38-42<br />
| ground brushing<br />
| Scrotal flesh grows taut for a moment as your balls expand, testes literally large enough to brush the ground. On the plus, walking is a little easier, but on the downside that scraping makes stealth a hassle.<br />
| Scrotal flesh dwindles as your balls shrink, testes becoming slightly more manageable, but stealth harder. Giant orbs dragging along the ground have their downsides.<br />
|-<br />
| 43-48<br />
| unwieldly sized<br />
| Scrotal flesh grows taut for a moment as your balls expand until each is large enough to comfortably fit in to the crook of your back. Still ungainly, but at least you will always have something to lean on.<br />
| Scrotal flesh dwindles as your balls shrink, becoming a little more manageable, but by no means easy. A convenient thing to lean on, as either could fit comfortably against your mid-back.<br />
|-<br />
| 49-54<br />
| body sized<br />
| Scrotal flesh grows taut for a moment as your balls expand, each nut as large as you are tall, and probably wider to boot.<br />
| Scrotal flesh dwindles as your balls shrink to something slightly less inconvenient, but strangely more comical. Trouble with doorways, halls, and seating abound!<br />
|-<br />
| 55+<br />
| unfathomably over sized<br />
| Scrotal flesh grows taut for a moment as your balls expand to simply ridiculous proportions. Far larger than you, these grand balls could probably get caught in a door or hallway that you would normally be able to pass easily in to.<br />
|-<br />
|}<br />
<br />
=== Breast Size ===<br />
<br />
It is important to note again, that for the description and the shifting message that your breast individually might not match up with the number. Please make sure to reference your character such that your description and shifting message match up, as these are more important than the actual stat number.<br />
<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Size<br />
! Description<br />
! Transforming (Growing)<br />
! Transforming (Shrinking)<br />
|-<br />
| 0<br />
| nipples<br />
|<br />
| You shudder as you become flatter than FlatsVille. Your chest could pass as a billboard save for the nipples. This could be good or bad depending on your views.<br />
|-<br />
| 1-3<br />
| flat<br />
| You shudder as your bust expands, leaving you slightly less flat than the billboard you were before, two slight mounds giving the impression of bust.<br />
| You shudder as you become flatter than FlatsVille. Your chest could pass as a billboard save for the nipples. This could be good or bad depending on your views.<br />
|-<br />
| 4-7<br />
| small/petite<br />
| You shudder as your breasts expand, leaving you with two perky mounds.<br />
| You shiver as your breasts retract, but you still seem to retain some semblance of a chest, your breasts pert mounds upon your chest.<br />
|-<br />
| 8-11<br />
| average<br />
| You shudder as your breasts expand to a rather average size.<br />
| You shiver as your breasts retract to a rather average looking size.<br />
|-<br />
| 12-15<br />
| large/hand filling<br />
| You shudder as your breasts expand, each bulge of flesh easily able to fill the palm of your hand. Literal handfuls indeed.<br />
| You shiver as your breasts shrink to a smaller size. Still, they are quite generous, each being a rather pleasant handful.<br />
|-<br />
| 16-19<br />
| hefty<br />
| You shudder as your breasts expand a bit beyond the scope of one hand, two now required to grasp the jiggly flesh. Your quite the handful now, and you seem to have a little heft to your chest now.<br />
| You shiver as your breasts shrink down to being two handfuls apiece. You still got quite a bit of jiggle, if slightly less of a handful than you were before.<br />
|-<br />
| 20-23<br />
| grand<br />
| You shudder as your breasts expand and are now quite large and plush, a few cup sizes short of something that could hold your head. Crossing your arms could support these puppies quite nicely.<br />
|You shiver as your breasts shrink down to a rather generous and impressive size, smaller than your head at least. If you crossed your arms, you could support them quite nicely.<br />
|-<br />
| 24-27<br />
| head sized<br />
| You shudder as your breasts expand to a point that each pliant mound is as large as your head. (If have Normal Physics) You are also greeted with a growing soreness in your back. (If you don't have Normal Physics) You are also greeted with a surprising lack of back pain.<br />
| You shiver as your breasts shrink down until they are about as large as your head.<br />
|-<br />
| 28-31<br />
| chest filling<br />
| You shudder as your breasts expand, each impressive easily covering each half of your chest, far larger than your head. The soft fleshy orbs jiggle and bounce quite a bit as you walk, occasionally bumping in to the side of your arms.<br />
| You shudder as your breasts shrink down to a more manageable size, though they are by no means small, each breast far larger than your head. (If you have Normal Physics) Your back does not hurt quite as much. (End if) Your balance improves a little.<br />
|-<br />
| 32-35<br />
| arm filling<br />
| You shudder as your bust expands further, your chest reaching such proportions as they begin to bottom out near the top of your stomach. You have barely enough room to clasp your fingers together if you were to reach around your mammaries. You notice some problems with balance, and you are carrying quite a bit of weight.<br />
| You gasp as your breasts shrink to a point where you can actually reach your fingers if you were to wrap your arms around your titflesh.<br />
|-<br />
| 36-39<br />
| waist bumping<br />
| You shudder as your breasts expand to such immense proportions that the fleshy spheres bump and brush against your waist as you walk. You are really beginning to have balance problems.<br />
| You shiver as your breasts shrink down to around your waist, greatly alleviating balancing issues. Still, they bounce and jiggle against your waist, so that is not saying much.<br />
|-<br />
| 40-43<br />
| knee bouncing<br />
| You shudder as your breasts expand to even greater proportions, the rounded mammaries knocking against your knees as you walk, greatly contributing to bounce and jiggle.<br />
| You sigh as your breasts shrink to a far more reasonable proportion, greatly solving many problems that you were plagued with. Still, your knees bounce those breasts as you walk, and it can be a rather odd sensation.<br />
|-<br />
| 44-47<br />
| body-sized<br />
| You shudder as your breasts expand expand further, billowing out until they are as large as you are. Unsupported they would drag upon the ground, (if you have Normal Physics) but at least the growing back pain is gone, (end if) and if supported, your balance is significantly compromised. How can you even manage to move? That is a mystery only you can answer, considering others will have to deal with all the extra space you take up.<br />
| You shiver as your breasts shrink to far less insane proportions. Still, it is quite maddening, taking up all that space- breasts as large as you are. Balance issues are still abound, but at least you are mobile.<br />
|-<br />
| 48+<br />
| impossibly huge<br />
| You shudder as your breasts expand expand to completely unreasonable proportions. Good luck moving, as these puppies are now larger than you are. It is doubtful you may be able to walk forwards, so you may have to deal with going backwards, if you can even move.<br />
|<br />
|-<br />
|}<br />
<br />
=== Cunt Length ===<br />
They have X (description) vagina(s)/cunt(s)/puss(y/ies)/cleft(s).<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
! Transformation (Growing)<br />
! Transformation (Shrinking)<br />
|-<br />
| 1-2<br />
| minuscule<br />
| You tremble as the nanites rework your anatomy, eventually leaving you with a small mound of flesh between your legs- a small vagina. It is little more than a small hole capable of housing a finger.<br />
| You shudder, in each pussy feeling wet as it shrinks down to minuscule proportions- almost nothing more than a mound of flesh and accompanying hole to go with it. Barely enough room for a finger.<br />
|-<br />
| 3-4<br />
| small<br />
| Your pussy feels wet as it seems to grow deeper, mound growing more prominent. It is not too terribly deep.<br />
| Your pussy feels wet as it shrinks, growing tighter and tighter. It can now only house a few fingers comfortably.<br />
|-<br />
| 5-6<br />
| standard<br />
| Your pussy feels wet as it becomes more prominent, finally resembling something normal. It seems to be fairly standard in size, nothing overly large or small.<br />
| Your pussy feels wet as it shrinks, eventually becoming something more average in size.<br />
|-<br />
| 7-8<br />
| moderately large<br />
| Your pussy feels wet as a shudder runs through your form. Nothing really seems to change outwardly, but a private check reveals your sex to be more able to stretch, and a bit deeper.<br />
| Your pussy feels wet as it seems to tighten, though still above the average depth, retaining a bit of stretch, your hips narrowing a little as well.<br />
|-<br />
| 9-10<br />
| large<br />
| Your pussy feels wet and you squirm uncomfortably, nanites making a few more changes, deepening your sex your hips growing a little wider, as if to allow larger things inside you more comfortably.<br />
| Your pussy feels wet as it shrinks, nanites making changes until it is tighter, your feminine lips becoming a little less pronounced in the process.<br />
|-<br />
| 11-12<br />
| wide<br />
| Your cleft feels wet as it thickens a little, cleft becoming a little more pronounced and defined, the familiar tingle of deepening accompanying such a transformation.<br />
| Your pussy feels wet as it tightens, internals shifting as it reworks itself. You cannot easily take something the size of your forearm anymore.<br />
|-<br />
| 13-15<br />
| thick-lipped<br />
| Your pussy feels wet as it seems to deepen further. There is almost no outward change, but you could comfortably fit something the size of your forearm in there if you had the dexterity to do so.<br />
| Your pussy feels wet as it tightens, shrinking in size, your hips narrowing as well. You're still quite deep, you just cannot cram as much in, only really able to manage something the size of your arm down to your elbow.<br />
|-<br />
| 16-17<br />
| elbow-deep<br />
| Your pussy feels wet as your hips seem to widen a more, greatly enhancing your figure along with giving some much needed room to fit some larger things in. You could easily squeeze a good two thirds of your arm in there.<br />
| Your pussy feels wet as that literal hollow feeling fades, sex tightening as some previous elasticity vanishes.<br />
|-<br />
| 18-19<br />
| arm deep<br />
| Your pussy feels wet as it deepens even more. You begin to wonder a few things, and seem to feel a little hollow in the literal sense. You could easily fit something as long and thick as your entire arm in there.<br />
| Your pussy feels wet as an odd feeling overtakes you. You can take something the size of your arm with ease, but you are not quite as stretchy as you once were.<br />
|-<br />
| 20-21<br />
| cavernous<br />
| Your pussy feels wet as it becomes little more elastic. You cannot help but feel slightly odd as things shift around. You could swear that your sex take takes up a good deal of your body at this point.<br />
| Your pussy feels wet as much of your elasticity fades. You still got something as deep as your torso, but your hips are not as insane as they were, and your bones and internals are now much more normal than they were.<br />
|-<br />
| 22-23<br />
| body length<br />
| Your pussy feels wet as your internals shift drastically. You feel odd- although you cannot pinpoint why. The outward appearance of your vagina seems fine- much the same as it was before, except that it seems to stretch through your entire torso.<br />
|<br />
|-<br />
| 24+<br />
| impossibly elastic<br />
| Your feel pussy feels wet with a familiar sensation as your female parts shift yet again. It is hard to say exactly what happened, aside from some rather impressive hips and an altered bone structure, but you are highly elastic at this point- A torso has its limits, but you might just be able to cram a portion of things larger than that within you.<br />
|<br />
|-<br />
|}<br />
<br />
=== Clit Length ===<br />
<br />
They have X (description) clits(s)/buzzers(es)/buttons(s).<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
|-<br />
| 0-1<br />
| non-existent/always hidden <br />
|-<br />
| 2-3<br />
| nubby/insignificant<br />
|-<br />
| 4-5<br />
| average<br />
|-<br />
| 6-7<br />
| large/plump<br />
|-<br />
| 8-9<br />
| finger length/prominent<br />
|-<br />
| 10-11<br />
| grippable/exposed<br />
|-<br />
| 12-13<br />
| hand length/cock-like<br />
|-<br />
| 14-15<br />
| lengthy <br />
|-<br />
| 16-17<br />
| belly slapping<br />
|-<br />
| 18-19<br />
| awkwardly oversized<br />
|-<br />
| 20-21<br />
| thigh slapping <br />
|-<br />
| 22-23<br />
| forearm sized/thigh length<br />
|-<br />
| 24+<br />
| unspeakably huge<br />
|-<br />
|}<br />
<br />
=== Udder Size ===<br />
<br />
Udder size is tied directly to your breast size, but has a different description. If you want to change your udder size, assuming you have one, you need to change your breast sizes.<br />
<br />
They have an udder, it seems (description) and has (number of breasts) teats.<br />
{| border="1" align="center" class="wikitable"<br />
|-<br />
! Value <br />
! Description<br />
|-<br />
| 0-1<br />
| flat<br />
|-<br />
| 2-4<br />
| small<br />
|-<br />
| 5-7<br />
| average<br />
|-<br />
| 8-10<br />
| large<br />
|-<br />
| 11-13<br />
| bloated<br />
|-<br />
| 14-18<br />
| lap filling<br />
|-<br />
| 19-21<br />
| amazingly huge<br />
|-<br />
| 22-26<br />
| impossibly huge<br />
|-<br />
<br />
|}<br />
<br />
== Size shifting guides ==<br />
<br />
The following tables are the main table's information, a little reworked and sorted into certain categories of <br />
interest.<br><br />
This is mostly done to supply [[Nanite Adepts]] with the [[Nanite Carnal Equalizer]] or [[Nanite Fine Tuner]], or people who like to <br />
use [[Nanite Hypo]]s and [[Sexual Fixative]]s to change their organ sizes. ''This is also good for monster creators who want to <br />
see what has and hasn't been done when it comes to scale tendencies''<br />
<br />
<br><br />
<br><br />
The following table has the following categories:<br />
* Female<br />
* Single organs<br />
* Boob size is the primary factor<br />
* Cunt lengths were selected to start at 8, with a medium and large value supplemented with each available boob size, where <br />
possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Cunt Length<br />
|----<br />
|[[Banshee]]<br />
|1<br />
|8<br />
|----<br />
|[[Squid Girl]]<br />
|1<br />
|8<br />
|----<br />
|[[Lollipop Lady]]<br />
|2<br />
|9<br />
|----<br />
|[[Eagle Girl]]<br />
|2<br />
|16<br />
|----<br />
|[[Valkyrie]]<br />
|3<br />
|8<br />
|----<br />
|[[Female Commando]]<br />
|3<br />
|9<br />
|----<br />
|[[Leech]]<br />
|3<br />
|15<br />
|----<br />
|[[Latex Snow Leopard]]<br />
|4<br />
|8<br />
|----<br />
|[[Female Widow Convert]]<br />
|4<br />
|10<br />
|----<br />
|[[Farm Hen]]<br />
|4<br />
|14<br />
|----<br />
|[[Slurry Girl]]<br />
|4<br />
|28<br />
|----<br />
|[[Hair-bound Woman]]<br />
|5<br />
|8<br />
|----<br />
|[[Knockout Mouse]]<br />
|5<br />
|16<br />
|----<br />
|[[Snow Leopardtaur|Female Snow Leopardtaur]]<br />
|5<br />
|18<br />
|----<br />
|[[Peregrine Girl]]<br />
|6<br />
|7<br />
|----<br />
|[[Fire Elemental]]<br />
|6<br />
|16<br />
|----<br />
|[[Evil Nurse]]<br />
|7<br />
|9<br />
|----<br />
|[[Cherry Cordial]]<br />
|7<br />
|10<br />
|----<br />
|[[Liquid Panthress]]<br />
|7<br />
|24<br />
|----<br />
|[[F15 Girl]]<br />
|8<br />
|8<br />
|----<br />
|[[Busty Succubus]]<br />
|8<br />
|20<br />
|----<br />
|[[Anime Babe]]<br />
|9<br />
|8<br />
|----<br />
|[[Icy Phoenix]]<br />
|9<br />
|10<br />
|----<br />
|[[Busty Cow]]<br />
|10<br />
|8<br />
|----<br />
|[[Cowgirl]]<br />
|10<br />
|15<br />
|----<br />
|[[VTOL Lady]]<br />
|10<br />
|20<br />
|----<br />
|[[Dark Elf Female]]<br />
|14<br />
|18<br />
|----<br />
|[[Wolf Spider]]<br />
|8<br />
|10<br />
|----<br />
|----<br />
|[[Arachne]]<br />
|10<br />
|80<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Female<br />
* Single organs<br />
* Cunt length is the primary factor<br />
* Small, medium and large Boob sizes were included with each cunt length, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Cunt Length<br />
!Cup Sizes<br />
|----<br />
|[[Chocolate Bunny]]<br />
|4<br />
|2<br />
|----<br />
|[[Honey Bee]]<br />
|6<br />
|2<br />
|----<br />
|[[Bearded Dragon Recruit]]<br />
|6<br />
|4<br />
|----<br />
|[[Giant]]<br />
|6<br />
|6<br />
|----<br />
|[[Peregrine Girl]]<br />
|7<br />
|6<br />
|----<br />
|[[Banshee]]<br />
|8<br />
|1<br />
|----<br />
|[[Latex Snow Leopard]]<br />
|8<br />
|4<br />
|----<br />
|[[Anime Babe]]<br />
|8<br />
|9<br />
|----<br />
|[[Busty Cow]]<br />
|8<br />
|10<br />
|----<br />
|[[Lollipop Lady]]<br />
|9<br />
|2<br />
|----<br />
|[[Female Commando]]<br />
|9<br />
|3<br />
|----<br />
|[[Evil Nurse]]<br />
|9<br />
|7<br />
|----<br />
|[[Bunny Girl]]<br />
|10<br />
|3<br />
|----<br />
|[[Leather Mistress]]<br />
|10<br />
|4<br />
|----<br />
|[[Cherry Cordial]]<br />
|10<br />
|7<br />
|----<br />
|[[Icy Phoenix]]<br />
|10<br />
|9<br />
|----<br />
|[[Palmetto Roach]]<br />
|11<br />
|0<br />
|----<br />
|[[Skunk Girl]]<br />
|12<br />
|3<br />
|----<br />
|[[Corota]]<br />
|12<br />
|4<br />
|----<br />
|[[Sexy Dragoness]]<br />
|12<br />
|8<br />
|----<br />
|[[Furie]]<br />
|13<br />
|5<br />
|----<br />
|[[Farm Hen]]<br />
|14<br />
|4<br />
|----<br />
|[[Leech]]<br />
|15<br />
|3<br />
|----<br />
|[[Cowgirl]]<br />
|15<br />
|10<br />
|----<br />
|[[Eagle Girl]]<br />
|16<br />
|2<br />
|----<br />
|[[Knockout Mouse]]<br />
|16<br />
|5<br />
|----<br />
|[[Lizard Girl]]<br />
|17<br />
|3<br />
|----<br />
|[[Snow Leopardtaur|Female Snow Leopardtaur]]<br />
|18<br />
|5<br />
|----<br />
|[[Dark Elf Female]]<br />
|18<br />
|14<br />
|----<br />
|[[Shadow Dragon]]<br />
|19<br />
|4<br />
|----<br />
|[[Goo Girl]]<br />
|20<br />
|3<br />
|----<br />
|[[Busty Succubus]]<br />
|20<br />
|8<br />
|----<br />
|[[VTOL Lady]]<br />
|20<br />
|10<br />
|----<br />
|[[Female Lamia]]<br />
|24<br />
|3<br />
|----<br />
|[[Liquid Panthress]]<br />
|24<br />
|7<br />
|----<br />
|[[Slurry Girl]]<br />
|28<br />
|4<br />
|----<br />
|[[Centaur Mare]]<br />
|30<br />
|3<br />
|----<br />
|[[Wolf Spider]]<br />
|10<br />
|8<br />
|----<br />
|----<br />
|[[Arachne]]<br />
|80<br />
|10<br />
|----<br />
|}<br />
<br />
<br />
The following table has the following categories:<br />
* Male<br />
* Single organs<br />
* Cock length is the primary factor<br />
* Small, and large ball sizes, as well as nipple and nippleless were included with each cock length, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Cock Length<br />
!Ball Size<br />
!Nipples?<br />
|----<br />
|[[Mountain Man]]<br />
|5<br />
|4<br />
|*<br />
|----<br />
|[[Male Alley Cat]]<br />
|6<br />
|1<br />
|<br />
|----<br />
|[[Anole]]<br />
|6<br />
|2<br />
|<br />
|----<br />
|[[Fey Folke]]<br />
|6<br />
|4<br />
|<br />
|----<br />
||[[Water Moccasin|Male Water Moccasin]]<br />
|6<br />
|4<br />
|<br />
|----<br />
||[[Villainous Gnome]]<br />
|6<br />
|6<br />
|<br />
|----<br />
|[[Horseshoe Crab]]<br />
|6<br />
|13<br />
|<br />
|----<br />
|[[Raptorian]]<br />
|7<br />
|4<br />
|<br />
|----<br />
|[[Aassahke Male]]<br />
|8<br />
|3<br />
|<br />
|----<br />
|[[Fox Boy]]<br />
|8<br />
|3<br />
|<br />
|----<br />
|[[Ebony Raven]]<br />
|8<br />
|4<br />
|<br />
|----<br />
|[[Pangolin]]<br />
|8<br />
|4<br />
|<br />
|----<br />
|[[German Shepherd]]<br />
|8<br />
|4<br />
|*<br />
|----<br />
|[[Quilled Tousky]]<br />
|8<br />
|5<br />
|<br />
|----<br />
|[[Latex Fox]]<br />
|8<br />
|6<br />
|<br />
|----<br />
|[[Treant]]<br />
|8<br />
|8<br />
|<br />
|----<br />
|[[Circus Clown]]<br />
|8<br />
|10<br />
|<br />
|----<br />
|[[Orthom Brute]]<br />
|8<br />
|12<br />
|<br />
|----<br />
|[[Orc]]<br />
|9<br />
|5<br />
|<br />
|----<br />
|[[Gladiator]]<br />
|10<br />
|4<br />
|<br />
|----<br />
|[[Half-Lizard]]<br />
|10<br />
|4<br />
|<br />
|----<br />
|[[Stegosaurian]]<br />
|10<br />
|7<br />
|<br />
|----<br />
|[[Honey Bear]]<br />
|10<br />
|10<br />
|<br />
|----<br />
|[[Nephilim]]<br />
|10<br />
|16<br />
|*<br />
|----<br />
|[[Skunk Beast]]<br />
|11<br />
|7<br />
|<br />
|----<br />
|[[Wolf Boy]]<br />
|12<br />
|4<br />
|<br />
|----<br />
|[[Porcupine]]<br />
|12<br />
|6<br />
|<br />
|----<br />
|[[Wolf Beast]]<br />
|12<br />
|6<br />
|<br />
|----<br />
|[[Gargoyle Sentinel]]<br />
|12<br />
|12<br />
|<br />
|----<br />
|[[White Siberian Tiger]]<br />
|12<br />
|16<br />
|<br />
|----<br />
|[[Male Rex]]<br />
|13<br />
|6<br />
|<br />
|----<br />
|[[Clockwork Fox Guy]]<br />
|13<br />
|6<br />
|<br />
|----<br />
|[[Troll]]<br />
|14<br />
|7<br />
|<br />
|----<br />
|[[Killer Whale]]<br />
|14<br />
|10<br />
|<br />
|----<br />
|[[Fox Taur]]<br />
|14<br />
|16<br />
|<br />
|----<br />
|[[Dandy Peacock]]<br />
|15<br />
|15<br />
|<br />
|----<br />
|[[Lion Beast]]<br />
|16<br />
|6<br />
|<br />
|----<br />
|[[Clydesdale Stud]]<br />
|16<br />
|10<br />
|<br />
|----<br />
|[[Anthro Dolphin]]<br />
|16<br />
|15<br />
|<br />
|----<br />
|[[Arctic Fox]]<br />
|16<br />
|20<br />
|<br />
|----<br />
|[[Muscle Hulk]]<br />
|16<br />
|26<br />
|<br />
|----<br />
|[[Dark Elf Male]]<br />
|18<br />
|10<br />
|<br />
|----<br />
|[[Tarragon]]<br />
|18<br />
|13<br />
|<br />
|----<br />
|[[Clownfish]]<br />
|18<br />
|19<br />
|<br />
|----<br />
|[[Donkey Boy]]<br />
|18<br />
|30<br />
|*<br />
|----<br />
|[[Horned Wyvern]]<br />
|20<br />
|9<br />
|<br />
|----<br />
|[[Friesian Stallion]]<br />
|20<br />
|14<br />
|<br />
|----<br />
|[[Ogre]]<br />
|24<br />
|24<br />
|<br />
|----<br />
|[[Centaur Stallion]]<br />
|28<br />
|20<br />
|<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Herm<br />
* Single organs<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Cunt Length<br />
!Cock Length<br />
!Ball Size<br />
|----<br />
|[[Magma Wurm]]<br />
|0<br />
|10<br />
|12<br />
|0<br />
|----<br />
|[[Palmetto Roach]]<br />
|0<br />
|11<br />
|12<br />
|0<br />
|----<br />
|[[Priapan Orca]]<br />
|0<br />
|12<br />
|12<br />
|6<br />
|----<br />
|[[Water Hydra]]<br />
|0<br />
|14<br />
|14<br />
|8<br />
|----<br />
|[[Ancient Tortoise]]<br />
|2<br />
|5<br />
|4<br />
|0<br />
|----<br />
|[[Kobold Herm]]<br />
|2<br />
|6<br />
|5<br />
|1<br />
|----<br />
|[[Math Teacher]]<br />
|4<br />
|2<br />
|8<br />
|0<br />
|----<br />
|[[Jorogumo]]<br />
|4<br />
|12<br />
|12<br />
|0<br />
|----<br />
||[[Deer Herm]]<br />
|4<br />
|12<br />
|12<br />
|12<br />
|----<br />
|[[Vampire Herm]]<br />
|4<br />
|18<br />
|14<br />
|0<br />
|----<br />
|[[Water Dragon]]<br />
|5<br />
|6<br />
|6<br />
|5<br />
|----<br />
|[[Genetically Superior Human]]<br />
|5<br />
|15<br />
|16<br />
|5<br />
|----<br />
|[[Kangaroo]]<br />
|5<br />
|36<br />
|36<br />
|14<br />
|----<br />
|[[Ember Breeder]]<br />
|6<br />
|6<br />
|6<br />
|2<br />
|----<br />
|[[Striped Snake Beast]]<br />
|6<br />
|13<br />
|13<br />
|6<br />
|----<br />
|[[M1A1H]]<br />
|6<br />
|16<br />
|16<br />
|0<br />
|----<br />
|[[Amazonian]]<br />
|6<br />
|16<br />
|16<br />
|6<br />
|----<br />
|[[Blue Gryphon]]<br />
|8<br />
|13<br />
|13<br />
|7<br />
|----<br />
|[[Blue Sphinx]]<br />
|8<br />
|18<br />
|18<br />
|19<br />
|----<br />
|[[Hugely Hung Happy Hyper Herm Horse]]<br />
|20<br />
|60<br />
|60<br />
|20<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Female<br />
* Single organs, as many boobs as possible<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Breasts<br />
!Cunt Length<br />
|----<br />
|[[Feral Wolfess]]<br />
|3<br />
|8<br />
|9<br />
|----<br />
|[[Shadow Vixen]]<br />
|3<br />
|6<br />
|8<br />
|----<br />
|[[Fox Girl]]<br />
|4<br />
|6<br />
|12<br />
|----<br />
|[[Female Alley Cat]]<br />
|4<br />
|6<br />
|6<br />
|----<br />
|[[Female Husky]]<br />
|6<br />
|4<br />
|10<br />
|----<br />
|[[MSPA Series 6]]<br />
||8<br />
|8<br />
|8<br />
|----<br />
|[[Pink Panda]]<br />
|9<br />
|8<br />
|10<br />
|----<br />
|[[Chocolate Cow]]<br />
|12<br />
|4<br />
|28<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Herm<br />
* Single organs, as many boobs as possible<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Breasts<br />
!Cunt Length<br />
!Cock Length<br />
!Ball Size<br />
|----<br />
||[[Hyena|Hyena Herm]]<br />
|2<br />
|6<br />
|8<br />
|14<br />
|6<br />
|----<br />
||[[Wolfen Predator]]<br />
|3<br />
|6<br />
|24<br />
|18<br />
|13<br />
|----<br />
|[[Cerberus Herm]]<br />
|5<br />
|12<br />
|18<br />
|18<br />
|0<br />
|----<br />
|[[Painted Wolf Herm]]<br />
|7<br />
|4<br />
|10<br />
|10<br />
|10<br />
|----<br />
|[[Panther Taur]]<br />
|8<br />
|6<br />
|14<br />
|14<br />
|15<br />
|----<br />
|[[Collie Herm]]<br />
|10<br />
|6<br />
|13<br />
|12<br />
|4<br />
|----<br />
|[[Ember Render]]<br />
|12<br />
|4<br />
|18<br />
|12<br />
|18<br />
|----<br />
|[[Ember Matriarch]]<br />
|14<br />
|14<br />
|20<br />
|20<br />
|18<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Male<br />
* Multiple organs<br />
* Cock length is the primary factor<br />
(Siren is techincally not even male, but it does not matter for organ scaling)<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Cock Length<br />
!Ball Size<br />
!Cocks<br />
|----<br />
|[[King Cobra]]<br />
|16<br />
|12<br />
|2<br />
|----<br />
|[[Crimson Wyrm]]<br />
|12<br />
|6<br />
|2<br />
|----<br />
|[[Siren]]<br />
|18<br />
|19<br />
|2<br />
|----<br />
|[[Octopus Guy]]<br />
|18<br />
|10<br />
|3<br />
|----<br />
|[[Komodo Dragon]]<br />
|20<br />
|15<br />
|2<br />
|----<br />
|}<br />
<br />
Fhe following table has the following categories:<br />
* Herm<br />
* Multiple organs, single boobs<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Cunt Length<br />
!Cock Length<br />
!Ball Size<br />
!Cocks<br />
!Cunts<br />
|----<br />
|[[Giant Bat]]<br />
|2<br />
|8<br />
|9<br />
|3<br />
|2<br />
|1<br />
|----<br />
|[[Cuddlefish]]<br />
|3<br />
|18<br />
|18<br />
|0<br />
|2<br />
|2<br />
|----<br />
|[[Bull Shark]]<br />
|5<br />
|11<br />
|11<br />
|8<br />
|2<br />
|1<br />
|----<br />
|[[Anglerfish]]<br />
|6<br />
|12<br />
|10<br />
|20<br />
|3<br />
|1<br />
|----<br />
|[[Quicksilver Serpent]]<br />
|24<br />
|48<br />
|48<br />
|32<br />
|2<br />
|1<br />
|----<br />
|}<br />
<br />
The following table has the following categories:<br />
* Herm<br />
* Multiple organs, multiboobs<br />
* Bust Size is the primary factor<br />
* Small and large organ sizes were included with each boob scale, where possible.<br />
<br />
{| class="wikitable sortable" border="1"<br />
!Species<br />
!Breast Size<br />
!Breasts<br />
!Cunts<br />
!Cunt Length<br />
!Cocks<br />
!Cock Length<br />
!Ball Size<br />
|----<br />
|[[Parasitic Plant]]<br />
|6<br />
|4<br />
|3<br />
|20<br />
|4<br />
|12<br />
|5<br />
|----<br />
|[[Manticore]]<br />
|6<br />
|6<br />
|1<br />
|7<br />
|2<br />
|7<br />
|16<br />
|----<br />
|[[Margay Taur]]<br />
|6<br />
|12<br />
|2<br />
|15<br />
|2<br />
|8<br />
|6<br />
|----<br />
|[[Parade Dragon]]<br />
|7<br />
|42<br />
|7<br />
|6<br />
|14<br />
|6<br />
|4<br />
|----<br />
|[[Rept-Taur]]<br />
|8<br />
|6<br />
|2<br />
|20<br />
|2<br />
|20<br />
|0<br />
|----<br />
|[[Mutant Hyena]]<br />
|12<br />
|4<br />
|1<br />
|10<br />
|2<br />
|10<br />
|32<br />
|----<br />
|[[Green Hydra]]<br />
|15<br />
|4<br />
|1<br />
|15<br />
|3<br />
|15<br />
|4<br />
|----<br />
|}<br />
<br />
<br />
[[Category:Guides]] [[Category:Theme]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Portals_and_Portents_-_RPLOG&diff=628110Portals and Portents - RPLOG2017-09-30T23:28:46Z<p>Glitch: /* Log */</p>
<hr />
<div>=Participants=<br />
* [[Escherr]]<br />
* [[Mokou]]<br />
* [[Phosphorus]]<br />
* [[Maya]]<br />
* [[Emacs]]<br />
* [[Edel]]<br />
* [[Tova]]<br />
=Date=<br />
30/09/2017<br />
=Log=<br />
<div></div><br> <br>Though the high priestess of the Dusk Dragon's strongest duties lay with her, Tova still had ties to several of entities in good standing. The dreams had come to her, like others who had ties to Inari, and she heeded its call. Coming to the shrine during the midday hour, the dragon woman projected an air of calm serenity about her, surveying the shrine proper while striding along.<br />
<br> <br>It was never hard to hear a whisper of something going on, strange dreams for a few lucky or unlucky few have greeted his ears. It was a hobby of Escherr's to know what was going on around the city. So with that in mind he made his way to the shrines, after all having a diety owe you one couldn't hurt buisness either.<br />
<br> <br>There was but one supernatural being Edel followed, and she followed them enough to name her own business after it! And enough to count herself a shrine priest. If she was going to be here anyway, today, sweeping up the stone and tending the shrine, she might as well look into the strange happenings. Smoothing down her ornate silk robes, she sets aside the broom once others seem to be arriving, and wanders over into the neighboring shrine to take her own place among the inquisitive.<br />
<br> <br>Not too much major happens without the rumor mill starting up, and given the not insignificant number of Kitsune/Tanuki/Nekomata dedicants that are about, the mill was certainly in high gear. Phosphorus figured that the potential of supernatural intrigue would outweigh the potential danger of checking the scene out, so the panda decided to stalk her way into the shrine in her typical fashion, showing up at the gathering group with nary a word or whisper.<br />
<br> <br>To answer the call of Inari was foremost on Emacs's mind as shi entered the shrine. Shi was no priestess, nor avid zealot, but shi knew the scope of hir duties to him. Shi enters the shrine with a measured, careful gait, deferring to other that shi passes. Shi was uncertain and anxious, but as shi continued,a sense of calm fell onto hir as shi got further, a measure of a smile could be seen emerging upon hir face. <br />
<br> <br>The messengers of Inari had invited hir along, so she resolved that shi was surely good enough to be here. Hir robes were plain and simple, undyed fabric worn over the armor shi was accustomed to when fighting. Shi hoped it would not come to that today though.<br />
<br> <br>Where supernaturals were concerned, Mokou held a disturbingly simple outlook upon them. They exist. Beyond that, their nature was obscured in mystery as much as the nanites themselves. So when it came to her ears that there was something stirring, those drawn from what had been Shinto belief, from those of Eastern lore were about, it was not with panic or fear that Mokou reacted. It was a saddened sigh and a slight change in the day's plans. After all... a shrine that had not been there in years gone by... Was not what she expected. So her work in hand, her day hardly at the cusp, she set out. Perhaps something would come of it.. perhaps she would simply take use of the garden she's heard of. Twas yet to be told...<br />
<br> <br>As those hearkening to the beckons, whether directly or indirectly, collected toagher at the shrine, the grounds were filled with an assortment of civil mutants. Dedicants and mystery-seekers gatehred at the spot of worship and dedication until a hush falls over the crowd...<br />
<br> <br>The sky's light distorts, becoming a rosy hue even in the midst of the day, and a pair of lights form before the shrine, lofted to tower over the shrine's exterior. One light is fire and gold, the foxfire dancing into the vague visage of a many-tailed fox whereas the other is burnt oranges and gay browns, banding before displaying thee semblance of a raccoon dog bearing a swell, full sac. Though abstracted form the light, the figures are unmistakeable for their shapes. Voices mingle together, androgynous in that they're masculine and feminine at once, the sound fading in like an echo but stronger in volume.<br />
<br> <br>"Daughters, Sons, Allies, and Friends... We have come to you with matters of concern," The voiec emitting seeming a hint more feminine and coming from the foxish vision overhead. The other vision, a hint more masculine in tone, but still about as androgynous, emits, "Affairs have taken place from afar, and our brethren have fallen mute. We are unable to clearly hear what has transpired, and, without the aid of you, our dedicated, we will not be able to investigate nor provide aid where needed."<br />
<br> <br>Pausing to let the impact of what they've conveyed sink in for a moment, the visions of light projected overhead look over those present somberly.<br />
<br> <br>Turning her face up towards the images projected, Tova listens intently, and her brow knits. Piecing together the visions from the dreams with what news she'd heard, some assumptions niggled at her mind, but she sorted them aside, waiting to hear what facts could be established before making any true deductions through the crystalline facets of her mind.<br />
<br> <br>Having been one of the first to arrive the rodent settled into a position of sitting on the mossy cobblestone and overlooking each to arrive. If he had to hazard to guess a few probably heeded the call with some link to the proper deities of these scattered shrines. Not to say it wasn’t tempting to dedicate oneself to these strange, supernatural like beings, but being tied to one never felt like the intelligent idea and keep to a monotheistic nature. Each being had some sway or control over what lay within the bubble, and for now these three had something important or event changing to summon those to help. If the city was to be viewed as a working organism these deities were the organs.As the lights started to show and voices rang out together the rat turned to look to the source, hearing what was said it seemed his idea of something being off in the city was not a bad assumption. Looking over the group again and even including himself it may have him wondering just how much desperation was in the air if the simple masses were to be involved, this though was something he lived for and dedicated to in knowing the world and even the supernatural aspects. Not being directly connected Escherr felt he should wait to say anything, least until those that chose to worship such things spoke first having a strong connection.<br />
<br> <br>Edel places her arms together, sleeves linked as she listens to the words from beyond. She had heard mention of the things that happened over-seas. She could only assume that is what was being spoken of. "What would you have us do?" She asks simply, long, fluffy tail sweeping back and forth over the stone in slow, lazy movements. "I am all for another trip to the east, if that is what you wish of us, but more information is always a boon."<br />
<br> <br>Phosphorus was dedicated to naught but her work, but that doesn't prevent her from moving in closer to the center of the group, nodding to familiar faces while the light show started. She shifted her weight a bit to rest in a more comfortable position, passively listening to the voices speak and agents respond, looking towards the ethereal beings with a bit of a quirked eyebrow and tilted ear. She's already trying to piece together what's properly going on, but that doesn't externally show.<br />
<br> <br>Looking up at the light of the sky, feeling the power of something beyond hir, listening to what these inscrutable and powerful beings have to say, Emacs felt speechless, frustrated, and impotent. If gods could not do it, how could anyone? Shi cools down again, resolving itself into certainty, if they want hir and other mortals to help, then they must have some idea that mortals would be better at what they need.<br />
<br> <br>Emacs determines that shi can't really add anything to this conversation yet, if it's not actually just an announcement by a pair of gods in the sky.<br />
<br> <br>Where the world beyond met the world so fettered, Mokou could only look up, wondering for a time. Lights coalessing into form and spectacle, the lass only spent a moment in though, her hand instinctivly running to her comms, flicking it to record. The words that pounded out, echoing through her ears though... they seemed to burn. Their words cut and shod light upon what she'd been digging around through. The history that was shown, the records that were recorded by these... beings. Silent for a long time, but now? Now... <br />
<br> <br>The fennec wrapped her tail about her leg, gazing up at those swirling collection of lights. They were. And they mattered. So when they were silent... When they could not hear something she could but bite her tongue. Something had happened... somewhere beyond where the... the rest could reach. Europe? Where she had heard a few had drawn interest? Japan? The radio was up, but monitored like it was the end times. Suppose it was... "Help... You need our help. To find out... something." A simple question followed, but a single word. "Where?"<br />
<br> <br>After the pause, while questions and queries were voiced, the visions shimmer and pulse, and silence collects over the crowd again. The foxy vision emanates, "Help is indeed needed. Though our influence is presently hindered, we are not without means, but it requires you, the loyal, the curious, to help seek out answers..." and then the dogged figure adds, "We will be openning a way, a means to travel between, for you to pass through to the other... area. There is a point that is still strong enough to our ties there that we can transport you between. We ask that you venture there with care."<br />
<br> <br>"Something of your world, a calamity, has been interfering with the strength of our ties, the paradigm of our connection, affecting your world's 'magic', there, your... machines and affecting the landscape..." the mildly more masculine voice continues before the fox adds in, "What ills that have occurred will undoubtedly still be permeated through where you must explore and investigate. It would be wise to protect yourselves and guard against potential harm. Its nature... we are not familiar with, but you are resourceful, and we trust in your ability to unveil truths to this mystery..." They again fall silent for this all to sink in.<br />
<br> <br>Nodding slowly as she takes in the resonant voices that hum down from the projections, Tova mentally muses and analyzes the information. Whatever calamity had occurred, her mind turning mroe and more towards what had been heard over the radios, it must have changed the landscape, changed how things related and touched the other dimensions, but, more importantly, it had interfered with the nanites, the 'machines' mentioned. There were certainly a couple sources of influence that could hinder, and fewer than that on a broad scale.<br />
<br> <br>Escherr stood some and put his paws within his hoodie pocket looking to the two creatures some and giving a shrug. "Say what you will about us but you are correct, we adapt to many situations. I am all for a road trip though. Always telling myself I need to get out more." It was a bit interesting though trying to come up with what could be worse then what already happened to some places, curiosity nagged at the back of his skull though. Even more concerning was if the machines of this land were weakened or compromised there it would make some things a bit tougher.<br />
<br> <br>Edel nods slowly, bouncing idly on her paws. A trip! Exciting. She was eager. Life had grown dull lately, and this was the kind of adventure she longed for. And for a noble goal, too! "Well, I am ready," she says, patting the sword at her hip. "For whatever comes, be it friend or foe." She roll sher shoulders, tail flicking again. "I will find whatever I can, and I shall return to tell it all!"<br />
<br> <br>Enemy unknown? Ills? Danger? Phosphorus emits a quiet, weary sigh, pulling her rifle up into her hands and checking the magazine. The panda was not a stranger to dealing with unknown threats, but that didn't make it a less difficult task. Not to mention, trusting any sort of arcane transportation system that the supernatural beings would have them use. Whatever they encountered, she only could hope that it could be stopped with conventional means. It'd save them a whole lot of heartache. "Can you tell us anything besides this? Any... fine details?"<br />
<br> <br>Wearing hir nanite power suit under the robes, Emacs was suddenly very aware of it. A sneaking suspicion worked its way into hir head, "Radiation." shi whispered to hirself. The bombs dropped, and the contamination felt acutely by the machines at such fine scales. Shi felt nauseous. The world shi thought was near indestructable was suddenly in jeopardy. <br />
<br> <br>Emacs barely noticed the questions asked, absorbed by hir own concerns.<br />
<br> <br>It took a few moments for Mokou to catch up with what had been said. It was rolled over, and... confussing. some calamity that had broken connection in part with the nature of the beyond. Something that interiered with their... machines and the land. Some cataclysm. Her ears dipped, a quiet question never breaching her lips. The events of what had been created as of late... What had come though the coms... Pieces were put together, but the full story too terrible to consider. What it would imply... Her eyes scoured the crowd... finding a few others queasy. They had seen it too... had heard it...She shook her head. "Very... very well. Where shall this gate be... And when." Not a question. A foregone conclusion.<br />
<br> <br>Assent and questions mingle together in the crowd, a burbling hub-bub that again dies down as the two projections subtly flare, a soft pulse of intensity, and the foxier one emanates, "The portal will reside here, where our tie is strongest..." And, with the abstract light image's motion, poles root in the ground, planting themselves before shooting upwards and growing thick and sturdy. Appearing crossbeams snap into place to create the classical arch. Within the containment of this archway, light blooms and begins to swirl and whorl. Both images flare again, and the light intensifies within teh arch, particles effervescing from the center as it bleeds out, erupting outwards briefly before settling back into place, a flattened spiral saucer of light.<br />
<br> <br>The voices come again, in tandem this time, "... here is the gateway that will cross you to the other place, to where the calamity has struck.. to its fringes where we can still touch strongly. Those who can bring back details and ascertain... the cause and meaning... will be rewarded..." Their emanating voices are a bit more wan from the efforts shown, it seems. "Until then, we leave you to venture... and explore."<br />
<br> <br>With her eyes growing wide, Tova watches the display of the extradimensional powers manifesting before them all, a clear proof of some of what they are capable of. As the projections fade from view, the Dusk Dragon looks around at the others present to ensure she wasn't the only witness to this.<br />
<br> <br>Escherr whistles some to the display. "Impressive fanfare, then again wouldn't expect any less" Giving a bit of a chitter and chuckling some as he looked around to the group seeing many doubting faces, well except the overly excitable one. "Come on now stop looking like we are attending a funeral. Not every day we get asked by gods. Just think if survive may get something nice." Shrugging off most of the worries, little to do when you are in a worry. "Besides if hide and turn tail who says whatever is there won’t come here."<br />
<br> <br>"Ah... Radiation." Edel murmurs, ears twitching when someone else mentions it. She never thought about that. Did the place get blasted? That would be unfortunate. And here the tanuki priestess was hoping the whatever happened over seas was some kind of magical rejoining the planes- Or something grandiose of that nature. Oh, she'd have loved that. "Wishful thinking, I suppose," she mutters to herself. "Some extra precautions will need to be made." The display of a portal itself was pretty, but not exactly new to her. Not enough to pull her out of other thoughts, at least.<br />
<br> <br>"Once more, unto the breach." Phosphorus mutters, watching the rapid construction of the arch with a bit of a raised eyebrow, observing the activation of the gateway with a sigh. Nothing suprises her anymore, not now in the world in which rapid construction is the norm, rather than the exception. Radiation was... unfortunate, and she did have a suit of the nanite power armor, though she would prefer not to wear it. That is, if it even was radiation. The panda starts walking towards the portal, intending to just get closer, but not necessarily go through.<br />
<br> <br>Looking at the portal, Emacs put up the hood and helmet of hir nanite power suit and enters. Uncertain of the what lies beyond the threshold,but absolutely certain that it will be interesting. Hoping it will not be the charnel house shi expects. Maybe the gods are just asleep, but shi knows that the odds are not in hir favor.<br />
<br> <br>A planar rift of sorts. Mokou couldn't help but let a slight chuckle fall from her lips. How not months ago she'd call it impossible. Now though? Now it simply made her wonder how long till Zephyr would make money off it. It swirled and cast strange shadows... the lass simply moving slowly closer. A grim facination pulled at her, ideas she dare not entertain bubbling just beneath the surface of her mind. But... if the beyond was anything like here... Her muzzle fixed itself in a steady, sturdy expression. Flat. Bland. She slowly weaved her way through the crowd, at least thankful for her stature in that regards.. Before slowly looking up at the arch. "Torii. Classical, without the second beam," she murmured, a slight sigh falling from her lips. "What a strange... new world..." A curse lobbied at the one who held a grip upon her as she stood there... At the threshold.<br />
<br> <br>Spying the fellow clad in the Nanite Power Armor entering into teh portal, Tova purses her lips and looks around, seeing at least another approaching it. She calls over towards the panda, "Careful... that one at least pushed through wearing something to guard against potential ill environs, like water, gas, and any number of unknown variables... do you really want to pass through just yet without protection after being warned by the powers that be?" She heads up to the portal itself, standing besides it, looking at those that might approach.<br />
<br> <br>Escherr moved about and approched the portal and stared up at it, almost tempted to touch the light show of the portal. "Personally I don't have any of the gear to gaurd against such problems." Ears twitching to the comment about the powers that be and motions around some "They seem done talking, or could of warned us without anything cryptic. Wouldn't send us into danger wihtout knowing right?" Giving a shurg some knowing many would just to watch the common folk slip up. Taking out a cigarette and taking a drag on it. "Fuck it I like to gamble" Moving to step through.<br />
<br> <br>Edel eyes the portal for a moment, and those two heading within. "While I might like to gamble from time to time, not with my body. And while I might be incredibly curious to see what's on the other side... I would like to make sure it is either safe, or that I have proper protection first. While I love leaving bubbles, I tend to avoid... Ah, radiation."<br />
<br> <br>"Yes, yes, I just need to get the suit on first... I know they're climate controlled and all, but I still hate wearing them." Phosphorus grumbles. She typically wears the base "armor" without the helmet due to the minor strength benefit it confers, but wearing a piece of insulated headgear is... detrimental to awareness. At least, in her opinion, it is. She rummages the helmet from her pack, placing it over her head and starting to check seals. The panda glances up over at the agents entering the portal already, shaking her head. Not how you conduct an assault.<br />
<br> <br>Mokou looked slowly up to the swirling spiral of light. The portal that was to be.. an adventure. The fennec lass glanced back, her ears flickering at the dragon lass whom warned those whom entered. A sigh fell from her, before she shook her head, "You are right. We don't know what is past this, nor what will be beyond untill we try. And besides.." A sigh fell from her lips as she shrugs, "You don't know when one of the other people will come along, and try to close this, or shut it down. And... perhaps... it may close on its own." A slow shake of her head, the lass gesturing closer to the portal. "So for now...?" She shot a sad smile, walking quietly closer, moving up to the portal. A wash of strange... peculiar... sensations? Feeling? She couldn't tell. Only brushing past... Through.<br />
<br> <br>On behalf of her Patron, Nekomata, Maya has shown up. Unlike the last time, she's actually prepared for some danger, being clad in the form fitting nanite power armor that makes her look quite robotic from the outside. She purrs softly. "So this is the portal Oka-sama told me about." She looks about for familiar faces, hoping to meet someone before she takes the leap through the portal.<br />
<br> <br>Letting out a soft sigh when the individual doesn't head the warnings of deities and peers alike and simply goes in without protection, Tova heeds her own warnings and pulls out her own rudimentary nanite power armor and slips into it, fastening and securing before sealing the helmet overtop. She looks about before she, too, slips through the portal.<br />
<br> <br>Edel rolls her shoulders, offering a wave to Maya as she starts to suit up, herself. It takes her a few moments to squeeze into it all, and then her nanomagic reforms an... Approximation of her robe over it. More as decoration than anything. Can't go off to new lands looking like a brute. When that's all done, she turns and starts for the portal.<br />
<br> <br>The portal seems to have a consistency akin to watery gelatin. As figures enter, the most eager and or brazen, it's as if they are sucked into the congealing light, encased within. Though some may have entered sooner, their arrival is fairly simultaneous, passing through the portal's exit-point in the same stride they'd entered with, as if the transition had never happened. To most, there's nothing different about the feel due to their suits, but, to Escherr, a sense of nausea strikes almost immediately. Something akin to fire-ants crawling along his skin, a permeating heat that bubbles at the surface moves through his body. This is not pleasant at all, and it doesn't seem like it's going to stop or be adjusted to!<br />
<br> <br>The scenery is that of a modern Japanese shrine's Zen garden, though visual details show that there's an ill effect, here. Browning a whithering combined with singe marks on the terrain allude to the effects of fallout and still-permeating radiation, though on the outermost fringes.<br />
<br> <br>Tova takes a look over the shrine's grounds and back over the hill's cliff, across the landscape, and she telecomms to nearby comms, "Are you all seeing this?" except the signal is a bit staticy and garbled.<br />
<br> <br>Escherr not having the same protection he could feel that watery gelatin consistency of the portal, it was strange to say the least. Then hit with a sickness that made him rest a bit against the portals outlining pillars trying to work with it, more sheer will then anything. "Well god are assholes" Trying to chuckle some, all the power they show and can't offer some sort of defense. He went this far and is already affected, not having a suit though it seems a bit pointless to turn back and miss out. Leaning back against the pillar some though he looked over the land, having seen art of these sort of places before well this. While affected tree petals almost were an eerie beauty.<br />
<br> <br>"This is lovely," Edel comments, stroking her chin as she takes notes. Though her tea house is supposed to be more Chinese inspired... Well. These days, who would tell the difference? "A pity what has happened to it all... I wonder why..." She taps the side of her helmet in thought, looking around. "Well! So much for my hope of moving out here. Maybe we can get a door to China or something, later."<br />
<br> <br>Much of what's said while wearing hte helmet is garbled due to the intererence.<br />
<br> <br>Angry beeping starts to emit from some part of Phosphorus' suit, her dosimeter rather insistently trying to get her attention, the panda fiddling with it for a second to mute the device. She opens comms, notes how the radio signal is clearly rather incomprehensible, and instead approaches Tova and calmly places her helmet visor against the dragon's. "Try doing this, instead, if you need to talk to someone." Her tired voice is definitely more clear than the scrambled radio, but the conduction of dome to dome produces an odd distortion effect. "Do you have a dosimeter? Or a geiger counter? Anything of the sort?"<br />
<br> <br>Maya lands outside the portal, blinking a bit. "Rather pretty." She says to no one in particular. "Eerie, though." She moves to join the female tanuki she recognized from earlier. Of course, she's just going to stick to investigation for now. She shivers a bit, tapping the tanuki on the shoulder. "Do you know this place?"<br />
<br> <br>Looking around at the rest of the party, shi was surprised shi wasn't the first. Emacs looks at the scenery. "Hmm, this is too bad. This must have been such a pretty place" Shi says. "I wasn't aware there were nanites in Japan. They aren't taking this very well." <br />
There's still life though, even though it is withered, suffering an awful time, there is life. Emacs believes that this means that there's reason to hope that this place will recover. <br />
Emacs looks at the unarmored Escher with some concern, "You should go home, this place will kill you, maybe not though, maybe there are still things alive here."<br />
<br> <br>Tova, too, turns towards Escherr, seeing his state. She doesn't ask, though, she does. Moving over to where he leans, she tries to forceably push him back through the portal.<br />
<br> <br>Escherr swats a bit at the arm trying to do so and not having the bulky armor helped his mobility to slip past. Waving off the cocern some or those that look to him. "Just like a bad hangover" Giving a grimicing grin as held his stomach some and moved to walk near the tree. It seemed communcation was limited due to the effect so when he spoke it was most likely to no one. Getting closer some and touching at the tree a bit "It took awhile to fully effect the area and while sick and altered the tree was not dead. This effect had to only be recent in effects. Though rather then stay around he looked about looking for more green, perhapse not the entire area was effected.<br />
<br> <br>Edel looks towards Maya and leans over, getting closer in an approximation of Phosphorus' suggestion. "I do not," she replies. "I am from China, not Japan. This is my first time being here, since I wouldn't count Tanuki's realm as Japan." She returns her attention to the area, ears flicking under her helmet. "Shall we get to searching, then?"<br />
<br> <br>Phosphorus glances at Escherr, before just shaking her head and moving on. Since it was pretty clear that there was no need to expect any hostile beings to jump out and attack them, the panda clicks the safety selector back into place on her rifle and moves it off to the side, letting it hang from straps to the side. Beginning to search the area for signs of anything interesting, she takes a glance back at the others to make sure they're actually, you know, coming. The area is as alien to her as everyone else, but hopefully a keen eye will make up for deficiencies in the other department.<br />
<br> <br>Emacs nods at the suggestion that they look around. <br />
Clearly the Kitsune and the Tanuki have some idea of what we're looking for, shi thinks, we don't though. Shi puts hir head close to the others, "So where to?"<br />
<br> <br>Maya nods. "Searching sounds good." She starts poking her head around, wondering what might be around here as she tries to see if any of the nearby buildings or alcoves have inhabitants that might be persuaded to help fill them in.<br />
<br> <br>The Dusk Dragon gives a shake of her head. If the fellow had a deathwish, so be it. Her kind valued clarity of mind, and this one had obviously made a clear decision.. a wrong decision, but it was clear it wasn't under duress or influence outside his own machinations. She motions to the others with a thumb up, since the comms wren't functioning right to translate words well enough to make out in the garble.<br />
<br> <br>As they start to investigate, several figures exit out from the shrine proper, the activity of their presence having drawn attention to... what looks to be partially-mutated figures.<br />
<br> <br>The mutants don't seem to pose too much of a problem for the prepared group, though Escherr's swiftly getting worse and worse, the nausea increasing, exhasperated by the conflict. The mutants flee after the bout seems to have them at a disadvantage, and, on inspecting those who've been knocked out, their bodies are unevenly mutated. Some are more human in one spot or another, and the forms of their infections aren't like most seen in Fairhaven.<br />
<br> <br>Tova straightens after examining one of them, and she hefts the figure, shouldering the unconscious form. With hand gestures, she motions towards the portal and at herself. Through the visor of her helmet, she scowls at Escherr and pointedly points at him before thumbing back at the portal, but she shrugs, whether he does or not before heading back to bring the findings over to the other side.<br />
<br> <br>[[Category:RPLogs]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Portals_and_Portents_-_RPLOG&diff=628109Portals and Portents - RPLOG2017-09-30T22:56:26Z<p>Glitch: Created page with "=Participants= * Escherr * Mokou * Phosphorus * Maya * Emacs * Edel * Tova =Date= 30/09/2017 =Log= <div></div><br> <br><br> <br>Though the high pri..."</p>
<hr />
<div>=Participants=<br />
* [[Escherr]]<br />
* [[Mokou]]<br />
* [[Phosphorus]]<br />
* [[Maya]]<br />
* [[Emacs]]<br />
* [[Edel]]<br />
* [[Tova]]<br />
=Date=<br />
30/09/2017<br />
=Log=<br />
<div></div><br> <br><br> <br>Though the high priestess of the Dusk Dragon's strongest duties lay with her, Tova still had ties to several of entities in good standing. The dreams had come to her, like others who had ties to Inari, and she heeded its call. Coming to the shrine during the midday hour, the dragon woman projected an air of calm serenity about her, surveying the shrine proper while striding along.<br />
<br> <br>It was never hard to hear a whisper of something going on, strange dreams for a few lucky or unlucky few have greeted his ears. It was a hobby of Escherr's to know what was going on around the city. So with that in mind he made his way to the shrines, after all having a diety owe you one couldn't hurt buisness either.<br />
<br> <br>There was but one supernatural being Edel followed, and she followed them enough to name her own business after it! And enough to count herself a shrine priest. If she was going to be here anyway, today, sweeping up the stone and tending the shrine, she might as well look into the strange happenings. Smoothing down her ornate silk robes, she sets aside the broom once others seem to be arriving, and wanders over into the neighboring shrine to take her own place among the inquisitive.<br />
<br> <br>Not too much major happens without the rumor mill starting up, and given the not insignificant number of Kitsune/Tanuki/Nekomata dedicants that are about, the mill was certainly in high gear. Phosphorus figured that the potential of supernatural intrigue would outweigh the potential danger of checking the scene out, so the panda decided to stalk her way into the shrine in her typical fashion, showing up at the gathering group with nary a word or whisper.<br />
<br> <br>To answer the call of Inari was foremost on Emacs's mind as shi entered the shrine. Shi was no priestess, nor avid zealot, but shi knew the scope of hir duties to him. Shi enters the shrine with a measured, careful gait, deferring to other that shi passes. Shi was uncertain and anxious, but as shi continued,a sense of calm fell onto hir as shi got further, a measure of a smile could be seen emerging upon hir face. <br />
<br> <br>The messengers of Inari had invited hir along, so she resolved that shi was surely good enough to be here. Hir robes were plain and simple, undyed fabric worn over the armor shi was accustomed to when fighting. Shi hoped it would not come to that today though.<br />
<br> <br>Where supernaturals were concerned, Mokou held a disturbingly simple outlook upon them. They exist. Beyond that, their nature was obscured in mystery as much as the nanites themselves. So when it came to her ears that there was something stirring, those drawn from what had been Shinto belief, from those of Eastern lore were about, it was not with panic or fear that Mokou reacted. It was a saddened sigh and a slight change in the day's plans. After all... a shrine that had not been there in years gone by... Was not what she expected. So her work in hand, her day hardly at the cusp, she set out. Perhaps something would come of it.. perhaps she would simply take use of the garden she's heard of. Twas yet to be told...<br />
<br> <br>As those hearkening to the beckons, whether directly or indirectly, collected toagher at the shrine, the grounds were filled with an assortment of civil mutants. Dedicants and mystery-seekers gatehred at the spot of worship and dedication until a hush falls over the crowd...<br />
<br> <br>The sky's light distorts, becoming a rosy hue even in the midst of the day, and a pair of lights form before the shrine, lofted to tower over the shrine's exterior. One light is fire and gold, the foxfire dancing into the vague visage of a many-tailed fox whereas the other is burnt oranges and gay browns, banding before displaying thee semblance of a raccoon dog bearing a swell, full sac. Though abstracted form the light, the figures are unmistakeable for their shapes. Voices mingle together, androgynous in that they're masculine and feminine at once, the sound fading in like an echo but stronger in volume.<br />
<br> <br>"Daughters, Sons, Allies, and Friends... We have come to you with matters of concern," The voiec emitting seeming a hint more feminine and coming from the foxish vision overhead. The other vision, a hint more masculine in tone, but still about as androgynous, emits, "Affairs have taken place from afar, and our brethren have fallen mute. We are unable to clearly hear what has transpired, and, without the aid of you, our dedicated, we will not be able to investigate nor provide aid where needed."<br />
<br> <br>Pausing to let the impact of what they've conveyed sink in for a moment, the visions of light projected overhead look over those present somberly.<br />
<br> <br>Turning her face up towards the images projected, Tova listens intently, and her brow knits. Piecing together the visions from the dreams with what news she'd heard, some assumptions niggled at her mind, but she sorted them aside, waiting to hear what facts could be established before making any true deductions through the crystalline facets of her mind.<br />
<br> <br>Having been one of the first to arrive the rodent settled into a position of sitting on the mossy cobblestone and overlooking each to arrive. If he had to hazard to guess a few probably heeded the call with some link to the proper deities of these scattered shrines. Not to say it wasn’t tempting to dedicate oneself to these strange, supernatural like beings, but being tied to one never felt like the intelligent idea and keep to a monotheistic nature. Each being had some sway or control over what lay within the bubble, and for now these three had something important or event changing to summon those to help. If the city was to be viewed as a working organism these deities were the organs.As the lights started to show and voices rang out together the rat turned to look to the source, hearing what was said it seemed his idea of something being off in the city was not a bad assumption. Looking over the group again and even including himself it may have him wondering just how much desperation was in the air if the simple masses were to be involved, this though was something he lived for and dedicated to in knowing the world and even the supernatural aspects. Not being directly connected Escherr felt he should wait to say anything, least until those that chose to worship such things spoke first having a strong connection.<br />
<br> <br>Edel places her arms together, sleeves linked as she listens to the words from beyond. She had heard mention of the things that happened over-seas. She could only assume that is what was being spoken of. "What would you have us do?" She asks simply, long, fluffy tail sweeping back and forth over the stone in slow, lazy movements. "I am all for another trip to the east, if that is what you wish of us, but more information is always a boon."<br />
<br> <br>Phosphorus was dedicated to naught but her work, but that doesn't prevent her from moving in closer to the center of the group, nodding to familiar faces while the light show started. She shifted her weight a bit to rest in a more comfortable position, passively listening to the voices speak and agents respond, looking towards the ethereal beings with a bit of a quirked eyebrow and tilted ear. She's already trying to piece together what's properly going on, but that doesn't externally show.<br />
<br> <br>Looking up at the light of the sky, feeling the power of something beyond hir, listening to what these inscrutable and powerful beings have to say, Emacs felt speechless, frustrated, and impotent. If gods could not do it, how could anyone? Shi cools down again, resolving itself into certainty, if they want hir and other mortals to help, then they must have some idea that mortals would be better at what they need.<br />
<br> <br>Emacs determines that shi can't really add anything to this conversation yet, if it's not actually just an announcement by a pair of gods in the sky.<br />
<br> <br>Where the world beyond met the world so fettered, Mokou could only look up, wondering for a time. Lights coalessing into form and spectacle, the lass only spent a moment in though, her hand instinctivly running to her comms, flicking it to record. The words that pounded out, echoing through her ears though... they seemed to burn. Their words cut and shod light upon what she'd been digging around through. The history that was shown, the records that were recorded by these... beings. Silent for a long time, but now? Now... <br />
<br> <br>The fennec wrapped her tail about her leg, gazing up at those swirling collection of lights. They were. And they mattered. So when they were silent... When they could not hear something she could but bite her tongue. Something had happened... somewhere beyond where the... the rest could reach. Europe? Where she had heard a few had drawn interest? Japan? The radio was up, but monitored like it was the end times. Suppose it was... "Help... You need our help. To find out... something." A simple question followed, but a single word. "Where?"<br />
<br> <br>After the pause, while questions and queries were voiced, the visions shimmer and pulse, and silence collects over the crowd again. The foxy vision emanates, "Help is indeed needed. Though our influence is presently hindered, we are not without means, but it requires you, the loyal, the curious, to help seek out answers..." and then the dogged figure adds, "We will be openning a way, a means to travel between, for you to pass through to the other... area. There is a point that is still strong enough to our ties there that we can transport you between. We ask that you venture there with care."<br />
<br> <br>"Something of your world, a calamity, has been interfering with the strength of our ties, the paradigm of our connection, affecting your world's 'magic', there, your... machines and affecting the landscape..." the mildly more masculine voice continues before the fox adds in, "What ills that have occurred will undoubtedly still be permeated through where you must explore and investigate. It would be wise to protect yourselves and guard against potential harm. Its nature... we are not familiar with, but you are resourceful, and we trust in your ability to unveil truths to this mystery..." They again fall silent for this all to sink in.<br />
<br> <br>Nodding slowly as she takes in the resonant voices that hum down from the projections, Tova mentally muses and analyzes the information. Whatever calamity had occurred, her mind turning mroe and more towards what had been heard over the radios, it must have changed the landscape, changed how things related and touched the other dimensions, but, more importantly, it had interfered with the nanites, the 'machines' mentioned. There were certainly a couple sources of influence that could hinder, and fewer than that on a broad scale.<br />
<br> <br>Escherr stood some and put his paws within his hoodie pocket looking to the two creatures some and giving a shrug. "Say what you will about us but you are correct, we adapt to many situations. I am all for a road trip though. Always telling myself I need to get out more." It was a bit interesting though trying to come up with what could be worse then what already happened to some places, curiosity nagged at the back of his skull though. Even more concerning was if the machines of this land were weakened or compromised there it would make some things a bit tougher.<br />
<br> <br>Edel nods slowly, bouncing idly on her paws. A trip! Exciting. She was eager. Life had grown dull lately, and this was the kind of adventure she longed for. And for a noble goal, too! "Well, I am ready," she says, patting the sword at her hip. "For whatever comes, be it friend or foe." She roll sher shoulders, tail flicking again. "I will find whatever I can, and I shall return to tell it all!"<br />
<br> <br>Enemy unknown? Ills? Danger? Phosphorus emits a quiet, weary sigh, pulling her rifle up into her hands and checking the magazine. The panda was not a stranger to dealing with unknown threats, but that didn't make it a less difficult task. Not to mention, trusting any sort of arcane transportation system that the supernatural beings would have them use. Whatever they encountered, she only could hope that it could be stopped with conventional means. It'd save them a whole lot of heartache. "Can you tell us anything besides this? Any... fine details?"<br />
<br> <br>Wearing hir nanite power suit under the robes, Emacs was suddenly very aware of it. A sneaking suspicion worked its way into hir head, "Radiation." shi whispered to hirself. The bombs dropped, and the contamination felt acutely by the machines at such fine scales. Shi felt nauseous. The world shi thought was near indestructable was suddenly in jeopardy. <br />
<br> <br>Emacs barely noticed the questions asked, absorbed by hir own concerns.<br />
<br> <br>It took a few moments for Mokou to catch up with what had been said. It was rolled over, and... confussing. some calamity that had broken connection in part with the nature of the beyond. Something that interiered with their... machines and the land. Some cataclysm. Her ears dipped, a quiet question never breaching her lips. The events of what had been created as of late... What had come though the coms... Pieces were put together, but the full story too terrible to consider. What it would imply... Her eyes scoured the crowd... finding a few others queasy. They had seen it too... had heard it...She shook her head. "Very... very well. Where shall this gate be... And when." Not a question. A foregone conclusion.<br />
<br> <br>Assent and questions mingle together in the crowd, a burbling hub-bub that again dies down as the two projections subtly flare, a soft pulse of intensity, and the foxier one emanates, "The portal will reside here, where our tie is strongest..." And, with the abstract light image's motion, poles root in the ground, planting themselves before shooting upwards and growing thick and sturdy. Appearing crossbeams snap into place to create the classical arch. Within the containment of this archway, light blooms and begins to swirl and whorl. Both images flare again, and the light intensifies within teh arch, particles effervescing from the center as it bleeds out, erupting outwards briefly before settling back into place, a flattened spiral saucer of light.<br />
<br> <br>The voices come again, in tandem this time, "... here is the gateway that will cross you to the other place, to where the calamity has struck.. to its fringes where we can still touch strongly. Those who can bring back details and ascertain... the cause and meaning... will be rewarded..." Their emanating voices are a bit more wan from the efforts shown, it seems. "Until then, we leave you to venture... and explore."<br />
<br> <br>With her eyes growing wide, Tova watches the display of the extradimensional powers manifesting before them all, a clear proof of some of what they are capable of. As the projections fade from view, the Dusk Dragon looks around at the others present to ensure she wasn't the only witness to this.<br />
<br> <br>Escherr whistles some to the display. "Impressive fanfare, then again wouldn't expect any less" Giving a bit of a chitter and chuckling some as he looked around to the group seeing many doubting faces, well except the overly excitable one. "Come on now stop looking like we are attending a funeral. Not every day we get asked by gods. Just think if survive may get something nice." Shrugging off most of the worries, little to do when you are in a worry. "Besides if hide and turn tail who says whatever is there won’t come here."<br />
<br> <br>"Ah... Radiation." Edel murmurs, ears twitching when someone else mentions it. She never thought about that. Did the place get blasted? That would be unfortunate. And here the tanuki priestess was hoping the whatever happened over seas was some kind of magical rejoining the planes- Or something grandiose of that nature. Oh, she'd have loved that. "Wishful thinking, I suppose," she mutters to herself. "Some extra precautions will need to be made." The display of a portal itself was pretty, but not exactly new to her. Not enough to pull her out of other thoughts, at least.<br />
<br> <br>"Once more, unto the breach." Phosphorus mutters, watching the rapid construction of the arch with a bit of a raised eyebrow, observing the activation of the gateway with a sigh. Nothing suprises her anymore, not now in the world in which rapid construction is the norm, rather than the exception. Radiation was... unfortunate, and she did have a suit of the nanite power armor, though she would prefer not to wear it. That is, if it even was radiation. The panda starts walking towards the portal, intending to just get closer, but not necessarily go through.<br />
<br> <br>Looking at the portal, Emacs put up the hood and helmet of hir nanite power suit and enters. Uncertain of the what lies beyond the threshold,but absolutely certain that it will be interesting. Hoping it will not be the charnel house shi expects. Maybe the gods are just asleep, but shi knows that the odds are not in hir favor.<br />
<br> <br>A planar rift of sorts. Mokou couldn't help but let a slight chuckle fall from her lips. How not months ago she'd call it impossible. Now though? Now it simply made her wonder how long till Zephyr would make money off it. It swirled and cast strange shadows... the lass simply moving slowly closer. A grim facination pulled at her, ideas she dare not entertain bubbling just beneath the surface of her mind. But... if the beyond was anything like here... Her muzzle fixed itself in a steady, sturdy expression. Flat. Bland. She slowly weaved her way through the crowd, at least thankful for her stature in that regards.. Before slowly looking up at the arch. "Torii. Classical, without the second beam," she murmured, a slight sigh falling from her lips. "What a strange... new world..." A curse lobbied at the one who held a grip upon her as she stood there... At the threshold.<br />
<br> <br>Spying the fellow clad in the Nanite Power Armor entering into teh portal, Tova purses her lips and looks around, seeing at least another approaching it. She calls over towards the panda, "Careful... that one at least pushed through wearing something to guard against potential ill environs, like water, gas, and any number of unknown variables... do you really want to pass through just yet without protection after being warned by the powers that be?" She heads up to the portal itself, standing besides it, looking at those that might approach.<br />
<br> <br>Escherr moved about and approched the portal and stared up at it, almost tempted to touch the light show of the portal. "Personally I don't have any of the gear to gaurd against such problems." Ears twitching to the comment about the powers that be and motions around some "They seem done talking, or could of warned us without anything cryptic. Wouldn't send us into danger wihtout knowing right?" Giving a shurg some knowing many would just to watch the common folk slip up. Taking out a cigarette and taking a drag on it. "Fuck it I like to gamble" Moving to step through.<br />
<br> <br>Edel eyes the portal for a moment, and those two heading within. "While I might like to gamble from time to time, not with my body. And while I might be incredibly curious to see what's on the other side... I would like to make sure it is either safe, or that I have proper protection first. While I love leaving bubbles, I tend to avoid... Ah, radiation."<br />
<br> <br>"Yes, yes, I just need to get the suit on first... I know they're climate controlled and all, but I still hate wearing them." Phosphorus grumbles. She typically wears the base "armor" without the helmet due to the minor strength benefit it confers, but wearing a piece of insulated headgear is... detrimental to awareness. At least, in her opinion, it is. She rummages the helmet from her pack, placing it over her head and starting to check seals. The panda glances up over at the agents entering the portal already, shaking her head. Not how you conduct an assault.<br />
<br> <br>Mokou looked slowly up to the swirling spiral of light. The portal that was to be.. an adventure. The fennec lass glanced back, her ears flickering at the dragon lass whom warned those whom entered. A sigh fell from her, before she shook her head, "You are right. We don't know what is past this, nor what will be beyond untill we try. And besides.." A sigh fell from her lips as she shrugs, "You don't know when one of the other people will come along, and try to close this, or shut it down. And... perhaps... it may close on its own." A slow shake of her head, the lass gesturing closer to the portal. "So for now...?" She shot a sad smile, walking quietly closer, moving up to the portal. A wash of strange... peculiar... sensations? Feeling? She couldn't tell. Only brushing past... Through.<br />
<br> <br>On behalf of her Patron, Nekomata, Maya has shown up. Unlike the last time, she's actually prepared for some danger, being clad in the form fitting nanite power armor that makes her look quite robotic from the outside. She purrs softly. "So this is the portal Oka-sama told me about." She looks about for familiar faces, hoping to meet someone before she takes the leap through the portal.<br />
<br> <br>Letting out a soft sigh when the individual doesn't head the warnings of deities and peers alike and simply goes in without protection, Tova heeds her own warnings and pulls out her own rudimentary nanite power armor and slips into it, fastening and securing before sealing the helmet overtop. She looks about before she, too, slips through the portal.<br />
<br> <br>Edel rolls her shoulders, offering a wave to Maya as she starts to suit up, herself. It takes her a few moments to squeeze into it all, and then her nanomagic reforms an... Approximation of her robe over it. More as decoration than anything. Can't go off to new lands looking like a brute. When that's all done, she turns and starts for the portal.<br />
<br> <br>The portal seems to have a consistency akin to watery gelatin. As figures enter, the most eager and or brazen, it's as if they are sucked into the congealing light, encased within. Though some may have entered sooner, their arrival is fairly simultaneous, passing through the portal's exit-point in the same stride they'd entered with, as if the transition had never happened. To most, there's nothing different about the feel due to their suits, but, to Escherr, a sense of nausea strikes almost immediately. Something akin to fire-ants crawling along his skin, a permeating heat that bubbles at the surface moves through his body. This is not pleasant at all, and it doesn't seem like it's going to stop or be adjusted to!<br />
<br> <br>The scenery is that of a modern Japanese shrine's Zen garden, though visual details show that there's an ill effect, here. Browning a whithering combined with singe marks on the terrain allude to the effects of fallout and still-permeating radiation, though on the outermost fringes.<br />
<br> <br>Tova takes a look over the shrine's grounds and back over the hill's cliff, across the landscape, and she telecomms to nearby comms, "Are you all seeing this?" except the signal is a bit staticy and garbled.<br />
<br> <br>Escherr not having the same protection he could feel that watery gelatin consistency of the portal, it was strange to say the least. Then hit with a sickness that made him rest a bit against the portals outlining pillars trying to work with it, more sheer will then anything. "Well god are assholes" Trying to chuckle some, all the power they show and can't offer some sort of defense. He went this far and is already affected, not having a suit though it seems a bit pointless to turn back and miss out. Leaning back against the pillar some though he looked over the land, having seen art of these sort of places before well this. While affected tree petals almost were an eerie beauty.<br />
<br> <br>"This is lovely," Edel comments, stroking her chin as she takes notes. Though her tea house is supposed to be more Chinese inspired... Well. These days, who would tell the difference? "A pity what has happened to it all... I wonder why..." She taps the side of her helmet in thought, looking around. "Well! So much for my hope of moving out here. Maybe we can get a door to China or something, later."<br />
<br> <br>Much of what's said while wearing hte helmet is garbled due to the intererence.<br />
<br> <br>Angry beeping starts to emit from some part of Phosphorus' suit, her dosimeter rather insistently trying to get her attention, the panda fiddling with it for a second to mute the device. She opens comms, notes how the radio signal is clearly rather incomprehensible, and instead approaches Tova and calmly places her helmet visor against the dragon's. "Try doing this, instead, if you need to talk to someone." Her tired voice is definitely more clear than the scrambled radio, but the conduction of dome to dome produces an odd distortion effect. "Do you have a dosimeter? Or a geiger counter? Anything of the sort?"<br />
<br> <br>Maya lands outside the portal, blinking a bit. "Rather pretty." She says to no one in particular. "Eerie, though." She moves to join the female tanuki she recognized from earlier. Of course, she's just going to stick to investigation for now. She shivers a bit, tapping the tanuki on the shoulder. "Do you know this place?"<br />
<br> <br>Looking around at the rest of the party, shi was surprised shi wasn't the first. Emacs looks at the scenery. "Hmm, this is too bad. This must have been such a pretty place" Shi says. "I wasn't aware there were nanites in Japan. They aren't taking this very well." <br />
There's still life though, even though it is withered, suffering an awful time, there is life. Emacs believes that this means that there's reason to hope that this place will recover. <br />
Emacs looks at the unarmored Escher with some concern, "You should go home, this place will kill you, maybe not though, maybe there are still things alive here."<br />
<br> <br>Tova, too, turns towards Escherr, seeing his state. She doesn't ask, though, she does. Moving over to where he leans, she tries to forceably push him back through the portal.<br />
<br />
<br />
[[Category:RPLogs]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Glazed_Scarab&diff=139165Glazed Scarab2014-06-24T22:20:53Z<p>Glitch: Updating wiki to reflect in-game update.</p>
<hr />
<div>{{Mako Item|name=Glazed Scarab|desc=Those of Anbuis Servants bearing the Glazed Scarab are shown more favor by their patron. When defeated in combat, hey suffer no lasting Wounds when risen again. The disciple must be actively dedicated in order for this affect to occur.|cost=25}}</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=34814Monster Maker2013-09-22T01:58:35Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
: If you like someone else's work, be sure to make use of the ''commend'' command to show your appreciation. You can ''commend'' '''form''' where '''form''' is replaced with the name of the form, such as ''commend'' '''goblin girl'''. This is one way to help authors know their work's appreciated, and it also gives them a little boost of Mako to show how much their work was liked.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
==== Taur and Serpentine Forms ====<br />
::Different from the process you'd put together a standard, bipedal form with, this one takes a few exceptions and additional string parsing. Make sure to add that they are a Taur or Serpentine in the Notes so that a flag can be set to the Ass section and to the monster itself so that, if the ass is present, their legs won't show (we use a Legless property in the monster infection, so the entire lower torso description would go into the ass, not at all into the legs). In the Legs Description, instead of a normal description, you'd have something along the lines of this:<br />
<br />
Taur:<br />
[if taur is present in [player]]part of a lower torso.[else]<description as if they were bipedal>>[end if]<br />
<br />
Serpentine:<br />
[if serpentine is present in [player]]nonexistent.[else]<description as if they were bipedal>[end if]<br />
<br />
:: This way, if you don't have the ass of said form, you'd have some bipedal legs, but if you do, the legs will be invisible anyhow. In the Ass portion, you would put the entire description for the Taur or Serpentine form:<br />
<br />
Taur:<br />
Their lower body is that of a horse complete with four sturdy legs meant for long strides and a rounded, taut flanks with a whippety horse's tail.<br />
<br />
Serpentine:<br />
Their torso melts down into a long, sinuously serpentine tail that supports their upper body. Its length tapers down to a fine tip, and muscles ripple all along its length.<br />
<br />
:: This way, the form will display properly so long as the ass is in place. If the ass isn't that of the mutation, well, then there will be bipedal legs.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites. ''NOTE'': String Parsing has been updated with [if [player] is feminine] which will trigger for nonmasculine females and feminine characters and herms. This streamlines things well!<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
::* Case statements can be used in lieu of messy, repeatedly nested 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.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
::''Example:''<br />
::Arm Description: are lean and powerful. [if local stat Kitsune/Quad of [player] = 0][They] resemble those of a human ending in hands tipped with foxy claws.[else][They] resemble those of a fox with clawed paws at the end, ready to support their chest and head.[end if]<br />
::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 quadraped's. The 'Quad' naming was arbitrary, and the form is Kistune. It's a good way to organize variables.<br />
<br />
:'''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 two colors supported, Color and Color2.<br />
<br />
::''Color''<br />
:[if color is present in [player]][local stat color of [player]][else]<default>[end if]<br />
::''Color2''<br />
:[if color2 is present in [player]][local stat color2 of [player]][else]<default>[end if]<br />
::''Example:''<br />
::Skin Description: a sleek coat of [if color is present in [player]][local stat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 is present in [player]][local stat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.<br />
<br />
:'''Arm/Tail Divider Support''': The string parsing used in order to add in alternative descriptions for arm and tail divider usage.<br />
<br />
::''Arm Divider''<br />
:[if stat misc/arm divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Tail Divider''<br />
:[if stat misc/tail divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Example:''<br />
::Arm Description: powerfully built with [if stat misc/arm divider of [player] = 1]stacked shoulders leading to three pairs of arms.[else]sturdy shoulders leading down to their powerful arms.[end if] Each terminates in dexterous hands capped in wicked talons.<br />
<br />
<br />
:'''Mutation Check''': When you need to check for a certain bodypart carrying a certain mutation, here's how.<br />
<br />
:[if stat mutation/<body part> of [player] = <mutation>]<statement if true>[else]<statement if false>[end if]<br />
::''Example:''<br />
:Arm Description: long and lean[if stat mutation/skin of [player] = Feral Dragon] with a dense covering of scaled articulating down over their joints[end if].<br />
<br />
<br />
'''There is a pair of INVALUABLE commands created by Fauna. They are: @nviewparse and @formparse.<br />
:: 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!<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Waiting_For_Godot_and_Bop_It_-_RPLOG&diff=32830Waiting For Godot and Bop It - RPLOG2013-08-21T05:37:27Z<p>Glitch: Removing a double-posted line by Lukas.</p>
<hr />
<div>=Participants=<br />
* [[Inis]]<br />
* [[Lotus]]<br />
* [[Lukas]]<br />
=Date=<br />
21/8/2013<br />
=Log=<br />
<div></div><br> <br>Whisper and rumor has been travelling around the headquarters of Zephyr and several of the other local Fairhaven haunts about a surviving piece of tech from pre-P-Day that still functions. Not too long after the fresh grisel is chewed over by the rumormongers, a posting had been placed in Zephyr's Lobby area reading:<br />
<br />
Expedition - Looking for a few intelligent individuals to help find and procur functional pre-P-Day Tech. Please meet just outside Zephyr HQ at ~time~. I will be there, and I will be willing to provide compensation upon success.<br />
- Peabody Broomshanks<br />
<br />
When the time comes around, though, there doesn't appear to be anyone more than just one figure standing outside of Zephyr. A dapper-dressed rat with a pith helmet and khaki capris and vest looking well the part of a Great White Hunter. Teetering on hefty boots, the rodent surveys the area for potential aides.<br> <br>A figure approaches from the northeast. Judging by the bushy tail, it's probably a skunk. As he gets closer, his gear becomes apparent: A kevlar vest worn over a black t-shirt, khaki pants, a belt with big pockets on it, and a suppressed FN P90 slung over his shoulder. "Are you Broomshanks?" he asks.<br> <br>Seeing the two at the described meeting point confirms this must be the right spot. Lotus, a completely naked goo girl, that looks completely unprepared for any sort of risky adventure, moves toward the two.<br> <br>The rodent lifts a crop to tip the brim of his pith hat up. In a strong British accent that lies high in the nasal cavity of that tapered bridge, he says, "Why, yes, I'm Peabody Broomshanks. Are you here to proceed on the expedition?" His ratty eyes peruse over the skunk's rather ready attire approvingly before spying the nearing goo and blinking a few times, but says nothing, the question open to the pair.<br> <br>Lukas nods an affirmative. "That's why I'm here," he says. "Name's Lukas White." He extends a hand to the rat, and notices the goo girl approach out of the corner of his eye. She's, well, rather attractive, honestly, but that's not what he needs to be thinking about right now. "Hello there," he says to her.<br> <br>Lotus smiles and warmly greets the pair, "I'm Lotus." She seems completely oblivious, or possibly content in her nudity. A closer look shows some fairly enticing assets as well as a medkit in a bag slug over her shoulder.<br> <br>The rodent seems positively pleased at the greeting Lukas gives, a gloved hand taking the skunks and giving it a genteel wag before looking to Lotus, some visible relief showing after she speaks. "Ah, good, good," he banters in his accented voice, the high nasality of it rolling with each clipped word, "well, then, the rumors have it that an artifact from several years back seems to have been unearthed... or scavenged, if you will, by one of a small collection of folks due northeast of here, not far from the highway area. There's a small community, there. No more than twenty or thirty folks gatehred together. I figure we can traverse there and make some sort of arrangement to procur the oddity, what?"<br> <br>Lukas nods again. "Sounds good to me," he says. "Anything we should know about the locals before we head out?" He gives his hip a little pat, making sure that his sidearm is still there. It is. Good.<br> <br>A little intimidated by the firearms Lotus keeps her distance. "They're not violent, are they?"<br> <br>"From there? I shouldn't think so. Not to us, anyway. We're not wild feral types masquerading around and raping and pillaging, now, are we? Civility is the way to communicate well, I always say, what!" Peabody chips in cheerily, "Mmm, well, the area's a tit bit nipply. Breast be prepared for a breeze bit, but nothing worth bundling up snug for, really. The climate of the people there's about as chill, but not so much to warrant hostility, I should think."<br> <br>Lukas has to work pretty hard to stifle a laugh at the Brit's Freudian slip. Or subtle hint. He chooses to ignore it in his response. "Good to know," he says. "We should get moving," he says. "We've only got a few hours of daylight left."<br> <br>Wether through sheer obliviousness or taking it as some posh saying, Lotus misses the nipple slip entirely, "Is the settlement far from here?"<br> <br>"Not far from here, no. Stiff upper lip!" Peabody says towards the goo before realizing what he's talking to and blinks, rubbing at his own lip thoughtfully, "WEll... stiff as it can get, I suppose. Shouldn't take more than fifteen minutes to reach from ehre if we head now." He motions to them both.<br> <br>The travel was fairly uneventful. Occassionally, along the way, the pith-helmeted rodent would take out a kerchief and hug it over his nose while passing some of the less savory sorts, but many of the ferals kept their distance. The group seemed too well armed or at least had an air of experience about them that kept the monstrous-minded from drawing in.<br />
<br />
As they approached the small settlement comprised of makeshift hovels comprised of debris and concrete slabs with rebar sticking out. General pathes of less dross grid about the living arrangements. Those who move about give the party of travellers wary looks, but, as Peabody had described, they wwere chill but not hostile... yet. "Somewhere about here.... perhaps you two could ask around?"<br> <br>Lukas takes a few steps toward one of the locals. "Excuse me," he says. "Could you spare a minute? We need some help locating something."<br> <br>Lotus follows Lukas, keeping an eye out for danger. She looks back at peabody, wary of splitting up a group.<br> <br>The rodent keeps where he is, that kerchief held over his nose and muzzle-end. He gives Lotus a solid thumb-up from where he stands. The person, a part-skunk, part-feline with a gtyphon's beak wearing a tattered shawl looks at Lukas as if he'd asked her to strip naked and play her knee like bongos. "�Qu�?" she inquires in a perplexed tone, "No hablo Inglish."<br> <br>"Oh. Um..." Lukas thinks for a moment. "High school spanish, don't fail me now..." Looking at the woman, he says, "Habla espanol muy poco. Pero, donde estas... uh..." He looks over his shoulder. "The artifact?"<br> <br>Lotus purses her lips, trying to nut out some way to get their objective across, "Technology?, she offers weakly.<br> <br>The woman tilts her head a little and says, "Wakarimasen!" before swiftly scuttling away. A younger-seeming figure that had been watching hops up onto a pile of rubble, "Ey... you guys lookin' for Godot's gadget?" This one's primarily feline with some accents of Raccoon guy in them, though they're fairly androgynous.<br> <br>"Yeah, probably," Lukas says. "We heard there was some pre-nanite tech around."<br> <br>Wanting to make sure Lukas' appearance didn't give the wrong impression, Lotus adds, "We've come to trade for it."<br> <br>The figure gives a scritch against its scalp, "Pre-nanny-whatsit? Well... Godot's got a nifty gadget that some say's been 'round b'fore the 'splosion'n stuff, if that's what you mean. He's pretty good with it, too! I've not been able to beat him at his game, that's for sure!" and the youthful figure points of towards where several slabs of concrete are stacked into a larger hovel than the others.<br> <br>Lukas looks towards the other two. Game? He shrugs, and follows the feline.<br> <br>Lotus follows lukas and throws a quick glance back to peabody, "A game? That shouldn't be too hard? right?"<br> <br>The rodent follows after the pair of them, looking about with his tail sweeping side to side as he goes. "Game? I say, mayhaps the device has some sort of mechanism that these people wager on?"<br />
<br />
The felicoon scampers on ahead, "Godot! Godot! Some challengers are here!" before looking back and saying, "You don't want to be waiting for Godot, so I'll let'm know you're here, y'know?"<br> <br>A voice comes out from the hovel, and a lanky figure that's mostly lizard save for some raccoon hands peers out, "What what? Challengers, eh?" And he skitters from his dwelling, "Have you come to challenge me in.. the Bop It?" and he holds up said device.<br> <br>It takes Lukas nearly fifteen second to collect his thoughts. "...I... Yes. Yes we have." He looks over his shoulder at the other two, and shrugs.<br> <br>Lotus moves in closer, eager to get a look at the artifact.<br> <br>The fellow does a hop and a skip back when the goo moves in closer and holds up a hand, "Wait, wait... one challenger at a time... who will be challenging Godot?"<br> <br>Lukas has to look away to keep from laughing. "I will," he says.<br> <br>Lotus watches on, trying to peek around Lukas.<br> <br>Setting the machine going, the figure of Godot begins to play at it... "Bop It..." bop "Twist it..." a cranking noise "Pull it" a slidewhistle noise "Pull it" and again... on through to about a hundred sets total "Your score is... one hundred!" before the figure offers it to Lukas, "Your turn."<br> <br>When the device is handed over to Lukas, the skunk seems a little akward at first, but with Lotus' encouragement, the combat-vested mephit manages not only to quicken his reactions, but he's able to beat the score by a good margin! Godot guffaws and motions, "You have beaten me fair and square... the device, it is yours to take." Peabody steps forwards, "Excellent, excellent! You two have proven fine additions to this excursion. Come, come, and I will pay you both for your assistance towards science!"<br> <br>Lotus blinks and follows, considering a career in artifact hunting, "Well, I, ..."[[Category:RPLogs]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Dusk_Dragon_(Dedication)&diff=32267Dusk Dragon (Dedication)2013-07-24T03:53:10Z<p>Glitch: Created page with "{{Monster |Arms=Rending Claws |Ass=Tail Smash |Groin= |Head=Drain Vitae |Legs=Pounce |Skin=Mirage, Smooth Hide |Torso=Feline Agility, Vitality ..."</p>
<hr />
<div>{{Monster<br />
|Arms=[[Rending Claws]]<br />
|Ass=[[Tail Smash]]<br />
|Groin=<br />
|Head=[[Drain Vitae]]<br />
|Legs=[[Pounce]]<br />
|Skin=[[Mirage]], [[Smooth Hide]]<br />
|Torso=[[Feline Agility]], [[Vitality]]<br />
}}<br />
<br />
== Dusk Dragon Dedication ==<br />
<br />
Dusk Dragons are a race of lesser celestial dragon-like beings, harbingers of the twilight. They draw on the passions of others, draining out aggression and perpetuating calmness. Peaks of passion are drawn towards the plains of placidity. All the potential for passion, whether it be anger or lust, is taken as sustenance, but rather than instill others with passion to feed themselves, they draw on the rather abundant supply of it that exists already. Uber Foxes do not like them, as they're a competitor for food supply and often leave no passions to draw towards lust.<br />
Costs 50 mako.<br />
<br />
== Features ==<br />
They sap at passions. This means the excess of heightened emotion like Lust and Rage. This does NOT steal people's abilities to feel normal emotions nor steal their will away.<br />
Shift between a Dusk Dragon shape and human.<br />
<br />
== Abilities ==<br />
[[Abyssal Aura]]<br><br />
[[Dusk Phantoms]]<br><br />
[[Serenity]]<br><br />
<br />
== Commands ==<br />
<br />
[[Category:Dedications]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Yama_Inu&diff=32266Yama Inu2013-07-24T03:43:10Z<p>Glitch: </p>
<hr />
<div>{{Monster<br />
|arms=[[Gouging Claws]]<br />
|tail=[[Enervating Poison]]<br />
|groin=<br />
|head=[[Infectious Bite]], [[Poison Breath]]<br />
|legs=<br />
|skin=[[Abrasive Hide]], [[Furry Hide]]<br />
|torso=[[Muscle Mass]]<br />
|location1=Jutting Peaks<br />
|level1=55-61<br />
}}<br />
<br />
Yama Inu, literally "Mountain Dog" is named for its similarity to a Japanese demon dog. Large in size, they're a highly poisonous species that can be found in the Jutting Peaks region of Fairhaven.<br />
There are several custom stats that can be set on the Yama Inu to change its appearance a bit.<br />
:Mane Type: What type of style their mane is shaped. Example: curving fur spikes<br />
::@set me=Inu/ManeType:<description><br />
:Fur Type: How their fur is groomed. Example: neat<br />
::@set me=Inu/FurType:<description><br />
:Dog 1: Their muzzle is a mix between two dogs. This is the first. Example: Boxer<br />
::@set me=Inu/Dog1:<dog type><br />
:Dog 2: Their muzzle is a mix between two dogs. This is the second. Example: Beagle<br />
::@set me=Inu/Dog2:<dog type><br />
:Dog 3: Their ears are those of a dog breed. Example: Wolfhound<br />
::@set me=Inu/Dog3:<dog type><br />
<br />
Their fur is Color Chooser compatible!<br />
[[Category:Monsters]]<br />
[[Category:Canines]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Yama_Inu&diff=32263Yama Inu2013-07-24T03:41:09Z<p>Glitch: Created page with "{{Monster |arms=Gouging Claws |tail=Enervating Poison |groin= |head=Infectious Bite, Poison Breath |legs= |skin=Abrasive Hide, Furry Hide |torso=[[Musc..."</p>
<hr />
<div>{{Monster<br />
|arms=[[Gouging Claws]]<br />
|tail=[[Enervating Poison]]<br />
|groin=<br />
|head=[[Infectious Bite]], [[Poison Breath]]<br />
|legs=<br />
|skin=[[Abrasive Hide]], [[Furry Hide]]<br />
|torso=[[Muscle Mass]]<br />
|location1=Jutting Peaks<br />
|level1=55-61<br />
}}<br />
<br />
Yama Inu, literally "Mountain Dog" is named for its similarity to a Japanese demon dog. Large in size, they're a highly poisonous species that can be found in the Jutting Peaks region of Fairhaven.<br />
There are several custom stats that can be set on the Yama Inu to change its appearance a bit.<br />
:Mane Type: What type of style their mane is shaped. Example: curving fur spikes<br />
::@set me=Inu/ManeType:<description><br />
:Fur Type: How their fur is groomed. Example: neat<br />
::@set me=Inu/FurType:<description><br />
:Dog 1: Their muzzle is a mix between two dogs. This is the first. Example: Boxer<br />
::@set me=Inu/Dog1:<dog type><br />
:Dog 2: Their muzzle is a mix between two dogs. This is the second. Example: Beagle<br />
::@set me=Inu/Dog2:<dog type><br />
:Dog 3: Their ears are those of a dog breed. Example: Wolfhound<br />
::@set me=Inu/Dog3:<dog type><br />
<br />
Their fur is Color Chooser compatible!<br />
[[Category:Released Infection]]<br />
[[Category:Canines]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=32222Monster Maker2013-07-20T05:36:07Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
: If you like someone else's work, be sure to make use of the ''commend'' command to show your appreciation. You can ''commend'' '''form''' where '''form''' is replaced with the name of the form, such as ''commend'' '''goblin girl'''. This is one way to help authors know their work's appreciated, and it also gives them a little boost of Mako to show how much their work was liked.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
==== Taur and Serpentine Forms ====<br />
::Different from the process you'd put together a standard, bipedal form with, this one takes a few exceptions and additional string parsing. Make sure to add that they are a Taur or Serpentine in the Notes so that a flag can be set to the Ass section and to the monster itself so that, if the ass is present, their legs won't show (we use a Legless property in the monster infection, so the entire lower torso description would go into the ass, not at all into the legs). In the Legs Description, instead of a normal description, you'd have something along the lines of this:<br />
<br />
Taur:<br />
[if taur is present in [player]]part of a lower torso.[else]<description as if they were bipedal>>[end if]<br />
<br />
Serpentine:<br />
[if serpentine is present in [player]]nonexistent.[else]<description as if they were bipedal>[end if]<br />
<br />
:: This way, if you don't have the ass of said form, you'd have some bipedal legs, but if you do, the legs will be invisible anyhow. In the Ass portion, you would put the entire description for the Taur or Serpentine form:<br />
<br />
Taur:<br />
Their lower body is that of a horse complete with four sturdy legs meant for long strides and a rounded, taut flanks with a whippety horse's tail.<br />
<br />
Serpentine:<br />
Their torso melts down into a long, sinuously serpentine tail that supports their upper body. Its length tapers down to a fine tip, and muscles ripple all along its length.<br />
<br />
:: This way, the form will display properly so long as the ass is in place. If the ass isn't that of the mutation, well, then there will be bipedal legs.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
::''Example:''<br />
::Arm Description: are lean and powerful. [if local stat Kitsune/Quad of [player] = 0][They] resemble those of a human ending in hands tipped with foxy claws.[else][They] resemble those of a fox with clawed paws at the end, ready to support their chest and head.[end if]<br />
::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 quadraped's. The 'Quad' naming was arbitrary, and the form is Kistune. It's a good way to organize variables.<br />
<br />
:'''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 two colors supported, Color and Color2.<br />
<br />
::''Color''<br />
:[if color is present in [player]][local stat color of [player]][else]<default>[end if]<br />
::''Color2''<br />
:[if color2 is present in [player]][local stat color2 of [player]][else]<default>[end if]<br />
::''Example:''<br />
::Skin Description: a sleek coat of [if color is present in [player]][local stat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 is present in [player]][local stat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.<br />
<br />
:'''Arm/Tail Divider Support''': The string parsing used in order to add in alternative descriptions for arm and tail divider usage.<br />
<br />
::''Arm Divider''<br />
:[if stat misc/arm divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Tail Divider''<br />
:[if stat misc/tail divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Example:''<br />
::Arm Description: powerfully built with [if stat misc/arm divider of [player] = 1]stacked shoulders leading to three pairs of arms.[else]sturdy shoulders leading down to their powerful arms.[end if] Each terminates in dexterous hands capped in wicked talons.<br />
<br />
<br />
:'''Mutation Check''': When you need to check for a certain bodypart carrying a certain mutation, here's how.<br />
<br />
:[if stat mutation/<body part> of [player] = <mutation>]<statement if true>[else]<statement if false>[end if]<br />
::''Example:''<br />
:Arm Description: long and lean[if stat mutation/skin of [player] = Feral Dragon] with a dense covering of scaled articulating down over their joints[end if].<br />
<br />
<br />
'''There is a pair of INVALUABLE commands created by Fauna. They are: @nviewparse and @formparse.<br />
:: 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!<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=32216Monster Maker2013-07-18T01:47:12Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
: If you like someone else's work, be sure to make use of the ''commend'' command to show your appreciation. You can ''commend'' '''form''' where '''form''' is replaced with the name of the form, such as ''commend'' '''goblin girl'''. This is one way to help authors know their work's appreciated, and it also gives them a little boost of Mako to show how much their work was liked.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
==== Taur and Serpentine Forms ====<br />
::Different from the process you'd put together a standard, bipedal form with, this one takes a few exceptions and additional string parsing. Make sure to add that they are a Taur or Serpentine in the Notes so that a flag can be set to the Ass section and to the monster itself so that, if the ass is present, their legs won't show (we use a Legless property in the monster infection, so the entire lower torso description would go into the ass, not at all into the legs). In the Legs Description, instead of a normal description, you'd have something along the lines of this:<br />
<br />
Taur:<br />
[if taur is present in [player]]part of a lower torso.[else]<description as if they were bipedal>>[end if]<br />
<br />
Serpentine:<br />
[if serpentine is present in [player]]nonexistent.[else]<description as if they were bipedal>[end if]<br />
<br />
:: This way, if you don't have the ass of said form, you'd have some bipedal legs, but if you do, the legs will be invisible anyhow. In the Ass portion, you would put the entire description for the Taur or Serpentine form:<br />
<br />
Taur:<br />
Their lower body is that of a horse complete with four sturdy legs meant for long strides and a rounded, taut flanks with a whippety horse's tail.<br />
<br />
Serpentine:<br />
Their torso melts down into a long, sinuously serpentine tail that supports their upper body. Its length tapers down to a fine tip, and muscles ripple all along its length.<br />
<br />
:: This way, the form will display properly so long as the ass is in place. If the ass isn't that of the mutation, well, then there will be bipedal legs.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
::''Example:''<br />
::Arm Description: are lean and powerful. [if local stat Kitsune/Quad of [player] = 0][They] resemble those of a human ending in hands tipped with foxy claws.[else][They] resemble those of a fox with clawed paws at the end, ready to support their chest and head.[end if]<br />
::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 quadraped's. The 'Quad' naming was arbitrary, and the form is Kistune. It's a good way to organize variables.<br />
<br />
:'''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 two colors supported, Color and Color2.<br />
<br />
::''Color''<br />
:[if color is present in [player]][local stat color of [player]][else]<default>[end if]<br />
::''Color2''<br />
:[if color2 is present in [player]][local stat color2 of [player]][else]<default>[end if]<br />
::''Example:''<br />
::Skin Description: a sleek coat of [if color is present in [player]][local stat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 is present in [player]][local stat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.<br />
<br />
:'''Arm/Tail Divider Support''': The string parsing used in order to add in alternative descriptions for arm and tail divider usage.<br />
<br />
::''Arm Divider''<br />
:[if stat misc/arm divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Tail Divider''<br />
:[if stat misc/tail divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Example:''<br />
::Arm Description: powerfully built with [if stat misc/arm divider of [player] = 1]stacked shoulders leading to three pairs of arms.[else]sturdy shoulders leading down to their powerful arms.[end if] Each terminates in dexterous hands capped in wicked talons.<br />
<br />
<br />
:'''Mutation Check''': When you need to check for a certain bodypart carrying a certain mutation, here's how.<br />
<br />
:[if stat mutation/<body part> of [player] = <mutation>]<statement if true>[else]<statement if false>[end if]<br />
::''Example:''<br />
:Arm Description: long and lean[if stat mutation/skin of [player] = Feral Dragon] with a dense covering of scaled articulating down over their joints[end if].<br />
<br />
<br />
<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=32185Monster Maker2013-07-15T15:41:20Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
==== Taur and Serpentine Forms ====<br />
::Different from the process you'd put together a standard, bipedal form with, this one takes a few exceptions and additional string parsing. Make sure to add that they are a Taur or Serpentine in the Notes so that a flag can be set to the Ass section and to the monster itself so that, if the ass is present, their legs won't show (we use a Legless property in the monster infection, so the entire lower torso description would go into the ass, not at all into the legs). In the Legs Description, instead of a normal description, you'd have something along the lines of this:<br />
<br />
Taur:<br />
[if taur is present in [player]]part of a lower torso.[else]<description as if they were bipedal>>[end if]<br />
<br />
Serpentine:<br />
[if serpentine is present in [player]]nonexistent.[else]<description as if they were bipedal>[end if]<br />
<br />
:: This way, if you don't have the ass of said form, you'd have some bipedal legs, but if you do, the legs will be invisible anyhow. In the Ass portion, you would put the entire description for the Taur or Serpentine form:<br />
<br />
Taur:<br />
Their lower body is that of a horse complete with four sturdy legs meant for long strides and a rounded, taut flanks with a whippety horse's tail.<br />
<br />
Serpentine:<br />
Their torso melts down into a long, sinuously serpentine tail that supports their upper body. Its length tapers down to a fine tip, and muscles ripple all along its length.<br />
<br />
:: This way, the form will display properly so long as the ass is in place. If the ass isn't that of the mutation, well, then there will be bipedal legs.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
::''Example:''<br />
::Arm Description: are lean and powerful. [if local stat Kitsune/Quad of [player] = 0][They] resemble those of a human ending in hands tipped with foxy claws.[else][They] resemble those of a fox with clawed paws at the end, ready to support their chest and head.[end if]<br />
::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 quadraped's. The 'Quad' naming was arbitrary, and the form is Kistune. It's a good way to organize variables.<br />
<br />
:'''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 two colors supported, Color and Color2.<br />
<br />
::''Color''<br />
:[if color is present in [player]][local stat color of [player]][else]<default>[end if]<br />
::''Color2''<br />
:[if color2 is present in [player]][local stat color2 of [player]][else]<default>[end if]<br />
::''Example:''<br />
::Skin Description: a sleek coat of [if color is present in [player]][local stat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 is present in [player]][local stat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.<br />
<br />
:'''Arm/Tail Divider Support''': The string parsing used in order to add in alternative descriptions for arm and tail divider usage.<br />
<br />
::''Arm Divider''<br />
:[if stat misc/arm divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Tail Divider''<br />
:[if stat misc/tail divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Example:''<br />
::Arm Description: powerfully built with [if stat misc/arm divider of [player] = 1]stacked shoulders leading to three pairs of arms.[else]sturdy shoulders leading down to their powerful arms.[end if] Each terminates in dexterous hands capped in wicked talons.<br />
<br />
<br />
:'''Mutation Check''': When you need to check for a certain bodypart carrying a certain mutation, here's how.<br />
<br />
:[if stat mutation/<body part> of [player] = <mutation>]<statement if true>[else]<statement if false>[end if]<br />
::''Example:''<br />
:Arm Description: long and lean[if stat mutation/skin of [player] = Feral Dragon] with a dense covering of scaled articulating down over their joints[end if].<br />
<br />
<br />
<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=32184Monster Maker2013-07-15T15:24:57Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
==== Taur and Serpentine Forms ====<br />
::Different from the process you'd put together a standard, bipedal form with, this one takes a few exceptions and additional string parsing. Make sure to add that they are a Taur or Serpentine in the Notes so that a flag can be set to the Ass section and to the monster itself so that, if the ass is present, their legs won't show (we use a Legless property in the monster infection, so the entire lower torso description would go into the ass, not at all into the legs). In the Legs Description, instead of a normal description, you'd have something along the lines of this:<br />
<br />
Taur:<br />
[if taur is present in [player]]part of a lower torso.[else]<description as if they were bipedal>>[end if]<br />
<br />
Serpentine:<br />
[if serpentine is present in [player]]nonexistent.[else]<description as if they were bipedal>[end if]<br />
<br />
:: This way, if you don't have the ass of said form, you'd have some bipedal legs, but if you do, the legs will be invisible anyhow. In the Ass portion, you would put the entire description for the Taur or Serpentine form:<br />
<br />
Taur:<br />
Their lower body is that of a horse complete with four sturdy legs meant for long strides and a rounded, taut flanks with a whippety horse's tail.<br />
<br />
Serpentine:<br />
Their torso melts down into a long, sinuously serpentine tail that supports their upper body. Its length tapers down to a fine tip, and muscles ripple all along its length.<br />
<br />
:: This way, the form will display properly so long as the ass is in place. If the ass isn't that of the mutation, well, then there will be bipedal legs.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
::''Example:''<br />
::Arm Description: are lean and powerful. [if local stat Kitsune/Quad of [player] = 0][They] resemble those of a human ending in hands tipped with foxy claws.[else][They] resemble those of a fox with clawed paws at the end, ready to support their chest and head.[end if]<br />
::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 quadraped's. The 'Quad' naming was arbitrary, and the form is Kistune. It's a good way to organize variables.<br />
<br />
:'''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 two colors supported, Color and Color2.<br />
<br />
::''Color''<br />
:[if color is present in [player]][local stat color of [player]][else]<default>[end if]<br />
::''Color2''<br />
:[if color2 is present in [player]][local stat color2 of [player]][else]<default>[end if]<br />
::''Example:''<br />
::Skin Description: a sleek coat of [if color is present in [player]][local stat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 is present in [player]][local stat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.<br />
<br />
:'''Arm/Tail Divider Support''': The string parsing used in order to add in alternative descriptions for arm and tail divider usage.<br />
<br />
::''Arm Divider''<br />
:[if stat misc/arm divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Tail Divider''<br />
:[if stat misc/tail divider of [player] = 1]<Arm Divider active description>[else]<Normal Description>[end if]<br />
::''Example:''<br />
::Arm Description: powerfully built with [if stat misc/arm divider of [player] = 1]stacked shoulders leading to three pairs of arms.[else]sturdy shoulders leading down to their powerful arms.[end if] Each terminates in dexterous hands capped in wicked talons.<br />
<br />
:'''Mutation Check''': When you need to check for a certain bodypart carrying a certain mutation, here's how.<br />
:[if stat mutation/<body part> of [player] = <mutation>]<statement if true>[else]<statement if false>[end if]<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=32182Monster Maker2013-07-15T14:31:49Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
==== Taur and Serpentine Forms ====<br />
::Different from the process you'd put together a standard, bipedal form with, this one takes a few exceptions and additional string parsing. Make sure to add that they are a Taur or Serpentine in the Notes so that a flag can be set to the Ass section and to the monster itself so that, if the ass is present, their legs won't show (we use a Legless property in the monster infection, so the entire lower torso description would go into the ass, not at all into the legs). In the Legs Description, instead of a normal description, you'd have something along the lines of this:<br />
<br />
Taur:<br />
[if taur is present in [player]]part of a lower torso.[else]<description as if they were bipedal>>[end if]<br />
<br />
Serpentine:<br />
[if serpentine is present in [player]]nonexistent.[else]<description as if they were bipedal>[end if]<br />
<br />
:: This way, if you don't have the ass of said form, you'd have some bipedal legs, but if you do, the legs will be invisible anyhow. In the Ass portion, you would put the entire description for the Taur or Serpentine form:<br />
<br />
Taur:<br />
Their lower body is that of a horse complete with four sturdy legs meant for long strides and a rounded, taut flanks with a whippety horse's tail.<br />
<br />
Serpentine:<br />
Their torso melts down into a long, sinuously serpentine tail that supports their upper body. Its length tapers down to a fine tip, and muscles ripple all along its length.<br />
<br />
:: This way, the form will display properly so long as the ass is in place. If the ass isn't that of the mutation, well, then there will be bipedal legs.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
::''Example:''<br />
::Arm Description: are lean and powerful. [if local stat Kitsune/Quad of [player] = 0][They] resemble those of a human ending in hands tipped with foxy claws.[else][They] resemble those of a fox with clawed paws at the end, ready to support their chest and head.[end if]<br />
::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 quadraped's. The 'Quad' naming was arbitrary, and the form is Kistune. It's a good way to organize variables.<br />
<br />
:'''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 two colors supported, Color and Color2.<br />
<br />
::''Color''<br />
:[if color is present in [player]][local stat color of [player]][else]<default>[end if]<br />
::''Color2''<br />
:[if color2 is present in [player]][local stat color2 of [player]][else]<default>[end if]<br />
::''Example:''<br />
::Skin Description: a sleek coat of [if color is present in [player]][local stat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 is present in [player]][local stat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=32181Monster Maker2013-07-15T14:30:00Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
==== Taur and Serpentine Forms ====<br />
::Different from the process you'd put together a standard, bipedal form with, this one takes a few exceptions and additional string parsing. Make sure to add that they are a Taur or Serpentine in the Notes so that a flag can be set to the Ass section and to the monster itself so that, if the ass is present, their legs won't show (we use a Legless property in the monster infection, so the entire lower torso description would go into the ass, not at all into the legs). In the Legs Description, instead of a normal description, you'd have something along the lines of this:<br />
<br />
Taur:<br />
[if taur is present in [player]]part of a lower torso.[else]<description as if they were bipedal>>[end if]<br />
<br />
Serpentine:<br />
[if serpentine is present in [player]]nonexistent.[else]<description as if they were bipedal>[end if]<br />
<br />
:: This way, if you don't have the ass of said form, you'd have some bipedal legs, but if you do, the legs will be invisible anyhow. In the Ass portion, you would put the entire description for the Taur or Serpentine form:<br />
<br />
Taur:<br />
Their lower body is that of a horse complete with four sturdy legs meant for long strides and a rounded, taut flanks with a whippety horse's tail.<br />
<br />
Serpentine:<br />
Their torso melts down into a long, sinuously serpentine tail that supports their upper body. Its length tapers down to a fine tip, and muscles ripple all along its length.<br />
<br />
:: This way, the form will display properly so long as the ass is in place. If the ass isn't that of the mutation, well, then there will be bipedal legs.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
::''Example:''<br />
::Arm Description: are lean and powerful. [if local stat Kitsune/Quad of [player] = 0][They] resemble those of a human ending in hands tipped with foxy claws.[else][They] resemble those of a fox with clawed paws at the end, ready to support their chest and head.[end if]<br />
::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 quadraped's. The 'Quad' naming was arbitrary, and the form is Kistune. It's a good way to organize variables.<br />
<br />
::'''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 two colors supported, Color and Color2.<br />
<br />
:''Color''<br />
:[if color is present in [player]][local stat color of [player]][else]<default>[end if]<br />
:''Color2''<br />
:[if color2 is present in [player]][local stat color2 of [player]][else]<default>[end if]<br />
::''Example:''<br />
::Skin Description: a sleek coat of [if color is present in [player]][local stat color of [player]][else]tawny orange[end if] fur all over their body with [if color2 is present in [player]][local stat color2 of [player]][else]black[end if] stripes banding in a tabby pattern from nose to end.<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30643Monster Maker2013-05-05T06:02:19Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''<br />
<br />
[[Category:Guides]]</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30212Monster Maker2013-04-19T22:58:23Z<p>Glitch: Adding comments about [they] and like parsing not being necessary to maintain normal writing in Transformation messages.</p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they]. The exception to this is in Transformation messages. They are not parsed in Transformation messages and therefore do not need the [] surrounding them to remain normal.<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30194Monster Maker2013-04-18T23:57:11Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof. Make sure ''not'' to click on ''Mark Entry as ready to approve'' until '''after''' all the requisite fields and information has been applied.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30193Monster Maker2013-04-18T23:51:39Z<p>Glitch: Main finishing, but still able to add more on player requests.</p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
<br />
''If you would like to see templates for other nifty string parsing tricks you can add to your monsters, feel free to mail Glitch or post a +request under 'Building' to get it added here!''</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30192Monster Maker2013-04-18T23:47:12Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
=== Victory and Defeat Messages ===<br />
::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:<br />
::*Monster Defeats Player, 1st Person Defeat<br />
::*Player Defeats Monster, 1st Person Victory<br />
::*Player Defeats Monster, 3rd Person Victory<br />
::*Misc. Notes<br />
<br />
::'''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.<br />
<br />
::'''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]''<br />
<br />
::'''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.<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
<br />
(In Progress)</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30183Monster Maker2013-04-18T07:16:09Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
=== Templates ===<br />
::'''Cock Transformation''': Most often-needed string parsing.<br />
<br />
:You can feel your groin start to shift.[if [player] is male] <cock transformation message>[end if][if [player] is female]<cunt transformation message>[end if] Now, your groin resembles that of a <monster name>.<br />
<br />
::'''Storing Randomized Information''': If you want to make each person a little unique for this monster, it's sometimes fun to add in a variable, often color or texture, that locks in as something random from a list for that person. For example, with the Dusk Dragon, when someone transforms into it for the first time, a random color from a set list is picked and stored in a stat. If the stat already exists, it doesn't pick again, and it's locked in. Here're the formats for that.<br />
<br />
:''In Transformation message'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''Breakdown of action'': <br />
::You start with an if statement that checks to see if the stat exists, If it has a value of 0, it doesn't exist. So, if it's empty, the set function is triggered. It'll set that stat to one of the variables in your list. You need [one of] at the beginning and separate each variable with [or] and end it with [at random]. Then, the entire if statement ends with an [end if].<br />
:''Example'':<br />
:[if stat Goblin/EyeColor of [player] = 0][set the Goblin/EyeColor to [one of]green[or]brown[or]black[or]white[or]yellow[at random][end if]<br />
:''In Description message'':<br />
:[stat <critter name>/<variable name> of [player]]<br />
:''Example'':<br />
:The goblin has [stat Goblin/EyeColor of [player]] eyes.<br />
<br />
:'''Player-set variables''': These can be fun for letting players choose what they want in a spot, though be sure to have a default.<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <monster name>/<variable name> of [player]][else]<default>[end if]<br />
:''Breakdown'':<br />
::The if statement checks if the variable exists. If it != or doesn't equal 0, it means there's a value set there. If there is a value, the local stat will be displayed. If it isn't set, then the false message, the default for this, will show. Close it all off with an end if.<br />
:''Example'':<br />
:[if local stat Goblin/EyeColor of [player] != 0][local stat Goblin/EyeColor of [player]][else]green[end if]<br />
<br />
:'''Player-set variables with random-set, locked-in variable for default''': Combining the two above templates can be done in this fashion.<br />
:''In Transformation'':<br />
:[if stat <critter name>/<variable name> of [player] = 0][set the <critter name>/<variable name> of [player] to [one of]<variable 1>[or]<variable 2>[or]<variable 3>...[or]<variable n>[at random][end if]<br />
:''In Description'':<br />
:[if local stat <critter name>/<variable name> of [player] != 0][local stat <critter name>/<variable name> of [player]][else][stat <critter name>/<variable name> of [player]][end if]<br />
:''Note'': Note that a local stat and a stat are in two different areas, so they may have the exact same name but be two different variables. Local stats are set directly on the player whereas Stats are set in staff-access-only parts of the player.<br />
<br />
(In Progress)</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30182Monster Maker2013-04-18T06:50:33Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
<br />
== String Parsing ==<br />
:The bane and fear of many a monster making exercise: String Parsing. The greatest issue that many have is they do not understand the syntax and format of string parsing. Well, here are some helpful tips, hints, and templates.<br />
<br />
=== Tips and Hints ===<br />
::* When referencing 'male' and 'female' in if statements, it refers specifically to the existence of a cock and cunt. For example: [if [player] is male] checks to see if the [player] has a cock stat that's not 0. This means it will trigger true for both males and hermaphrodites.<br />
::* When making an [if] statement, remember to end it with an [end if] statement. The syntax is [if <statement to be checked if true or false>]<what displays if true>[end if]. If you want something to display if false, you use this syntax: [if <statement to be checked for true or false>]<what displays if true>[else]<what displays if false>[end if].<br />
::* If you decide to nest if statements (placing one inside of another), make sure that you have an [end if] for each if statement.<br />
::* [player] is used in the descriptions and transformations as a reference whereas [victor] and [loser] are used in the Defeat/Victory messages.<br />
::* String parsing can be used for many fun additives, like changeable sections or randomization. Check out the templates for some interesting ones.<br />
::* Local stats refer to stats that you the player can change with either @set me=<stat>:<value> or &<stat> me=<value>.<br />
<br />
(In Progress)</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30181Monster Maker2013-04-18T06:40:34Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''': Just like the Skin Description, what you place here will be shown to the player when this part is infected with this monster.<br />
<br />
::'''Cock and Cunt Descriptions''': First off, Cunt description is ''not'' optional. We need it. With these descriptions, they're sandwiched between and adjective and a word for their genital type. For example, your cock field will often be sandwiched between "large" and "shaft" or something similar. So, when inputting into the field, keep this in mind. If you wish it to display: They have a large, juicy cock with barbs all along its lengthy shaft.", you'd enter: ''juicy cock with barbs all along its'' in the field. Similarly for cunt. Best to look at the description preview to check and see how well it read.<br />
<br />
::'''Cock Transformation''': This is the one that throws a lot of people. It almost always requires string parsing unless you're extremely vague. Vague would be like this: ''Your groin shifts and shudders, changing until it resembles something reptilian.'' For something in-depth and specific, look later on this page for our string parsing templates and explanations.<br />
<br />
<br />
<br />
(In Progress)</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30180Monster Maker2013-04-18T06:31:25Z<p>Glitch: </p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
::'''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''.<br />
<br />
::'''Ass/Tail Description''': Like the other descriptions except it has nothing before it. What you type is what's placed in this spot. If you put ''A long, whip-like tail switches to and fro behind them.'', it will display "A long, whip-like tail switches to and fro behind them."<br />
<br />
::'''Head, Torso, Arms, Legs, and Ass/Tail Transformation''':<br />
<br />
(In Progress)</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30179Monster Maker2013-04-18T06:15:40Z<p>Glitch: A run-down on how to use the monster maker to produce successful monsters.</p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
::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 these fields, and, most importantly, using a document editor like Word that has grammar and spell-checking is ''highly suggested''.<br />
<br />
::Here is the list of fields:<br />
::* Long Skin Description<br />
::* Short Skin Description<br />
::* Skin Transformation<br />
::* Head Description<br />
::* Head Transformation<br />
::* Torso Description<br />
::* Torso Transformation<br />
::* Arms Description<br />
::* Arms Transformation<br />
::* Legs Description<br />
::* Legs Transformation<br />
::* Cock Description<br />
::* Cunt Description<br />
::* Cock Transformation<br />
::* Ass/Tail Description<br />
::* Ass/Tail Transformation<br />
<br />
::'''Note''': ''They'', ''they'', ''Their'', ''their'', ''Them'', and ''them'' will be replaced with the proper pronouns automatically! Do not use he, she, shi, or the like. If you want ''they'', ''their'', or ''them'' to appear normally, you must enclose them in square brackets like this: [they].<br />
<br />
::'''Long Skin Description''': This is the description that will show in the player's description when they have this monster's skin infection. It will always begin with "Their body is covered in ", and need not be written. For example, if you wanted them to have skin that's made from chunks of granite, you'd fill the field with: ''chunks of granite''. It would read: "Their body is covered in chucnks of granite."<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
<br />
<br />
(In Progress)</div>Glitchhttps://wiki.flexiblesurvival.com/index.php?title=Monster_Maker&diff=30178Monster Maker2013-04-18T05:50:41Z<p>Glitch: Created page with ": The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for..."</p>
<hr />
<div>: The Monster Maker is a useful tool to express your ideas for new and interesting monsters to be applied to the game. It is for original monsters, and it is '''not''' for copying the works of others, whether it be your fellow players or copyrighted pieces from other media.<br />
<br />
== Starting a Monster ==<br />
: There are several steps to making a monster. The first is to get it started. When you select Monster Maker from the Contributions tab of your on-line interface, you will see several drop down menus and a prompt that reads: '''New Monster Name''' with a button after it labelled '''Create'''.<br />
<br />
: It's very important that you pick an appropriate name for your monster because once you set it, it's difficult to change. Some key things to remember are:<br />
<br />
:* Don't use copyrighted names.<br />
:* Capitalize the name properly and use the correct spelling, if it exists.<br />
:* It's best ''not'' to have gender or sex-specific words like 'Girl', 'Man', or 'Herm' or the like.<br />
:* Keep it concise, one or two words.<br />
:* Make sure something like it doesn't already exist.<br />
<br />
: Having something original and new is always best. Once you've entered the name, click on '''Create''', and it will be created and ready for you to start filling out. Once you enter information into any of the fields, the monster you're working on is saved and able to be referred back to at any time. If you leave the Monster Maker without inputting any information into any of the monster's fields, then it will go poof.<br />
<br />
== Inputting Information for Your Monster ==<br />
: There are three main sections. They are:<br />
<br />
:* Descriptions and Transformations<br />
:* Bodypart Sizes<br />
:* Victory and Defeat Messages<br />
<br />
: You can start in any section, but it's easiest to start with the Bodypart Sizes.<br />
<br />
=== Bodypart Sizes ===<br />
:: The Bodypart Sizes section is divided into several fields. These are as follows:<br />
::* Size<br />
::* 1st Person Say<br />
::* 3rd Person Say<br />
::* Breasts<br />
::* Breast Size<br />
::* Cocks<br />
::* Cock Length<br />
::* Ball Size<br />
::* Extra Balls<br />
::* Cunts<br />
::* Cunt Length<br />
<br />
::'''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).<br />
<br />
::'''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!"<br />
<br />
::'''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!"<br />
<br />
::'''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.<br />
<br />
::'''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.<br />
<br />
=== Descriptions and Transformations ===<br />
<br />
(In Progress)</div>Glitch