Print

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

[Knight Otu]

This thread is meant as a gathering of potential additions and changes to the raw files. While a number of them are interlocking, most should be able to stand on their own. For each suggestion block of my suggestions, I'll try to add a "why" I think that the particular suggestion is worth adding.

Spoiler: Creature/Caste tags (click to show/hide)

[CREATIVE_BEAST_ARTIFACT:timing]
[CREATIVE_BEAST_ITEM:item identifiers]
[CREATIVE_BEAST_ENGRAVINGS]
[CREATIVE_BEAST_MATERIAL_PREF:material identifiers]
[CREATIVE_BEAST_MONSTER]

These creative beast tags should allow creatures, especially (semi)megabeasts, to do more during worldgen than rampage and steal. Especially artifact creation might be cause for more interaction between megabeasts and individuals. A artifact-creative beast that also is an item-creative beast should probably limit its artifact(s) to the item in question.

Engraving beasts (and maybe wallpainting if that is implemented) might be additional sources of information in certain cases, and could add flavor to other creatures. Entering a place that held/holds engravers/painters should of course create such images. Monster creation obviously must wait for more randomized critters.

[WOUND_EFFECT:SEVER:BY_CATEGORY:HEAD:WE_REPLACE_SEVER:CREATURE:FLOATING_HEAD:ANY]
[WOUND_EFFECT:SEVER:BY_BP:ALL:WE_DESTROY_SEVER]
[WOUND_EFFECT:BRUISE:BY_BP:ALL:WE_PREVENT_WOUND]
WE_DEATH
WE_SEVER
WE_SELF_SYNDROME

Wound effects, where a certain kind of wound has a certain effect by creature. The first would take any severed head, (or severed head and neck ideally), and replace it with a new creature (such as the Gleeok of Legend of Zelda fame). Wound effects should probably be handled with care (that is, the third one where bruises are prevented is likely a no-no), though I believe they can create interesting effects such as severed limbs fighting on.

[SELF_AFFLICT]
   Syndrome
[INDIVIDUAL_SYNDROME]
   [TRIGGER_MATERIAL:material]
[AFFLICTING_DEATH]
   Syndrome
[SYNDROME_IMMUNE:syndrome]
[SYNDROME_CLASS_IMMUNE:syndrome]

Some further uses for syndromes - self-afflict could be used to create things like berserker rages in a creature. Obviously, there need to be some kinds of checks.
Individual syndromes I believe are important in at least two situations - one, the werewolf scenario (or maybe gnomeblight scenario) - when you have a material that is harmful to a single creature, you can add it to that creature itself rather than meddling with the other files. This would be most useful when adding a modded creature that is vulnerable to a existing material. Two, the Oz scenario, where a creature is vulnerable to a material that modders can't touch, such as water.
Afflicting death would be the case where a creature afflicts the person who landed the mortal strike on it with a certain syndrome - say an unicorn causing melancholy in its killer.
Also, some tags to add immunity to syndromes to creatures without editing syndromes. Again, the idea here is to minimize editing existing raw files when adding new creatures. Syndrome class immunity would be things like immunity to spider bites.

[WANDERING_BEAST]
Creatures like escaping demons and titans don't dwell in caves like most megabeasts, but wander a certain region. This tag would allow modders to duplicate this behavior, and might impact the number of megabeasts.

[LEARNING_BEAST]
Currently, creatures that are able to learn are tagged as sentient, and thus unbutcherable. This tag would allow a creature to learn without becoming ineligible for butchering. Ideally this should be used for smart but bestial megabeasts (dragon in some myths).

[ATTACK_FLAG_TOOL:DIGGER:TUNNEL/NO_TUNNEL]
[ATTACK_FLAG_TOOL:WOODCUTTER]
A tag that allows natural attacks to be used as tools (and maybe also such a tag for body parts). The two above are the most obvious tools as they are needed in fortress mode, though adventure mode tools could join in as well.

[SELECT_BP:body part]
[PLUS_BP:body part]
[PLUS_BP_CHILDREN]
There are already ways to select creature castes, materials, and tissues and apply changes to them easily. Body parts are left out for now, though it seems having that ability would be great to minimize body file additions. You could add the stance tag to unusual feet or the thought tag to an unusual brain body part less need to create a new body part.

[MINUS_TISSUE_LAYER:tissue]
[MINUS_MATERIAL:material]
[MINUS_BP:body part]
On the flip side, I believe it is not possible to easily deselect a tissue layer or material (andwith the above tags, body parts). While you could select each object that you want to change, that is not really easy with complex bodies, so it might be easier to fine-tune your selection after the fact.

