Bay 12 Games Forum

Yes it would work for variant(innate) types of Vampires and werebeasts.

 To prevent custom werebeasts settlements from collapsing simple make a variant werebeast interaction without it adding the [CRAZED] token and make sure the werecreature also lacks [CRAZED] or [OPPOSED_TO_LIFE].

 on a side note if you want werebeasts with gender that are fertile(no fertility resets due to becoming genderless or opposite gendered temporarily) try this:
(Use I_SOURCE and I_TARGET above, i.e. like innate necromancy posted above)
[I_EFFECT:ADD_SYNDROME]
[IE_TARGET:A]
[IE_IMMEDIATE]
[SYNDROME]
[IE_ARENA_NAME:(your werecreature here+_M)]
[SYN_CLASS:WERECURSE]
[SYN_AFFECTED_CREATURE:ALL:MALE(or the ID of another MALE sexed caste)]
[CE_BODY_TRANSFORMATION:START:0]
[CE:CREATURE:(your werecreatures creature ID):(the ID of your creatures MALE sexed Caste)]
[CE:PERIODIC:MOON_PHASE:27:0]
[CE_ADD_TAG:NO_AGING:START:0]
[SYNDROME]
[IE_ARENA_NAME:(your werecreature here+_F)]
[SYN_CLASS:WERECURSE]
[SYN_AFFECTED_CREATURE:ALL:FEMALE(or the ID of another FEMALE sexed Caste]
[CE_BODY_TRANSFORMATION:START:0]
[CE:CREATURE:(your werecreatures creature ID):(the ID of your creatures FEMALE sexed Caste)]
[CE:PERIODIC:MOON_PHASE:27:0]
[CE_ADD_TAG:NO_AGING:START:0]The only drawback is that very rarely female werecreatures can give birth to 'pure-blooded' versions of the Creature, natural(native form) members of the werebeast creature... That are also fertile.

 The above assumes you have designed your own werebeast creature already or just for this. You can limit this further by using [IT_AFFECTED_CREATURE:(creature ID):(caste ID or ALL for all castes)] within the Interactions [I_TARGET]. You can specify multiple creatures:castes by having multiple [IT_AFFECT_CREATURE] tokens listing the ones you want, all within a single [I_TARGET].

It's up to you if the werebeasts are infectious. If you want that just tinker with a variant of the sample interactions_werebeasts bite interaction, then paste your custom version along with your other interactions in the same RAW. Remember to add [SPECIALATTACK_INTERACTION:(your werecreatures custom bite interaction ID here)] token to your werecreature's (infectious)attacks.

Credit to Meph for the info/research about custom secrets for innate learning. He made his own necromancer civ that way months back(it might have been more than a year actually).

 You might want to give them a custom Secret interaction(i.e. like the necromancer example in the example interacts folder, remember to make its 'child' custom RAISE interaction too).

  You will want to do this to add the [NO_AGING] tag which can only be applied by interactions and syndromes. That plus [NOT_LIVING] allows them to avoid being automatically hostile to the Undead. Do Not give them [OPPOSED_TO_LIFE] if you want them to be playable in Fortress mode(a fort auto-fails if all citizens are opposed to life for some reason).

 After you have made the custom secret interaction(and placed it into the standard interacts RAW or a custom [INTERACTION:x] Raw) make sure your creatures have the matching [SPHERE:x] token(s) and the [SUPERNATURAL] token so all members auto-learn the secret.

They are sort of hardcoded(see points 1 & 2)

 1.To be precise vanilla necromancy secrets, werebeast and vampire curses are procedurally generated at world gen. Changing some of your world gen settings can limit their number or eliminate them altogether. But not change them(see point 2.)

 2. There are example versions in the interaction examples folder. You can make customized variations on these, and then have them in your own custom interactions RAWs. They will be used in world gen just like the Vanilla procedural ones. Even when you set it to not create the vanilla ones at world gen.

EDIT: more ranty version of what Max™ said 

Quote from: Lukander on February 25, 2015, 03:36:23 pm

[OPPOSED_TO_LIFE] creatures attack those that lack the [NO_AGING] tag. [NOT_LIVING] is used to denote something that can't be reanimated(nor resurrected?) in vanilla RAWs(and Generated Creatures) primarily, [OPPOSED_TO_LIFE] creatures don't factor it in when picking out 'enemies' at all.

Um...ok.

BTW, I've been toying around with these tags and figured out that [OPPOSED_TO_LIFE] creatures don't attack [NOT_LIVING], if not provoked. However, every creature who lacks [OPPOSED_TO_LIFE] will attack creatures those having it. For no obvious reasons (even if the attacker has [AT_PEACE_WITH_WILDLIFE] and the attacked has [NATURAL]). Seems a little bit weird for me.

And no, members of same species won't attack each other just because of [OPPOSED_TO_LIFE].


UPD:
I have some more questions. Will megabeast appear if it's modded to be a cavern creature? Also, can a megabeast be a spouse converter or it's only available for night creatures?

Cavern Megabeasts should work; just give it one or more of the [SUBTERRANEAN_*] Biome types and set [UNDERGROUND_DEPTH:*:*] to range anywhere below 0(0 is the surface layer, 5 is normally the demonic 'underworld' layer).
  Valikdu found [SPOUSE_CONVERTER] Megabeasts too work just fine(they still follow the Megabeast per world pop cap though). The [LAIR::] token common to (Semi-)Megabeasts and Night Creatures appears to be the important part for it to work(the [POWER] token disrupts this because the creature may live in a Civ site instead of a Lair, at which point they also stop spouse-hunting/converting)

   I know virtually all vanilla [NOT_LIVING] creatures also have [NO_AGING] so it could be reading either tag in most cases.
The results both I (and I believe Meph) have seen in testing were: Any creature that acquires [NO_AGING] won't be targeted by [OPPOSED_TO_LIFE] ones, unless otherwise provoked(there can be loyalty-cascade issues though). I tried to make friendly necromancers and a race of 'natural' necromancer's/'undead' using innate supernatural learning of a custom secret that granted [NO_AGING] but not [OPPOSED_TO_LIFE](so they were fortress playable). Other 'undead', Husks and necromancers ignored them but would assault foreign caravans/invaders.

I am uncertain how much(if any) effect being equipped with superior metal has on worldgen battles. But, the higher VALUE of steel goods will attract Megabeast and hostile Civ attacks early on.

Actually in a spell system that is moderately or mostly like the FoE one; the [MAGIC_NATURE] skill could stand in place of [ALCHEMY]. Leaving the [ALCHEMY] skill for the cloud stuff perhaps?

I'm currently tinkering with a system that uses secrets for worldgen and adventure mode, and a Reaction/syndrome side for Fortress mode.

Well off the top of my head in descriptor_color_pony.txt you have:
 [COLOR:1]
[NAME:mysterious]
[WORD:BLACK]
[RGB:0:0:0]are any of the castes calling that color descriptor?

because even with cntrl+F search I so far can't find a instance of 1: as a color in creature_pony_pony.txt, so far...

Besides the jugular be a weak point, the new neck part(basically the spinal column in the real neck) is a key weak point. severely damaging it(especially to the point of destroying it) can make a creature a paraplegic, makes the other 'neck' parts vulnerable to pulping and severing(decapitation) etc. This part in vanilla DF is vulnerable to punching (obviously using a weapon is better though); and accounts for a number of unarmed kills... Well, this is just something to think about if combat seems a little anomalous at times.
Ooh, and plate armor (specifically steel and adamantine) is more resistant to ranged attacks(very, very resistant) in vanilla. This is due to fixing bow/crossbow max velocity and fixing a internal rounding error for arrow/bolt wt. calculations(for attack purposes) etc.

Eh, pardon the info-dump. Good luck on the reactions!