If Evulsion causes you to reach 8 paradoxes, it’s cooldown isn’t reset by this item’s effect.
I’m using a mythic Focus of the Unwritten Talisman of Destruction Mk III, just in case that proves relevant. 
I would think it has something to do with proc order. I would think Getting 8 paradoxes, registers before the CD is applied to whichever ability triggered the final paradox. That would mean there is no CD to remove. But that is all just guess work =P.
Well yeah, it’s obviously to do with proc order but the point is the proc order is wrong. 
From my understanding, Evulsion being cast and generating Paradoxes are part of a single event, and so the Tome of Unwritten Talisman cannot remove the cooldown for Evulsion since the triggering of the extraordinary weapon doesn’t occur until before the ability has dealt its damage and finished its casting animation. Here is a screenshot from a frame captured in a video recording as evidence:
As you can see, Paradoxes have been generated as Evulsion was being cast. The animation cue for the ability activation is still visible six-hundredths of a second later, indicating that it corresponds with my input. In fact, further analysis of my recording suggests Paradoxes are generated at the moment of activation, followed by part of the ability’s animation, and then the damage is dealt to the target and displayed before the animation is finished, and then is concluded with the resetting of the global cooldown. Evulsion isn’t reset by the Unwritten Tome until the moment before damage is dealt, which is prior to a full global cooldown having been cycled.
I don’t see how it makes sense to reset the cooldown for an ability as it’s still being cast, especially since this Special ability doesn’t follow the same rules as other instant-cast Basic and Power abilities. It appears intentional that Evulsion can’t reset its own cooldown since that might allow players to cast it twice in a single second.
2 Likes
Again, the expected behaviour is that it does reset its cooldown, so I reported it as a bug. Are there technical limitations in the engine that mean it might remain a bug forever? Quite possibly and it wouldn’t be the first bug like that. Still a bug though.