9 replies to this topic

[HRose]

This is what happens when my priest summons undead the first time she got the spell:



I guess it's related to this.

I've tried the Turambar fix, but it did nothing.

So I tried uninstall the "Distinctive Undead: v5" and now I have my skeletons back, they are GREEN, but at least they are skeletons.

Is this a known problem? If so why it wasn't fixed? It seems odd since I'd guess the summon undead spell is quite popular...

[Miloch]

This is a known issue and AFAIK corrected by Turambar's fix. The IA code is currently too complex to implement a simple fix for this but I expected Turambar's fix to be implemented in the BWP Fixpack (some time ago actually). As for "green skeletons" they are probably just ghouls, which was the problem with some other mod in the first place.

[Wisp]

Green skeletons from Animate Dead are vanilla. They have some funky colouring going.

[HRose]

I tried installing Turambar's fix before I uninstalled "Distinctive Undead", but it didn't work.

[Wisp]

The IA code is currently too complex to implement a simple fix for this

I get how a thing like this could have occurred, but I don't get why you say this. The problem is not that the ghast is red. The problem is that you change it into a ghast. But ghastsu.cre is not a ghast, it never was a ghast and it should not be a ghast. From what I can see, the code makes a single reference to the file. Removing ghastsu.cre from the ghast list completely and correctly fixes the problem. I don't see anything complex about it.

[Wisp]

Yes, Wisp, it is an easy fix and I fixed it locally some time ago, but I have also been working on quite a few other changes/enhancements, so the current development version of IA is quite different from the current released version.

Oh, you mean comlex like that. Well, you could take the version that is currently available to the public, make the corrections to that and release it as a new version. No need to involve any more of that other stuff you have been working on than you really have to. But as you say, the issue is rather minor, so maybe it is not worth the bother.

[horred the plague]

This one's not so 'complex' as the last skeleton issue....

I saw another problem with the Skeleton Warriors, and tracked it down to this mod (via windows search, dltcep and weidu.log). Your code is setting their General field as "Monster", when it should be left as "Undead". This affects a lot of hardcoded and scripted behavior alike in relation to them. No longer can clerics turn/control them, e.g.

The real giveaway for me was when I saw Imoen trying to backstab one of them while using the BP Series scripts. This naturally caused me to look into it, as I was just bug-fixing that code the night before. My conditional check for General(...,UNDEAD) was still in place....

[Lollorian]

And the Vecna mod does this too

Line 11 of t-skelwa.tpa in both mods need to WRITE_BYTE 0x271 4 //General (undead) instead of WRITE_BYTE 0x271 255 //General (monster)

Attached Files

•  infinityanimations_vecna_skellie_warrior_undeadification.7z   889bytes   279 downloads

[Miloch]

This is intentional. Skeleton warriors cannot be turned per PnP rules. Before someone else objects to putting these kinds of fixes in an animation mod, it's redundant to what's already in existing fixpacks (at least BG1 certainly from what I recall) possibly even the unmodded game if they did it correctly, which they sometimes did. Maybe SCS too, and I'm kinda surprised BP doesn't set the field correctly. The intention here is to enforce field consistency when making global .cre changes. Sex and gender are particularly buggered in many cases; we have to pay special attention to those because they're linked to casting sounds, which would other be inconsistent with the sound 2DAs and files the mod provides.