Current behaviour: (Tell us what happens.)
Sapphiron casts http://wowhead.com/spell=28560 without cooldown
Expected behaviour: (Tell us what should happen instead.)
should cast spell with cooldown
Steps to reproduce the problem:
go to sapph(10 or 25), start fight
TC rev. hash/commit: b1fa8ff
TDB version: TDB 62 + all updates
Operating system: Debian 8 x64
This issue is not considered valid because of the following reasons:
Please read http://bit.ly/tc-issuetracker-and-you and add the missing information to this issue. Thanks.
Based on script, Blizzard has "cooldown"
Btw summoning @Treeston, he know better about timers of this boss ^^
Detailed repro steps please. Script has a cooldown for this spell unless somebody fucked around with it.
Is this unmodded core?
@Keader can you try to repro ingame I don't have a core on hand right now.
ummm taking a wild guess, this seems like the npc misses flags and melee attacks
going to test right now
the problem seems to be that the debuffs stack on 25 man mode (up to 4 appear), on 10 normal only one appears.
If you're standing in multiple blizzards?
sorry for the bad English, the boss hangs on a single player single stack if a lot of players, but the spells cooldown is 10 seconds and it needs to end then knit castes should go, and then casted spell without cooldown
with kelthuzad almost the same problem only he spawned mobs without Cooldown
Summon Blizzard uses spellmgr override to limit target count to 1. Maybe 25man has difficulty entry that doesn't have it?
Maybe this happens because Blizzard uses this script?
That is intended.
With this script he will cast Chill every 3 seconds. Instead of 10.
It ticks every 3 sec.
Hm or no the aura ticks every so often but should cast every 10.
Is swing timer different on 10 vs 25?
Summon Blizzard spawns a Blizzard beacon npc. That beacon npc chases players and casts Chill every 3 seconds.
The Chill spell drops a blizzard dynobj (the actual visible damaging area) when cast.
Script is fine.
Confirmed, you can see multiple blizzard npcs being spawned, one at a time.
It can go up to 4 npcs following random players.
events.ScheduleEvent(EVENT_BLIZZARD, RAID_MODE(Seconds(20), Seconds(7)), 0, PHASE_GROUND);
Seems like the timer is too low, that or the script needs to be updated so that players that are already followed by another blizzard cant have a new one chasing.
Also it might be a good idea to check the number of players facing the boss, so only one active blizzard is possible if there are only 3-2 players fighting, for example.
And one last point, when air phase begins is it intended to have blizzards still active? Hiding all together while a killing rain is chasing you seems kinda off to me xd
I will make a video and show exactly what the bug can do so even easier to find a fix
@ccrs multiple blizzards on one target, you might be on to something there
blizzard during air is intended i think, iirc they time out shortly after phase starts due to how timers line up
if you want to look or test I can give realmlist my server.
iirc the blizzard dummy casts a spell on players to select its chase target, @ccrs check if that applies a hidden aura or something.