11-21-2022, 11:37 PM
Testing it out, placing a haste, then elemental, then magnet rune causes a miss chance that does not ignore evasion. The same seems to apply if you place a haste and then razor.
https://i.imgur.com/SvvccUO.png
You can see the haste in the center.
https://i.imgur.com/Pu24FQo.png
https://i.imgur.com/etA7yHd.png
Both lack the no_evasion tag which it seems to have when haste is placed above the damaging runes rather than below it.
https://i.imgur.com/0SQQtzC.png
This one, placed by placing a haste, then a magnet to attract the haste, and then an elemental on top of that did actually proc the no_evasion tag.
https://i.imgur.com/kEalxDx.png
It also gave me this error message.
https://i.imgur.com/KohxuBT.png
https://i.imgur.com/M8rGVJF.png
This one looks functionally identical to the one above, but it was made by placing the magnet, then haste above, then elemental.
https://i.imgur.com/AADlBi9.png
It also gave a no_evasion trigger.
To speed things up with other tests.
Haste->magnet on same space->Elemental on same space: Evasion triggered.
Destruction, anchor, illuminated, haste, elemental: No evasion
Haste, destruction, anchor, chilling, warding, elemental: evasion triggered.
Smoking, haste, elemental, magnet: No evasion.
haste, then nearly every other rune except null: Evasion triggered
Haste, elemental off to the side, magnet on top of haste to attract elemental onto it: Evasion triggered
Haste, then a bunch of other runes just like before, but then I magneted next to it to make magnet the bottom link rune?: No evasion.
Conclusion: Haste being the bottom rune in a chain makes it not work for evasion ignoring. It must be the bottom and first placed rune in that stack. Magneting it onto another stack will make it work again for evasion ignoring.
Further study because something else weird was noticed?
Warding in general just seems odd. With one or two runes in a link and warding placed on top, it creates a spike directly on its space.
3-4 runes? It creates no spikes whatsoever.
5-6?: https://i.imgur.com/o2Fiuve.png
7-8: https://i.imgur.com/BHNtKvw.png
All of it seems rather small for what you get. And 3-4 is no spikes at all. Might be intended because large fields of spikes are fun(!) gameplay, but maybe it should be changed so that you don't lose warding functionality in that range of runes now that runes generally won't survive as long.
https://i.imgur.com/SvvccUO.png
You can see the haste in the center.
https://i.imgur.com/Pu24FQo.png
https://i.imgur.com/etA7yHd.png
Both lack the no_evasion tag which it seems to have when haste is placed above the damaging runes rather than below it.
https://i.imgur.com/0SQQtzC.png
This one, placed by placing a haste, then a magnet to attract the haste, and then an elemental on top of that did actually proc the no_evasion tag.
https://i.imgur.com/kEalxDx.png
It also gave me this error message.
https://i.imgur.com/KohxuBT.png
https://i.imgur.com/M8rGVJF.png
This one looks functionally identical to the one above, but it was made by placing the magnet, then haste above, then elemental.
https://i.imgur.com/AADlBi9.png
It also gave a no_evasion trigger.
To speed things up with other tests.
Haste->magnet on same space->Elemental on same space: Evasion triggered.
Destruction, anchor, illuminated, haste, elemental: No evasion
Haste, destruction, anchor, chilling, warding, elemental: evasion triggered.
Smoking, haste, elemental, magnet: No evasion.
haste, then nearly every other rune except null: Evasion triggered
Haste, elemental off to the side, magnet on top of haste to attract elemental onto it: Evasion triggered
Haste, then a bunch of other runes just like before, but then I magneted next to it to make magnet the bottom link rune?: No evasion.
Conclusion: Haste being the bottom rune in a chain makes it not work for evasion ignoring. It must be the bottom and first placed rune in that stack. Magneting it onto another stack will make it work again for evasion ignoring.
Further study because something else weird was noticed?
Warding in general just seems odd. With one or two runes in a link and warding placed on top, it creates a spike directly on its space.
3-4 runes? It creates no spikes whatsoever.
5-6?: https://i.imgur.com/o2Fiuve.png
7-8: https://i.imgur.com/BHNtKvw.png
All of it seems rather small for what you get. And 3-4 is no spikes at all. Might be intended because large fields of spikes are fun(!) gameplay, but maybe it should be changed so that you don't lose warding functionality in that range of runes now that runes generally won't survive as long.