Open kaytotes opened 6 months ago
There must have been a change during the beta, as current behavior on internal seems to be undertuned if anything.
He starts with 2 adds and will spawn another pair when his health falls below 50%. The adds tickle (they are elites but deal nonelite damage) and Antu'sul himself deals the same damage as any other boss in the dungeon. He does not seem to be using his direct healing spell at all, or the Earthgrab totem ability, only a healing ward totem. Also the adds aren't using their Petrify ability (stun) at all, instead they are using a Poison(spell ID 81893, this is pretty strong). The encounter properly resets if the group dies, all adds despawn. If the boss is defeated, adds also despawn.
Based on descriptions from 2006 (patch 1.12), this boss was the hardest in ZF dungeon. He is supposed to spawn a swarm of nonelite basilisks (4-6 of them) called Sul'lithuz Broodlings upon pull (these adds are supposed to have a Poison ability), and he has a short timer (seems 30sec on videos) for spawning his first elite basilisk, and then spawns 2 more after about 45seconds more (and he keeps spawning adds if the fight drags longer). He has a flash heal ability he uses periodically once he falls below 50% which can elongate the encounter and sometimes uses a Chain Lightning as well.
Here is a somewhat clear video that shows roughly the events during the fight https://www.youtube.com/watch?v=7UXwjNrdjTc although the damage values might be tuned differently as this seems to be from wotlk classic, but the spawns behave the same way. Another video of classic era https://www.youtube.com/watch?v=mr9q2KCBGY0
Overall the fight on Epoch looks very different from blizzlike, with the buffed health and damage just slightly balancing for the missing mechanics. I am not sure if any of the changes are intentional or if the fight was purposefully revamped. I'll confirm this issue for now as it seems the encounter may need fixing to be the proper experience.
Related https://github.com/Project-Epoch/bugtracker/issues/7671 it seems it was busted on the beta and there was indeed a hotfix