Monty

Ah, yes, it works. And I don't have to deal with two creatures. All I needed was to have the creature break its invisibility on attack and it's like she's already been checking for enemies. This is awfully simple and very clean.

Thank you very much, Miloch. I still have one further question...

Should I want an ethereal buffer who appears only when I'm hurt to heal me, then this is usable, right?

***Code deleted.***

Thank you for your patience.

EDIT: Figured it out. My code was more complicated than it should be. Will follow up with some more questions soon enough, if need be.

Nevermind. I'll figure it out on my own.

Thanks.

@Monty/SoS: I think you've got "Disable_TobEx 0" and "Disable_TobEx 1" the wrong way round in that last post.

"Disable_TobEx 0" (default) is the one where TobEx gets installed along with SCS/SCSII. MDR doesn't work properly (for me) in this case.
"Disable_TobEx 1" is the one where TobEx doesn't get installed along with SCS/SCSII. MDR works properly (for me) in this case.

Sorry about that. I interchanged them as I was already too sleep to check it out. Anyway, the combinations stand. Right now, though, I used the following set-up and stuck with it:

Fresh BG2 install --> other mods --> SCSII v19 with ToBEx enabled --> renamed ToBEx.dll to ToBExdisable.dll.

This works perfectly as I can just turn it on or off depending on what I want to do.

Hello, Ascension 64. Thanks for your time. There, I've registered. This is Saint of Sinners by the way.

I updated my ToBEx to beta0020. Still, the magic damage problem persists. Here are a lists of combinations I did with the installs and their respective results:

- SCSII v19 = damage is still there
- SCSII v19, Disable ToBEx 1, reinstall = damage gone
- SCSII v19, Disable ToBEx 0, reinstall = damage returns
- SCSII v19, Disable ToBEx 0, renamed ToBEx.dll to ToBExdisable.dll = damage gone
- Fresh BG2 ToB install, patched, Disable ToBEx 1 before SCSII install, SCSII v19 install = damage gone
- Fresh BG2 ToB install, patched, Disable ToBEx 0 before SCSII install, SCSII v19 install = damage there
- Fresh BG2 ToB install, patched, SCSII v19 install, ToBEx beta0020 install = damage there
- Fresh BG2 ToB install, patched, SCSII v19 install, ToBEx beta0020 install, ToBExdisable.dll = damage gone

At this point, it is fairly safe to assume that ToBEx causes the problem. Right now, I'm playing it again with the modifications I've posted in post #479 with ToBEx.dll renamed to ToBExdisable.dll. The game is working fine, but ToBEx is, well, gone. Which is kind of a big thing, really.

Hopefully, this helps you as you update along with ToBEx. This has also been experienced by at least two more players over at the Bioware forums. One settled for SCSII v15, while the other installed SCSII v19 but with Disable ToBEx 0. Really praying to pin this one down.

Again, thank you for your time. All the best.

Monty

EDITED: As per Anonymous_Hero's post. I interchanged Disable ToBEx 0 with Disable ToBEx 1.