Print

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

[exarion]

A while ago, there a bug about duplicate companions after they left and rejoined. As it turns out, the same thing happens to necromancers whenever they animate a corpse that was in their party when it died. Another problem is that this increases your companions count despite not actually increasing the number of companions you have. This means that ambushes quickly get to be very large, which will probably mean the you need to reanimate your corpses more. This can eventually lead to blatantly impossible ambush sizes, as you'll encounter 3000 goblins from a civilization of 1500, and eventually encounter an ambush of 6000 kobolds in world with 5000 total population. These battle predicatably cause massive amounts of lag, and it takes about 3 seconds to complete one move on my system.

Spoiler: technical (click to show/hide)

As for the bug itself, I believe its caused by the game adding a new pointer to the companions list whenever you attain a new companion, as in DF2010 it was safe to assume that any companions in your party would be unable to leave without be removed from the list. Additionally, there was no way to re-add companions who were already in your party. However, because dead companions aren't removed, necromancy lets you regain companions in your party, resulting in duplicate entries. A quick fix for this would be to add a check when gaining a new companion to see if they're already in you party, and not add them to the companions list if they are.

Brief version: If you play as a necromancer, be careful about reanimating a corpse that was in your party, and be sure to attack one of your corpses occasionally to keep your bugged large army from generating lag-inducing ambushes.

[i2amroy]

Even if this is a bug, if you have a computer that can handle it is seems like an awesome way to enact those "1 man versus and army battle scenes" that you dream of in so many adventure games.

[Zale]

Even if this is a bug, if you have a computer that can handle it is seems like an awesome way to enact those "1 man versus and army battle scenes" that you dream of in so many adventure games.

Of course, those don't usually end with the hero being riddled with crossbow bolts.

[WisdomThumbs]

Even if this is a bug, if you have a computer that can handle it is seems like an awesome way to enact those "1 man versus and army battle scenes" that you dream of in so many adventure games.

Of course, those don't usually end with the hero being riddled with crossbow bolts.

I actually can't think of any examples where the 1 man vs. Army scenario plays out in any way that includes the 1 man surviving. Well, maybe if you include really over the top action movies like Rambo, but that's not so much a last stand as a supersoldier hunting down mooks.

[Nyan Thousand]

Even if this is a bug, if you have a computer that can handle it is seems like an awesome way to enact those "1 man versus and army battle scenes" that you dream of in so many adventure games.

Of course, those don't usually end with the hero being riddled with crossbow bolts.

I actually can't think of any examples where the 1 man vs. Army scenario plays out in any way that includes the 1 man surviving. Well, maybe if you include really over the top action movies like Rambo, but that's not so much a last stand as a supersoldier hunting down mooks.

Yeah, most last stands usually don't work in favor of the standing (Thermopylae, Constantinople, Tirad Pass, Alamo, Iwo Jima, and many many many others). There's Zulu, of course (I just googled it, it's Rorke's Drift), but that's the exception and not the rule.

Still, this is Dorf Fort. This is where we go beyond the impossible and we kick reason to the curb. Who the hell do you think we are?

[Rumrusher]

A while ago, there a bug about duplicate companions after they left and rejoined. As it turns out, the same thing happens to necromancers whenever they animate a corpse that was in their party when it died. Another problem is that this increases your companions count despite not actually increasing the number of companions you have. This means that ambushes quickly get to be very large, which will probably mean the you need to reanimate your corpses more. This can eventually lead to blatantly impossible ambush sizes, as you'll encounter 3000 goblins from a civilization of 1500, and eventually encounter an ambush of 6000 kobolds in world with 5000 total population. These battle predicatably cause massive amounts of lag, and it takes about 3 seconds to complete one move on my system.

Spoiler: technical (click to show/hide)

As for the bug itself, I believe its caused by the game adding a new pointer to the companions list whenever you attain a new companion, as in DF2010 it was safe to assume that any companions in your party would be unable to leave without be removed from the list. Additionally, there was no way to re-add companions who were already in your party. However, because dead companions aren't removed, necromancy lets you regain companions in your party, resulting in duplicate entries. A quick fix for this would be to add a check when gaining a new companion to see if they're already in you party, and not add them to the companions list if they are.

Brief version: If you play as a necromancer, be careful about reanimating a corpse that was in your party, and be sure to attack one of your corpses occasionally to keep your bugged large army from generating lag-inducing ambushes.

Toady coded it so that when you reanimate a body you make a new unit that copies the body description, wounds, and race. re-reanimating said body again just copies the zombie unit body again so if you reanimate a companion you have 1 companion soul and 1 zombie soul. The only way this doesn't work is if you resurrect the body which will bring back the unit from death. What happen to the guy seem totally different and really is a bug.

