[Known 9746] Farsight in (Chain) Contingencies/Triggers
Galactygon
Member, Developer Posts: 412
Reposting this as suggested by @Gate70. See original post here:
http://forum.baldursgate.com/discussion/comment/531719/#Comment_531719
Existing behavior: Placing multiple Farsights in a contingency/trigger-type spell when will result in you getting stuck on the minimap when they fire without revealing any fog of war (you have to manually esc from the minimap). On the other hand, placing one Farsight and other spells work just fine.
Desired behavior: Placing multiple farsights in a contingency/trigger shouldn't make you get stuck in the minimap.
Suggested implementation1: Prevent both the priest and mage version from being cast in a contingency/trigger by appending SPWI424 and SPPR415 to CONTINGX.2da.
Suggested implementation2 (I prefer this one): add 2 protection from spell effects (opcode 206) to both SPWI424 and SPPR415 with durations of 1 with one effect having SPWI424 as a resource key and the other having SPPR415 as a resource key. This will still allow either Farsight to be cast in a contingency/trigger but will prevent multiple farsights from being activated at the same time (the rest will be lost).
Suggested implementation3 (if the developers have lots of time and patience): allow multiple targets to be selected in the minimap when the contingency/trigger fires. This will require hardcoded adjustments to the farsight opcode.
http://forum.baldursgate.com/discussion/comment/531719/#Comment_531719
Existing behavior: Placing multiple Farsights in a contingency/trigger-type spell when will result in you getting stuck on the minimap when they fire without revealing any fog of war (you have to manually esc from the minimap). On the other hand, placing one Farsight and other spells work just fine.
Desired behavior: Placing multiple farsights in a contingency/trigger shouldn't make you get stuck in the minimap.
Suggested implementation1: Prevent both the priest and mage version from being cast in a contingency/trigger by appending SPWI424 and SPPR415 to CONTINGX.2da.
Suggested implementation2 (I prefer this one): add 2 protection from spell effects (opcode 206) to both SPWI424 and SPPR415 with durations of 1 with one effect having SPWI424 as a resource key and the other having SPPR415 as a resource key. This will still allow either Farsight to be cast in a contingency/trigger but will prevent multiple farsights from being activated at the same time (the rest will be lost).
Suggested implementation3 (if the developers have lots of time and patience): allow multiple targets to be selected in the minimap when the contingency/trigger fires. This will require hardcoded adjustments to the farsight opcode.
Post edited by Gate70 on
1
Comments
A mix of #1 and # 2 would be best, a new .2da limiting selected spells to only one instance in a given Sequencer/Contingency.
It's not just Farsight that needs this though, all of the "Select Spell" spells need it as well, especially NRD.
Did you mean implementation of #3 in your first post? If so then I agree, it's too much time for little benefit. I think #2 (add 2 protection from spell effects with durations of 1) is the best solution that is easy to implement.
Spell immunity type select spells do not need special treatment because they are now correctly handled by the engine so that the child spells appear in the contingency selection GuI. Try and remove SPWI510 or SPWI417 from CONTINGX.2da and see what happens.