Professor Putricide and specific classes issues against the Oozes.
1 - https://www.wowhead.com/spell=70447/...-ooze-adhesive ( Green ooze ) https://www.wowhead.com/npc=37697/vo...ooze#abilities
2 - My complain is specifically about 3 classes : Rogue , Hunter and Mage... what's wrong : Rogue cannot stop the green ooze cast by using vanish , Hunter cannot stop it either by using feign death and mage cannot stop it by using [Invisibility]. ( What is happening in circle wow 100x wotlk realm is basically :I am using [Invisibility] spell, becoming invisible for a sec but the ooze does not stop his cast, like i didn't do anything. Same for hunter and rogue not successfully try to make the oozes interrupt their cast and start a new re-cast to another random player. )
3 - Im gonna say how it should work : ( and for a fact it works in most of the private servers since long time ago, witch forces me to think that you guys for some reasons did customized it to be that way , which kills the game-play by my opinion ) ... When using the hunter spell :Feign Death the ooze must immediately interrupt his "rooting Volatile Ooze Adhesive" cast and start re-casting a new random player target, same for rogue who uses Vanish and same for mage who uses Invisibility.
4 - I saw this behavior a weeks ago in the 100x wotlk realm
5 - Im new to this server , but based on players that i asked and their experience, it has been that way for years ( i can't call it a bug , i call it just a way how you guys made it , but it doesn't have for me any logical reason to be like that, if so let me know what was the reason behind to be customized that way. )
6 - https://wowroad.info/?npc=38431
7 - Yes i think the bug is permanent at least since 1 year +
8 - I have some videos from circle wow , but i didn't managed to record my self while casting Invisibility , because the ooze died way to fast before that + i have a friend who plays hunter and he confirmed as well that he did tried 2 different icc ID raids to use FD , but nothing happened. ( any tester account can go and confirm that "bug" / behavior )