[ADVENTURER_RESTRICTED]
A simple caste level tag that would prevent a caste from being choosable for adventure mode. This would be useful for cases where you've added a rare super-caste that you generally don't want playable in adventure mode.

[CHOOSY_PET]
The cat behavior of choosing their own owners, decoupled from vermin hunter. For one, I feel that tags should be as... "atomic" as possible, and it is kind of a family motto of ours that the pet should choose the owner.

[ITEM_CORPSE:A:ITEM_WEAPON:ITEM_WEAPON_SWORD_LONG:INORGANIC:IRON]
[INHERENT_ITEM:A:ITEM_WEAPON:ITEM_WEAPON_SWORD_LONG:INORGANIC:IRON]
[ITEM_DROP:A:ITEM_WEAPON:ITEM_WEAPON_SWORD_LONG:INORGANIC:IRON]
The first is a bit of a change to the existing item corpse tag, to allow a creature to have a) multiple item corpses and b) have different item corpse sets. A creature may have two item corpse tags that are both in "set A", and a single is chosen at random on its death. It may have one "set A" and one "set B", and both would be generated upon death. The item corpse quality tag should change accordingly, of course.
Inherent item would work similarly, except the creature starts with those items in life unless it is part of an entity. That would also be the main reason to add such a token, allowing non-entity creatures to wield equipment.
I'll be honest and say that I'm uncertain that an item drop tag would be needed with the first two tags - it would be an item that the creature for some reason doesn't have available in life, but also doesn't replace the corpse. Maybe a gem embedded in the forehead, though that might be removed with butchery.

[TELEPORT:TRUE:range]
[TELEPORT:PARTIAL:range]
[TELEPORT:SIGHT:range]
[TELEPORT_TRAIL:material]
Teleportation of certain kinds is a staple in fantasy of course. TRUE teleportation would allow blind teleporting anywhere (with failsafes to avoid teleporting into solid matter). PARTIAL teleportation would  be blocked if there is some barrier in the path that couldn't be circumvented with a few steps (walls block, trees don't, ideally). And with sight teleportation, you could only teleport to places you can see.

[SUMMONER:CREATURE:WOLF:ALL:number:chance]
[SUMMONER:VERMIN:BAT:ALL:10:50]
[SUMMONER:ITEM_WEAPON:ITEM_WEAPON_WHIP:material:1:100]
Much like teleportation, summoning is a fantasy staple. The syntax assumes of course that creatures might at some point be created in some way similar to items. Summoner abilities should be especially interesting for demons.

[ARISER:SETTLE/WANDER:ariser text:year range:previous home (optional?)]
An ariser would be a creature, presumably a megabeast, that arises during worldgen, but after the other beasts have been placed, similar to how unique demons are currently able to escape the underworld. The settle/wander distinction may not be necessary - either they wander the world, or settle in a cave/adventurer location. The main use would primarily to allow restocking megabeasts at some point in time (not that they need it at the moment). A unique demon currently might look something like this:
 demon: [ARISER:WANDER:escaped from the Underworld:1:10:Underworld]

 [USURPER]
 [IMPERSONATOR]
 [DOPPELGANGER]
Creature tags that may determine how a power enters an entity and obtains power. An usurper would try to gain power by raw strength. An impersonator would claim to be a manifestation of a deity as demons currently do. A doppelganger would claim to be an important historical figure (potentially killed by the doppelganger itself), and take that figure's place.

Material Breaths:
   DART
   DISK
   DEATH_BURST
   UNDIRECTED_LIQUID
   TRAILING_LIQUID_FLOW
A few more material "breath" types. Darts would be edged solid projectiles with small contact areas, while disks would have a larger contact area, potentially cutting off limbs. Darts would be useful for manticore type creatures, and while I can't currently think of a creature shooting "disks", I'm sure they exist.
Death burst would be a "breath weapon" that activates upon the creature's death, causing a blast centered on it (a fire version would be nice to have as well, I think, if fire isn't being folded into the materials or possibly energies).
Undirected liquid and trailing liquid flow would work similar to the gas and dust versions, but with liquids, which should be easier to cause contact syndromes.

All Breaths:
   SIZE
   FREQUENCY
   VELOCITY
   IS_VOLLEY:volley_size (dart, disk, solid glob, liquid glob)
A few attributes for breath weapons. Breath weapons might need an identifier for them to work, so that the tag isn't overloaded with options, though. Size would be the size of the cone, flow, blast, or trail for normal breath weapons, and the size of the projectile for the projectile attacks like globs or darts. The other important damage variable, velocity, could also be used for the deadliness of dust attacks. Frequency is obviously how often the breath weapon is used. A volley attack would shoot multiple projectiles in a narrow "cone", which again would be useful for creatures like manticores.

