Print

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

[Putnam]

1. Yes. You want 2WINGS, though, not WINGS. Make sure you get your tokens straight.

2. Yes. A CE_BODY_TRANSFORMATION syndrome with no END will be permanent.

[MCipher]

Thanks for answering.

EDIT: Crap. I remembered something, I made the codes to make a creature be morphed into a "Manslayer", but it is always temporary, I added no END to the token line.

[Putnam]

Hmm. Let's see the token line, then.

[Xangi]

Has anyone tested [ITEMCORPSE] enough to tell me why it sometimes just doesn't work? I'm trying to make a gaseous humanoid that drops a sword upon death, but most of the time it just explodes and no sword is dropped.

[Admiral_Aorta]

More stupid questions about creature modding.
I have been wondering if the "[WINGS]" attachment to the "[BODY:]" token would give creatures flight...
I know the "[FLIER]" token exists, but I am wondering if wings would give the creature flight, but only while the wings are attached.

A completely different question, can you make a creature permanentally count as a different one using syndromes? For example:

Spoiler: before (click to show/hide)

Code: [Select]

U------
-------
------#


(The ASCII is just demonstrational)
Could you, say make a creature turn from that, To:

Spoiler: after (click to show/hide)

Code: [Select]

#------
-------
------#


Permanentally, and it count as that creature (the "#" in the demonstrations), no longer counting as "Human" (the "U")?

I'm pretty sure that having wings is independent of flight, but if a unit with [FLIER] also has wings then it will lose flying if those wings are removed.

[MCipher]

Hmm. Let's see the token line, then.

Okay.

Spoiler: code line (click to show/hide)

Code: [Select]

[LOCAL_CREATURE_MAT:MORPHGAS]
[USE_MATERIAL_TEMPLATE:MORPHGAS:CREATURE_EXTRACT_TEMPLATE]
[STATE_NAME:ALL_SOLID:frozen morph fluid]
[STATE_ADJ:ALL_SOLID:frozen morph fluid]
[STATE_NAME:LIQUID:morph fluid]
[STATE_ADJ:LIQUID:morph fluid]
[STATE_NAME:GAS:morph gas]
[STATE_ADJ:GAS:morph gas]
[PERFIX:NONE]
[SYNDROME]
[SYN_NAME:doombringer morph]
[SYN_AFFECTED_CLASS:GENERAL_POISON]
[SYN_CONTACT]
[CE_BODY_TRANSFORMATION:START:150]
[CE:CREATURE:DOOMBRINGER:FEMALE]


-note- The "Doombringer" has multiple types, AKA Castes. This is simply demonstration.

[Putnam]

Wouldn't it be easier to directly use an ADD_SYNDROME interaction?

[random_odd_guy]

Actually, I found that all you need is [FLIER] wings do nothing without that. Incidentally, you don't NEED wings to fly, however, if you DO have them, the tag gets bound to them, and when removed (but still displayed in your body parts list as having been removed) you lose the ability to fly, but if you dont have wings, you just fly superman style.

[Urist Da Vinci]

Is it just me, or is CE_IMPAIR_FUNCTION really damn weak? I mean setting SEV:100 on a creature's brain doesn't even harm it in the slightest.

EDIT: Upon further testing, I've found that for this syndrome

Code: [Select]

[SYNDROME]
[SYN_CLASS:BUFF]
[SYN_NAME:Brain Impairment test]
[SYN_INGESTED]
[SYN_INJECTED]
[CE_IMPAIR_FUNCTION:SEV:<severity>:PROB:100:BP:BY_TYPE:THOUGHT:ALL:START:0:END:20]
<severity> must be at least 9900 to completely impair brain function, even 9899 doesn't cause an "impaired" status. Can anyone confirm this in the arena? This is on a clean copy of DF by the way.

I'm not sure if brain impairment actually does anything other than cause some weird instant death oddities involving combat.

Yeah, the idea was to find the threshold of "Alright if you get this much you're screwed" and put that onto some syndromes so if you had too many you'd die almost instantly. Still though, 9900 is a bit much, but now as I'm testing it ON said syndromes and not alone, it seems to be impairing fine... I don't even.

EDIT: Alright what the tits. Now 100 is enough to kill some poor idiot who I forced to drink bogeyman ichor.

I haven't tested this a lot, but I found that if you have the END of a syndrome too close to the START, it is weakened. My favorite rapid death syndrome (severity 30000 bleeding from every body part) had START:0:PEAK:60 and no END. I couldn't put the PEAK closer than ~60 to the START. I don't know if I even need a PEAK. It's like there is a maximum rate of increase of syndrome worsening.

Perhaps the syndrome only procs on the creature's turn, and since typical creatures have 10-11 ticks between turns it might not proc twice in the 20 ticks that you have in your syndrome (if it needs to proc twice).

[adwarf]

Just making sure, but is there a limit to the number of regents you can have to make an item?

[Stirk]

Just making sure, but is there a limit to the number of regents you can have to make an item?

Well nothing except practicality. Put as many as you want.

[i2amroy]

Just making sure, but is there a limit to the number of regents you can have to make an item?

Well nothing except practicality. Put as many as you want.

Probably 32,767; or maybe 2,147,483,647. But yeah, for all intents and purposes it's unlimited (though a large number of reagents will slow down a reaction since the workshop will become cluttered due to the large number of items within it).

[adwarf]

Just making sure, but is there a limit to the number of regents you can have to make an item?

Well nothing except practicality. Put as many as you want.

Probably 32,767; or maybe 2,147,483,647. But yeah, for all intents and purposes it's unlimited (though a large number of reagents will slow down a reaction since the workshop will become cluttered due to the large number of items within it).

That's good, though I don't think I'll be going beyond 8 at most.

[narhiril]

Just making sure, but is there a limit to the number of regents you can have to make an item?

Well nothing except practicality. Put as many as you want.

Probably 32,767; or maybe 2,147,483,647. But yeah, for all intents and purposes it's unlimited (though a large number of reagents will slow down a reaction since the workshop will become cluttered due to the large number of items within it).

That's good, though I don't think I'll be going beyond 8 at most.

The most I have ever used was around 35.  It was horribly inefficient, as dwarves would get hungry, thirsty, or fall asleep while gathering materials.  I ended up changing it shortly afterwards.

You should be fine with 8, though.

[vjek]

Looking for some confirmation or more information on some observations.

My goal is to make GIANT and *_MAN "animals" more aggressive, so they attack everything, everyone all the time, without hesitation.

to that end, I've modified c_variation_default.txt and successfully added in:

   [CV_NEW_TAG:LIKES_FIGHTING]
   [CV_NEW_TAG:LARGE_PREDATOR]
   [CV_NEW_TAG:NOFEAR]
   [CV_NEW_TAG:OPPOSED_TO_LIFE]

to the appropriate areas, and saw good results, as expected.

However, I've been trying to add in

   [CV_NEW_TAG:CURIOUSBEAST_EATER]
   [CV_NEW_TAG:CURIOUSBEAST_GUZZLER]
   [CV_NEW_TAG:CURIOUSBEAST_ITEM]

And if I do, it seems to break things.  Specifically, I never seen any GIANT or *_MAN creatures at all.  If I remove those entries, things go back to normal.  These values are extremely useful in getting animals to investigate the fortress, so having them would be quite beneficial for my goal.  It's like DF is seeing the entries as an error, and will never spawn them on the embark.

Is there something special about these tags that I can't use them as part of a variation?  Or is there a syntax I'm missing?
If you know, please share!