[davros]

Even if this is a bug, if you have a computer that can handle it is seems like an awesome way to enact those "1 man versus and army battle scenes" that you dream of in so many adventure games.

Of course, those don't usually end with the hero being riddled with crossbow bolts.

I actually can't think of any examples where the 1 man vs. Army scenario plays out in any way that includes the 1 man surviving. Well, maybe if you include really over the top action movies like Rambo, but that's not so much a last stand as a supersoldier hunting down mooks.

Yeah, most last stands usually don't work in favor of the standing (Thermopylae, Constantinople, Tirad Pass, Alamo, Iwo Jima, and many many many others). There's Zulu, of course (I just googled it, it's Rorke's Drift), but that's the exception and not the rule.

Still, this is Dorf Fort. This is where we go beyond the impossible and we kick reason to the curb. Who the hell do you think we are?

Some guys whose forts eventually end up mindraped by the HFS?

[exarion]

A while ago, there a bug about duplicate companions after they left and rejoined. As it turns out, the same thing happens to necromancers whenever they animate a corpse that was in their party when it died. Another problem is that this increases your companions count despite not actually increasing the number of companions you have. This means that ambushes quickly get to be very large, which will probably mean the you need to reanimate your corpses more. This can eventually lead to blatantly impossible ambush sizes, as you'll encounter 3000 goblins from a civilization of 1500, and eventually encounter an ambush of 6000 kobolds in world with 5000 total population. These battle predicatably cause massive amounts of lag, and it takes about 3 seconds to complete one move on my system.

Spoiler: technical (click to show/hide)

As for the bug itself, I believe its caused by the game adding a new pointer to the companions list whenever you attain a new companion, as in DF2010 it was safe to assume that any companions in your party would be unable to leave without be removed from the list. Additionally, there was no way to re-add companions who were already in your party. However, because dead companions aren't removed, necromancy lets you regain companions in your party, resulting in duplicate entries. A quick fix for this would be to add a check when gaining a new companion to see if they're already in you party, and not add them to the companions list if they are.

Brief version: If you play as a necromancer, be careful about reanimating a corpse that was in your party, and be sure to attack one of your corpses occasionally to keep your bugged large army from generating lag-inducing ambushes.

Toady coded it so that when you reanimate a body you make a new unit that copies the body description, wounds, and race. re-reanimating said body again just copies the zombie unit body again so if you reanimate a companion you have 1 companion soul and 1 zombie soul. The only way this doesn't work is if you resurrect the body which will bring back the unit from death. What happen to the guy seem totally different and really is a bug.

I can confirm that I am encountering multiple entries for the same companion.

[Rumrusher]

A while ago, there a bug about duplicate companions after they left and rejoined. As it turns out, the same thing happens to necromancers whenever they animate a corpse that was in their party when it died. Another problem is that this increases your companions count despite not actually increasing the number of companions you have. This means that ambushes quickly get to be very large, which will probably mean the you need to reanimate your corpses more. This can eventually lead to blatantly impossible ambush sizes, as you'll encounter 3000 goblins from a civilization of 1500, and eventually encounter an ambush of 6000 kobolds in world with 5000 total population. These battle predicatably cause massive amounts of lag, and it takes about 3 seconds to complete one move on my system.

Spoiler: technical (click to show/hide)

As for the bug itself, I believe its caused by the game adding a new pointer to the companions list whenever you attain a new companion, as in DF2010 it was safe to assume that any companions in your party would be unable to leave without be removed from the list. Additionally, there was no way to re-add companions who were already in your party. However, because dead companions aren't removed, necromancy lets you regain companions in your party, resulting in duplicate entries. A quick fix for this would be to add a check when gaining a new companion to see if they're already in you party, and not add them to the companions list if they are.

Brief version: If you play as a necromancer, be careful about reanimating a corpse that was in your party, and be sure to attack one of your corpses occasionally to keep your bugged large army from generating lag-inducing ambushes.

Toady coded it so that when you reanimate a body you make a new unit that copies the body description, wounds, and race. re-reanimating said body again just copies the zombie unit body again so if you reanimate a companion you have 1 companion soul and 1 zombie soul. The only way this doesn't work is if you resurrect the body which will bring back the unit from death. What happen to the guy seem totally different and really is a bug.

I can confirm that I am encountering multiple entries for the same companion.

Yeah because there different unit each reanimation. your not reanimating the same zombie unit but a new zombie unit with the name "[person's body]'s corpse" due to companions keep track of living and dead folks you can pile up a huge list of the same zombie name for each new unit companion. Dfusion or dfhack could properly fully heal each of those guys and you could technically make an army of clones.