Monolith of storms bug....again

ZhuJiuyin · February 17

Monoliths of storms do not necessarily deal damage every 2 seconds, sometimes delayed to about a 3 second tick.
My test method is to use Overload to perform a light attack every 2 seconds, so I can rule out the situation where there are less than 2 Monoliths and cannot connect.
I think this is because when a Monolith disappears, even if there are still 2 Monoliths on the field, this set will still cause a delay in the connection between the Monoliths for some reason.

This is already the third or fourth bug in Monolith of storms, Monolith of storms really needs to be reworked.

ZhuJiuyin · February 18

https://youtu.be/nfNSxKoZhtU

As shown in the video, Monolith of storms do not necessarily deal damage every 2 seconds, sometimes delayed to about every 3 seconds.
Since I used Mages' Wrath as a spam to attack, I can rule out the situation where there are less than 2 Monoliths and the connection is impossible.
Based on the speculation in the previous article, I think this is because when a Monolith is created or disappears, the server needs to calculate whether there are still more than 2 Monoliths connected on the field, which results in a damage delay.
In addition, according to other people in the guild, it may be because Monolith of storms is restricted to the condition "An enemy can only take damage from this set once every 2 seconds.", so the server needs to calculate this condition at the same time. As a result, the attack frequency of Monolith of storms does not tick every 2 seconds as expected, but is randomly delayed to about once every 3 seconds.

Whatever the reason, Monolith of storms has been very bad since the PTS, with bad damage, harsh proc conditions (compare Pyrebrand, Aerie's Cry), and an unreasonable damage limit of once every 2 seconds (compare Corpseburster).

ZOS, the Monolith of storms need a complete rework (as do most of the classes sets, of course)