IESDP Updated, Information Compilation Options

[igi]

The IESDP has been updated once again.

There's quite a few updates this time, if you're interested visit http://iesdp.gibberlings3.net/history.htm for a semi-complete list. If you're not interested, just visit the main IESDP site!


The IESDP is located at:
http://www.iesdp.info/

The IESDP update board is at:
http://forums.gibberlings3.net/index.php?showforum=54

[devSin]

Right, so in your estimation, the IESDP must define SpellNoDec() so that all of the following are emphasized:

Unlike Spell(): the spell doesn't have to be known or memorized

Unlike ForceSpell():
the spell respects the round-based system
the spell respects the range
the spell respects game mechanics regarding spellcasting
the spell respects game mechanics regarding the target

Unlike ReallyForceSpell():
the spell respects the round-based system
the spell respects the range
the spell respects game mechanics regarding spellcasting
the spell respects game mechanics regarding the target
the spell respects casting time

Unlike ApplySpell():
the spell respects the round-based system
the spell respects the range
the spell respects game mechanics regarding spellcasting
the spell respects game mechanics regarding the target
the spell respects casting time
the spell displays standard console feedback
the spell uses the set casting glow and projectile

As well as anything else I've left out. I'm a big fan of accuracy, but more so of common sense. If SpellNoDec() is Spell() without the need to know or memorize, then all of these other points are implied.

Keep in mind that the IESDP is largely maintained by a single person and is comprised of far more than a list of the triggers and actions for BG2. If you would like to write comprehensive details of each and every scripting trigger and action available, then I'm certain it would be a welcome addition, but running around shouting "You left out the most important thing! THE PAUSE! THE PAUSE!" isn't really accomplishing anything.

ForceSpell() and ReallyForceSpell() (and ApplySpell()) allow casting on entirely invisible creatures. The only requisite is that the target exists; the engine doesn't care the visibility, state, range, or path to the target. They are all instant actions. My point, then, must be why you insist on forcing a comparison between ForceSpell() and SpellNoDec(), when SpellNoDec() is clearly an extension of Spell().

Anyway, none of this matters. igi will read your note eventually and do what he thinks is right.

This post has been edited by devSin: Jul 13 2006, 03:03 AM