Print

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

Me

16 (22.9%)

Me!

54 (77.1%)

Total Members Voted: 69

[Lost in Nowhere]

Here are the raws for the Daemonic Cherubim, and all other related raws:
-snip-

IMPORTANT:

• To force compatibility with both vanilla DF and other players' contributions, so that raws never clash, and novelty so that copypasting simply does not work, you must add _XYZ to the end of every object that you newly add/define, where XYZ is an at least 3 letter handle that you chose. Mine was HLG, so that I would add a "BODY:REALLY_SIMPLE_BODY_HLG" instead of "BODY:REALLY_SIMPLE_BODY". The exception to this is language words. Not doing this will eventually destroy everything. Referring to other players raws of course does not need this, if XYZ came before me I could use BODY_XYZ in my creature, but if I make a new body... as above.
• Similarly name your files by turn, eg. "creature_domestic_halfling", so we can keep track of things.

You probably should add the _XYZ before uploading.

[laularukyrumo]

I, for one, love the idea of having C_Variations all up in the everywhere. I'm working on c_variation_infect, which causes the affected creature to have attacks that cause the victims to become permanently weaker, and causes them to instantly die if too many of the debuffs stack on them.

I'm not getting it to work though, because apparently, if you attempt to apply two different syndromes with CE_PHYS_ATT_CHANGE tags, the second one just doesn't do anything. It doesn't even overwrite the first one. Which is bollocks, because not only does it make vamps and maybe paladins immune to infect damage, but since there's no way to delete a syndrome from a creature, not even transformation, it doesn't appear to be possible to implement the way I intended, with progressive decreases to physical stats.

[Putnam]

END timers should work.

[WillowLuman]

Is it really not possible to have more than 1 syndrome affecting stats?

[Halfling]

There's different claims. Even I'm not sure and I've used syndromes a ton. Research is needed...

I, for one, love the idea of having C_Variations all up in the everywhere. I'm working on c_variation_infect, which causes the affected creature to have attacks that cause the victims to become permanently weaker, and causes them to instantly die if too many of the debuffs stack on them.

I'm not getting it to work though, because apparently, if you attempt to apply two different syndromes with CE_PHYS_ATT_CHANGE tags, the second one just doesn't do anything. It doesn't even overwrite the first one. Which is bollocks, because not only does it make vamps and maybe paladins immune to infect damage, but since there's no way to delete a syndrome from a creature, not even transformation, it doesn't appear to be possible to implement the way I intended, with progressive decreases to physical stats.

Anything is possible with interactions and syndromes if you use your imagination. Like, really, I'm not even kidding. They probably make a Turing complete language and you could build a dwarven syndrome computer.

For example to make a syndrome that you can also make end when you like:

Syndrome 1: Can do interaction 1, duration t+100; Target cannot have syndrome class: SYN_CLASS; Self only, free action
Interaction 1: Target cannot have syndrome class STOP_SYN_CLASS; Add syndrome [syndrome content] to target, duration t, syndrome class is SYN_CLASS; Add copy of syndrome 1 to target;

Simple loop. Now the creature will
1) Suffer from the syndrome for t phases, and be able to restart the syndrome for t+100 phases
2) During the 100 phases when the creature does not suffer from the syndrome but can restart it, go to 1, except
3) If it at that time is also infected with a syndrome of class STOP_SYN_CLASS, instead let the syndrome expire

That would work for your system. For example. Then you make various severities of the syndrome - they only need the one loop, you can have multiple syndrome "branches" and define conditions for when each one is applied.

