v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing Syndrome examples

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

If you are creating a redirect to the current version's page, do not use any namespace. For example: use #REDIRECT [[Cat]], not #REDIRECT [[Main:Cat]] or #REDIRECT [[cv:Cat]]. See DF:Versions for more information.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 19: Line 19:
 
Note that syndromes applied in this manner will only be added to creatures when they are loaded in fortress or adventure mode, as secretions aren't currently simulated in world generation or the like.  
 
Note that syndromes applied in this manner will only be added to creatures when they are loaded in fortress or adventure mode, as secretions aren't currently simulated in world generation or the like.  
  
Of course, you can also add a <code>[[Syndrome#Creature effect tokens|PROB]]</code> value to the syndrome's various effects to determine how likely they are to actually manifest, which could be useful if you want a particular type of creature to only occasionally appear with a special ability/curse/disease/immunity/etc (as an alternative to messing around with extra [[Creature_token#CASTE|castes]]). Make sure to add at least one guaranteed permanent syndrome effect - such as one of the dummy examples shown [[Interaction_examples#Syndromes with no effect|here]], but with no <code>END</code> specified - to prevent the syndrome from being reapplied undesirably (which can occur when the secreted coating is removed and replaced by a new secretion), as this would give creatures who initially failed the <code>PROB</code> check another chance to pass it. Having a permanent effect in place prevents this from happening as reinfection cannot occur before a syndrome has ended fully.
+
Of course, you can also add a [[Syndrome#Creature effect tokens|PROB]] value to the syndrome's various effects to determine how likely they are to actually manifest, which could be useful if you want a particular type of creature to only occasionally appear with a special ability/curse/disease/immunity/etc (as an alternative to messing around with extra [[Creature_token#CASTE|castes]]). Make sure to add at least one guaranteed permanent syndrome effect - such as one of the dummy examples shown [[Interaction_examples#Syndromes with no effect|here]], but with no END specified - to prevent the syndrome from being reapplied undesirably (which can occur when the secreted coating is removed and replaced by a new secretion), as this would give creatures who initially failed the PROB check another chance to pass it. Having a permanent effect in place prevents this from happening as reinfection cannot occur before a syndrome has ended fully.
  
Expanding on the above, this one-off opportunity to develop a certain syndrome effect can be turned into a recurring event by adding an <code>END</code> duration of your choice to the guaranteed dummy effect (henceforth referred to as the 'inhibitor'). For example, you might want to give a particular creature species the opportunity to evolve into another creature once every [[time|month]], with a 1/100 chance of the [[Syndrome#CE_BODY_TRANSFORMATION|transformation]] manifesting: this could be implemented as a secretion-applied syndrome with a <code>PROB:1</code> transformation effect and an <code>END:33600</code> inhibitor.
+
Expanding on the above, this one-off opportunity to develop a certain syndrome effect can be turned into a recurring event by adding an END duration of your choosing to the guaranteed dummy effect (henceforth referred to as the 'inhibitor'). For example, you might want to give a particular creature species the opportunity to evolve into another creature once every [[time|month]], with a 1/100 chance of the [[Syndrome#CE_BODY_TRANSFORMATION|transformation]] manifesting: this could be implemented as a secretion-applied syndrome with a <code>PROB:1</code> transformation effect and an <code>END:33600</code> inhibitor.
 
 
This can also be used to impose delays between the active phase of particular syndrome effects. For example, say you want to give your creature an intermittently activating regenerative ability: you could give it a secretion-derived syndrome providing the requisite [[Syndrome#Healing_Effects|healing effects]] with their <code>END</code> set to X, alongside an 'inhibitor' effect with an <code>END</code> set to X+Y, where Y is the duration of the delay.
 
  
 
==Stat-modifying syndromes==
 
==Stat-modifying syndromes==

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)

This page is a member of 1 hidden category: