Jump to content
Sign in to follow this  
DavidW

SCS v32 and spell targetting

Recommended Posts

Both the Enhanced Edition and the ToBEX-enhanced original game now have substantial advances in scripting options as compared to the original game. Version 32 of SCS (to be released fairly imminently, at least in playtest form) takes advantage of this rather more than previous versions; partly as a consequence, there are several substantive changes in targetting. These are all somewhat experimental and I'm keen to get feedback.

 

1) In previous versions, spellcasters totally ignore anyone protected by Spell Deflection, Spell Turning or Spell Trap. V32 is a bit more aggressive: it will use single-target spells on mages with Spell Deflection (but not the other protection types) in the hope of burning through the protection. The spellcaster's most powerful spells won't be used in this way: only spells 2 levels or more below the caster's highest level are used against Spell Deflection.

 

2) One dilemma in previous versions was how to handle magic items that provide protection (e.g., should you cast Domination on someone wearing a Helm of Charm Protection?) Previously, I've erred on the side of detecting these items, on the grounds that while it's a bit unrealistic for a mage to immediately see your items, it's not that obvious, whereas if a mage repeatedly targets someone who's obviously immune to an effect, it breaks immersion.

 

V32 takes advantage of new scripting options to do something more sophisticated: the *first time* that a spell type is cast, the caster will fail to notice the protective item, but subsequently it is noticed. (So a mage might cast Domination on the protected creature, but won't then try a Dire Charm on the same opponent).

 

3) Previous versions of SCS were very cautious with party-unfriendly spells like Fireball, usually only using them if the caster was immune to the spell and if there are no allies anywhere around. V32 is significantly more aggressive with area-effect spells: it tries to target clumps of enemies, and it is willing to cast with allies or an unprotected caster around because it tries to detect if they're actually in range. I'm not sure exactly how this will play out; realistically there will be *some* friendly fire, but I'm keen to find out just how much.

 

One consequence of embracing the full range of modern scripting options is that SCS now requires either the Enhanced Edition engine or a ToBEx-compatible engine. What that means in practice is that I no longer support OSX versions of the vanilla game. Apologies for this, but it's a very small fraction of my player base and maintaining backwards compatibility has just become too difficult.

Share this post


Link to post

1) I am SCS enemy AI and on difficulty settings HARD and INSANE I will do anything, ANYTHING in order to destroy you, filthy casul!!!

 

2) Monsters should not bother detecting anything. Casters should (Tanova, Alhoon, dragons, special beholders are casters of course). No casting on protected characters at all! Smarter AI more important than sophistication, imo.

 

3) Could be fun in BG1EE.

 

Imagine Mulahey casting remove magic first just to be sure and then casting one or two fireballs, destroying his entire skellingtons army.....

 

 

 

 

but also your entire party. hehe

 

Nope, he is a cleric I know, just like Bassilius. Don't worry, just imagine Khark!!! Thanks all, have a nice day.

Share this post


Link to post
On 11/13/2018 at 3:04 AM, DavidW said:

2) One dilemma in previous versions was how to handle magic items that provide protection (e.g., should you cast Domination on someone wearing a Helm of Charm Protection?) Previously, I've erred on the side of detecting these items, on the grounds that while it's a bit unrealistic for a mage to immediately see your items, it's not that obvious, whereas if a mage repeatedly targets someone who's obviously immune to an effect, it breaks immersion.

 

V32 takes advantage of new scripting options to do something more sophisticated: the *first time* that a spell type is cast, the caster will fail to notice the protective item, but subsequently it is noticed. (So a mage might cast Domination on the protected creature, but won't then try a Dire Charm on the same opponent).

Speaking of this, why do SPLs like DW#MMSEE or DW#WBSEE offer a Save vs. Spell? Shouldn't they offer no save?

Share this post


Link to post
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×