Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[nullBolt]

Also posted on the Modding forum.

One of the big parts of DF's popularity is how moddable it is, so these tokens don't even have to be implemented with anything in the base game, just there so people can edit it. Post all your token suggestions here and I'll compile them into one big list. Please include the category of your token before you post it so I can easily sort them to be read through.

Post them in the following format:
Token Type
[TOKEN]: What this token would do. Why this token should exist.

[nullBolt]

Token Suggestions

Spoiler: Creature Tokens (click to show/hide)

[BUTCHERABLE]: Explicitly states a caste as butcherable, overriding everything else. This would allow for greater control over what does and doesn't get butchered, including making cannibalistic entities.

Spoiler: Entity Tokens (click to show/hide)

[ADDITIONAL_SECRET:CLASS]-Allows members of the entity to pursue and study other secrets. Multiple entries allowed.
[ARMOR:x] Where x is how much armor the soldiers in that civ will wear. 1 would be what goblins wear for the most part now, 8 or something would be full set with mail shirt, greaves, boots, etc.
[CAVERN_ACTIVE:MINLAYER:MAXLAYER]-Allows a civ to travel or settle (if the appropriate BIOME tag is in place) underground. Values default to 0:0.
[COMMON_MATERIAL:CLASS]
[COMMON_PLANT:CLASS]
[CRAFTING:x] Where x is how well a civ can craft anything at all. 1 would be the basic item, 5 would be masterpiece.
[CULT_WORSHIP:TYPE:OBJECT]-What an entity, if it is a cult, will worship. Valid types include CREATURE, CREATURE_CLASS, SYNDROME_CLASS (used for vampires,) DEITY, FORCE, and SPHERE. If DEITY is chosen, the last value is a sphere. If FORCE is chosen, the last value is a biome. Multiple entries allowed.
[DOMESTICATED_CREATURE_CLASS:CREATURE_CLASS]: All creatures of said class start off as domesticated by this civ. Similar to dwarves and [COMMON_DOMESTIC]. Would allow the removal of those tags and allow the introduction of stuff like entities who only domesticate reptiles.
[ENTITY_CLASS:CLASS]
[ETHIC:CHILD_LABOR:REACTION]-Player forts from civs with ACCEPTABLE for this behavior will automatically have child-labor enabled. Should the player enable it, or disable it, in spite of his civ's ethics, his citizens may react adversely.
[INITIAL_SECRET:CLASS]-If the entity is a splinter-group with the PURSUE_SECRET cause, it can be formed to pursue secrets with this class. Multiple entries are allowed.
[NO_INTERACTION]-The entity keeps to itself, never initiating contact with another. Overrides SENDS_CARAVANS.
[NOMADIC]-Entity lives in camps, moving from place to place, in accordance with weather, food sources, etc. Overrides DEFAULT_SITE_TYPE and its ilk.
[RELIGION_FORCE_APPEARANCE:CREATURE:CASTE:FREQ]: Forces gods of this civilization to pick this creature / caste of creature for appearance. Allows for certain civilizations that would only worship creatures of the given type.
[RELIGION_PREVENT_APPEARANCE:CREATURE:CASTE]: Prevents any gods of this civilization from picking this creature / caste as it's appearance. Allows preventing high-population castes from appearing constantly as gods.
[SENDS_CARAVANS]
[SIEGE_TIME:MINTIME:MAXTIME]-The time, in ticks, a civ will spend before ending a siege. Defaults to 201600:403200.
[SPLINTER:CLASS:CAUSE]-Allows the entity to form by separating from an entity with the appropriate entity class, for the given cause. Valid causes include INSURRECTION, SECESSION, CRIME, LIFESTYLE, PURSUE_SECRET, RELIGIOUS_DIFFERENCE, RELIGIOUS_INSURRECTION, RELIGIOUS_SECESSION, and CULT. Multiple tags of this type are allowed.
[SPLINTER_HIDDEN]-If the entity is a splinter-group, dwelling within another entity, it will strive to hide its existence, acting as inconspicuous as its values allow, until circumstances force it to reveal itself.
[SPLINTER_REFUGE:PLACE:TYPE (if ABANDONED_SITE or NEW_SITE chosen)]-Where the entity goes, upon splintering. Valid values include SEWER, DWELLING, ABANDONED_SITE, NEW_SITE, WILDERNESS, and NOWHERE. Multiple entries are allowed.
[TAVERN]-Allows member of the entity to build taverns.

