Flexible Survival - User contributions [en]

User:Songbird

2017-08-15T18:16:46Z

Strongbird:

Staffer known as Song in-game.

Dedicated writer. Versed in stringparsing and talkscript.

Alternate wiki account is Strongbird.

User:Strongbird

2017-08-15T18:16:42Z

Strongbird: Created page with "Alternate wiki account of Songbird, known as Song in-game. Largely not used anymore."

Alternate wiki account of Songbird, known as Song in-game.

Largely not used anymore.

Abomination

2017-08-15T06:03:37Z

Strongbird:

You'd prefer to meet this in a dark alley. At least then you wouldn't see it.
{{Monster
|arms=[[Wild Swing]]
|tail=[[Gigantic Body Slam]]
|head=[[Frenzy]]
|legs=[[Foot Stomp]]
|skin=[[Thick Hide]]
|torso=[[Juggernaut]], [[Muscle Mass]]
|groin=
}}

[[Category:Monsters]] [[Category:Supports Kemonomimi]]

Abomination

2017-08-15T06:03:23Z

Strongbird:

You'd prefer to meet this in a dark alley. At least then you wouldn't see it.
{{Monster
|arms=[[Wild Swing]]
|ass=[[Gigantic Body Slam]]
|head=[[Frenzy]]
|legs=[[Foot Stomp]]
|skin=[[Thick Hide]]
|torso=[[Juggernaut]], [[Muscle Mass]]
|groin=
}}

[[Category:Monsters]] [[Category:Supports Kemonomimi]]

Whimsical Twinkubus

2017-08-15T06:00:38Z

Strongbird: Created page with "{{Monster |head=Transfixing Gaze |torso=Vitality |arms=Drain Vitae |legs=Skitter |tail=Crushing Coils, Erotic Dance |skin= |groin=Biting Wit }} Kn..."

{{Monster
|head=[[Transfixing Gaze]]
|torso=[[Vitality]]
|arms=[[Drain Vitae]]
|legs=[[Skitter]]
|tail=[[Crushing Coils]], [[Erotic Dance]]
|skin=
|groin=[[Biting Wit]]
}}

Known to cherish teasing foreplay and rough anal reaming alike.

==Gender==
Male

[[Category:Supports Arm Divider]][[Category:Supports Tail Divider]]

NPCs (Multiplayer)

2017-08-15T05:50:53Z

Strongbird:

__NOTOC__
Note from Song: This page is a WIP. Please be patient while it is organized and expanded upon.

There are a wide array of non-player characters (NPCs) in the game for the player to interact with. Some of these are friendly, others are merely ambivalent about the player. Certain NPCs can provide the player with quests, often with a reward to be earned.

'''Alphabetical Lists of NPCs:''' 
[[:Category:NPC (Multiplayer)|All NPCs]] 
[[:Category:NPC: Male (MP)|Male]] 
[[:Category:NPC: Female (MP)|Female]] 
[[:Category:NPC: Herm (MP)|Hermaphrodite]]

For Single Player NPCs, see [[NPCs_(Single_Player)|here]]