[ITEM_BREATH_WEAPON:item identifiers:?]
I'm not quite certain how item breath weapons would be typed out, but their usefulness does range from creatures shooting arrows and throwing boulders to creatures covered in vermin and coughing up vermin.

[PARENTS:creature 1:caste 1:creature 2:caste 2:...]
mule:
[PARENTS:DONKEY:MALE:HORSE:FEMALE]
half-elf:
[PARENTS:HUMAN:MALE_FEMALE:ELF:FEMALE_MALE]
[PARENTS:HUMAN:MALE_FEMALE:HALF_ELF:FEMALE_MALE]
[PARENTS:HALF_ELF:MALE_FEMALE:ELF:FEMALE_MALE]
worm:
[PARENTS:WORM:ANY]
Yeah, some tags for crossbreeding, in the child creature (maybe even caste?). The male/female and female/male tags are to control that one caste is male and the other female. If no female caste is included among the parents, there should be one default for the childbearing caste (first listed in the tag?). I suppose there needs to be a parent default working as something like [PARENTS:OWN_RACE:MALE_FEMALE:OWN_RACE:FEMALE_MALE]. And a [NO_DEFAULT_PARENTS] tag to override that default.

[SPONTANEOUS_GENESIS]
[MELD:creature 1:caste 1:creature 2:caste 2:...]
Two more tags for population increase/change. I suppose a form of spontaneous genesis occurs in world gen to create creatures without male/female castes.
Melding would replace the component creatures with the new creature/caste. Maybe there needs some way to tell the creature what gender to retain, if any. It would be useful for creatures like illithids, I think.

[ENVIRON_PAR:ELEVATION:95:100]
[ENVIRON_PAR:RAINFALL:0:10:DRAINAGE:90:100:TEMPERATURE:??:??]
A tag for more fine-tuned creature (plant/stone) placement beyond biomes. Environment parameters would be the same as the worldgen parameters. If multiple parameters occur in a single tag, all need to be fulfilled. If they occur in separate tags, only one set of parameters needs to be fulfilled.

Spoiler: Syndrome raws (click to show/hide)

[SYNDROME_NAME:ID]
[SYNDROME_CLASS:]
This is to add the ability to identify certain syndromes in other raw files.

[CE_ARTIFACT:type]
[CE_THOUGHT:thought:happiness modifier:optional modifier by personality?]
[CE_BERSERK]
[CE_MELANCHOLY]
[CE_INSANITY]
A number of creature effects related to mood and sanity. CE_ARTIFACT would incur a strange mood of the given type when the syndrome peaks (syndrome ending should not impact that), and the latter three would incur the three types of insanity dwarf fortress currently knows for the duration of the syndrome.
CE_THOUGHT would be rather open-ended - you could have unicorns incur a syndrome that gives a bad thought of "killed a creature of innocence recently", which might be turned into a good thought for particular individuals.

[CE_SKILL:skill:percentage]
[CE_ATTRIBUTE:attribute:percentage]
[CE_PERSONALITY:personality:change by x]
Some creature effects that change certain abilities and variables of the affected creature, increasing or decreasing them as appropriate - perhaps the kiss of a muse, or the touch of a wraith.

[CE_REPLACE_MATERIAL:old material:new material]
Yeah, a syndrome that would change materials of the affected creature - useful for things like petrification or turning to salt, maybe even "turning" blood infectious.

[SYNDROME_BENEFICIAL]
[SYNDROME_INVISIBLE]
Two syndrome tags potentially for beneficial syndromes. Dwarves should attempt to cure or diagnose beneficial syndromes, or do other stuff triggered by being poisoned. Certain syndromes also shouldn't show up as syndromes (say again a muse's kiss or maybe berserker rage).

Spoiler: Class lists and class list modifications (click to show/hide)

Class lists would be a new raw file type that gathers a number of objects together under certain labels. These would include the current creature class and reaction class (ideally renamed material class to allow reaction classes to be classes of reactions), as well as potentially syndrome classes, reaction classes, and other class types as they are added. Creature class lists could then used in entities as lists of pets or mounts, for "at peace with" tags, and similar places where lists of creatures could be called for. Similarly, material classes could be used as identifiers of building materials available (or not available) to an entity. Also, class lists could act as a grouping for likes and dislikes, so that, for instance, a dwarf could like all flux stones equally. There should of course a way to automatically populate larger class lists.

class_list_creature.txt
[CREATURE_CLASS:GENERAL_POISON:NO_TEXT]
   [POPULATE_LIST:BY_TOKEN:GETS_WOUND_INFECTIONS]
   [NOT_LIKEABLE]