Spoiler: Interaction Tokens (click to show/hide)

[INTERACTION_CLASS:CLASS]

Spoiler: Cerapter's Food Tokens (click to show/hide)

Creature Tokens
[SUSTENANCE:ARG1:ARG2:ARG3:ARG4:ARG5:ARG6]

• Defines some sort of food or drink that the creature can or must consume to survive (or just to enjoy life, or to function normally).
• ARG1: Can be VITAL, IMPORTANT, ENJOYMENT, PREFERENCE.
• ARG2: Can be FOOD or DRINK.
• ARG3: Can be ANY, ALCOHOL, ALCOHOL_CREATURE, ALCOHOL_PLANT, CREATURE, PLANT, ITEM.
• ARG4: If you chose CREATURE, PLANT or ITEM before, then now you type in an ID. In case of ITEM, this can also be an item token. Otherwise NONE.
• ARG5: Previous whatever's any material. If you previously chose ITEM, then this just defines what material should it be made of. Otherwise NONE.
• ARG6: Number. This will be the amount of ticks after which the creature will carve for the sustenance item. Going over the allocated time without consuming the given thing will make the creature "unsatisfied" then "very unsatisfied". A creature's sustenance demands can be checked in the health screen. "(Very) hungry for X" means that the creature requires X food, and "(Very) thirsty for X" means the creature requires X drink.

Example usage:
[SUSTENANCE:VITAL:FOOD:ANY:NONE:NONE:50400]
The creature require food of any type to exist at all. 50400 ticks is roughly 1.5 months. In other words, the creature will require two pieces of food a season, similarly to how dwarves behave currently.

[SUSTENANCE:VITAL:DRINK:ANY:NONE:NONE:50400]
Same as above, but with drinks.

[SUSTENANCE:IMPORTANT:DRINK:ALCOHOL_PLANT:NONE:NONE:33600]
This creature will work slower if it doesn't get some alcohol beverage every month. It will however only accept alcohol made from plants.

[SUSTENANCE:ENJOYMENT:FOOD:CREATURE:ELF:FAT:16800]
This creature derives enjoyment from eating elven meat. If the creature has FOOD as VITAL, but the food can be anything, this creature will choose elven meat above any other type of food, as it satisfies the vitality requirement AND gives the creature a happy thought.

Also note how this has less time than the vital food part. This means that the creature will go out of their way, even if they're not hungry, just to eat this type of food every half a month. Creatures with low self-control will give in the temptation, and might get fat this way.

[SUSTENANCE:PREFERENCE:FOOD:PLANT:SOFT_WHEAT:MILL:67200]
This creature prefers to eat soft wheat flour if it's available above all else (assuming there is nothing that is marked as ENJOYMENT for the creature in the fort), but it does not derive any satisfaction from it.
Also note the increased time. This makes it so that the creature will ONLY prefer to eat soft wheat flour every second month.

[SUSTENANCE:ENJOYMENT:DRINK:ITEM:ANVIL:STEEL:1200]
This creature derives enjoyment from drinking a steel anvil every day.

Entity Tokens
[RECIPE:ARG1:ARG2:ARG3:ARG4]

• Defines a recipe that the members of this civilisation can cook up. See below for actually defining recipes.
• ARG1: FOOD or DRINK. Food is made in the kitchen, drink at the still.
• ARG2:ARG3:ARG4: singular name, plural name, and adjective, respectively.

[RECIPE_SKILL_REQUIRED:ARG1:ARG2]

• Adds a skill requirement to the recipe.
• ARG1: Skill token.
• ARG2: Number. Denotes the minimal level of the above skill required.

[RECIPE_ADD_INGREDIENT:ARG1:ARG2:ARG3:ARG4:ARG5]

• Adds an ingredient to the recipe.
• ARG1: Can be VITAL or EXTRA. Denotes whether the ingredient is absolutely required, or if it can be left out.
• ARG2: Can be ANY, ALCOHOL, ALCOHOL_CREATURE, ALCOHOL_PLANT, CREATURE, PLANT, ITEM or RECIPE.
• ARG3: If you chose CREATURE, PLANT, or ITEM before, then now you type in an ID. In case of ITEM, this can also be an item token. In case of RECIPE, type in the singular name of the recipe you want to use. Otherwise NONE.
• ARG4: Previous whatever's any material. If you previously chose ITEM, then this just defines what material should it be made of. No need when using RECIPE. Otherwise NONE.
• ARG5: Number. The amount of the above ingredient required.