In case that doesn't work and the timer doesn't get extended correctly (it's been a while), then:

Syndrome 0: Can do interaction 0, start:t+101, duration 100; Self only, free action
Interaction 0: [Add syndrome 1 to self]
Syndrome 1: Can do interaction 1, duration t+100; Target cannot have syndrome class: SYN_CLASS; Self only, free action
Interaction 1: Target cannot have syndrome class STOP_SYN_CLASS; Add syndrome [syndrome content] to target, duration t, syndrome class is SYN_CLASS; Add copy of syndrome 0 to target;

is sure to work, adding a step where you wait for the content and loop syndromes to clear before restarting the loop. It's obviously not optimized at all and a mess, but you get the idea.

[Halfling]

Speaking of, here's an example of how you might use syndromes to store and operate on information. I think? "How many more units of dwarven wine were drunk during the last x phases than units of dwarven ale? Calculate and print result."

Spoiler (click to show/hide)

I'll omit most obvious syndrome details like time.

First, define a stored integer (maximum size is 100). The integer size is stored in a syndrome loop.
Transform the creature that is supposed to act to store numbers into an INTEGER_CREATURE with a syndrome beforehand.

Code: [Select]

Syndrome group integer array: [INTEGER_100 - INTEGER_1]
Can do interaction: PRESERVE_INTEGER_N (N is integer number)
It cannot have class: INTEGER_N+1
It cannot have class: INTEGER_N-1
Add to self: INTEGER_N

Adds a higher integer syndrome, removes the existing one

Code: [Select]

Interaction INCREMENT_INTEGER_[100-1]
It requires: INTEGER_N
Adds syndrome INTEGER_N+1
Adds a lower integer syndrome, removes the existing one

Code: [Select]

Interaction DECREMENT_INTEGER_[100-1]
It requires: INTEGER_N
Adds syndrome INTEGER_N-1
Add this to plump helmet wine

Code: [Select]

Syndrome COUNTER_INCREMENT
Can do interaction INCREMENT_INTEGER_[100-1]
Targets INTEGER_CREATURE on map
Add this to dwarven ale

Code: [Select]

Syndrome COUNTER_DECREMENT
Can do interaction DECREMENT_INTEGER_[100-1]
Targets INTEGER_CREATURE on map
Infect the integer creature with this when you start:

Code: [Select]

Syndrome PRINT
After time x,
Can do interaction: FIND_INTEGER_[100-1], targeting self
FIND_INTEGER_N: It cannot have class INTEGER_[0...N-1]; It cannot have class INTEGER_[N+1...100]: Add syndrome: Can do PRINT_INTEGER_N
PRINT_INTEGER_N: Maximum targets: N, anywhere on the map: Add syndrome: Bleeding:9001: by bp category:all:all:start:0

Requires that one dwarf is transformed into an INTEGER_CREATURE affected by the INTEGER syndromes. Increments and decrements the integer when things happen on the map for x phases, then prints it by near-instantly killing as many random creatures on the map as the integer is at that point.

[WillowLuman]

The principle sounds useful, though that specific example is weird.

[Zorg Master Xyon]

Hey guys! May I do a play turn? I've been playing a little bit of this in the older versions and thought it might be cool to do a play turn.

[Halfling]

Hey guys! May I do a play turn? I've been playing a little bit of this in the older versions and thought it might be cool to do a play turn.

Please do, we need one

The principle sounds useful, though that specific example is weird.

Not at all, the idea is that you can use it to read, increment and decrement an integer value, so it's possible to discriminate which state and which square of memory you are in by syndromes alone (compare to the classic tape, state, table, r/w Turing machine, however, with limited pre-initialized memory as is often the case). When you can further use this value to point to itself or other values (INTEGER_N: CDI: TARGET_DWARF_N) and perform operations on them it is clear that syndromes in fact form a programmable computer.

I will not be spending hours actually proving this as there is a line, though.

[WillowLuman]

I didn't dispute your claim, I just said your example was weird.

[Halfling]

True. It was lazy. You could do a prime test where you feed creatures a number of mushrooms to initialize the syndrome-interaction computing, and in the end the computer creature vomits if the number of mushrooms eaten is prime and sweats blood if it's not. It's doable if those above registers work, (and if they don't due to the syndrome stacking, you just have to create a copy of them and make them alternate between themselves and the copy) and you add a syndrome to represent zero, with the algorithm

Spoiler (click to show/hide)

Code: [Select]

Using the above...

Initialize I, J, K to 0 (infect 3 creatures with integer syndromes; they must also have a syn_class to identify which creature is which)
Increment integer J to 1
Increment integer I to P (add a syndrome to pumpkins that causes this to happen whenever one is eaten, and another to start the rest of the program to, say, a tarnish stalk)
While J < I (creature hosting J is infected with a syndrome from I to stop it at that point)
   Copy value from I to K (infect with same integer syndrome)
   Increment integer J
   Initialize L to 0
   While K > 0
      Decrement K by J steps'
      Copy value of K to L
      If L equals zero, infect creature hosting I with syn NOT_PRIME (causes sweating blood)
When J is stopped from incrementing, infect creature I with a syndrome to vomit (unless it has syn NOT_PRIME)


but if I ever am bored enough to do that, I'll make it its own thread. It doesn't look like I have a chance to be that bored in a long while though.

[Lost in Nowhere]

Hey guys! May I do a play turn? I've been playing a little bit of this in the older versions and thought it might be cool to do a play turn.

If you're playing Halflings, build a wall around your town. It helps immensely.

[Kazimuth]

I'd also be interested in a play turn; I've been playing with the most recent raws from Zanzetkuken's turn, and I realized I might as well contribute 

Some random quibbles:
Formics are extremely weak to eye hits; eye attacks pretty much always open major arteries, and then they bleed out pretty quickly.

Spoiler (click to show/hide)

This is the entire combat log from a fight with a formic bandit:

(also, eyes and antennae appear to be kept inside robes. Is that intentional?)

There does not appear to be any way to manufacture quivers. You can spawn with them in adventure mode (silk quiver) but aside from that they are nonexistent. I think this may be interfering with hunting; my halfling hunters generally refuse to hunt, even if there are animals, bows, and arrows available (and they don't appear to use rocks to hunt).

On embark, if you pick 'prepare for the journey carefully', you start out with no points available, as they are all invested in a 400-coin iridium anvil. You can get rid of it, but it's still initially disconcerting. Also, some odd items show up for purchase: 'nothing leather' and 'tarnish stalk cloth cloth', if I remember correctly.

I'm also getting 'unrecognized inorganic token' spam in the errorlog:

Spoiler (click to show/hide)

Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COAL_BITUMINOUS
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: IRON
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: IRON
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: SAND_TAN
Unrecognized Inorganic Token: SAND_WHITE
Unrecognized Inorganic Token: SAND_BLACK
Unrecognized Inorganic Token: SAND_RED
Unrecognized Inorganic Token: SAND_YELLOW
Unrecognized Inorganic Token: GYPSUM
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: IRON
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: IRON
Unrecognized Inorganic Token: COPPER
Unrecognized Inorganic Token: COPPER

And I've just started getting these errors:

Spoiler (click to show/hide)

path fail: water strider,108,112,4 -> 109,111,5: Id #345:Path Goal Conflict Defense:Station None at 96,110,4
path fail: dirigible antelope,113,113,4 -> 113,114,5: Id #374:Path Goal Conflict Defense:Station None at 116,110,4
path fail: dirigible antelope,113,113,4 -> 113,114,5: Id #374:Path Goal Conflict Defense:Station None at 116,110,4

This universe is coming along great though. Pitting dragons against swarms of dirigible antelopes in the arena is hilarious

[Zanzetkuken The Great]

This universe is coming along great though. Pitting dragons against swarms of dirigible antelopes in the arena is hilarious

I'm curious as to the results.


Lizardfolk Play Guide (Not Finished!)

-Get rid of the anvil.  The Lizardfolk have their own custom type of forge that does not need the anvil.

-Smithing is entirely tied to the 'Woodburner' profession.  This is necessary in order to have a limit to the number of metals that they have the ability to utilize.

-Don't bother with getting plants, the Lizardfolk race is entirely carnivorous.  Instead, get a decent amount of tamed animals.  Preferably not dragons, they won't eat anything that has scales.

-All of the other races are hostile, due to the child snatching tag on the Lizardfolk.  In universe, this was intended to represent the fact that  other races use the Lizardfolk as warriors, and the Dragonkin take Lizardfolk to use their magic upon the Lizardfolk to turn them into more Dragonkin.

-Lizardfolk nobility is an evolving system.  If you are less than a certain population, then they are named one way, but after that population is reached, then they gain new names.

-Lizardfolk do not build up walls.  The most that they build in terms of defenses is the occasional barricade in the marshes.  (Note: they are an aboveground race.)

-A word to authors: Lizardfolk do not believe in the concept of good and evil.  The closest they come is the concepts of chaos and order.

[kero42]

-Don't bother with getting plants, the Lizardfolk race is entirely carnivorous.  Instead, get a decent amount of tamed animals.  Preferably not dragons, they won't eat anything that has scales.

-All of the other races are hostile, due to the child snatching tag on the Lizardfolk.  In universe, this was intended to represent the fact that  other races use the Lizardfolk as warriors, and the Dragonkin take Lizardfolk to use their magic upon the Lizardfolk to turn them into more Dragonkin.

-Lizardfolk do not build up walls.  The most that they build in terms of defenses is the occasional barricade in the marshes.  (Note: they are an aboveground race.)

This should give fortress defense an interesting twist, at least for people like me who are used to digging into hills  . Are the lizardfolk stronger than other races, to compensate for the (as I see it) openness and vulnerability that comes with being enemies with everyone and unable to build or dig enclosures? Still, I really wish I had the time and patience to learn how to mod so that I could work on this too.

On a side note, how many playable races do we have thus far, and where do they live? Just curious to see where they overlap map-wise.