Anti magic attacked on Mac scs v31 still using area of effect

[culmore]

I downloaded osx-stratagems-v31.tar.gz on my Mac, for the enhanced Edition of Baldurs Gate II. Installation seemed to be okay. When I play the game in the spell description for Spell Strikes talks about "closest hostile creature to the point that the spell caster designates" and this is how the spell behaves I can even target the ground I dont need to target a enemy.

 

I thought version 31 of SCS did not use an area of effect or did I not understand correctly?? I said yes to the option below.

In the read me file I see:

 

"Antimagic attacks penetrate improved invisibility

This component changes those spells which target a creature's spell defences (e.g. Secret Word, Spellstrike, Ruby Ray of Reversal - but not Breach) so as to allow them to target creatures which are protected by Improved Invisibility. The idea of this component is that these spells can now be cast on enemy mages who are protected by Improved Invisibility - this makes the Improved Invisibility / Spell Immunity: Divination combination less overpowering.

Prior to version 16, this component worked by giving the spells a small area of effect. This option remains, as a legacy component, for those who prefer it.

The antimagic attacks of enemy mages will bypass Improved Invisibility even if you don't install this component."

which I assume means no area of effect as the default behaviour.

[Bartimaeus]

I could swear I read somebody else having this problem just within the past month (or possibly you in a different one), but I can't find that post anymore.

[culmore]

Thanks Bartimaeus, probably me here

 

http://gibberlings3.net/forums/index.php?showtopic=29544&&page=12

 

At this point I am just looking for a confirmation that I am not nuts and this is indeed incorrect behaviour.

 

I do appreciate SCS lots, hope I dont' sound ungrateful. Cant play BG2 withOUT SCS

Edited October 24, 2018 by culmore

[DavidW]

Don't look at me, I'm afraid: v31 is a maintenance release and I wasn't involved on it.

 

This was never intended behavior though. (It's faintly possible that SCS is erroneously going with the OSX-vanilla version - which did work this way - on OSX-EE.)