NWN2Wiki
m (Line-breaks)
Tag: Source edit
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  +
{{SpellInfo
{{spell
 
 
|icon=Is_curecritical.png
 
|icon=Is_curecritical.png
 
|image=
 
|image=
Line 15: Line 15:
 
|spell_resistance=Yes
 
|spell_resistance=Yes
 
|hostile=No
 
|hostile=No
  +
|empower=Yes
  +
|extend=No
  +
|maximize=Yes
  +
|quicken=Yes
  +
|silent=Yes
  +
|still=Yes
  +
|persist=No
 
}}
 
}}
  +
 
== Description ==
 
== Description ==
   
Line 25: Line 33:
   
 
== Bug Notes ==
 
== Bug Notes ==
 
This spell does several odd things with the function spellsCure(), in nw_i0_spells.nss. This refers to that include file for bugged lines:
 
 
Line 436: The maximised damage for spells being cast at the PC is done always, rather then being difficulty based. This seems to be intentional, but why? Why not do it for NPC's in the PC's party? Why not NPC's in general? Why do hardcore players (Who are meant to be playing full D&D rules) get stuck with the better healing? This seems an odd decision. It would be best just to have the old maximised healing/damage for difficulty < GAME_DIFFICULTY_CORE_RULES, which Bioware used, for several reasons;
 
 
* NPC's in the PC's party are not healed maximised amounts, even though the PC is, so its current implementation is broken
 
* For Hardcore rule players it is the only spell which acts differently if you are a PC rather then an NPC (apart from charming and domination).
 
* It can maximize a spell twice, which...is simply not how the feat works, in the current implementation.
 
* Maximise and Maximise is quite unbalanced, and simply doesn't work correctly in the current implementation anyway (line 450)
 
 
The problematic lines from line 435 to 462, could be replaced with this code (Using the basis we do Maximize first, then empower, according to ApplyMetamagicVariableMods() ):
 
 
// Maximise, empower checks.
 
 
// Maximize spell.
 
// If PC or their party is casting this at normal or lower difficulty, we assume maximized.
 
if(nMetaMagic & METAMAGIC_MAXIMIZE || ( GetGameDifficulty() < GAME_DIFFICULTY_CORE_RULES && ( GetIsPC(OBJECT_SELF) || GetIsPC(GetMaster()) ) ))
 
{
 
nDamage = nMaximized; // Ignore the rolled value, we are MAXED!
 
}
 
// Empower spell.
 
// If we are not maximising this spell, we check for healing domain empower
 
if(nMetaMagic & METAMAGIC_EMPOWER || ( GetHasFeat( FEAT_HEALING_DOMAIN_POWER ) && !GetIsObjectValid( GetSpellCastItem()) ))
 
{
 
nDamage = nDamage + (nDamage / 2); // Add in 50%
 
}
 
 
// Add additional caster level damage
 
nDamage += nExtraDamage;
 
   
 
Line 493: The touch attack is done even if the target cannot be affected (if the reputation check fails). Doing the reputation check before the touch attack means a caster has feedback that it won't work on the designated target. Doing this, you'd have to move the signal event too.
 
Line 493: The touch attack is done even if the target cannot be affected (if the reputation check fails). Doing the reputation check before the touch attack means a caster has feedback that it won't work on the designated target. Doing this, you'd have to move the signal event too.
   
 
== External resources ==
 
== External resources ==
  +
 
*[[NWNWiki:Cure Critical Wounds]]
 
*[[NWNWiki:Cure Critical Wounds]]
 
*[http://www.d20srd.org/srd/spells/curecriticalwounds.htm d20 SRD Cure Critical Wounds]
 
*[http://www.d20srd.org/srd/spells/curecriticalwounds.htm d20 SRD Cure Critical Wounds]

Latest revision as of 00:42, 13 March 2021

Is curecritical.png
Cure Critical Wounds
Spell Information
Spell level : Innate level: 4, Bard: 4, Cleric: 4, Druid: 5
School : Conjuration
Components : Verbal and Somatic
Range : Touch
Target/Area : Single
Duration : Instantaneous
Save : Will 1/2
Spell resistance : Yes

Description[]

The target creature is healed of 4d8 points of damage, + 1 point per caster level to a maximum of +20. Healing spells have a reverse effect when used on undead, causing the targeted undead to take an amount of damage equal to what the spell normally heals. A successful touch attack must first be made when this spell is used against undead.

Notes[]

Bug Notes[]

Line 493: The touch attack is done even if the target cannot be affected (if the reputation check fails). Doing the reputation check before the touch attack means a caster has feedback that it won't work on the designated target. Doing this, you'd have to move the signal event too.

External resources[]