Example usage:

[RECIPE:FOOD:strange soup:strange soups:strange soup]
    [RECIPE_SKILL_REQUIRED:COOKING:1]
    [RECIPE_ADD_INGREDIENT:VITAL:ALCOHOL:NONE:NONE:5]
    [RECIPE_ADD_INGREDIENT:VITAL:ITEM:ANVIL:STEEL:1]
    [RECIPE_ADD_INGREDIENT:EXTRA:ANY:NONE:NONE:10]
This would result in a standard-issue Sodexo soup, but dwarven style.

[RECIPE:DRINK:lumberjack tea,lumberjack teas,lumberjack tea]
    [RECIPE_SKILL_REQUIRED:COOKING:1]
    [RECIPE_SKILL_REQUIRED:BREWING:5]
    [RECIPE_SKILL_REQUIRED:WOODCUTTING:10]
    [RECIPE_ADD_INGREDIENT:VITAL:ALCOHOL:NONE:NONE:5]
    [RECIPE_ADD_INGREDIENT:VITAL:RECIPE:strange soup:NONE:1]
    [RECIPE_ADD_INGREDIENT:VITAL:PLANT:OAK:WOOD:50]
This would result in a tasty tea that uses the previous soup, too.

[nullBolt]

Creature Token
[DOMESTICABLE:CLASS]: Gives the creature a domestication class that entities can reference. If, say, I want goblins to be able to domesticate giant spiders in world gen but no one else, I'd give them [DOMESTICATED:GOBLIN] and give the giant spiders [DOMESTICABLE:GOBLIN]. Similar to [COMMON_DOMESTIC] in this regard.

Entity Token
[DOMESTICATED:CLASS]: All creatures of said class start off as domesticated by this civ. Similar to dwarves and [COMMON_DOMESTIC].

[Urlance Woolsbane]

Interaction Tokens
[INTERACTION_CLASS:CLASS]
Entity Tokens
[SENDS_CARAVANS]
[NO_INTERACTION]-The entity keeps to itself, never initiating contact with another. Overrides SENDS_CARAVANS.
[TAVERN]-Allows member of the entity to build taverns.
[NOMADIC]-Entity lives in camps, moving from place to place, in accordance with weather, food sources, etc. Overrides DEFAULT_SITE_TYPE and its ilk.
[COMMON_MATERIAL:CLASS]
[COMMON_PLANT:CLASS]
[CAVERN_ACTIVE:MINLAYER:MAXLAYER]-Allows a civ to travel or settle (if the appropriate BIOME tag is in place) underground. Values default to 0:0.
[SIEGE_TIME:MINTIME:MAXTIME]-The time, in ticks, a civ will spend before ending a siege. Defaults to 201600:403200.
[ETHIC:CHILD_LABOR:REACTION]-Player forts from civs with ACCEPTABLE for this behavior will automatically have child-labor enabled. Should the player enable it, or disable it, in spite of his civ's ethics, his citizens may react adversely.
[ENTITY_CLASS:CLASS]
[SPLINTER:CLASS:CAUSE]-Allows the entity to form by separating from an entity with the appropriate entity class, for the given cause. Valid causes include INSURRECTION, SECESSION, CRIME, LIFESTYLE, PURSUE_SECRET, RELIGIOUS_DIFFERENCE, RELIGIOUS_INSURRECTION, RELIGIOUS_SECESSION, and CULT. Multiple tags of this type are allowed.
[SPLINTER_REFUGE:PLACE:TYPE (if ABANDONED_SITE or NEW_SITE chosen)]-Where the entity goes, upon splintering. Valid values include SEWER, DWELLING, ABANDONED_SITE, NEW_SITE, WILDERNESS, and NOWHERE. Multiple entries are allowed.
[SPLINTER_HIDDEN]-If the entity is a splinter-group, dwelling within another entity, it will strive to hide its existence, acting as inconspicuous as its values allow, until circumstances force it to reveal itself.
[CULT_WORSHIP:TYPE:OBJECT]-What an entity, if it is a cult, will worship. Valid types include CREATURE, CREATURE_CLASS, SYNDROME_CLASS (used for vampires,) DEITY, FORCE, and SPHERE. If DEITY is chosen, the last value is a sphere. If FORCE is chosen, the last value is a biome. Multiple entries allowed.
[INITIAL_SECRET:CLASS]-If the entity is a splinter-group with the PURSUE_SECRET cause, it can be formed to pursue secrets with this class. Multiple entries are allowed.
[ADDITIONAL_SECRET:CLASS]-Allows members of the entity to pursue and study other secrets. Multiple entries allowed.

