[Known 8332] Casting times of (Chain) Contingency
![Galactygon](https://forums.beamdog.com/uploads/userpics/ZWDUTYDSLP2R/nHZDSR9TSTAIE.png)
Existing behavior1: Both Contingency (SPWI617) and Chain Contingency (SPWI908) have a targettype of 7 set (self ignore pause) meaning that both are cast instantly and during a game pause.
Existing behavior2: Both contingency spells start to cast SPIN905.spl (called "DO_NOTHING" in SPELL.ids) at a delay, which inconveniently breaks the PC's actions.
Expected behavior1: Both spells should have a targettype of 5 (self) set with a casting time of 9 as per their descriptions.
Expected behavior2: Neither spell should force the caster to cast SPIN905 (just a bunch of white sparkles).
Suggested solution1: Set the targettype of both contingency spells (SPWI617, SPWI908) to 5 instead of 7.
Suggested solution2: Remove the casting of SPIN905.spl from all extended headers of all contingency spells.
Existing behavior2: Both contingency spells start to cast SPIN905.spl (called "DO_NOTHING" in SPELL.ids) at a delay, which inconveniently breaks the PC's actions.
Expected behavior1: Both spells should have a targettype of 5 (self) set with a casting time of 9 as per their descriptions.
Expected behavior2: Neither spell should force the caster to cast SPIN905 (just a bunch of white sparkles).
Suggested solution1: Set the targettype of both contingency spells (SPWI617, SPWI908) to 5 instead of 7.
Suggested solution2: Remove the casting of SPIN905.spl from all extended headers of all contingency spells.
Post edited by Gate70 on
0
Comments
I'm not sure I understand the second behaviour. Preparing a contingency should break any other actions?
The second issue is that a few seconds after you finish casting any of the contingency spells (regardless what you did in the contingency menu), the caster starts to cast a spell with white sparkles that does nothing. If the player has started another action (such as begun casting another spell), then the action is broken to the player's annoyance.
Or are you saying the second part would break the first part?
Trying to make sure I understand correctly so I don't report the wrong thing.
Thanks
The first issue is due to the wrong targettype set in the spells' headers (should be set to 5 instead of 7).
The second issue is due to an extra effect set in the extended headers that forces the caster to cast another completely unrelated spell (via opcode 146). The unrelated spell is SPIN905.spl (called "DO_NOTHING" in SPELL.ids).