==Ember Sanctum==
===[[Ember Matriarch (MP)|Ember Matriarch]]===
*'''Species:''' [[Ember Matriarch]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==Graveyard==
===[[Caretaker]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==Gryphon Nest==
===[[Obsidian]]===
*'''Species:''' [[Shadow Dragon]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Violet]]===
*'''Species:''' [[Blue Gryphon]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==Gun Shop Shelter==
===[[Alice]]===
*'''Species:''' [[Gun Bunny]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==Hotel Oblivion==
===[[Bound Egyptian Mau]]===
*'''Species:''' [[Egyptian Mau]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Charlie]]===
*'''Species:''' German Shepherd (actual animal)
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Ellie]]===
*'''Species:''' [[Latex Fox]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Presenting Mephit]]===
*'''Species:''' Skunk
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==Husky Den==
===[[Chris (MP)|Chris]]===
*'''Species:''' [[Alpha Husky (MP)]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Sarah_(MP)|Sarah]]===
*'''Species:''' [[Female Husky]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Saul]]===
*'''Species:''' [[Alpha Husky (MP)]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Twinky]]===
*'''Species:''' [[Quilled Tousky]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==Rev'n Rave Techno Safari==
===[[Mortimitri]]===
*'''Species:''' [[Slut Rat]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==RSX Solutions==
===[[Alton]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Agent Jackson]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Colonel Arnold]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Doctor Browning]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Major Jack]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Maxwell Power]] (Danger Technician)===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Mr Simon]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===Old Soldier===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Paul Metoxis]] (Pheromone Technician)===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Penelope]]===
*'''Species:''' [[Valkyrie]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Jennifer Trilby]] (Requisitions Clerk)===
*'''Species:''' [[Human]] (with cat ears and tail)
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Research Lead Renley]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Sally (MP)|Sally]]===
*'''Species:''' [[Valkyrie]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Venice]]===
*'''Species:''' [[Goo Girl]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==Secluded Home==
===[[Obsidian]]===
*'''Species:''' [[Shadow Dragon]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==Slut Rat Den==
===[[Axel]]===
*'''Species:''' [[Slut Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Herm]]

===[[Dmitri]]===
*'''Species:''' [[Slut Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Herm]]

==The Devil's Bar==
===[[Casey]]===
*'''Species:''' [[Whimsical Twinkubus]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Tess]]===
*'''Species:''' [[Busty Succubus]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==The Mall==
===[[Lisa (MP)|Lisa]]===
*'''Species:''' [[Mouse Taur]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Missy]]===
*'''Species:''' [[Mall Rat]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Rod (MP)|Rod]]===
*'''Species:''' [[Mall Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Smiley]]===
*'''Species:''' [[Mall Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==The Trick or Treat Motel==
===Animate Pumpkin Patch===
*'''Species:''' Some plantlike amalgamation
*'''Gender:''' Bona Fide Tentaclebeast

===Kurt===
*'''Species:''' [[Wolf Beast]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===Sobek===
*'''Species:''' Crocodile
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Theodore the Corgi]]===
*'''Species:''' [[Welsh Corgi]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===Vampire Bat Twins===
*'''Species:''' [[Vampire Bat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]] and [[:Category:NPC: Female (MP)|Female]]

===Witch===
*'''Species:''' Cat
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==The Zoo==
===[[Kangaroo God]]===
*'''Species:''' [[Kangaroo]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==Zephyr Inc==
===[[Agent Jonathan]]===
*'''Species:''' [[Blue Gryphon]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

===[[Alex (MP)|Alex]]===
*'''Species:''' [[Zebra]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

===[[Ron Danger]] (Danger Technician)===
*'''Species:''' [[Human]] (with a [[House Cat]] head)
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Dr Joan]]===
*'''Species:''' [[Shy Gecko]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===Eureka Pilot===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Ian the Shark]]===
*'''Species:''' [[Bull Shark]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

===[[Louis Ledoyen]]===
*'''Species:''' [[Salamander Femme]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[James Jorgen]]===
*'''Species:''' [[Plump Tigress]]
*'''Gender:''' Shemale

===[[Mike the Chopper Pilot]]===
*'''Species:''' [[Blue Gryphon]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Miura Mercedes]]===
*'''Species:''' [[Shadow Vixen]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Mona Nasawri]] (Pheromone Technician)===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Noel Winters]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Jeffrey Lebowski]] (Requisitions Clerk)===
*'''Species:''' [[Pampered Poodle]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Robert]]===
*'''Species:''' [[Zebra]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Sandra]]===
*'''Species:''' [[Human]] (with Kemonomimi [[Bunny Girl]] features)
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Scarlet Sebb]]===
*'''Species:''' [[Female Widow Convert]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===Tactics Soldier===
*'''Species:''' [[Skunk Beast]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Teacher Jenny]]===
*'''Species:''' [[Skunk Girl]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===Workshop Technician===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

[[Category:Multiplayer]]

Dmitri

2017-08-15T05:29:31Z

Strongbird: Created page with "{{NPC(MP) |species=Slut Rat |gender=Herm |location=Slut Rat Den |sex=No |infectious=No }} ==Appearance== A voluptuous Slut Rat with a thic..."

{{NPC(MP)
|species=[[Slut Rat]]
|gender=[[:Category:NPC: Herm_(MP)|Herm]]
|location=[[Slut Rat Den]]
|sex=No
|infectious=No
}}
==Appearance==
A voluptuous Slut Rat with a thick Russian accent, Dmitri Novikov is an intelligent and articulate woman whose cunning wit is cleverly belied by her punk-themed appearance. Past experience in arms trafficking has lent her a tongue as silver as the studs in her ears, and with a voice that cuts through the crowd, she's quickly risen to a position of power among the den.

[[Category:NPC: Herm_(MP)]]

Axel

2017-08-15T05:29:29Z

Strongbird: Created page with "{{NPC(MP) |species=Slut Rat |gender=Herm |location=Slut Rat Den |sex=No |infectious=No }} ==Appearance== Axel is a tall, busty herm with a..."

{{NPC(MP)
|species=[[Slut Rat]]
|gender=[[:Category:NPC: Herm_(MP)|Herm]]
|location=[[Slut Rat Den]]
|sex=No
|infectious=No
}}
==Appearance==
Axel is a tall, busty herm with a commanding presence and a sharp tongue. The rat boasts a well-kempt purple mohawk and a column of fat silver studs down each ear. She's dressed in a navy blue blazer, sleek black jeans, and thick stomping boots that serve as more of a fashion statement than protection. Overall, her clothes are in good repair, with few cuts or signs of wear.

When not playing darts or cards, the curvy rat can be seen sitting at the main table with her kin to talk about their past successes and plans for the future.

[[Category:NPC: Herm_(MP)]]

Ember Sanctum

2017-08-15T05:26:55Z

Strongbird:

The Ember Sanctum can be found under the Fairhaven Mall and is the home of the [[Ember Matriarch (MP)|Ember Matriarch]].

Room description:
The room is massive and spherical in construction. For whatever reason, the walls here have been warped and expanded far beyond the normal limitations of a sewer pipe, breaking out into an unrestrained wilderness of marsh, beasts and simple prosperity. At the top of the dome are sewer grates that help filter in some much-needed light from surface level.

The Ember mutants make their home here. Both of the common strains, Warrior and Breeder, coexist peacefully with each other, taking part in various games and activities to keep themselves occupied. Their leader is curled up in a large nest near the center, humming peacefully as sie incubates the next in kin. Sie is flanked by a circle of tough-looking guards, who wear little more than leather strips over their body to protect them during combat. It appears as though this tribe has plenty of natural means to secure their survival, for their sharp, fierce claws and constant physical activity keeps them at the top of the food chain.

Ember Sanctum

2017-08-15T05:26:27Z

Strongbird:

The Ember Sanctum can be found under the Fairhaven Mall and is the home to the [[Ember Matriarch (MP)|Ember Matriarch]].

Room description:
The room is massive and spherical in construction. For whatever reason, the walls here have been warped and expanded far beyond the normal limitations of a sewer pipe, breaking out into an unrestrained wilderness of marsh, beasts and simple prosperity. At the top of the dome are sewer grates that help filter in some much-needed light from surface level.

The Ember mutants make their home here. Both of the common strains, Warrior and Breeder, coexist peacefully with each other, taking part in various games and activities to keep themselves occupied. Their leader is curled up in a large nest near the center, humming peacefully as sie incubates the next in kin. Sie is flanked by a circle of tough-looking guards, who wear little more than leather strips over their body to protect them during combat. It appears as though this tribe has plenty of natural means to secure their survival, for their sharp, fierce claws and constant physical activity keeps them at the top of the food chain.

Gryphon Nest

2017-08-15T05:25:28Z

Strongbird:

This is the home of Violet the hermaphrodite Blue Gryphon and can be accessed by speaking with Obsidian in the Secluded Home.

Room description:
A comfortable 'nest' of sorts. The nest consists of a layer of carpets on the otherwise barebone concrete floor, all interior surfaces scrubbed clean and sanded for maximum smoothness. You see a single gryphon here, Violet, and your lover, Obsidian. The two are currently discussing what favors Obsidian owes in exchange for her beloved gryphon milk.

Alice

2017-08-15T05:24:33Z

Strongbird: Created page with "{{NPC(MP) |species=Gun Bunny |gender=Female |location=Gun Shop Shelter |sex=No |infectious=No }} ==Appearance== Leaning back in her seat..."

{{NPC(MP)
|species=[[Gun Bunny]]
|gender=[[:Category:NPC: Female (MP)|Female]]
|location=[[Gun Shop Shelter]]
|sex=No
|infectious=No
}}
==Appearance==
Leaning back in her seat, this peculiar lapine seems all too happy to show smug defiance to a world gone wild. She's dressed in a snug white tank top and a too-small denim jean jacket, the scuffed material scarcely fitting over her shoulders. Healthy hips strain the seams of a tattered mini-skirt, and dirty striped stockings hug her muscular legs before they whither to nothing near her large, four-toed feet. Above, overly large aviator goggles are strapped tightly to her forehead, partially obscuring her ears.

The ferals endemic to this area seem to avoid her whenever she leaves the shelter, and with good reason; displayed prominently on her chest is a pair of criss-crossing bandoleers, replete with enough ammunition to lay waste to a small town. Strapped to her right hip is a compact submachine gun, a magazine prepared and mode set to auto. From where you stand, you also spot the thick wooden stock of a hunting rifle peeking out from behind her shoulder, likely used for stopping power should she cross paths with a more potent opponent.

[[Category:NPC: Female (MP)]]

NPCs (Multiplayer)

2017-08-15T05:22:33Z

Strongbird:

__NOTOC__
Note from Songbird: This page is a WIP. Please be patient while it is organized and expanded upon.

There are a wide array of non-player characters (NPCs) in the game for the player to interact with. Some of these are friendly, others are merely ambivalent about the player. Certain NPCs can provide the player with quests, often with a reward to be earned.

'''Alphabetical Lists of NPCs:''' 
[[:Category:NPC (Multiplayer)|All NPCs]] 
[[:Category:NPC: Male (MP)|Male]] 
[[:Category:NPC: Female (MP)|Female]] 
[[:Category:NPC: Herm (MP)|Hermaphrodite]]

For Single Player NPCs, see [[NPCs_(Single_Player)|here]]

==Ember Sanctum==
===[[Ember Matriarch (MP)|Ember Matriarch]]===
*'''Species:''' [[Ember Matriarch]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==Graveyard==
===[[Caretaker]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==Gryphon Nest==
===[[Obsidian]]===
*'''Species:''' [[Shadow Dragon]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Violet]]===
*'''Species:''' [[Blue Gryphon]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==Gun Shop Shelter==
===[[Alice]]===
*'''Species:''' [[Gun Bunny]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==Hotel Oblivion==
===[[Bound Egyptian Mau]]===
*'''Species:''' [[Egyptian Mau]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Charlie]]===
*'''Species:''' German Shepherd (actual animal)
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Ellie]]===
*'''Species:''' [[Latex Fox]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Presenting Mephit]]===
*'''Species:''' Skunk
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==Husky Den==
===[[Chris (MP)|Chris]]===
*'''Species:''' [[Alpha Husky (MP)]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Sarah_(MP)|Sarah]]===
*'''Species:''' [[Female Husky]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Saul]]===
*'''Species:''' [[Alpha Husky (MP)]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Twinky]]===
*'''Species:''' [[Quilled Tousky]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==Rev'n Rave Techno Safari==
===[[Mortimitri]]===
*'''Species:''' [[Slut Rat]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==RSX Solutions==
===[[Alton]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Agent Jackson]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Colonel Arnold]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Doctor Browning]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Major Jack]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Maxwell Power]] (Danger Technician)===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Mr Simon]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===Old Soldier===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Paul Metoxis]] (Pheromone Technician)===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Penelope]]===
*'''Species:''' [[Valkyrie]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Jennifer Trilby]] (Requisitions Clerk)===
*'''Species:''' [[Human]] (with cat ears and tail)
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Research Lead Renley]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Sally (MP)|Sally]]===
*'''Species:''' [[Valkyrie]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Venice]]===
*'''Species:''' [[Goo Girl]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==Secluded Home==
===[[Obsidian]]===
*'''Species:''' [[Shadow Dragon]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==Slut Rat Den==
===[[Axel]]===
*'''Species:''' [[Slut Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Herm]]

===[[Dmitri]]===
*'''Species:''' [[Slut Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Herm]]

==The Devil's Bar==
===[[Casey]]===
*'''Species:''' [[Whimsical Twinkubus]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Tess]]===
*'''Species:''' [[Busty Succubus]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==The Mall==
===[[Lisa (MP)|Lisa]]===
*'''Species:''' [[Mouse Taur]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Missy]]===
*'''Species:''' [[Mall Rat]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Rod (MP)|Rod]]===
*'''Species:''' [[Mall Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Smiley]]===
*'''Species:''' [[Mall Rat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

==The Trick or Treat Motel==
===Animate Pumpkin Patch===
*'''Species:''' Some plantlike amalgamation
*'''Gender:''' Bona Fide Tentaclebeast

===Kurt===
*'''Species:''' [[Wolf Beast]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===Sobek===
*'''Species:''' Crocodile
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Theodore the Corgi]]===
*'''Species:''' [[Welsh Corgi]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===Vampire Bat Twins===
*'''Species:''' [[Vampire Bat]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]] and [[:Category:NPC: Female (MP)|Female]]

===Witch===
*'''Species:''' Cat
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

==The Zoo==
===[[Kangaroo God]]===
*'''Species:''' [[Kangaroo]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

==Zephyr Inc==
===[[Agent Jonathan]]===
*'''Species:''' [[Blue Gryphon]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

===[[Alex (MP)|Alex]]===
*'''Species:''' [[Zebra]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

===[[Ron Danger]] (Danger Technician)===
*'''Species:''' [[Human]] (with a [[House Cat]] head)
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Dr Joan]]===
*'''Species:''' [[Shy Gecko]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===Eureka Pilot===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Ian the Shark]]===
*'''Species:''' [[Bull Shark]]
*'''Gender:''' [[:Category:NPC: Herm (MP)|Herm]]

===[[Louis Ledoyen]]===
*'''Species:''' [[Salamander Femme]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[James Jorgen]]===
*'''Species:''' [[Plump Tigress]]
*'''Gender:''' Shemale

===[[Mike the Chopper Pilot]]===
*'''Species:''' [[Blue Gryphon]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Miura Mercedes]]===
*'''Species:''' [[Shadow Vixen]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Mona Nasawri]] (Pheromone Technician)===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Noel Winters]]===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Jeffrey Lebowski]] (Requisitions Clerk)===
*'''Species:''' [[Pampered Poodle]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Robert]]===
*'''Species:''' [[Zebra]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Sandra]]===
*'''Species:''' [[Human]] (with Kemonomimi [[Bunny Girl]] features)
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===[[Scarlet Sebb]]===
*'''Species:''' [[Female Widow Convert]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===Tactics Soldier===
*'''Species:''' [[Skunk Beast]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

===[[Teacher Jenny]]===
*'''Species:''' [[Skunk Girl]]
*'''Gender:''' [[:Category:NPC: Female (MP)|Female]]

===Workshop Technician===
*'''Species:''' [[Human]]
*'''Gender:''' [[:Category:NPC: Male (MP)|Male]]

[[Category:Multiplayer]]

Miura Mercedes

2017-08-15T05:17:50Z

Strongbird:

{{NPC(MP)
|species=[[Shadow Vixen]]
|gender=[[:Category:NPC: Female (MP)|Female]]
|location=[[Zephyr Inc]]
|sex=No
|infectious=No
}}
==Appearance==
She has a white apron tied around her waist which covers her three rows of breasts down at her front. A small green name tag is pinned up on the strap over her left shoulder which reads "Mercedes", while much of the area over her top row of breasts is covered in flair buttons with a multitude of different designs upon them. The dark green shirt behind her apron presses outwards due to her rather large breasts, the other two rows being of average size.

There's a smile to her canine muzzle, and whether she means it or not, there's a sensual nature to her grin. The deep velvet of the fur over her fox-like head wraps to the strong bone structure of her vixen snout. Off the back of her head, behind her fuzzy fox ears, are a set of pitch black knots of hair which drop into pigtails that dangle down to either side of the back of her skull and past her shoulders.

A myriad of ebony furred and poofy fox tails wag back and forth in an almost hypnotic way, drawing your attention. The mass takes up quite a bit of space behind her, even more so than a skunk tail might, and occasionally she bumps into objects atop the countertops through her inadvertent actions.

Her arms are slim and lead down to smooth, padded paws. The ends of her fingers are blunted nails, painted over with purple nail polish. You can tell that she has a strong grip, something the original owner of her mutation probably used for more sexually oriented tasks.

[[Category:NPC: Female (MP)]]

Scarlet Sebb

2017-08-15T05:16:21Z

Strongbird:

{{NPC(MP)
|species=[[Female Widow Convert]]
|gender=[[:Category:NPC: Female (MP)|Female]]
|location=[[Zephyr Inc]]
|sex=No
|infectious=No
}}
==Appearance==
Standing at the far west side of the balcony, looking out at Downtown Fairhaven beyond, you see a woman standing in a light green Zephyr custodial uniform. Leaning against the railing with her lower two arms, she appears to be deep in thought. Turning to the side, you can see one of her upper arms reach into a breast pocket to pull out a cigarette, lighting up with a lighter in a different hand. Continuing to turn, you can just make out her name tag: Scarlet Sebb.

Leaning back against the guard rail, she notices you looking at her and simply nods her head politely. Her eight eyes all look at you from inside her chitinous black skin, seeming to have retained a mostly human appearance except with red irises. Plush lips curl back to reveal deadly fangs as she smiles, removing the cancer stick from her mouth.

Over the back of her head are narrow, notched shafts of black chitinous covering that fall around her shoulders and down to the middle of her back like dreadlocks. Sebb's uniform is parted just a bit at the front, revealing the top of a red hourglass shape over her two breasts. Of her four slender arms, the lower two are back behind her on the railing as she leans. One of the other two holds the white cylinder to her lips and the last hangs limply at her side.

Scarlet's torso sits atop the front of an abdomen that juts out back behind her with a functional spinneret at its tip. Covering over it is a length of cloth which covers up from her underside and is tied loosely over her thick back with another red hourglass symbol peaking out from within her uniform. She stands atop four legs that are thicker than her arms, yet still delicate and feminine in their overall shape. Those feet end in claws which are designed more for locomotion than any complex tasks. Above her ankles and up to her back, her legs are covered in the light green cloth of her uniform. Overall, she may appear alien, but she looks to be doing her best to maintain an appearance of normality... like so many others are these days.

[[Category:NPC: Female (MP)]]

Scarlet Sebb

2017-08-15T05:16:06Z

Strongbird:

{{NPC(MP)
|species=[[Female Widow Convert]]
|gender=[[:Category:NPC: Female (MP)|Female]]
|location=[[Zephyr Inc]]
|sex=No
|infectious=No
}}
==Appearance==
Standing at the far west side of the balcony, looking out at ^cyan^Downtown Fairhaven^normal^ beyond, you see a woman standing in a light green Zephyr custodial uniform. Leaning against the railing with her lower two arms, she appears to be deep in thought. Turning to the side, you can see one of her upper arms reach into a breast pocket to pull out a cigarette, lighting up with a lighter in a different hand. Continuing to turn, you can just make out her name tag: Scarlet Sebb.

Leaning back against the guard rail, she notices you looking at her and simply nods her head politely. Her eight eyes all look at you from inside her chitinous black skin, seeming to have retained a mostly human appearance except with red irises. Plush lips curl back to reveal deadly fangs as she smiles, removing the cancer stick from her mouth.

Over the back of her head are narrow, notched shafts of black chitinous covering that fall around her shoulders and down to the middle of her back like dreadlocks. Sebb's uniform is parted just a bit at the front, revealing the top of a red hourglass shape over her two breasts. Of her four slender arms, the lower two are back behind her on the railing as she leans. One of the other two holds the white cylinder to her lips and the last hangs limply at her side.

Scarlet's torso sits atop the front of an abdomen that juts out back behind her with a functional spinneret at its tip. Covering over it is a length of cloth which covers up from her underside and is tied loosely over her thick back with another red hourglass symbol peaking out from within her uniform. She stands atop four legs that are thicker than her arms, yet still delicate and feminine in their overall shape. Those feet end in claws which are designed more for locomotion than any complex tasks. Above her ankles and up to her back, her legs are covered in the light green cloth of her uniform. Overall, she may appear alien, but she looks to be doing her best to maintain an appearance of normality... like so many others are these days.

[[Category:NPC: Female (MP)]]

Mortimitri

2017-08-15T05:09:45Z

Strongbird:

{{NPC(MP)
|species=[[Slut Rat]]
|gender=[[:Category:NPC: Herm (MP)|Herm]]
|location=[[Rev'n Rave Techno Safari]]
|sex=Yes
|infectious=No
}}
==Appearance==
Looking over Mortimitri, she is about five feet tall. Her body is covered in white, short fur. There is the occassional patch where fur's been shaved away to reveal tattooed skin. Her head is capped with tapered rodent ears that bear hoops and studs. Her hair is shaven into a perpetual mohawk that's side-swept with its bangs hanging over one eye, and its fibers are dyed a glossy, vibrant violet. Full, sucking lips bare an exceptionally pouty lower lip with a pair of fine hoops off-center, for your pleasure. Her bedroom eyes are darkly mascaraed with long lashes spiking out over the languorous lids. Around her neck is a dark, leather collar studded with long, chromed spikes. Her body is fit and lean with just a hint of her ribcage showing above her cinched abdomen. Barbells pierce her nipples with a fine but sturdy chain arcing between them. Though lean, she still bares curves in all the right places. She has 2 large breasts. Her arms are toned but streamlined, built for action. Long fingers terminate in rodent claws, her palms soft and padded for girth-gripping. Leather cuffs hug her wrists with short, spiked studs along the thick bands. Her legs are free of excess save a little pleasing roundness on the thighs and calves. Her feet are hidden within leather stomping boots. Though not fat, her butt bares a pleasing fleshiness that's both fit and round. Her lengthy whips of rat tail bear broad cuffs of spike-studded leather. A private peek would reveal that: She has a heavy pierced dick with a Jacob's Ladder of barbells metered along the underbelly of her cock. She has fist sized balls. She has an average pink clit. She has a large, hoop-pierced cunt.

Glowing bangles and sticks adorn her body, and she's got wide-legged raver pants with UV reactive stripes forming V's up the outside of her legs. Every ring, every stud, every piercing and chain glows vibrantly.

[[Category:NPC: Herm (MP)]]

Alex (MP)

2017-08-15T05:08:40Z

Strongbird: /* Appearance */

{{NPC(MP)
|species=[[Zebra]]
|gender=[[:Category:NPC: Herm (MP)|Herm]]
|location=[[Zephyr Inc]]
|sex=Yes
|infectious=No
}}
==Appearance==
This zebra waitress certainly stands out from the rest of the cafeteria's personnel--except in terms of stature. She makes her best effort to flirt with all the customers. The hermaphrodite has two full D cup breasts straining the uniform and her skirt, which is clearly a size too small and stretched thin over her behind. The final, most eye-catching feature is a heavy equine member bulging under the cloth, along with the impression of an equally hefty ballsack just below.

She notices you gawking and winks, waving as if offering to come closer. She has a small nametag pinned to her chest that reads 'Alex'.

[[Category:NPC: Herm (MP)]]

Violet(NPC)

2017-08-15T05:07:20Z

Strongbird: /* Appearance */

{{NPC(MP)
|species=[[Blue Gryphon]]
|gender=[[:Category:NPC: Herm (MP)|Herm]]
|location=[[Gryphon Nest]]
|sex=Yes
|infectious=Yes
}}
==Appearance==
A hermaphrodite Blue Gryphon. Violet is approximately six feet tall and incredibly voluptuous, her plush blue fur looking invitingly soft to the touch.

[[Category:NPC: Herm (MP)]]

Statuses

2017-06-11T22:57:02Z

Strongbird:

This is a page wherein all coded statuses are listed for reference.

Remember that just about every status can be reversed with 'Debuff' added to the end. For instance, DamageResistDebuff would cause additional damage to be taken. 

{| width="100%" cellspacing="1" cellpadding="1" border="1" align="left"
|-
! align="left" scope="col" | Status Name
! align="left" scope="col" | Status Effect
|-
! align="left" scope="row" | Accuracy
! align="left" | Increases accuracy by Magnitude, proportional to the power's base Accuracy after being compared against Defense. Has diminishing returns, gradually leveling off before reaching 50% along the following equation: 50*(Mag)/(Mag+100). If Accuracy is negative after contesting against Defense, use the equation listed in Defense instead.
|-
! align="left" scope="row" | Aggro
! align="left" | Increases automated NPC hate by Magnitude percentage.
|-
! align="left" scope="row" | AoEMod
! align="left" | Gives a scaling chance to hit an additional target. Rate of chance is AoEmod/AoEmod+1
|-
! align="left" scope="row" | AreaBlock
! align="left" | Decreases AOE damage on allies and increases it on you by mag percent. Only works when you are targeted directly with the AOE.
|-
! align="left" scope="row" | Attack
! align="left" | Increases damage of all powers by magnitude. Cannot increase the damage of a power by more than 1/3rd its normal level.
|-
! align="left" scope="row" | Cascading
! align="left" | Cascading is like damagebuff for repeat hits, not the direct hit. It soft caps by / 2 at 10, 20, 25, and 35. It hardcaps at 40.
|-
! align="left" scope="row" | Confused
! align="left" | Has magnitude chance of causing AoEs to strike a random friendly target, and increases the final deflection percent (after reduction from combat skills) on AoEs by its magnitude to a maximum final deflection of 50% (unless they rolled a 75%, in which case that is used instead).
|-
! align="left" scope="row" | Charge
! align="left" | Increases the rate at which powers charge by Magnitude percent. Has diminishing returns, gradually leveling off before reaching 150% along the following equation: 150*(Mag)/(Mag+75). When negative, use 25*(Mag)/(Mag+10) instead.
|-
! align="left" scope="row" | Cover
! align="left" | Take magnitude percent of damage meant for the target. Resistances still apply. Capped in effectiveness by the attacker's Concentrated skill level, at 90/80/70% of incoming damage.
|-
! align="left" scope="row" | Critical Damage
! align="left" | Ignores everything except Juggernaut-style DamageResist. Typed EnergyDamageResist and PhysicalDamageResist do not guard against it.
|-
! align="left" scope="row" | (X)Damage
! align="left" | Causes damage over time. Inflicts magnitude damage of (x) element every round, minimum 1 damage per round.
|-
! align="left" scope="row" | Stacked(Y)(X)Damage
! align="left" | Causes damage over time as above, but can stack up to y times, causing more damage if a victim is struck multiple times. Duration is renewed with each stack.
|-
! align="left" scope="row" | DamageBuff
! align="left" | Increases damage by Magnitude percent when attacking. Has diminishing returns, gradually leveling off before reaching 100 along the following equation: 100*(Mag+5)/(Mag+100). If negative, it instead follows -33*(Mag)/(Mag+5).
|-
! align="left" scope="row" | (X)DamageImmunity
! align="left" | Reduces X damage taken by magnitude percent, up to 100% (completely immune). If no specified type, resists all damage. These are a % of damage outright negated after resistances are calculated. So if you were taking 500 damage post resist, and you have 20 DamageImmunity, you will only take 400 damage.
|-
! align="left" scope="row" | DamageResist
! align="left" | Cause all damage received to be reduced by magnitude, up to a maximum of 40% of all damage resisted.
|-
! align="left" scope="row" | (X)DamageResist
! align="left" | Causes damage of specified type(FireDamageResist, IceDamageResist, Etc) to be reduced by magnitude, up to a maximum of 40%(X)resisted. Stacks with damageresist for a maximum of 80% damage resisted.
|-
! align="left" scope="row" | DebuffClear
! align="left" | Destroys negative statuses, magnitude against magnitude. If it can't destroy, it will weaken. Does not persist, has immediate effect then fades.
|-
! align="left" scope="row" | DebuffResist
! align="left" | Reduces incoming debuffs(Anything with 'debuff' at the end, as well as certain other statuses such as Confused) by Magnitude percent. Has diminishing returns, gradually leveling off before reaching 100% along the following equation: 100*(Mag)/(Mag+100). When negative, use 25*(Mag)/(Mag+25) instead.
|-
! align="left" scope="row" | Defense
! align="left" | Increases the odds of partially deflecting an attack by Magnitude, directly opposing the attacker's Accuracy. Has diminishing returns, gradually leveling off before reaching 25% along the following equation: 25*(Mag)/(Mag+10). If Accuracy is still a positive value after contesting against Defense, use the equation listed in Accuracy instead. Attacker then makes a percentile roll which is compared, in order, to Accuracy-45, Accuracy, and Accuracy+30. If the first hits, 0% is deflected; the second, 25% is deflected; the third, 50%; if all three miss, 75% is deflected.
|-
! align="left" scope="row" | Delay
! align="left" | Resists the magnitude of Delaydebuff point per point. 1 Delay + 1 Delaydebuff = No debuff. 1 Delay + 2 Delaydebuff = 1 Delaydebuff
|-
! align="left" scope="row" | Delaydebuff
! align="left" | Increases the base 1000 ATB turn delay by +25 atb per point.
|-
! align="left" scope="row" | EnergyBreak
! align="left" | Causes all powers to cost Magnitude percent less energy. Maximum amount is 50(half off). Negative energy break caps at 25.
|-
! align="left" scope="row" | EnergyDamageReturn
! align="left" | Returns Magnitude percent of damage taken, as above, but as energy damage.
|-
! align="left" scope="row" | EnergyMod
! align="left" | Gives mag energy at the start of each round for duration rounds.
|-
! align="left" scope="row" | Fertility
! align="left" | Not a combat stat, but increases chances of successful breeding.
|-
! align="left" scope="row" | FleeRate
! align="left" | Increases chance to flee by magnitude.
|-
! align="left" scope="row" | Haste
! align="left" | Deprecated status. Do not use and file a request if you see it as a status anywhere. Currently does the same as Charge, and was phased out.
|-
! align="left" scope="row" | Healing
! align="left" | Increases healing done by Magnitude percent. Has diminishing returns, gradually leveling off before reaching 100 along the following equation: 100*(Mag+5)/(Mag+100). If negative, it instead follows -33*(Mag)/(Mag+5).
|-
! align="left" scope="row" | HealEnergyResist
! align="left" | Hampers powers that restore energy by 1 per magnitude, to a minimum of 1.
|-
! align="left" scope="row" | HealGain
! align="left" | Causes healing effects that are incoming to be increased by magnitude, with soft caps at 25% and 50% more healing, hard cap at 75%.
|-
! align="left" scope="row" | HealResist
! align="left" | Causes healing effects that are incoming to be diminished by magnitude, to a minimum of 1.
|-
! align="left" scope="row" | HeatResist
! align="left" | Reduces the effect from a heat environment. If your HeatResist is at or above the environments heat effect, then you receive no penalty.
|-
! align="left" scope="row" | HPBuffer
! align="left" | Prevents standard damage in combat. Each point of magnitude is a kind of temporary hit point. Does not work in talk script  damage. Normal and repeatattacks only hit your largest HPbuffer and any damage over your largest buffer destroys the buffer, dealing the remaining damage to you as normal. The combat skills [[Damage]], [[Accuracy]] and [[Penetration]] can allow you to pierce HPbuffer up to a maximum of 70%.
|-
! align="left" scope="row" | InHeat
! align="left" | Causes the player to appear to be in heat, whether or not they actually are fertile.
|-
! align="left" scope="row" | InstantCooldown
! align="left" | Causes the power with the longest remaining cooldown to lose cooldown in a ratio of 1 mag per 1000 atb. Mag is expended in this, has effect once and goes away.
|-
! align="left" scope="row" | InstantCooldownDebuff
! align="left" | Causes the power with the longest remaining cooldown to gain cooldown in a ratio of 1 mag per 1000 atb. Mag is expended in this, has effect once and goes away.
|-
! align="left" scope="row" | Knockdown
! align="left" | Reduces your ATB(delaying when you can next take an action) by 100 per magnitude, directly resisted with KnockdownResist.
|-
! align="left" scope="row" | KnockdownResist
! align="left" | Lowers the magnitude of Knockdown by its own magnitude.
|-
! align="left" scope="row" | MaxHP
! align="left" | Increases maximum health by magnitude percent. Has diminishing returns, gradually leveling off before reaching 50% along the following equation: 50*(Mag)/(Mag+25). When negative, use 25*(Mag)/(Mag+10) instead.
|-
! align="left" scope="row" | Menace
! align="left" | Increases OVERALL automated NPC hate by Magnitude Percentage(As opposed to increasing per event hate)
|-
! align="left" scope="row" | (X)Penetration
! align="left" | Causes all attacks to penetrate X type of damage resistance. 10 points of status is the same as one point of Penetration combat skill. Soft caps are at 40, 60 and 80. If no damage type is specified, will apply to all damage types. Penetration status will work on energy/physical/critical damage (and dots) where any other damage types (poison, skunk, etc) will need a specific penetration eg: PoisonPenetration
|-
! align="left" scope="row" | ( Aggro Note)
! align="left" |
At time of hate gain, Aggro will increase/reduce the amount given. Once given, this hate is permanent. Menace applies to the total accrued when aggro is checked, but its effect fades entirely when the status goes away.

|-
! align="left" scope="row" | PhysicalDamageReturn
! align="left" | Returns Magnitude percent of all damage taken(Does not work on damage over time, does work on repeating attacks) as physical damage.
|-
! align="left" scope="row" | Recharge
! align="left" | Increases the speed at which all powers recharge by Magnitude percent. Soft caps at 50, 100, 150, etc, doubling the amount needed to gain one effective point per soft cap and hard caps at 200 effective value.
|-
! align="left" scope="row" | Regen
! align="left" | Cure 1/5th its magnitude every 1/5th round, obeys HealResist and Healing at 1/5th value each tick. Cannot regen more than 1/10th max HP in any given round.
|-
! align="left" scope="row" | RepeatAttack
! align="left" | Causes the attack to repeat itself Magnitude times over Duration span of time. The secondary attacks deal half damage, calculated after applying resistance. Note: No statuses are refreshed by repeats.
|-
! align="left" scope="row" | Rut
! align="left" | Adjusts the player Rut level by the magnitude.
|-
! align="left" scope="row" | Salvage
! align="left" | Increases or Decreases your odds of salvaging all types of salvage.
|-
! align="left" scope="row" | (X)Salvage
! align="left" | Increases or Decreases your odds of salvaging (X) type salvage.
|-
! align="left" scope="row" | Size
! align="left" | Increases or Decreases your bodysize by the magnitude. Max size is 60, minimum of 1.
|-
! align="left" scope="row" | StatusBoost
! align="left" | Increases magnitude of active power statuses by magnitude percent. Has diminishing returns, gradually leveling off before reaching 35% along the following equation: 35*(Mag)/(Mag+10) for positive values, or approaching -25 at 25*(Mag)/(Mag+10) for negative values or debuffed. Does not work in instantcooldown or itself. Will not work on Passives or Toggles are not effected. Does effect negative aspects of a friendly power and positive aspects of a hostile power (E.g. Howl)
|-
! align="left" scope="row" | Taunt
! align="left" | Causes the victim to target the caster while active. Latest taunt overrides all others.
|-
! align="left" scope="row" | Vampiric
! align="left" | Causes all attacks to cause a regenerative effect of MAG % of damage dealt. works in conjunction with the combat skill and item/power property of the same name. All combined sources of Vampiric are soft capped at 25 and effective 50 mag, with a hard cap at effective 75 mag, meaning over 25 divide by 2, over 50, divide by 4, and no attack can give more than 75% of hp back from damage.
|-
! align="left" scope="row" | WaterAdaption
! align="left" | Provides resistance to the penalties from Aquatic areas. If your WaterAdaption is lower than an area's AQ rating on +haz, you will suffer severe penalties.
|}

[[Category:Guides]] [[Category:Code]]

String Parsing Optimization

2017-06-10T03:21:05Z

Strongbird: /* Performance: Why should I care? */

String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code without reducing readability. For information on how to write parsing, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

 

== Performance: Why should I care? ==

Performance is important for a number of reasons.
:Optimized code reduces the perceived latency of navigation in a MUCK. Doing so should be enjoyable on even the most sluggish of connections.
:Optimized code reduces the Flexible Survival server load, thus permitting us to provide more and more detailed user-visible content.
:Optimized code reduces the memory cost of programs and #dbrefs. In the case of a fatal memory spike or other unforeseen circumstances, the chances of services ceasing function are reduced when baseline memory is kept to a reasonable minimum.

=== How does this relate to String Parsing? ===

String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute.

Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

== Conditionals ==

=== [if ][end if] ===
----
A basic [if ] statement is prone to some syntactic errors, but little in terms of optimization woes.

Always use the template [if [target] is <gender>] and [if time is <time of day/season>]. Do not use [if [target] = <gender>] or [if time = <time of day/season>]. Despite taking less space in the grand scheme of things, the 'is' function is specifically optimized for checking a target's gender and the time of day/season.
::'''[if [target] = <gender>]
::'''[if time = <time of day/season>]
::'''[if [target] is <gender>]
::'''[if time is <time of day/season>]

Do not check for integers with the '=' sign. This is a function designed to check a string. Use '==' instead.
Benchmarks have shown that checking directly for an integer is both faster and cleaner.
::'''[if stat cocks of [target] = 1]
::'''[if stat cocks of [target] == 1]

Avoid not statements when possible. For example, [if time is not night] is the same as [if time is day].
::'''[if time is not night]
::'''[if time is not day]
::'''[if time is day]
::'''[if time is night]
 

=== [if ][else][end if] ===
----
[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.

::'''[if time is day]A woman in tight jeans and an unassuming blouse mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work.[else]A woman in tight jeans and an unassuming blouse would normally man the counter. However, she doesn't appear to be here right now.[end if]

::'''A woman in tight jeans and an unassuming blouse [if time is day]mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work[else]would normally man the counter. However, she doesn't appear to be here right now[end if].

In the above example, repeated text has been removed from the [if ] statement itself and added as prefix. This provides the exact same user-visible output with less characters. Processing requirements are almost identical, but the text fits in less space and is just as readable.

Note: It's generally preferred to not cut off letters in words. Punctuation can be moved outside, but chopping up words results in text that is much less legible to people with screen readers.
 

=== [if ][else if ][else][end if] ===
----
[else if ] introduces further potential for code slowdown. Please read the following steps carefully to avoid that.

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest.[else if [player] is female]easily ignore the Skunk Girl's attempts to seduce you.[else]easily ignore the Skunk Girl's attempts to seduce you. Neuters 4ever![end if]

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest[else]easily ignore the Skunk Girl's attempts to seduce you[end if].[if [player] is neuter] Neuters 4ever![end if]

In the above example, a lengthy [if ][else if ][else][end if] statement is deconstructed into [if ][else][end if][if ][end if].

Converge the [else if ] and [else] statements into a single [else]. Move the neuter check into a separate [if ] statement at the end. Move the trailing periods in the [if ][else][end if] statement before the start of the neuter check.

::'''The [if time is morning]sun is rising, stirring all forms of life into motion[else if time is afternoon]sun is high, baking the earth with its furious light[else if time is evening]sun is starting to set, casting the land in long shadows[else]moon shines over the land[end if].

::'''The [if time is night]moon shines over the land[else if time is morning]sun is rising, stirring all forms of life into motion[else if time is evening]sun is starting to set, casting the land in long shadows[else]sun is high, baking the earth with its furious light[end if].

In the above example, a couple optimizations are made.

Place [if time is night] at the front. This is the longest period of time outside of 'day' (which is not used here), and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

=== [case ] ===
----
Case-statements are useful where lengthy [if ][else if ][end if] statements would result in redundancy.

::'''[case stat X of [target] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

::'''[case [stat X of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

If something is valid parsing on its own, such as '[stat X of [target]]' and '[the mutation X of [target]]', use that, so the statement will only have to be parsed once instead of in every [when ]-statement.

::'''[if stat blah/bluh/bleh of [target] == 1]A[else if stat blah/bluh/bleh of [target] == 2]B[else if stat blah/bluh/bleh of [target] == 3]C[else if stat blah/bluh/bleh of [target] == 4]D[else if stat blah/bluh/bleh of [target] == 5]E[else]F[end if]

::'''[case [stat blah/bluh/bleh of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when (target) 5]E[end when][when 1]F[end when][end case]

In the above example, a complex [if ][else if ][end if] statement is optimized.

Convert the code to a basic case-statement. Since all comparisons are alike, remove them from their [when ] statements and append one to [case (target)]. Add brackets around 'stat blah/bluh of [player]' to avoid computing that in every [when ] statement.

== Randomization ==

The following functions display content at random. Input is separated by [or].

=== [one of][or][at random] ===
----
The standard [one of][or][at random] statement is prone to redundancy.

::'''Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

::'''Sometimes, a man's gotta man. [one of]Other times[or]Sometimes[at random], he doesn't.

In the above example, redundancy is fixed by moving a comma after [at random].

==== [with odds: ] ====

[with odds: ] allows you to simplify many longer [one of] statements.

::'''[one of]1[or]1[or]1[or]1[or]1[or]2[at random]

::'''[one of]1[or]2[with odds: 5 1]

or

::'''[one of]1[or]1[or]1[or]2[or]2[or]3[at random]

::'''[one of]1[or]2[or]3[with odds: 3 2 1]

=== [random x to y] ===
----
This function is more specialized than [one of][or][at random], lending itself well to optimization. Note that it only accepts numerical input (negatives included) and that 'y' should be greater than 'x'.

::'''[one of]1[or]2[or]3[or]4[or]5[or]6[at random]

::'''[random 1 to 6]

A complex [one of][or][at random] statement converted into a [random x to y] statement.

Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.

 
----
 

This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songb's. Please only modify with either A) explicit permission to do so, or B) a fix for known factual inaccuracy / grammar errors.

[[Category:Guides]][[Category:Code]]

String Parsing Optimization

2017-06-10T03:19:17Z

Strongbird:

String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code without reducing readability. For information on how to write parsing, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

 

== Performance: Why should I care? ==

Performance is important for a number of reasons.
:Optimized code reduces the perceived latency of navigation in a MUCK. Doing so should be enjoyable on even the most sluggish of connections.
:Optimized code reduces the Flexible Survival server load, thus permitting us to provide more and more detailed user-visible content.
:Optimized code reduces the memory cost of programs and #dbrefs. In the case of a fatal memory spike or other unforeseen circumstances, the chances of services ceasing function are reduced when baseline memory is kept to a reasonable minimum.

=== How does this relate to String Parsing? ===

String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute

Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

== Conditionals ==

=== [if ][end if] ===
----
A basic [if ] statement is prone to some syntactic errors, but little in terms of optimization woes.

Always use the template [if [target] is <gender>] and [if time is <time of day/season>]. Do not use [if [target] = <gender>] or [if time = <time of day/season>]. Despite taking less space in the grand scheme of things, the 'is' function is specifically optimized for checking a target's gender and the time of day/season.
::'''[if [target] = <gender>]
::'''[if time = <time of day/season>]
::'''[if [target] is <gender>]
::'''[if time is <time of day/season>]

Do not check for integers with the '=' sign. This is a function designed to check a string. Use '==' instead.
Benchmarks have shown that checking directly for an integer is both faster and cleaner.
::'''[if stat cocks of [target] = 1]
::'''[if stat cocks of [target] == 1]

Avoid not statements when possible. For example, [if time is not night] is the same as [if time is day].
::'''[if time is not night]
::'''[if time is not day]
::'''[if time is day]
::'''[if time is night]
 

=== [if ][else][end if] ===
----
[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.

::'''[if time is day]A woman in tight jeans and an unassuming blouse mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work.[else]A woman in tight jeans and an unassuming blouse would normally man the counter. However, she doesn't appear to be here right now.[end if]

::'''A woman in tight jeans and an unassuming blouse [if time is day]mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work[else]would normally man the counter. However, she doesn't appear to be here right now[end if].

In the above example, repeated text has been removed from the [if ] statement itself and added as prefix. This provides the exact same user-visible output with less characters. Processing requirements are almost identical, but the text fits in less space and is just as readable.

Note: It's generally preferred to not cut off letters in words. Punctuation can be moved outside, but chopping up words results in text that is much less legible to people with screen readers.
 

=== [if ][else if ][else][end if] ===
----
[else if ] introduces further potential for code slowdown. Please read the following steps carefully to avoid that.

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest.[else if [player] is female]easily ignore the Skunk Girl's attempts to seduce you.[else]easily ignore the Skunk Girl's attempts to seduce you. Neuters 4ever![end if]

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest[else]easily ignore the Skunk Girl's attempts to seduce you[end if].[if [player] is neuter] Neuters 4ever![end if]

In the above example, a lengthy [if ][else if ][else][end if] statement is deconstructed into [if ][else][end if][if ][end if].

Converge the [else if ] and [else] statements into a single [else]. Move the neuter check into a separate [if ] statement at the end. Move the trailing periods in the [if ][else][end if] statement before the start of the neuter check.

::'''The [if time is morning]sun is rising, stirring all forms of life into motion[else if time is afternoon]sun is high, baking the earth with its furious light[else if time is evening]sun is starting to set, casting the land in long shadows[else]moon shines over the land[end if].

::'''The [if time is night]moon shines over the land[else if time is morning]sun is rising, stirring all forms of life into motion[else if time is evening]sun is starting to set, casting the land in long shadows[else]sun is high, baking the earth with its furious light[end if].

In the above example, a couple optimizations are made.

Place [if time is night] at the front. This is the longest period of time outside of 'day' (which is not used here), and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

=== [case ] ===
----
Case-statements are useful where lengthy [if ][else if ][end if] statements would result in redundancy.

::'''[case stat X of [target] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

::'''[case [stat X of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

If something is valid parsing on its own, such as '[stat X of [target]]' and '[the mutation X of [target]]', use that, so the statement will only have to be parsed once instead of in every [when ]-statement.

::'''[if stat blah/bluh/bleh of [target] == 1]A[else if stat blah/bluh/bleh of [target] == 2]B[else if stat blah/bluh/bleh of [target] == 3]C[else if stat blah/bluh/bleh of [target] == 4]D[else if stat blah/bluh/bleh of [target] == 5]E[else]F[end if]

::'''[case [stat blah/bluh/bleh of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when (target) 5]E[end when][when 1]F[end when][end case]

In the above example, a complex [if ][else if ][end if] statement is optimized.

Convert the code to a basic case-statement. Since all comparisons are alike, remove them from their [when ] statements and append one to [case (target)]. Add brackets around 'stat blah/bluh of [player]' to avoid computing that in every [when ] statement.

== Randomization ==

The following functions display content at random. Input is separated by [or].

=== [one of][or][at random] ===
----
The standard [one of][or][at random] statement is prone to redundancy.

::'''Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

::'''Sometimes, a man's gotta man. [one of]Other times[or]Sometimes[at random], he doesn't.

In the above example, redundancy is fixed by moving a comma after [at random].

==== [with odds: ] ====

[with odds: ] allows you to simplify many longer [one of] statements.

::'''[one of]1[or]1[or]1[or]1[or]1[or]2[at random]

::'''[one of]1[or]2[with odds: 5 1]

or

::'''[one of]1[or]1[or]1[or]2[or]2[or]3[at random]

::'''[one of]1[or]2[or]3[with odds: 3 2 1]

=== [random x to y] ===
----
This function is more specialized than [one of][or][at random], lending itself well to optimization. Note that it only accepts numerical input (negatives included) and that 'y' should be greater than 'x'.

::'''[one of]1[or]2[or]3[or]4[or]5[or]6[at random]

::'''[random 1 to 6]

A complex [one of][or][at random] statement converted into a [random x to y] statement.

Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.

 
----
 

This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songb's. Please only modify with either A) explicit permission to do so, or B) a fix for known factual inaccuracy / grammar errors.

[[Category:Guides]][[Category:Code]]

String Parsing Optimization

2017-06-10T03:18:01Z

Strongbird: /* [one of][or][at random] */

String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code. It will not tell you how to write clean or legible code, NOR will it teach you the fundamental markup of String Parsing. For information on those subjects, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

 

== Performance: Why should I care? ==

Performance is important for a number of reasons.
:Optimized code reduces the perceived latency of navigation in a MUCK. Doing so should be enjoyable on even the most sluggish of connections.
:Optimized code reduces the Flexible Survival server load, thus permitting us to provide more and more detailed user-visible content.
:Optimized code reduces the memory cost of programs and #dbrefs. In the case of a fatal memory spike or other unforeseen circumstances, the chances of services ceasing function are reduced when baseline memory is kept to a reasonable minimum.

=== How does this relate to String Parsing? ===

String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute

Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

== Conditionals ==

=== [if ][end if] ===
----
A basic [if ] statement is prone to some syntactic errors, but little in terms of optimization woes.

Always use the template [if [target] is <gender>] and [if time is <time of day/season>]. Do not use [if [target] = <gender>] or [if time = <time of day/season>]. Despite taking less space in the grand scheme of things, the 'is' function is specifically optimized for checking a target's gender and the time of day/season.
::'''[if [target] = <gender>]
::'''[if time = <time of day/season>]
::'''[if [target] is <gender>]
::'''[if time is <time of day/season>]

Do not check for integers with the '=' sign. This is a function designed to check a string. Use '==' instead.
Benchmarks have shown that checking directly for an integer is both faster and cleaner.
::'''[if stat cocks of [target] = 1]
::'''[if stat cocks of [target] == 1]

Avoid not statements when possible. For example, [if time is not night] is the same as [if time is day].
::'''[if time is not night]
::'''[if time is not day]
::'''[if time is day]
::'''[if time is night]
 

=== [if ][else][end if] ===
----
[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.

::'''[if time is day]A woman in tight jeans and an unassuming blouse mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work.[else]A woman in tight jeans and an unassuming blouse would normally man the counter. However, she doesn't appear to be here right now.[end if]

::'''A woman in tight jeans and an unassuming blouse [if time is day]mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work[else]would normally man the counter. However, she doesn't appear to be here right now[end if].

In the above example, repeated text has been removed from the [if ] statement itself and added as prefix. This provides the exact same user-visible output with less characters. Processing requirements are almost identical, but the text fits in less space and is just as readable.

Note: It's generally preferred to not cut off letters in words. Punctuation can be moved outside, but chopping up words results in text that is much less legible to people with screen readers.
 

=== [if ][else if ][else][end if] ===
----
[else if ] introduces further potential for code slowdown. Please read the following steps carefully to avoid that.

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest.[else if [player] is female]easily ignore the Skunk Girl's attempts to seduce you.[else]easily ignore the Skunk Girl's attempts to seduce you. Neuters 4ever![end if]

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest[else]easily ignore the Skunk Girl's attempts to seduce you[end if].[if [player] is neuter] Neuters 4ever![end if]

In the above example, a lengthy [if ][else if ][else][end if] statement is deconstructed into [if ][else][end if][if ][end if].

Converge the [else if ] and [else] statements into a single [else]. Move the neuter check into a separate [if ] statement at the end. Move the trailing periods in the [if ][else][end if] statement before the start of the neuter check.

::'''The [if time is morning]sun is rising, stirring all forms of life into motion[else if time is afternoon]sun is high, baking the earth with its furious light[else if time is evening]sun is starting to set, casting the land in long shadows[else]moon shines over the land[end if].

::'''The [if time is night]moon shines over the land[else if time is morning]sun is rising, stirring all forms of life into motion[else if time is evening]sun is starting to set, casting the land in long shadows[else]sun is high, baking the earth with its furious light[end if].

In the above example, a couple optimizations are made.

Place [if time is night] at the front. This is the longest period of time outside of 'day' (which is not used here), and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

=== [case ] ===
----
Case-statements are useful where lengthy [if ][else if ][end if] statements would result in redundancy.

::'''[case stat X of [target] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

::'''[case [stat X of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

If something is valid parsing on its own, such as '[stat X of [target]]' and '[the mutation X of [target]]', use that, so the statement will only have to be parsed once instead of in every [when ]-statement.

::'''[if stat blah/bluh/bleh of [target] == 1]A[else if stat blah/bluh/bleh of [target] == 2]B[else if stat blah/bluh/bleh of [target] == 3]C[else if stat blah/bluh/bleh of [target] == 4]D[else if stat blah/bluh/bleh of [target] == 5]E[else]F[end if]

::'''[case [stat blah/bluh/bleh of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when (target) 5]E[end when][when 1]F[end when][end case]

In the above example, a complex [if ][else if ][end if] statement is optimized.

Convert the code to a basic case-statement. Since all comparisons are alike, remove them from their [when ] statements and append one to [case (target)]. Add brackets around 'stat blah/bluh of [player]' to avoid computing that in every [when ] statement.

== Randomization ==

The following functions display content at random. Input is separated by [or].

=== [one of][or][at random] ===
----
The standard [one of][or][at random] statement is prone to redundancy.

::'''Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

::'''Sometimes, a man's gotta man. [one of]Other times[or]Sometimes[at random], he doesn't.

In the above example, redundancy is fixed by moving a comma after [at random].

==== [with odds: ] ====

[with odds: ] allows you to simplify many longer [one of] statements.

::'''[one of]1[or]1[or]1[or]1[or]1[or]2[at random]

::'''[one of]1[or]2[with odds: 5 1]

or

::'''[one of]1[or]1[or]1[or]2[or]2[or]3[at random]

::'''[one of]1[or]2[or]3[with odds: 3 2 1]

=== [random x to y] ===
----
This function is more specialized than [one of][or][at random], lending itself well to optimization. Note that it only accepts numerical input (negatives included) and that 'y' should be greater than 'x'.

::'''[one of]1[or]2[or]3[or]4[or]5[or]6[at random]

::'''[random 1 to 6]

A complex [one of][or][at random] statement converted into a [random x to y] statement.

Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.

 
----
 

This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songbird's. Please only modify with either A), explicit permission to do so, or B), a fix for known factual inaccuracy / grammar errors.

[[Category:Guides]][[Category:Code]]

String Parsing Optimization

2017-06-10T03:13:23Z

Strongbird: /* [if ][else if ][else][end if] */

String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code. It will not tell you how to write clean or legible code, NOR will it teach you the fundamental markup of String Parsing. For information on those subjects, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

 

== Performance: Why should I care? ==

Performance is important for a number of reasons.
:Optimized code reduces the perceived latency of navigation in a MUCK. Doing so should be enjoyable on even the most sluggish of connections.
:Optimized code reduces the Flexible Survival server load, thus permitting us to provide more and more detailed user-visible content.
:Optimized code reduces the memory cost of programs and #dbrefs. In the case of a fatal memory spike or other unforeseen circumstances, the chances of services ceasing function are reduced when baseline memory is kept to a reasonable minimum.

=== How does this relate to String Parsing? ===

String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute

Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

== Conditionals ==

=== [if ][end if] ===
----
A basic [if ] statement is prone to some syntactic errors, but little in terms of optimization woes.

Always use the template [if [target] is <gender>] and [if time is <time of day/season>]. Do not use [if [target] = <gender>] or [if time = <time of day/season>]. Despite taking less space in the grand scheme of things, the 'is' function is specifically optimized for checking a target's gender and the time of day/season.
::'''[if [target] = <gender>]
::'''[if time = <time of day/season>]
::'''[if [target] is <gender>]
::'''[if time is <time of day/season>]

Do not check for integers with the '=' sign. This is a function designed to check a string. Use '==' instead.
Benchmarks have shown that checking directly for an integer is both faster and cleaner.
::'''[if stat cocks of [target] = 1]
::'''[if stat cocks of [target] == 1]

Avoid not statements when possible. For example, [if time is not night] is the same as [if time is day].
::'''[if time is not night]
::'''[if time is not day]
::'''[if time is day]
::'''[if time is night]
 

=== [if ][else][end if] ===
----
[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.

::'''[if time is day]A woman in tight jeans and an unassuming blouse mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work.[else]A woman in tight jeans and an unassuming blouse would normally man the counter. However, she doesn't appear to be here right now.[end if]

::'''A woman in tight jeans and an unassuming blouse [if time is day]mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work[else]would normally man the counter. However, she doesn't appear to be here right now[end if].

In the above example, repeated text has been removed from the [if ] statement itself and added as prefix. This provides the exact same user-visible output with less characters. Processing requirements are almost identical, but the text fits in less space and is just as readable.

Note: It's generally preferred to not cut off letters in words. Punctuation can be moved outside, but chopping up words results in text that is much less legible to people with screen readers.
 

=== [if ][else if ][else][end if] ===
----
[else if ] introduces further potential for code slowdown. Please read the following steps carefully to avoid that.

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest.[else if [player] is female]easily ignore the Skunk Girl's attempts to seduce you.[else]easily ignore the Skunk Girl's attempts to seduce you. Neuters 4ever![end if]

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest[else]easily ignore the Skunk Girl's attempts to seduce you[end if].[if [player] is neuter] Neuters 4ever![end if]

In the above example, a lengthy [if ][else if ][else][end if] statement is deconstructed into [if ][else][end if][if ][end if].

Converge the [else if ] and [else] statements into a single [else]. Move the neuter check into a separate [if ] statement at the end. Move the trailing periods in the [if ][else][end if] statement before the start of the neuter check.

::'''The [if time is morning]sun is rising, stirring all forms of life into motion[else if time is afternoon]sun is high, baking the earth with its furious light[else if time is evening]sun is starting to set, casting the land in long shadows[else]moon shines over the land[end if].

::'''The [if time is night]moon shines over the land[else if time is morning]sun is rising, stirring all forms of life into motion[else if time is evening]sun is starting to set, casting the land in long shadows[else]sun is high, baking the earth with its furious light[end if].

In the above example, a couple optimizations are made.

Place [if time is night] at the front. This is the longest period of time outside of 'day' (which is not used here), and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

=== [case ] ===
----
Case-statements are useful where lengthy [if ][else if ][end if] statements would result in redundancy.

::'''[case stat X of [target] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

::'''[case [stat X of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

If something is valid parsing on its own, such as '[stat X of [target]]' and '[the mutation X of [target]]', use that, so the statement will only have to be parsed once instead of in every [when ]-statement.

::'''[if stat blah/bluh/bleh of [target] == 1]A[else if stat blah/bluh/bleh of [target] == 2]B[else if stat blah/bluh/bleh of [target] == 3]C[else if stat blah/bluh/bleh of [target] == 4]D[else if stat blah/bluh/bleh of [target] == 5]E[else]F[end if]

::'''[case [stat blah/bluh/bleh of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when (target) 5]E[end when][when 1]F[end when][end case]

In the above example, a complex [if ][else if ][end if] statement is optimized.

Convert the code to a basic case-statement. Since all comparisons are alike, remove them from their [when ] statements and append one to [case (target)]. Add brackets around 'stat blah/bluh of [player]' to avoid computing that in every [when ] statement.

== Randomization ==

The following functions display content at random. Input is separated by [or].

=== [one of][or][at random] ===
----
The standard [one of][or][at random] statement is prone to redundancy.

::'''Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

::'''Sometimes, a man's gotta man. [one of]Other [or]Some[at random]times, he doesn't.

In the above example, redundancy is nixed by moving a string shared by all inputs after [at random].

==== [with odds: ] ====

[with odds: ] allows you to simplify many longer [one of] statements.

::'''[one of]1[or]1[or]1[or]1[or]1[or]2[at random]

::'''[one of]1[or]2[with odds: 5 1]

or

::'''[one of]1[or]1[or]1[or]2[or]2[or]3[at random]

::'''[one of]1[or]2[or]3[with odds: 3 2 1]

=== [random x to y] ===
----
This function is more specialized than [one of][or][at random], lending itself well to optimization. Note that it only accepts numerical input (negatives included) and that 'y' should be greater than 'x'.

::'''[one of]1[or]2[or]3[or]4[or]5[or]6[at random]

::'''[random 1 to 6]

A complex [one of][or][at random] statement converted into a [random x to y] statement.

Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.

 
----
 

This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songbird's. Please only modify with either A), explicit permission to do so, or B), a fix for known factual inaccuracy / grammar errors.

[[Category:Guides]][[Category:Code]]

String Parsing Optimization

2017-06-10T03:11:38Z

Strongbird: /* [if ][else][end if] */

String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code. It will not tell you how to write clean or legible code, NOR will it teach you the fundamental markup of String Parsing. For information on those subjects, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

 

== Performance: Why should I care? ==

Performance is important for a number of reasons.
:Optimized code reduces the perceived latency of navigation in a MUCK. Doing so should be enjoyable on even the most sluggish of connections.
:Optimized code reduces the Flexible Survival server load, thus permitting us to provide more and more detailed user-visible content.
:Optimized code reduces the memory cost of programs and #dbrefs. In the case of a fatal memory spike or other unforeseen circumstances, the chances of services ceasing function are reduced when baseline memory is kept to a reasonable minimum.

=== How does this relate to String Parsing? ===

String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute

Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

== Conditionals ==

=== [if ][end if] ===
----
A basic [if ] statement is prone to some syntactic errors, but little in terms of optimization woes.

Always use the template [if [target] is <gender>] and [if time is <time of day/season>]. Do not use [if [target] = <gender>] or [if time = <time of day/season>]. Despite taking less space in the grand scheme of things, the 'is' function is specifically optimized for checking a target's gender and the time of day/season.
::'''[if [target] = <gender>]
::'''[if time = <time of day/season>]
::'''[if [target] is <gender>]
::'''[if time is <time of day/season>]

Do not check for integers with the '=' sign. This is a function designed to check a string. Use '==' instead.
Benchmarks have shown that checking directly for an integer is both faster and cleaner.
::'''[if stat cocks of [target] = 1]
::'''[if stat cocks of [target] == 1]

Avoid not statements when possible. For example, [if time is not night] is the same as [if time is day].
::'''[if time is not night]
::'''[if time is not day]
::'''[if time is day]
::'''[if time is night]
 

=== [if ][else][end if] ===
----
[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.

::'''[if time is day]A woman in tight jeans and an unassuming blouse mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work.[else]A woman in tight jeans and an unassuming blouse would normally man the counter. However, she doesn't appear to be here right now.[end if]

::'''A woman in tight jeans and an unassuming blouse [if time is day]mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work[else]would normally man the counter. However, she doesn't appear to be here right now[end if].

In the above example, repeated text has been removed from the [if ] statement itself and added as prefix. This provides the exact same user-visible output with less characters. Processing requirements are almost identical, but the text fits in less space and is just as readable.

Note: It's generally preferred to not cut off letters in words. Punctuation can be moved outside, but chopping up words results in text that is much less legible to people with screen readers.
 

=== [if ][else if ][else][end if] ===
----
[else if ] introduces further potential for code slowdown. Please read the following steps carefully to avoid that.

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest.[else if [player] is female]easily ignore the Skunk Girl's attempts to seduce you.[else]easily ignore the Skunk Girl's attempts to seduce you. Neuters 4ever![end if]

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest[else]easily ignore the Skunk Girl's attempts to seduce you[end if].[if [player] is neuter] Neuters 4ever![end if]

In the above example, a lengthy [if ][else if ][else][end if] statement is deconstructed into [if ][else][end if][if ][end if].

Converge the [else if ] and [else] statements into a single [else]. Move the neuter check into a separate [if ] statement at the end. Move the trailing periods in the [if ][else][end if] statement before the start of the neuter check.

::'''The [if time is morning]sun is rising, stirring all forms of life into motion[else if time is afternoon]sun is high, baking the earth with its furious light[else if time is evening]sun is starting to set, casting the land in long shadows[else]moon shines over the land[end if].

::'''The [if time is night]moon shines over the land[else if time is morning]sun is rising, stirring all forms of life into motion[else if time is evening]sun is starting to set, casting the land in long shadows[else]sun is high, baking the earth with its furious light[end if].

In the above example, a couple optimizations are made.

Place [if time is night] at the front. This is the longest period of time and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

=== [case ] ===
----
Case-statements are useful where lengthy [if ][else if ][end if] statements would result in redundancy.

::'''[case stat X of [target] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

::'''[case [stat X of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

If something is valid parsing on its own, such as '[stat X of [target]]' and '[the mutation X of [target]]', use that, so the statement will only have to be parsed once instead of in every [when ]-statement.

::'''[if stat blah/bluh/bleh of [target] == 1]A[else if stat blah/bluh/bleh of [target] == 2]B[else if stat blah/bluh/bleh of [target] == 3]C[else if stat blah/bluh/bleh of [target] == 4]D[else if stat blah/bluh/bleh of [target] == 5]E[else]F[end if]

::'''[case [stat blah/bluh/bleh of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when (target) 5]E[end when][when 1]F[end when][end case]

In the above example, a complex [if ][else if ][end if] statement is optimized.

Convert the code to a basic case-statement. Since all comparisons are alike, remove them from their [when ] statements and append one to [case (target)]. Add brackets around 'stat blah/bluh of [player]' to avoid computing that in every [when ] statement.

== Randomization ==

The following functions display content at random. Input is separated by [or].

=== [one of][or][at random] ===
----
The standard [one of][or][at random] statement is prone to redundancy.

::'''Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

::'''Sometimes, a man's gotta man. [one of]Other [or]Some[at random]times, he doesn't.

In the above example, redundancy is nixed by moving a string shared by all inputs after [at random].

==== [with odds: ] ====

[with odds: ] allows you to simplify many longer [one of] statements.

::'''[one of]1[or]1[or]1[or]1[or]1[or]2[at random]

::'''[one of]1[or]2[with odds: 5 1]

or

::'''[one of]1[or]1[or]1[or]2[or]2[or]3[at random]

::'''[one of]1[or]2[or]3[with odds: 3 2 1]

=== [random x to y] ===
----
This function is more specialized than [one of][or][at random], lending itself well to optimization. Note that it only accepts numerical input (negatives included) and that 'y' should be greater than 'x'.

::'''[one of]1[or]2[or]3[or]4[or]5[or]6[at random]

::'''[random 1 to 6]

A complex [one of][or][at random] statement converted into a [random x to y] statement.

Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.

 
----
 

This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songbird's. Please only modify with either A), explicit permission to do so, or B), a fix for known factual inaccuracy / grammar errors.

[[Category:Guides]][[Category:Code]]

String Parsing Optimization

2017-06-10T03:05:27Z

Strongbird: /* Conditionals */

String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code. It will not tell you how to write clean or legible code, NOR will it teach you the fundamental markup of String Parsing. For information on those subjects, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

 

== Performance: Why should I care? ==

Performance is important for a number of reasons.
:Optimized code reduces the perceived latency of navigation in a MUCK. Doing so should be enjoyable on even the most sluggish of connections.
:Optimized code reduces the Flexible Survival server load, thus permitting us to provide more and more detailed user-visible content.
:Optimized code reduces the memory cost of programs and #dbrefs. In the case of a fatal memory spike or other unforeseen circumstances, the chances of services ceasing function are reduced when baseline memory is kept to a reasonable minimum.

=== How does this relate to String Parsing? ===

String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute

Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

== Conditionals ==

=== [if ][end if] ===
----
A basic [if ] statement is prone to some syntactic errors, but little in terms of optimization woes.

Always use the template [if [target] is <gender>] and [if time is <time of day/season>]. Do not use [if [target] = <gender>] or [if time = <time of day/season>]. Despite taking less space in the grand scheme of things, the 'is' function is specifically optimized for checking a target's gender and the time of day/season.
::'''[if [target] = <gender>]
::'''[if time = <time of day/season>]
::'''[if [target] is <gender>]
::'''[if time is <time of day/season>]

Do not check for integers with the '=' sign. This is a function designed to check a string. Use '==' instead.
Benchmarks have shown that checking directly for an integer is both faster and cleaner.
::'''[if stat cocks of [target] = 1]
::'''[if stat cocks of [target] == 1]

Avoid not statements when possible. For example, [if time is not night] is the same as [if time is day].
::'''[if time is not night]
::'''[if time is not day]
::'''[if time is day]
::'''[if time is night]
 

=== [if ][else][end if] ===
----
[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.

::'''[if time is winter]The large bear returned to his cave to hibernate.[else]The small fox jumped over the fence.[end if]

::'''The [if time is winter]large bear returned to his cave to hibernat[else]small fox jumped over the fenc[end if]e.

In the above example, repeated text has been removed from the [if ] statement itself and added as prefix and suffix to the code, respectively. This provides the exact same user-visible output with less characters and processing requirements.

::'''[if time is day]A woman in tight jeans and an unassuming blouse mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work.[else]A woman in tight jeans and an unassuming blouse would normally man the counter. However, she doesn't appear to be here right now.[end if]

::'''A woman in tight jeans and an unassuming blouse [if time is day]mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work[else]would normally man the counter. However, she doesn't appear to be here right now[end if].

See above. Repeated text is removed from the [if ] statement itself and added as prefix and suffix to the code, respectively.
 

=== [if ][else if ][else][end if] ===
----
[else if ] introduces further potential for code slowdown. Please read the following steps carefully to avoid that.

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest.[else if [player] is female]easily ignore the Skunk Girl's attempts to seduce you.[else]easily ignore the Skunk Girl's attempts to seduce you. Neuters 4ever![end if]

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest[else]easily ignore the Skunk Girl's attempts to seduce you[end if].[if [player] is neuter] Neuters 4ever![end if]

In the above example, a lengthy [if ][else if ][else][end if] statement is deconstructed into [if ][else][end if][if ][end if].

Converge the [else if ] and [else] statements into a single [else]. Move the neuter check into a separate [if ] statement at the end. Move the trailing periods in the [if ][else][end if] statement before the start of the neuter check.

::'''The [if time is morning]sun is rising, stirring all forms of life into motion[else if time is afternoon]sun is high, baking the earth with its furious light[else if time is evening]sun is starting to set, casting the land in long shadows[else]moon shines over the land[end if].

::'''The [if time is night]moon shines over the land[else if time is morning]sun is rising, stirring all forms of life into motion[else if time is evening]sun is starting to set, casting the land in long shadows[else]sun is high, baking the earth with its furious light[end if].

In the above example, a couple optimizations are made.

Place [if time is night] at the front. This is the longest period of time and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

=== [case ] ===
----
Case-statements are useful where lengthy [if ][else if ][end if] statements would result in redundancy.

::'''[case stat X of [target] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

::'''[case [stat X of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

If something is valid parsing on its own, such as '[stat X of [target]]' and '[the mutation X of [target]]', use that, so the statement will only have to be parsed once instead of in every [when ]-statement.

::'''[if stat blah/bluh/bleh of [target] == 1]A[else if stat blah/bluh/bleh of [target] == 2]B[else if stat blah/bluh/bleh of [target] == 3]C[else if stat blah/bluh/bleh of [target] == 4]D[else if stat blah/bluh/bleh of [target] == 5]E[else]F[end if]

::'''[case [stat blah/bluh/bleh of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when (target) 5]E[end when][when 1]F[end when][end case]

In the above example, a complex [if ][else if ][end if] statement is optimized.

Convert the code to a basic case-statement. Since all comparisons are alike, remove them from their [when ] statements and append one to [case (target)]. Add brackets around 'stat blah/bluh of [player]' to avoid computing that in every [when ] statement.

== Randomization ==

The following functions display content at random. Input is separated by [or].

=== [one of][or][at random] ===
----
The standard [one of][or][at random] statement is prone to redundancy.

::'''Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

::'''Sometimes, a man's gotta man. [one of]Other [or]Some[at random]times, he doesn't.

In the above example, redundancy is nixed by moving a string shared by all inputs after [at random].

==== [with odds: ] ====

[with odds: ] allows you to simplify many longer [one of] statements.

::'''[one of]1[or]1[or]1[or]1[or]1[or]2[at random]

::'''[one of]1[or]2[with odds: 5 1]

or

::'''[one of]1[or]1[or]1[or]2[or]2[or]3[at random]

::'''[one of]1[or]2[or]3[with odds: 3 2 1]

=== [random x to y] ===
----
This function is more specialized than [one of][or][at random], lending itself well to optimization. Note that it only accepts numerical input (negatives included) and that 'y' should be greater than 'x'.

::'''[one of]1[or]2[or]3[or]4[or]5[or]6[at random]

::'''[random 1 to 6]

A complex [one of][or][at random] statement converted into a [random x to y] statement.

Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.

 
----
 

This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songbird's. Please only modify with either A), explicit permission to do so, or B), a fix for known factual inaccuracy / grammar errors.

[[Category:Guides]][[Category:Code]]

String Parsing Optimization

2017-06-10T03:03:17Z

Strongbird: /* How does this relate to String Parsing? */

String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code. It will not tell you how to write clean or legible code, NOR will it teach you the fundamental markup of String Parsing. For information on those subjects, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

 

== Performance: Why should I care? ==

Performance is important for a number of reasons.
:Optimized code reduces the perceived latency of navigation in a MUCK. Doing so should be enjoyable on even the most sluggish of connections.
:Optimized code reduces the Flexible Survival server load, thus permitting us to provide more and more detailed user-visible content.
:Optimized code reduces the memory cost of programs and #dbrefs. In the case of a fatal memory spike or other unforeseen circumstances, the chances of services ceasing function are reduced when baseline memory is kept to a reasonable minimum.

=== How does this relate to String Parsing? ===

String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute

Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

== Conditionals ==

Conditionals are the heart, brain, and skeletal structure of the String Parsing body.

=== [if ][end if] ===
----
A basic [if ] statement is prone to some syntactic errors, but little in terms of optimization woes.

Always use the template [if [target] is <gender>] and [if time is <time of day/season>]. Do not use [if [target] = <gender>] or [if time = <time of day/season>]. Despite taking less space in the grand scheme of things, the 'is' function is specifically optimized for checking a target's gender and the time of day/season.
::'''[if [target] = <gender>]
::'''[if time = <time of day/season>]
::'''[if [target] is <gender>]
::'''[if time is <time of day/season>]

Do not check for integers with the '=' sign. This is a function designed to check a string. Use '==' instead.
Benchmarks have shown that checking directly for an integer is both faster and cleaner.
::'''[if stat cocks of [target] = 1]
::'''[if stat cocks of [target] == 1]

Avoid not statements when possible. For example, [if time is not night] is the same as [if time is day].
::'''[if time is not night]
::'''[if time is not day]
::'''[if time is day]
::'''[if time is night]
 

=== [if ][else][end if] ===
----
[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.

::'''[if time is winter]The large bear returned to his cave to hibernate.[else]The small fox jumped over the fence.[end if]

::'''The [if time is winter]large bear returned to his cave to hibernat[else]small fox jumped over the fenc[end if]e.

In the above example, repeated text has been removed from the [if ] statement itself and added as prefix and suffix to the code, respectively. This provides the exact same user-visible output with less characters and processing requirements.

::'''[if time is day]A woman in tight jeans and an unassuming blouse mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work.[else]A woman in tight jeans and an unassuming blouse would normally man the counter. However, she doesn't appear to be here right now.[end if]

::'''A woman in tight jeans and an unassuming blouse [if time is day]mans the counter. She's twirling a pen in her fingers, seemingly disinterested in her body of work[else]would normally man the counter. However, she doesn't appear to be here right now[end if].

See above. Repeated text is removed from the [if ] statement itself and added as prefix and suffix to the code, respectively.
 

=== [if ][else if ][else][end if] ===
----
[else if ] introduces further potential for code slowdown. Please read the following steps carefully to avoid that.

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest.[else if [player] is female]easily ignore the Skunk Girl's attempts to seduce you.[else]easily ignore the Skunk Girl's attempts to seduce you. Neuters 4ever![end if]

::'''You [if [player] is male]try not to grow aroused by the Skunk Girl's sumptuous body, whining in protest[else]easily ignore the Skunk Girl's attempts to seduce you[end if].[if [player] is neuter] Neuters 4ever![end if]

In the above example, a lengthy [if ][else if ][else][end if] statement is deconstructed into [if ][else][end if][if ][end if].

Converge the [else if ] and [else] statements into a single [else]. Move the neuter check into a separate [if ] statement at the end. Move the trailing periods in the [if ][else][end if] statement before the start of the neuter check.

::'''The [if time is morning]sun is rising, stirring all forms of life into motion[else if time is afternoon]sun is high, baking the earth with its furious light[else if time is evening]sun is starting to set, casting the land in long shadows[else]moon shines over the land[end if].

::'''The [if time is night]moon shines over the land[else if time is morning]sun is rising, stirring all forms of life into motion[else if time is evening]sun is starting to set, casting the land in long shadows[else]sun is high, baking the earth with its furious light[end if].

In the above example, a couple optimizations are made.

Place [if time is night] at the front. This is the longest period of time and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

=== [case ] ===
----
Case-statements are useful where lengthy [if ][else if ][end if] statements would result in redundancy.

::'''[case stat X of [target] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

::'''[case [stat X of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when 1]E[end when]

If something is valid parsing on its own, such as '[stat X of [target]]' and '[the mutation X of [target]]', use that, so the statement will only have to be parsed once instead of in every [when ]-statement.

::'''[if stat blah/bluh/bleh of [target] == 1]A[else if stat blah/bluh/bleh of [target] == 2]B[else if stat blah/bluh/bleh of [target] == 3]C[else if stat blah/bluh/bleh of [target] == 4]D[else if stat blah/bluh/bleh of [target] == 5]E[else]F[end if]

::'''[case [stat blah/bluh/bleh of [target]] ==][when (target) 1]A[end when][when (target) 2]B[end when][when (target) 3]C[end when][when (target) 4]D[end when][when (target) 5]E[end when][when 1]F[end when][end case]

In the above example, a complex [if ][else if ][end if] statement is optimized.

Convert the code to a basic case-statement. Since all comparisons are alike, remove them from their [when ] statements and append one to [case (target)]. Add brackets around 'stat blah/bluh of [player]' to avoid computing that in every [when ] statement.

== Randomization ==

The following functions display content at random. Input is separated by [or].

=== [one of][or][at random] ===
----
The standard [one of][or][at random] statement is prone to redundancy.

::'''Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

::'''Sometimes, a man's gotta man. [one of]Other [or]Some[at random]times, he doesn't.

In the above example, redundancy is nixed by moving a string shared by all inputs after [at random].

==== [with odds: ] ====

[with odds: ] allows you to simplify many longer [one of] statements.

::'''[one of]1[or]1[or]1[or]1[or]1[or]2[at random]

::'''[one of]1[or]2[with odds: 5 1]

or

::'''[one of]1[or]1[or]1[or]2[or]2[or]3[at random]

::'''[one of]1[or]2[or]3[with odds: 3 2 1]

=== [random x to y] ===
----
This function is more specialized than [one of][or][at random], lending itself well to optimization. Note that it only accepts numerical input (negatives included) and that 'y' should be greater than 'x'.

::'''[one of]1[or]2[or]3[or]4[or]5[or]6[at random]

::'''[random 1 to 6]

A complex [one of][or][at random] statement converted into a [random x to y] statement.

Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.

 
----
 

This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songbird's. Please only modify with either A), explicit permission to do so, or B), a fix for known factual inaccuracy / grammar errors.

[[Category:Guides]][[Category:Code]]

Writing Bounties

2016-12-11T01:40:03Z

Strongbird:

== Overview ==

Writing Bounties are bounties for submitting specific content. Submitting a scene that is approved for in-game usage will earn you the posted Mako bounty.

- You do not need to include string parsing in your submission.

- You must submit your scene via +request in the Building category.

Staff can and will edit your submissions as they see fit. Staff word on your submissions is final.

As of 05/04/2014, this is an experimental project to encourage community involvement in content creation.

== Posted Bounties ==

Bounties which are unclaimed and open to work.

'''Monsters

For information on writing these scenes, see the in-game helpfile 'help monster writing', as well as the wiki pages on [[Monster Maker#Victory and Defeat Messages|Victory and Defeat messages]] and [[Monster Writing Guide|Monster Writing]] (pages 4-6)

In addition, note that it is NOT necessary to contact the original authors for these bounties. These are old, public forms which require revision. Submissions for their improvement are welcome. You can also write only one scene per list item and leave the rest for another writer.

<pre>
8 Mako - Kemonomimi descriptions and TF message variants (4 for descs and 4 for TFs per monster)
Black Panther
Busty Cow
Cheetah (only TFs)
Corporate Cougar
Diamond Drake (only TFs)
Female Husky (only TFs)
Flame Leopard
Harbinger Lynx
Latex Snow Leopard
Liquid Pantheress
Lizard Girl (only TFs)
Plump Tigress (only TFs)
Saber-toothed Bard
Saber-toothed Soldier
Salamander Femme (only TFs)
Skink Skank
Small Felinoid
Stalking Tigress
White Unicorn Mare

8 Mako - Latex Snow Leopard Victory and oVictory

8 Mako - Panther Taur Victory and oVictory

12 Mako - Tanuki Victory, oVictory, and Defeat.
Although it is a dedication, a defeat in case it is spawned artificially would be welcome.
</pre>

'''Existing NPCs

<pre>
Alex the Zebra

5 Mako - Threesome scene with a cook
</pre>

<pre>
Bound Egyptian Mau

5 Mako - 69 with Mau

5 Mako - Player fucks vaginally
</pre>

<pre>
Obsidian the Shadow Dragon

5 Mako - Female player uses feeldoe to vaginally fuck Obsidian

5 Mako - Female/herm player uses double-dildo

5 Mako - Female/neuter player anally pegs Obsidian

5 Mako - Player gets anally pegged

5 Mako - Player uses Shared Dream Nanomagic for dream threesome with Obsidian and Violet the Blue Gryphon
</pre>

<pre>
Skunk Beast (NPC in [Library]: Research Room)

5 Mako - Player willfully submits for an extended scene of rough, brutalizing sex

5 Mako - Threesome with player, Doctor Hellen, and Skunk Beast in cage
</pre>

'''New NPCs

<pre>
NONE
</pre>

== Claimed Bounties ==

Bounties which have been claimed and are being worked on.

'''Monsters

<pre>
NONE
</pre>

'''Existing NPCs

<pre>
NONE
</pre>

'''New NPCs

<pre>
NONE
</pre>

== Completed Bounties ==

Bounties which have been completed, implemented, and their creators awarded.

'''Monsters

<pre>
8 Mako - Kemonomimi descriptions and TF message variants (4 for descs and 4 for TFs per monster)
Alpha Husky (only TFs) - by Arona
Blue Gryphon (only descs) - by Armel
Blue Gryphon (only TFs) - by Machi
Bunny Boy - by Machi
Cheetah (only descs) - by Armel
Chocolate Cow - by Machi
Dandy Peacock - by Sherri
Diamond Drake (only descs) - by Armel
Donkey Boy - by Machi
Farm Hen - by Machi
Fox Boy - by Machi
Fox Girl - by Machi
German Shepherd - by Machi
Honey Bear - by Machi
House Mouse - by Arona
Lizard Girl (only descs) - by Armel
Otter - by Machi
Plump Tigress (only descs) - by Armel
Salamander Femme (only descs) - by Armel
Shadow Vixen - by Machi
Skunk Girl - by Arona
White Siberian Tiger - by Arona
Wolf Beast - by Machi

4 Mako - Anubis Servant Defeat
by Jade

8 Mako - Blue Gryphon Victory and oVictory
by Jade

1 Mako - Coatl Servant Defeat
by Menil

5 Mako - Female Husky male Defeat and Victory.
Alternate descriptions/TFs for specific genders and the Female Husky/demeanor:Alpha local stat
by Todde

8 Mako - Goo Girl Victory and oVictory
by Lochlan

2 Mako - House Cat Victory and oVictory
by Menil

8 Mako - Hyena Herm Victory and oVictory
by Jade

12 Mako - Rabid Beaver Victory, oVictory, and Defeat
by Armel

15 Mako - Rubber Balls complete rewrite
by Jade

50 Mako - Vixen Nurse port from the FS Singleplayer (paid out of Miranai's pocket)
by Lila

4 Mako - Wild Cannibal Defeat
by Acetyl and Jade
4 Mako awarded to each for full-length content

2 Mako - Wolf Beast Victory and oVictory
by Prios and Skade
2 Mako awarded to each for full-length content

4 Mako - Zebra Defeat
by Jade
</pre>

'''Existing NPCs

<pre>
Alex the Zebra

5 Mako - Frotting
by Foxheart
</pre>

<pre>
Chenoa the Aassahke Female

5 Mako - Player gives cunnilingus
by Jade

5 Mako - Player receives blowjob
by Jade
</pre>

<pre>
Chris the Alpha Husky

5 Mako - Player receives anilingus
by Foxheart
</pre>

<pre>
Doctor Lissal the Skunk Girl

5 Mako - Player gives cunnilingus
by Jade
</pre>

<pre>
Ellie the Latex Fox

5 Mako - Shower sex
by Jade

10 Mako - Glamour Slammer scene
by Foxheart
</pre>

<pre>
Husky Den Orgy

5 Mako - Sex toy use scene
by Jade

5 Mako - Tentacle Nanomagic variation for husky orgy
by Jade
</pre>

<pre>
Obsidian the Shadow Dragon

5 Mako - Player uses Illusion Nanomagic to sexually pleasure
by Foxheart
</pre>

<pre>
Sarah the Female Husky

5 Mako - Player receives blowjob
by Jade
</pre>

'''New NPCs

<pre>
25 Mako - Anton the Bull. NPC for [Eureka City]: The Cow Barn
Base 15 Mako reward for introduction, description, scent, and one initial sex scene.
5 Mako rewarded per additional scene.
by Skade

15 Mako - Domori the Chocolate Lab. NPC for [Seelie Sweets Kennels]: West Wing
A size 6 masculine herm and the leader of his group.
His personality is teasing; not aggressive, but reassured and very openly carnal in his desires.
Base 15 Mako reward for introduction, description, scent, and one initial sex scene.
5 Mako rewarded per additional scene.
by Adren
</pre>

Writing Bounties

2016-12-10T23:49:52Z

Strongbird:

== Overview ==

Writing Bounties are bounties for submitting specific content. Submitting a scene that is approved for in-game usage will earn you the posted Mako bounty.

- You do not need to include string parsing in your submission.

- You must submit your scene via +request in the Building category.

Staff can and will edit your submissions as they see fit. Staff word on your submissions is final.

As of 05/04/2014, this is an experimental project to encourage community involvement in content creation.

== Posted Bounties ==

Bounties which are unclaimed and open to work.

'''Monsters

For information on writing these scenes, see the in-game helpfile 'help monster writing', as well as the wiki pages on [[Monster Maker#Victory and Defeat Messages|Victory and Defeat messages]] and [[Monster Writing Guide|Monster Writing]] (pages 4-6)

In addition, note that it is NOT necessary to contact the original authors for these bounties. These are old, public forms which require revision. Submissions for their improvement are welcome. You can also write only one scene per list item and leave the rest for another writer.

<pre>
8 Mako - Kemonomimi descriptions and TF message variants (4 for descs and 4 for TFs per monster)
Black Panther
Busty Cow
Cheetah (only TFs)
Corporate Cougar
Diamond Drake (only TFs)
Female Husky (only TFs)
Flame Leopard
Harbinger Lynx
Latex Snow Leopard
Liquid Pantheress
Lizard Girl (only TFs)
Plump Tigress (only TFs)
Saber-toothed Bard
Saber-toothed Soldier
Salamander Femme (only TFs)
Skink Skank
Small Felinoid
Stalking Tigress
White Siberian Tiger
White Unicorn Mare

8 Mako - Latex Snow Leopard Victory and oVictory

8 Mako - Panther Taur Victory and oVictory

12 Mako - Tanuki Victory, oVictory, and Defeat.
Although it is a dedication, a defeat in case it is spawned artificially would be welcome.
</pre>

'''Existing NPCs

<pre>
Alex the Zebra

5 Mako - Threesome scene with a cook
</pre>

<pre>
Bound Egyptian Mau

5 Mako - 69 with Mau

5 Mako - Player fucks vaginally
</pre>

<pre>
Obsidian the Shadow Dragon

5 Mako - Female player uses feeldoe to vaginally fuck Obsidian

5 Mako - Female/herm player uses double-dildo

5 Mako - Female/neuter player anally pegs Obsidian

5 Mako - Player gets anally pegged

5 Mako - Player uses Shared Dream Nanomagic for dream threesome with Obsidian and Violet the Blue Gryphon
</pre>

<pre>
Skunk Beast (NPC in [Library]: Research Room)

5 Mako - Player willfully submits for an extended scene of rough, brutalizing sex

5 Mako - Threesome with player, Doctor Hellen, and Skunk Beast in cage
</pre>

'''New NPCs

<pre>
NONE
</pre>

== Claimed Bounties ==

Bounties which have been claimed and are being worked on.

'''Monsters

<pre>
NONE
</pre>

'''Existing NPCs

<pre>
NONE
</pre>

'''New NPCs

<pre>
NONE
</pre>

== Completed Bounties ==

Bounties which have been completed, implemented, and their creators awarded.

'''Monsters

<pre>
8 Mako - Kemonomimi descriptions and TF message variants (4 for descs and 4 for TFs per monster)
Alpha Husky (only TFs) - by Arona
Blue Gryphon (only descs) - by Armel
Blue Gryphon (only TFs) - by Machi
Bunny Boy - by Machi
Cheetah (only descs) - by Armel
Chocolate Cow - by Machi
Dandy Peacock - by Sherri
Diamond Drake (only descs) - by Armel
Donkey Boy - by Machi
Farm Hen - by Machi
Fox Boy - by Machi
Fox Girl - by Machi
German Shepherd - by Machi
Honey Bear - by Machi
House Mouse - by Arona
Lizard Girl (only descs) - by Armel
Otter - by Machi
Plump Tigress (only descs) - by Armel
Salamander Femme (only descs) - by Armel
Shadow Vixen - by Machi
Skunk Girl - by Arona
Wolf Beast - by Machi

4 Mako - Anubis Servant Defeat
by Jade

8 Mako - Blue Gryphon Victory and oVictory
by Jade

1 Mako - Coatl Servant Defeat
by Menil

5 Mako - Female Husky male Defeat and Victory.
Alternate descriptions/TFs for specific genders and the Female Husky/demeanor:Alpha local stat
by Todde

8 Mako - Goo Girl Victory and oVictory
by Lochlan

2 Mako - House Cat Victory and oVictory
by Menil

8 Mako - Hyena Herm Victory and oVictory
by Jade

12 Mako - Rabid Beaver Victory, oVictory, and Defeat
by Armel

15 Mako - Rubber Balls complete rewrite
by Jade

50 Mako - Vixen Nurse port from the FS Singleplayer (paid out of Miranai's pocket)
by Lila

4 Mako - Wild Cannibal Defeat
by Acetyl and Jade
4 Mako awarded to each for full-length content

2 Mako - Wolf Beast Victory and oVictory
by Prios and Skade
2 Mako awarded to each for full-length content

4 Mako - Zebra Defeat
by Jade
</pre>

'''Existing NPCs

<pre>
Alex the Zebra

5 Mako - Frotting
by Foxheart
</pre>

<pre>
Chenoa the Aassahke Female

5 Mako - Player gives cunnilingus
by Jade

5 Mako - Player receives blowjob
by Jade
</pre>

<pre>
Chris the Alpha Husky

5 Mako - Player receives anilingus
by Foxheart
</pre>

<pre>
Doctor Lissal the Skunk Girl

5 Mako - Player gives cunnilingus
by Jade
</pre>

<pre>
Ellie the Latex Fox

5 Mako - Shower sex
by Jade

10 Mako - Glamour Slammer scene
by Foxheart
</pre>

<pre>
Husky Den Orgy

5 Mako - Sex toy use scene
by Jade

5 Mako - Tentacle Nanomagic variation for husky orgy
by Jade
</pre>

<pre>
Obsidian the Shadow Dragon

5 Mako - Player uses Illusion Nanomagic to sexually pleasure
by Foxheart
</pre>

<pre>
Sarah the Female Husky

5 Mako - Player receives blowjob
by Jade
</pre>

'''New NPCs

<pre>
25 Mako - Anton the Bull. NPC for [Eureka City]: The Cow Barn
Base 15 Mako reward for introduction, description, scent, and one initial sex scene.
5 Mako rewarded per additional scene.
by Skade

15 Mako - Domori the Chocolate Lab. NPC for [Seelie Sweets Kennels]: West Wing
A size 6 masculine herm and the leader of his group.
His personality is teasing; not aggressive, but reassured and very openly carnal in his desires.
Base 15 Mako reward for introduction, description, scent, and one initial sex scene.
5 Mako rewarded per additional scene.
by Adren
</pre>