Epic Spell Focus: Enchantment
Posted: Sat Oct 24, 2020 11:50 am
Description of Bug Experienced:
Hello!
So, since its implementation the Epic Spell Focus: Enchantment ability to dominate two targets has been broken. I have played around with it on the PGCC and while you can dominate two targets, by dominating one creature, dominating a second creature and then re-dominate the first creature, as the domination breaks upon the second cast - there are still many bugs associated with this feature.
Steps to reproduce the Bug(s):
Make an ESF: Enchantment wizard on the PGCC.
1) Cast dominate on Target 1.
2) Cast Dominate on Target 2.
3) Re-cast Dominate on Target 1.
4) Summon Mummies.
5) Test the Associate tool.
Expected Result:
Second cast of dominate should not release the first target.
All summons should be able to be controlled by the Associate tool when clicking on yourself.
Actual Result:
First: You cannot release the dominated creatures.
Second: The second dominated creature cannot be controlled in tandem with the first creature. Assuming direct control of the first dominated target, will render the second dominated target inactive. This can somewhat be remedied by assuming direct control of the second target, and having the first target be controlled by the AI.
Third: Clicking on yourself with the associate tool assuming control of all summons/dominated targets, assumes control of elemental, outsider or undead summons and the first dominated target, again rendering the second dominated target inactive.
Fourth: Two dominated creatures in tandem with elemental, outsider or undead summons, follow the same rules as above. This means that in order to have use of your second dominated creature, you must have all other summons be controlled by the AI.
As a side note, the target associated with the -associate command will by default be the first target you dominate. However, assuming control of the second target will change the -associate command to work for that target.
Screenshot(s)
Not relevant.
Additional Information/Notes
I spoke to Zaphiel about this a while ago and he claimed to have a fix for this issue. It would be fantastic to have said fix implemented.
Hello!
So, since its implementation the Epic Spell Focus: Enchantment ability to dominate two targets has been broken. I have played around with it on the PGCC and while you can dominate two targets, by dominating one creature, dominating a second creature and then re-dominate the first creature, as the domination breaks upon the second cast - there are still many bugs associated with this feature.
Steps to reproduce the Bug(s):
Make an ESF: Enchantment wizard on the PGCC.
1) Cast dominate on Target 1.
2) Cast Dominate on Target 2.
3) Re-cast Dominate on Target 1.
4) Summon Mummies.
5) Test the Associate tool.
Expected Result:
Second cast of dominate should not release the first target.
All summons should be able to be controlled by the Associate tool when clicking on yourself.
Actual Result:
First: You cannot release the dominated creatures.
Second: The second dominated creature cannot be controlled in tandem with the first creature. Assuming direct control of the first dominated target, will render the second dominated target inactive. This can somewhat be remedied by assuming direct control of the second target, and having the first target be controlled by the AI.
Third: Clicking on yourself with the associate tool assuming control of all summons/dominated targets, assumes control of elemental, outsider or undead summons and the first dominated target, again rendering the second dominated target inactive.
Fourth: Two dominated creatures in tandem with elemental, outsider or undead summons, follow the same rules as above. This means that in order to have use of your second dominated creature, you must have all other summons be controlled by the AI.
As a side note, the target associated with the -associate command will by default be the first target you dominate. However, assuming control of the second target will change the -associate command to work for that target.
Screenshot(s)
Not relevant.
Additional Information/Notes
I spoke to Zaphiel about this a while ago and he claimed to have a fix for this issue. It would be fantastic to have said fix implemented.