Print

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

1

2

3

4

5

[than402]

yep. that's because they represent the time needed for the creature to eat, not the quantity it needs. cockroaches have 10000, stag beetles have 3000. baby beetles have the same as adults. you mentioned babies dying while adults being fine. I searched and could not find any grazer with baby token, so it seems plausible...

[Vitellozzo]

Tomorrow I'll try a test fort with only adults and children grazers to see how's going for time and working status.

[Insanegame27]

I'm away for 10 days so i cant do much. see yas in 10 days

[heydude6]

I think I know why this bug is happening. I think it's because babies can't feed themselves and they rely on mothers to do it for them. So when it's baby grazers mothers can't feed them. Try using CHILD instead.

[than402]

I'll remove the baby tag in the next edition.

[Vitellozzo]

The problem seemed exactly the BABY tag.

That what happened after I removed the tag from raws.

Spoiler (click to show/hide)

This is my stag beetle child test. 13 of malachite. More of 4 months grazing, he's feeding himself. I even started on snow, I put the grazers on the snow covered dense grass, no one felt hungry once.

The cockroaches work as intended even before the fix.
:edit: since I think you wanted to make the children grow for 3 years, after removing BABY:1 we can just prolong CHILD tag from 2 to 3 years.

:re-edit: I already had a queen, now another one came in a migration wave. My queen suddenly turned opposed to life, while the second one should be the one I'll take? awww man, my first queen was a good working mate.

[than402]

The problem seemed exactly the BABY tag.

That what happened after I removed the tag from raws.

Spoiler (click to show/hide)

This is my stag beetle child test. 13 of malachite. More of 4 months grazing, he's feeding himself. I even started on snow, I put the grazers on the snow covered dense grass, no one felt hungry once.

The cockroaches work as intended even before the fix.
:edit: since I think you wanted to make the children grow for 3 years, after removing BABY:1 we can just prolong CHILD tag from 2 to 3 years.

:re-edit: I already had a queen, now another one came in a migration wave. My queen suddenly turned opposed to life, while the second one should be the one I'll take? awww man, my first queen was a good working mate.

the RNG giveth, the RNG taketh away. we had raised the percentage of queens a bit because waspen civilizations were continuously ruled by megabeasts before that. no queens were spawned it worked, but it also means that having a queen in a migrant wave is a potential possibility.

ok, new update is up. I removed the baby token from the beetle, added a reaction to destroy slag in the smelter and also added new colors to many animals. finally, I made wasp coating and many reactions (like the Searskin, for instance) give titles so the player which wasp/animal has which mutation

http://dffd.bay12games.com/file.php?id=9734

well, I believe we can finally call it a beta. there may still be bugs around, but the race has defined features, a playstyle and is perfectly playable

finally I'd like to say thank you, Vitellozzo. your feedback allowed us to fix a ton of bugs and add a lot of stuff that were missing. thank you for what you're doing

[Vitellozzo]

I'm going to test the new beta version as soon as possible!

Anyway, thanks you too. It was natural that for a person with likes as me to be attracted by an insect race with so many peculiar traits! I love the concept and I love how did this mod became.
Anyway as soon as this baby is gonna touch the beta stage, we should beware that the game is going straight on: the 40xx version is out in the wild from months, and even Meph is going to work on the last game. Aside from that, succubi and orcs are gonna become updates soon, since their modders are working on them too.

So while we should follow the path to the final v1.0, we should also keep in mind that the stable full version must be just the starting point, to make the full mod once we hit 40xx too.
And that can be achieved only with the help of Meph.

Obviously, I'll continue testing this since I really love the concept, and I'd love to see the final version with full options and !GRAPHICS!, but it doesn't matter to much to me: I've started df in ascii, and that isn't gonna hurt me.
Anyway, time for me to make a(nother one) hive fortress!
I hope RNG will be kind to me this time.


Anyway, the queen problem can be read as "one of your queens is gonna become the bad one"? I thought they were gonna fight to the death until just one will prevail, and that will be your queen... but now I just have a opposed to life old queen (with good skills) just sitting near the map corner, really don't making too much mess of anything.

[than402]

Anyway as soon as this baby is gonna touch the beta stage, we should beware that the game is going straight on: the 40xx version is out in the wild from months, and even Meph is going to work on the last game. Aside from that, succubi and orcs are gonna become updates soon, since their modders are working on them too.

the raws are the easy part. The scripts on the other hand... there is no autosyndrome anymore. I don't know why, but it was replaced with reaction trigger and I have no clue how that works... that's the hardest part in my opinion. we have also borrowed boltgun's makeown

So while we should follow the path to the final v1.0, we should also keep in mind that the stable full version must be just the starting point, to make the full mod once we hit 40xx too.
And that can be achieved only with the help of Meph.

I agree. Masterwork changes, the mod must be updated too. but in order to update something, you must have a stable foundation to work on

Obviously, I'll continue testing this since I really love the concept, and I'd love to see the final version with full options and !GRAPHICS!, but it doesn't matter to much to me: I've started df in ascii, and that isn't gonna hurt me.
Anyway, time for me to make a(nother one) hive fortress!
I hope RNG will be kind to me this time.

well, that's heydude's turf, not mine

getting a queen shouldn't be that common. I remember it only happened to me once.

Anyway, the queen problem can be read as "one of your queens is gonna become the bad one"? I thought they were gonna fight to the death until just one will prevail, and that will be your queen... but now I just have a opposed to life old queen (with good skills) just sitting near the map corner, really don't making too much mess of anything.

if I remember correctly, heydude wrote the interactions for this one, so I can't really say what went wrong... I'll look it up, but there's no sure way to force them to duel. that I know of, at least. Did at least the other queen remain unaffected or did they both went opposed to life?

[Vitellozzo]

The new one is unaffected, yes. It's working and living as intended.

[than402]

well, that's something... it doesn't work perfectly, but at least it doesn't cause troubles. I'll see if there is any way we can make it work better...

[heydude6]

Anyway I just thought of a theoretical way to fix it although I don't know when I'll be able to test it.

[than402]

do tell

[heydude6]

Well basically it's the same system as before but both queens have an interaction that gives every wasp they see (except queens) [IMMOBILE] and [NON_LIVING]. Once the queens finish their duel and the [OPPOSED_TO_LIFE] syndrome expires fixloyaltycascade is run and then everything continues as normal.

[than402]

i'm not so sure freezing half the hive is a good idea... many things can go wrong, the two queens may be able to see but not reach each other, a megabeast or a siege may arrive during the duel, important jobs get delayed, rottable parts waste away... too many ways this can mess things up