[Cerapter]

Creature Tokens
[SUSTENANCE:ARG1:ARG2:ARG3:ARG4:ARG5:ARG6]

• Defines some sort of food or drink that the creature can or must consume to survive (or just to enjoy life, or to function normally).
• ARG1: Can be VITAL, IMPORTANT, ENJOYMENT, PREFERENCE.
• ARG2: Can be FOOD or DRINK.
• ARG3: Can be ANY, ALCOHOL, ALCOHOL_CREATURE, ALCOHOL_PLANT, CREATURE, PLANT, ITEM.
• ARG4: If you chose CREATURE, PLANT or ITEM before, then now you type in an ID. In case of ITEM, this can also be an item token. Otherwise NONE.
• ARG5: Previous whatever's any material. If you previously chose ITEM, then this just defines what material should it be made of. Otherwise NONE.
• ARG6: Number. This will be the amount of ticks after which the creature will carve for the sustenance item. Going over the allocated time without consuming the given thing will make the creature "unsatisfied" then "very unsatisfied". A creature's sustenance demands can be checked in the health screen. "(Very) hungry for X" means that the creature requires X food, and "(Very) thirsty for X" means the creature requires X drink.

Example usage:

Spoiler (click to show/hide)

[SUSTENANCE:VITAL:FOOD:ANY:NONE:NONE:50400]
The creature require food of any type to exist at all. 50400 ticks is roughly 1.5 months. In other words, the creature will require two pieces of food a season, similarly to how dwarves behave currently.

[SUSTENANCE:VITAL:DRINK:ANY:NONE:NONE:50400]
Same as above, but with drinks.

[SUSTENANCE:IMPORTANT:DRINK:ALCOHOL_PLANT:NONE:NONE:33600]
This creature will work slower if it doesn't get some alcohol beverage every month. It will however only accept alcohol made from plants.

[SUSTENANCE:ENJOYMENT:FOOD:CREATURE:ELF:FAT:16800]
This creature derives enjoyment from eating elven meat. If the creature has FOOD as VITAL, but the food can be anything, this creature will choose elven meat above any other type of food, as it satisfies the vitality requirement AND gives the creature a happy thought.

Also note how this has less time than the vital food part. This means that the creature will go out of their way, even if they're not hungry, just to eat this type of food every half a month. Creatures with low self-control will give in the temptation, and might get fat this way.

[SUSTENANCE:PREFERENCE:FOOD:PLANT:SOFT_WHEAT:MILL:67200]
This creature prefers to eat soft wheat flour if it's available above all else (assuming there is nothing that is marked as ENJOYMENT for the creature in the fort), but it does not derive any satisfaction from it.
Also note the increased time. This makes it so that the creature will ONLY prefer to eat soft wheat flour every second month.

[SUSTENANCE:ENJOYMENT:DRINK:ITEM:ANVIL:STEEL:1200]
This creature derives enjoyment from drinking a steel anvil every day.

Entity Tokens
[RECIPE:ARG1:ARG2:ARG3:ARG4]

• Defines a recipe that the members of this civilisation can cook up. See below for actually defining recipes.
• ARG1: FOOD or DRINK. Food is made in the kitchen, drink at the still.
• ARG2:ARG3:ARG4: singular name, plural name, and adjective, respectively.

[RECIPE_SKILL_REQUIRED:ARG1:ARG2]

• Adds a skill requirement to the recipe.
• ARG1: Skill token.
• ARG2: Number. Denotes the minimal level of the above skill required.

[RECIPE_ADD_INGREDIENT:ARG1:ARG2:ARG3:ARG4:ARG5]