[CREATURE_CLASS:CONSTRUCT:construct:constructs]
   [CREATURE:COLOSSUS_BRONZE:ALL]
   [PREFSTRING:creation processes]

[CREATURE_CLASS:WILDLIFE:NS:wildlife]
   [POPULATE_LIST:BY_TOKEN:NATURAL:AND_TOKEN:BIOME]
   [EXCLUDE_CREATURE:BY_TOKEN:EVIL]
   [NOT_LIKEABLE]

class_list_material.txt
[MATERIAL_CLASS:FLUX:flux:flux]
   [INORGANIC:CALCITE]
   [INORGANIC:CHALK]
   [INORGANIC:DOLOMITE]
   [INORGANIC:LIMESTONE]
   [INORGANIC:MARBLE]

As an extension to the above, as it is likely that lists would be among the most-changed files in mods, another way to change lists should come from other files, such as the following (yeah, cat would likely be already part of the common dwarf pet list). This would again be a way to minimize changing existing raw files.

class_list_creature_modification.txt
[EXPAND_CREATURE_CLASS:COMMON_DWARF_PET]
   [CREATURE:CAT:ALL]

Spoiler: Entity and Entity position raws, and entity modifications (click to show/hide)

[KIDNAPPER:preferred creature/class:caste]
A new entity behavior like item thief and baby snatcher, this would cause the entity to go and abduct adult entity members and slowly make them members of their own entity as slaves or otherwise. An entity could have multiple kidnapper tags for multiple kidnapping targets. Ideally, babysnatchers would also get the ability to target preferred creatures.


[PET:COMMON:USE_CLASS_LIST:COMMON_DWARF_PET]
[PULLER:RARE:USE_CLASS_LIST:RARE_DWARF_PULLER]
[WAR:EXOTIC:USE_CLASS_LIST:EXOTIC_DWARF_WAR_PET]
These tags would make the most sense with the creature class lists above, to allow fine-tuning of the creatures that a civilization has access to (say drow could get spider pets). The creature kinds would be likely MOUNT, PULLER, PACK, WAR and HUNT. The "rarities" I would see are common (as common domestic, the entity always has access to the creature), uncommon (the civilization will always use the creature if it has access to them via biomes or trade or similar), rare (only important positions will make use of the creature, and only with access (this rarity might be unneeded with economic rewrites?)), and exotic (where the civilization needs someone capable to tame/domesticate the creature first).

[CANNOT_USE_MATERIAL:IRON]
[CANNOT_USE_MATERIAL_CLASS:DARK_STONE]
These tags would again exist to fine-tune a civilization's capabilities, this time in terms of building and crafting material. While reations do so of that work, materials that are dug out or cut down are not limited that way (and non-reaction metal depends on STONE_PREF somehow).

[SPECIAL_MAT_WEAPON:BY_TOKEN:WOOD]
[SPECIAL_MAT_ARMOR:BY_TOKEN:WOOD]
[SPECIAL_MAT_BUILDING:BY_TOKEN:BONE]
A few tags that would generalize the wood weapons and wood armor tokens of elves into a more flexible set of tokens. Bone weapons, coral buildings...

[HOSTILE]
[NONHOSTILE]
Two tags that change the civ's behavior generated by other tags - a hostile civ would be at war much like an item-thief civilization automatically. A nonhostile civ would be at peace (excluding normal times of war) even if it is an item thief or kidnapper civ.


Entity position tags

[REQUIRED_AGE:50:NONE]
An obvious tag to include. Age would be a range to allow for those elected child queens of Naboo.

[CHILD_OF:position]
[SPOUSE_OF:position]
[SIBLING_OF:position]
[PARENT_OF:position]
Another set of tag that I think would be obvious to include for monarchies.

[REQUIRED_TL_COLOR:HAIR:SILVER:GREY:WHITE]
I think this was mentioned by a poster during the development of entity positions - only the silver-bearded shall be king.

[PREFERRED_ITEM:ITEM_WEAPON:ITEM_WEAPON_HAMMER:METAL:NO_SUBTYPE]
[PREFERRED_ITEM:ITEM_WEAPON:BY_SKILL:SWORD:METAL:NO_SUBTYPE]
[PREFERRED_MOUNT:LION]
[REQUIRED_SKILL:SWORD]
Yeah, the first is already kind of needed for the hammerer, but a generic tag would also allow for things like a court musician or outfitting a civ's invasion forces, along with the preferred mount tag. Also useful if you want to create knights, I would think. Required skill should be in to make sure that the position has the appropriate skill, or at least trains it (so once music skills are in, the court musician actually can do music).