• Adds an ingredient to the recipe.
• ARG1: Can be VITAL or EXTRA. Denotes whether the ingredient is absolutely required, or if it can be left out.
• ARG2: Can be ANY, ALCOHOL, ALCOHOL_CREATURE, ALCOHOL_PLANT, CREATURE, PLANT, ITEM or RECIPE.
• ARG3: If you chose CREATURE, PLANT, or ITEM before, then now you type in an ID. In case of ITEM, this can also be an item token. In case of RECIPE, type in the singular name of the recipe you want to use. Otherwise NONE.
• ARG4: Previous whatever's any material. If you previously chose ITEM, then this just defines what material should it be made of. No need when using RECIPE. Otherwise NONE.
• ARG5: Number. The amount of the above ingredient required.

Example usage:

Spoiler (click to show/hide)

[RECIPE:FOOD:strange soup:strange soups:strange soup]
    [RECIPE_SKILL_REQUIRED:COOKING:1]
    [RECIPE_ADD_INGREDIENT:VITAL:ALCOHOL:NONE:NONE:5]
    [RECIPE_ADD_INGREDIENT:VITAL:ITEM:ANVIL:STEEL:1]
    [RECIPE_ADD_INGREDIENT:EXTRA:ANY:NONE:NONE:10]
This would result in a standard-issue Sodexo soup, but dwarven style.

[RECIPE:DRINK:lumberjack tea,lumberjack teas,lumberjack tea]
    [RECIPE_SKILL_REQUIRED:COOKING:1]
    [RECIPE_SKILL_REQUIRED:BREWING:5]
    [RECIPE_SKILL_REQUIRED:WOODCUTTING:10]
    [RECIPE_ADD_INGREDIENT:VITAL:ALCOHOL:NONE:NONE:5]
    [RECIPE_ADD_INGREDIENT:VITAL:RECIPE:strange soup:NONE:1]
    [RECIPE_ADD_INGREDIENT:VITAL:PLANT:OAK:WOOD:50]
This would result in a tasty tea that uses the previous soup, too.

[Deboche]

I like all the tokens so far. I don't know exactly how tokens work but in the same vein, something like:

[ARMOR:x] Where x is how much armor the soldiers in that civ will wear. 1 would be what goblins wear for the most part now, 8 or something would be full set with mail shirt, greaves, boots, etc.

[CRAFTING:x] Where x is how well a civ can craft anything at all. 1 would be the basic item, 5 would be masterpiece.

[nullBolt]

Added everything to the second post.

Cerapter, you get your own spoiler. T_T

[Tiler]

I had a few token suggestions that I think would seriously open up the ability to create workable interactions. I do not believe they would require much work or testing to implement.

http://www.bay12forums.com/smf/index.php?topic=155167.0

[Cerapter]

Added everything to the second post.

Cerapter, you get your own spoiler. T_T

Thank you <3

But really, if we're doing tokens, I'm not going to do rigid ones like currently in the RAWs. I want flexibility!

[SixOfSpades]

For when the Lighting arc kicks in:

[EMITS_LIGHT:BRIGHTNESS:HORIZ_ARC:VERT_ARC1:VERT_ARC2:COLOR1:COLOR2:COLOR3]

BRIGHTNESS: The overall power of the light source, in lumens. Perceived brightness decreases with distance, ambient illumination decreases with the square of the distance.
HORIZ_ARC: The horizontal width of the light beam, in degrees. The direction of the light is either selected upon construction (if the light source is built in place) or fluid (if the light is being held/operated by a creature).
VERT_ARC1: The lower vertical limit of the light source's beam, in degrees, with 0 being straight down.
VERT_ARC2: The upper vertical limit of the light source's beam, in degrees, with 180 being straight up.
COLOR1: The primary hue of the light emitted, expressed in nanometers (400nm = deep violet, 700nm= dark red).
COLOR2 / COLOR3: Entirely optional, used only in light sources of multiple colors, a la through colored glass or gems. Multiple colors, if present, are weighted equally.

So a simple hand-held torch would be [EMITS_LIGHT:450:360:5:180:590],
a mining helmet would be [EMITS_LIGHT:500:90:45:135:570],
and a gem lantern (with a lens of garnets, peridots, and aquamarines) hanging from the ceiling with a mirrored reflector just above would be [EMITS_LIGHT:800:360:0:80:660:545:490].

[Abadrausar]

RFC:  generic variations

Procedural generation in Dwarf Fortress (DF) and modding possibilities are both leading in their respective categories, this makes DF deep and immersive.

We should have generic variations for each one of the DF objects (Ammo, Armor, Building, Body, Body_detail_plan, Bodygloss, Creature, Variation, Entity, Item, Interaction, Language, Material, Plant, Position, Syndrome, Tissue, Tool, Trap, Unit, Weapon, World, ...)
Why? better reuse of prototypes in modding, and almost all the necessary code is already there because nothing in the contextual lexical substitutions done by the variations is specifically and inherently vinculated to the creature prototypes.
If we are going this way, a syntax modification for the variations to indicate the kind of object that is being variated is also proposed.

Some examples of what we could do implementing this proposal:

Code: [Select]

[OBJECT:VARIATION]
[VARIATION:PLANT:SPROUTING]
[REMOVE_TAG:NAME]
[REMOVE_TAG:NAME_PLURAL]
[REMOVE_TAG:ADJ]
[CONVERT_TAG]
[MASTER:GROWDUR]
[TARGET:300]
[REPLACEMENT:60]
[CONVERT_TAG]
[MASTER:GROWDUR]
[TARGET:500]
[REPLACEMENT:100]
[CONVERT_TAG]
[MASTER:CLUSTERSIZE]
[TARGET:5]
[REPLACEMENT:1]
This could be used as:

Code: [Select]

[PLANT:SPROUTING_MUSHROOM_HELMET_PLUMP]
[COPY_TAGS_FROM:PLANT:MUSHROOM_HELMET_PLUMP]
[APPLY_VARIATION:PLANT:SPROUTING]
[REMOVE_TAG:SEED]
[APPLY_CURRENT_VARIATION]
[GO_TO_END]
[SELECT_NESTED:ALL]
[GO_TO_START]
        [SEED:plump helmet sproutings spawn:plump helmet sproutings spawn:4:0:1:LOCAL_PLANT_MAT:SEED]
[ALL_NAMES:plump helmet sproutings]


More of a modification of tokens that already exist than adding new tokens but well...

[Abadrausar]

Oops! double post.

[Button]

Spoiler: Material tokens (click to show/hide)

[COOKED_VALUE:X]. Sometimes, something is much tastier cooked than raw. Useful for steering dwarves towards food that's nice to eat raw, like fruits or cheese, instead of something that's edible raw but you'd rather they left alone until it was cooked, like fish.


[STARVATION_FOOD]. Dwarves will gather, plant, and eat this, but only if there's nothing else available that's not also a STARVATION_FOOD. You might want to further differentiate this into separate tokens for [STARVATION_FOOD_RAW] (won't eat it raw unless they're starving) and [STARVATION_FOOD_COOKED] (won't eat it cooked unless they're starving), with either token being present also carrying the planting/gathering implications.

This frees modders up to add nasty syndromes to certain foods, with the understanding that they won't come into play except in an emergency situation. For example, cassava root is edible, but eating very much of it without the proper processing (milling it to flour & then cooking it) will start to poison you. If you want to model this in DF currently, your options are:

• Make cassava inedible raw, so the dwarves will only eat it in its safe form
• Make cassava edible raw and give it a syndrome, taking as granted that some dwarves are just going to get arsenic poisoning.

I would much prefer to take a third option: make cassava a [STARVATION_FOOD] or [STARVATION_FOOD_RAW], give it a syndrome, and let it lay in wait for the odd dwarf with a cassava preference.

Spoiler: Plant and growth tokens (click to show/hide)

Better biome tokens. There's already a thread for this so I won't go into it too much here, but I would like the ability to differentiate a grassland in Alabama from a grassland in Maine.


A plant-level token, [BY_BIOME:class] (or [SELECT_BY_BIOME:class]). This would work something like CASTEs in animal tokens, in that all tokens you use before the first BY_BIOME token would apply to all biome-plant combos, if you want the same behaviors no matter where the plant is growing.

What this would allow us to do is define plants that can grow in different ways in different biomes. For example, many kinds of wheat can be grown as a summer crop in temperate zones, as a year-round crop in warm zones, and as a winter crop in tropical zones. To make this happen right now, you'd have to create three different nearly-identical plant definitions with seeds that aren't interchangeable. So you'd better hope those humans are bringing you temperate wheat seeds...