RESPONSIBILITY:JUDGMENT
RESPONSIBILITY:LABOR:METALCRAFTING
Two potential responsibilities - judgment wizks be for judging major site/civ transgressions, rather than a way to avoid hammering the poor chaps who happen to have a labor related to a missed production mandate. Responsibility for certain labors would allow a position to perform that labor even if they otherwise are exempt from laboring. This could be useful for guilds.

I've mentioned that class lists would likely be a target for heavy modding above, so that a modification file could be useful. The entity file already is by necessity a heavily modified file right now - new reaction? Toss it into the entity file. New buildings or items? Also go into the entity file. New entity position? Same. So, it would make sense for the entity file to also get an entity modification file to minimize the need to touch that file.

entity_modification_*.txt
[MODIFY_ENTITY:MOUNTAIN]

ADD_PERMITTED_REACTION
ADD_PERMITTED_REACTION_CLASS
ADD_PERMITTED_BUILDING
ADD_PERMITTED_BUILDING_CLASS
ADD_WEAPON/ARMOR...
ADD_ENTITY_POSITION
ADD_PET/MOUNT...

Spoiler: Material tokens (click to show/hide)

In general, I feel that a good number of specific material tokens should become more generic material tokens - for example, good and evil (or rather their successor token(s) as they probably won't exist all that much longer), plant product tokens (brewing a drink from certain spider silk, or milling down a rock), or biomes.

[RELEASE_MATERIAL:material:state:chance:triggers]
A material token where the material has a chance to release another material under certain circumstances - I'm thinking mined out (the blacklung thing that has been around, for instance), felled as a tree, picked as a plant, or on impact as a projectile/thrown weapon (deku nuts), including from a material breath weapon (to have dart breaths that could inject poison).

[NO_USE]
[NO_MANDATE]
[NOT_LIKEABLE]
Some materials kind of exist as placeholders (again the blacklung stuff), and it is possible that they might be brought in caravans, used in the starting wagon, or used in mandates. The no use tag should prevent the first two, while the no mandate and not likeable tags should prevent the latter. No mandate could be useful if the material could be likeable but for some reason can't be used anyway, such as slade.

[ALWAYS_STONE]
The behavior of deep stone to always leave a stone regardless of the miner's skill. This could be useful for really valuable stone that is treated with the same amount of care as adamantine, or for stuff like blacklung if the release material token is not used.

[STONE_ITEM:BOULDER:1]
[WOODCUT_ITEM:WOOD:1]
[GATHER_ITEM:PLANT:1]
Some tags to follow the butcher item example - ways to change what items are mined out, cut down, or gathered from plants. Maybe some plants provide ready thread without need to process them. Maybe someone wants to create a post-apocalyptic mod where "trees" are actually cars to be gutted (actually, someone does want). Gems and other stone already provide different items when dug out.

[MAGMA_PLANT]
[STONE_PLANT]
For plants that might be able to grow on stone or in/near magma.

[ENVIRON_PAR:ELEVATION:95:100]
[ENVIRON_PAR:RAINFALL:0:10:DRAINAGE:90:100:TEMPERATURE:??:??]
As in the creature section, this would allow fine-tuning of stone and plant placement.

Spoiler: Weapon tokens (click to show/hide)

[RETURN_ON_MISS]
[RETURN_ALWAYS]
Yeah, token for boomerangs and other ranged weapons. The first is the realistic option of course. The second could also be used for short-ranged rope or chain weapons (whips, Zelda hookshots).

[CAN_GRAB]
I suppose this is another Zelda-inspired token, the ability to grab objects with a weapon and/or maybe use it to climb up somewhere. Overlaps with grappling hooks I guess and may be used for whips. Maybe needs a variable to how much it can carry, to avoid catching boulders?

[SPECIAL_GRASP:BY_CATEGORY:TAIL]
Some races may be able to use limbs to grasp specially-made weapons without those limbs being able to grasp other tools. This token could be used for such races.

[WEAPON_TOOL:DIGGER:TUNNEL/NO_TUNNEL]
[WEAPON_TOOL:WOODCUTTER]
These tokens would allow a weapon to act as a specific tool, again with the most obvious tools. This would stop the need to rely on the axe skill to determine whether a weapon can cut wood, and might make the digger token in the entity files unneeded.

[CANNOT_DIG:LACKS_TOKEN:SOIL]
[CANNOT_DIG:BY_MATERIAL_CLASS:HARD_STONE]
[CANNOT_DIG:IMPACT_FRACTURE:2000000:NONE]
Kobold camp and shovels want a way to make certain materials undiggable by digging tools. A cannot dig tag would be useful to have.

Spoiler: Armor tokens (click to show/hide)

With credit to derigo, I feel that the armor position raws need a complete overhaul. Currently, they are a bit arcane, with somewhat redundant tags like UBSTEP, UPSTEP, and LBSTEP. Now, these tags exist for a reason, to make sure that odd body configurations are taken into account, but I feel that this could be done in more a predictable and transparent fashion. This might be expanded to other wearable items like rings and crowns if those enter the raws.
There may need to be distinctions on whether a given armor can cover more than one/all body parts of a type (as greaves probably should), and a single one (as masks should).
mask
   [POSITION:BY_CATEGORY:HEAD:FRONT:100]
   [ADD_PROTECT:CHILD_BP:BY_CATEGORY:HEAD:ALL:FRONT:80]

greaves
   [POSITION:BY_CATEGORY:LEG_UPPER:OR_CATEGORY:LEG:AROUND:80]
   [ADD_PROTECT:CONNECTED_BP:BY_CATEGORY:LEG_LOWER:ALL:AROUND:80]

derigo's version and commentary:

I originally had all kinds of criticisms and stuff, but the more I look at this the more I like it.   Since we're selecting parts by category, its pretty damned flexible by nature.  It lets you apply different amounts of coverage to different body parts, which is awesome.  As to distinguishing between covering all or one of a part, just add another field at the end that accepts ALL or ONE and maybe PAIR. 

Its too much to ask to have an OR_CATEGORY inner argument like that.  Just make them discreet statements.  It'll take up a little more space, but it'd certainly be healthier code.  like so:
 
   [POSITION:BY_CATEGORY:LEG_UPPER:AROUND:80]
     [ADD_PROTECT:CONNECTED_BP:BY_CATEGORY:LEG_LOWER:ALL:AROUND:80]
   [POSITION:BY_CATEGORY:LEG:AROUND:80]

Indicating that the armor can be work on a LEG_UPPER, in which case it will also cover a LEG_LOWER, or it can be worn on a LEG, in which case it won't bother.  Then you could do fun things like this!

[ARMOR_ITEM:WARMER]
   [POSITION:BY_CATEGORY:LEG_LOWER:AROUND:30]
   [POSITION:BY_CATEGORY:ARM_LOWER:AROUND:30]
   [POSITION:BY_CATEGORY:TAIL:AROUND:30]
   [POSITION:BY_CATEGORY:HEAD:AROUND:30]
     [ADD_PROTECT:CONNECTED_BP:BY_CATEGORY:EAR:ALL:AROUND:100]
   [POSITION:BY_CATEGORY:NECK:AROUND:90]

Maybe even throw in some GLOSS to change the name depending on where it's worn.  This idea, while fun, would certainly add yet another complication to the military equipment assignments.

Other new raw files

Spoiler: Religion raws (click to show/hide)

Basic raws for defining different religions. I think they are best illustrated by a few examples first:
[RELIGION:PANTHEON]
   [DIVINITY:DEITY:3:15]
      [NAME_GEN:deity:deities]
      [NAME_MALE:god:gods]
      [NAME_FEMALE:goddess:goddesses]
      [NAME_NEUT:deity:deities]
      [MANIFEST:OWN_RACE:ALL:9]
      [MANIFEST:LOCAL_CREATURE:ALL:1]
      [SPHERE:CULTURE_ALLIED:ALL]
      [SPHERE:CULTURE_NEUTRAL:SOME]
      [SPHERE:CULTURE_ENEMY:NONE]
      [IS_MEMBER]
      [APPEASEMENT:ACCEPTABLE]
      [WORSHIP:ACCEPTABLE]
      [DEDICATION:ACCEPTABLE]
      [PRIESTHOOD_MALE:priest:priests]
      [PRIESTHOOD_FEMALE:priestess:priestesses]
   [DIVINITY:NEMESIS:0:3]
      [NAME_GEN:nemesis:nemeses]
      [MANIFEST:OTHER_RACE:ALL:1]
      [MANIFEST:GLOBAL_CREATURE:BY_TOKEN:MEGABEAST:ALL:3]
      [MANIFEST:GLOBAL_CREATURE:BY_TOKEN:SEMIMEGABEAST:ALL:2]
      [MANIFEST:LOCAL_CREATURE:BY_TOKEN:LARGE_PREDATOR:AND_TOKEN:NATURAL:ALL:1]
      [SPHERE:CULTURE_ALLIED:NONE]
      [SPHERE:CULTURE_NEUTRAL:SOME]
      [SPHERE:CULTURE_ENEMY:SOME]
      [SPHERE:BY_CREATURE:ALL]
      [IS_ENEMY]
      [APPEASEMENT:ACCEPTABLE]
      [WORSHIP:MISGUIDED]
      [DEDICATION:SHUN]
      [PRIESTHOOD:cultist:cultists]

[RELIGION:REGIONAL_FORCE]
   [DIVINITY:FORCE:1:1]
      [NAME_GEN:force:forces]
      [MANIFEST:NONE:9]
      [MANIFEST:LOCAL_CREATURE:BY_TOKEN:LARGE_ROAMING:AND_TOKEN:NATURAL:ALL:1]
      [GENDER:NONE]
      [NO_IMPERSONATE]
      [SPHERE:NATURE]
      [SPHERE:BY_REGION:ONE]
      [PERMEATES_REGION]
      [IS_MEMBER]
      [APPEASEMENT:ACCEPTABLE]
      [WORSHIP:ACCEPTABLE]
      [DEDICATION:ACCEPTABLE]

[RELIGION:DEMON_LORD]
   [DIVINITY:DEMON:1:1]
      [NAME_GEN:demon lord:demon lords]
      [NAME_MALE:demon lord:demon lords]
      [NAME_FEMALE:demon lady:demon ladies]
      [NAME_NEUT:demon sovereign:demon sovereigns]
      [EXISTS:GLOBAL_CREATURE:BY_TOKEN:UNIQUE_DEMON:ALL:1]
      [SPHERE:BY_CREATURE:ALL]
      [IS_MEMBER]
      [APPEASEMENT:ACCEPTABLE]
      [WORSHIP:ACCEPTABLE]
      [DEDICATION:ACCEPTABLE]
      [PRIESTHOOD:servitor:servitors]

[RELIGION:ARMOK]
   [INDIVIDUAL:ARMOK]
      [IND_NAME:Armok]
      [NAME_GEN:god of blood:N/A]
      [GENDER:MALE]
      [MANIFEST:NONE:1]
      [SPHERE:WAR]
      [SPHERE:VOLCANOS]
      [IS_MEMBER]
      [APPEASEMENT:ACCEPTABLE]
      [WORSHIP:ACCEPTABLE]
      [DEDICATION:ACCEPTABLE]
      [PRIESTHOOD_MALE:priest:priests]
      [PRIESTHOOD_FEMALE:priestess:priestesses]

[RELIGION:BEAST_ALLIES]
   [DIVINITY:BEAST_ALLY:3:10]
      [NAME_GEN:beast ally:beast allies]
      [NAME:ally:allies]
      [MANIFEST:LOCAL_CREATURE:BY_TOKEN:LARGE_ROAMING:ALL:1]
      [SPHERE:NATURE:EVERY]
      [SPHERE:BY_CREATURE:ALL]
      [IS_MEMBER]
      [DUPLICATE_SPHERE_ALLOWED]
      [APPEASEMENT:ACCEPTABLE]
      [WORSHIP:ACCEPTABLE]
      [DEDICATION:ACCEPTABLE]
      [PRIESTHOOD:shaman:shamans]

A religion have a few different types of divinities. In the case of pantheons, the pantheon could have a number of divine nemeses (akin to Jormungandr, Fenrir and Hel to the Norse gods). The name_gen tag is for sentences like "Thad was a deity that occurs in the myths of The Blade of Persuaders", while the other name tags are used elsewhere (so that a beast ally may be a crocodile ally in the list of historical figures, but is correctly described as a beast ally most often depicted as a crocodile).
Manifestation tokens are just that, the most common description for a divinity. These might be specific creatures and castes, the own race, or chosen from among certain other creatures. They might even have no manifestation, like forces currently do. Existence tokens on the other hand would make the creature actually exist, like worshiped powers used to do. The is member and is enemy tokens should handle some behavior towards the divinities (and in the case of physical gods, whether they are placed in entity sites or "adventure" sites), along with the appeasement, worship, and dedication tokens (appeasement would be the minor worship megabeasts can attain already, and dedication would involve becoming a priest of that divinity).
Sphere division would be handled by tags as above - culture_allied spheres would be those defined in the entity entry as religion_spheres and sphere_alignments, as well as spheres allied to those spheres, and the other culture sphere tags would follow from those tags. By_creature tags would take spheres  associated to a creature such as demons and beasts, while by_region would take a sphere related to the region the divinity is worshiped in (or that it permeates), such as rivers, mountains or oceans, or in the future forests and the like. Another potential tag would be DIVINITY_ALLIED, when a divinity is given some fixed spheres, and gets additional random spheres based on that.

Spoiler: Calendar/Cosmology (click to show/hide)

[COSMOLOGY_CALENDAR]
   [MONTH:GRANITE:28]
   [MONTH:SLATE:28]
   [MONTH:FELSITE:28]
   [MONTH:HEMATITE:28]
      [SPHERE:FIRE]
   ...
[COSMOLOGY_SEASONS]
   [SEASON_START:GRANITE:1]
   [SPRING:84]
   [SUMMER:84]
Maybe a bit of a pipe dream, but a "cosmology" raw where you can define at least year length, month length, and month names, possibly with sphere links. I don't think they need identifiers unless different calendars can be chosen at random.

Spoiler: Item raws (click to show/hide)

Even more of a pipe dream I assume, moving many more items into the raws, from furniture, over containers, crafts and decorations, to "base items" like bars and boulders.
[FURNITURE_BED:BED]
   [GENERAL_NAME:bed:beds]
   [TILE:233]
   [BUILD_TILE:233]
   [SIZE:??]
   [ITEM_MATERIAL_CLASS:WOOD:CARPENTER]
   [ITEM_MATERIAL_CLASS:CLOTH:CLOTHIER]
   [PLUS_ITEM:MATERIAL_CLASS:LEATHER:LEATHERWORKER]
      [CLASS_NAME:sleeping bag:sleeping bags]

[FURNITURE_CONTAINER:BOX]
   [GENERAL_NAME:chest:chests]
   [TILE:146]
   [BUILD_TILE:146]
   [SIZE:??]
   [HOLDS:??]
   [ITEM_MATERIAL_CLASS:WOOD:CARPENTER]
   [PLUS_ITEM_MATERIAL_CLASS:METAL_FURNITURE:BLACKSMITH]
   [ITEM_MATERIAL_CLASS:STONE:MASON]
      [CLASS_NAME:coffer:coffers]
   [ITEM_MATERIAL_CLASS:CLOTH:CLOTHIER]
   [PLUS_ITEM_MATERIAL_CLASS:LEATHER:LEATHERWORKER]
      [CLASS_NAME:bag:bags]
      [CLASS_TILE:11]
      [CLASS_BUILD_TILE:11]
      [CLASS_HOLDS:??]


[FURNITURE_STATUE:STATUE]
   [GENERAL_NAME:statue:statues]
   [TILE:234]
   [SIZE:??]
   [BLOCK_MOVE]
   [ART_IMAGE:CREATURE]
   [ART_IMAGE:HISTORY]
   [ART_IMAGE:OBJECT]
   [ITEM_MATERIAL_CLASS:STONE:MASON]
   [PLUS_ITEM_MATERIAL_CLASS:GLASS:GLASSMAKER]
   [PLUS_ITEM_MATERIAL_CLASS:METAL_FURNITURE:BLACKSMITH]

[ITEM_CRAFT:FIGURINE]
   [GENERAL_NAME:figurine:figurines]
   [TILE:143]
   [SIZE:??]
   [ART_IMAGE:CREATURE]
   [ART_IMAGE:HISTORY]
   [ART_IMAGE:OBJECT]
   [ITEM_MATERIAL_CLASS:WOOD:WOODCRAFTER]
   [PLUS_ITEM_MATERIAL_CLASS:STONE:STONECRAFTER]
   [PLUS_ITEM_MATERIAL_CLASS:GLASS:GLASSMAKER]
   [PLUS_ITEM_MATERIAL_CLASS:GEM:GEMCUTTER]
   [PLUS_ITEM_MATERIAL_CLASS:METAL_ITEM:METALCRAFTER]


[ITEM_DECORATION:HANDLE]
   [GENERAL_PRE_NAME:handle of:handles of]
   [DESC:held with]
   [SIZE:??]
   [DECORATE_SPECIFIC:ITEM_BUCKET]
   [ITEM_MATERIAL_CLASS:WOOD:WOODCRAFTER]
   [PLUS_ITEM_MATERIAL_CLASS:STONE:STONECRAFTER]
   [PLUS_ITEM_MATERIAL_CLASS:GLASS:GLASSMAKER]
   [PLUS_ITEM_MATERIAL_CLASS:GEM:GEMCUTTER]
   [PLUS_ITEM_MATERIAL_CLASS:METAL_ITEM:METALCRAFTER]


[ITEM_BASE:BAR]
   [GENERAL_NAME:bar:bars]
   [TILE:240]
   [SIZE:?]
   [DIMENSION:150]

Other raws and related suggestions threads
Ability to Design Sites and Buildings
Architectural Freedom
Raw-Editable Procedural Worldgen Cities

Fun with Syndromes (My suggestion overlap a bit with these I see.)
Disease Outline (Potential disease vectors)

All workshops to the raws