So for example, you could remove the BIOME, SPRING and WINTER tags from the soft wheat definition, and then at the bottom add in:

Code: [Select]

[SELECT_BY_BIOME:tropical]
[BIOME:TROPICAL_GRASSLAND]
[BIOME:TROPICAL_SAVANNA]
[SPRING][WINTER]
[SELECT_BY_BIOME:temperate]
[BIOME:TEMPERATE_GRASSLAND]
[BIOME:TEMPERATE_SAVANNA]
This would mean that in tropical grasslands and savannas, soft wheat would grow year-round, but in temperate grasslands and savannas, soft wheat would grow only during the summer and fall.

Ideally growth definitions would also be able to vary by BY_BIOME, so that you could time flowering and fruiting to the time of the thaw in each different biome; but that's a little more involved to code up an example for.


Add timing parameters to the growth tokens [GROWTH_ITEM and [GROWTH_NAME, and let them be defined more than once per growth. This would allow behavior like the picking of an apple blossom flower preventing an apple from growing. This suggestion has its own thread.

Spoiler: Reaction tokens (click to show/hide)

Improvement token: [USE_IMPROVEMENT_COLOR] changes the color of the item as displayed to that of the improvement. Or, [PRODUCT_COLOR:X:X:X] with the option to use [PRODUCT_COLOR:GET_COLOR_FROM_REAGENT:reagent:color_def] instead.

Essentially, I want to be able to replicate the dye functionality on things like blocks, leather, furniture, what-have-you.


Reagent token: [MAX_IMPROVEMENTS_OF_TYPE:X:Y]. Valid values of X would be COVERED, GLAZED, DYE, BANDS, SPIKES, PAGES, that sort of thing. NONE would presumably mean "any", as usual. Y would be an integer. [NOT_IMPROVED] would become an alias for [MAX_IMPROVEMENTS_OF_TYPE:NONE:0].

This would allow us to say that for example if a pot is already glazed it can't be glazed again, but if it just has spikes on it that's fine; that once a certain item has 5 kinds of spikes it can't handle a 6th set; and so on.


Closely-related reagent tokens: [LACKS_MATERIAL_CLASS:class] or [LACKS_MATERIAL_REACTION_PRODUCT:product]. Maybe I want to make a reaction available that uses any non-flux stone, or any non-ore stone, without going through and giving every other stone a reaction class.


Closely-related reagent tokens: [COOKING_ENABLED], [BREWING_ENABLED] and [STONE_ENABLED]. Checks that the reagent is enabled on the applicable player menu.


Product token: GET_QUANTITY_FROM_REAGENT:x:quantity_def. Allows the reagent to tell you how much product this reaction should produce. No seeds? Right on. Ten seeds? Sure.

This would allow modders to code things like hyper-fertile strains of corn or seedless bananas right into the plant definitions.

Spoiler: Syndrome tokens (click to show/hide)

INGESTED_COOKED as a delivery mechanism. Right now, cooking seems to leech all the syndrome out of food and drink, and I'd like the option to let food still carry syndromes when cooked.

I'd prefer this to be its own delivery mechanism so that there's the option of having a completely different syndrome be present in cooked vs raw versions of a food; but a [COOKING_DILUTES] tag would probably be sufficient.


[COOKING_QUALITY_DILUTES] - the more well-"minced" the cooked material is, the more diluted the syndrome is. Perfect for modeling something like fugu.

Alternatively, [COOKING_QUALITY_MULTIPLIER:X] where X can be a decimal could allow some syndromes to be more potent the more well-cooked a meal is.

[Warlord255]

Creature tokens for predator-prey relations:

[HOSTILE_TO_CREATURE:creature:caste]
Causes creature to seek out and kill specific creatures or castes. Can be used to model predator-prey relations, make your livestock particularly interesting to otherwise uninterested predators, or model fights between males of the same species.

[HOSTILE_TO_CREATURE_CLASS:class]
As above, but more broadly applicable.

[CURIOUSBEAST_CORPSE]
Animal will seek out and eat corpses or corpse pieces, with an accompanying message. [SPECIFIC_FOOD:CREATURE:creature] exists already to narrow this but does not make wildlife interact with corpses. Great for vultures, lions/tigers/bears, and possibly elves.