blizzard simply cannot stop bringing headaches , every few days something new
we all know about Togc first mini boss that gives id, but what about Ulduar
joined a raid for ULD 10, we went straight to ALG, wiped 2 times and raid over
next day i found out i have id to ULD 10. without killing any boss
open a ticket , takes 8 days to be reviewed 
this is a great idea blizzard, we need more
This is intended, for my detailed explanation see here:
You also get a warning upon zoning in that you’ll get locked if you do not exit.
am talking about FRESH raid attempt, i did not join an id
i know when you join an id you get a prompt either you accept the id or leave the instance
not talking about that, we started a fresh raid , went straight for Algalon, wiped and raid over.
how the hell does that lock you to the raid , we havent done anything to get ‘locked’
Same thing occurs when you create a fresh raid, upon zoning into Ulduar it will create a raid Instance ID locking all players to that for the week.
hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
isnt that a bit retarded ?
what is the Blizzardium sense behind it ?
blizzard performance and mechanics is just god level embarrassing, i never seen anything like this in any other game since 1996
I believe the save occured when you unlocked the door to algalon, he was originally a 1h per week boss, so of course he will generate a raid ID.
Unsure how the saves work with the skip, since you would get saved when engaging the flame leviathan.
Im guessing changing this is more effort than its worth it for blizzard, after all this is a problem for such a tiny amount of players
The actual reasoning for this i believe is that when you activate something that changes the instance in some way, a instance ID is generated to remember your progress (activating flame leviathan or opening algalons door) and since raids are on a 1 week lockout, you cant generate a new ID.
This got changed in later expansions when they changed lockouts to a per boss, instead of the whole instance
Well, as soon as you skipped you get a raid lockout. Thats how it works. It worked the same on FL if you used the skip trash command from the guy youre supposed to talk to. Git gud, dont join bad groups.
You get locked to Ulduar as soon as the door to Algalon opens.
Quite dumb at this point since Algalon no longer has the 1 Hour limit .
They fixed that like 3 weeks into Ulduar phase.
This may have been intended when Algalon had a timer but it makes absolutely no sense now-a-days.
Changing it is probably more work than the tiny amount of people that are affected by it is worth
Could be, it should just be another nail in the coffin for folks who want classic+.
Imagine thinking this dev team could pull that off.
It may actually be a very complicated issue, since its so heavily integrated in the way raid lockouts operate, for all we know it require a complete rework of the instance ID system to get fixed, and for anyone with half a brain can understand that such a thing have a very low priority when it only affect such a tiny amount of players.
There’s been a visual bug in Ulduar all along where attempts on any boss got you notified that you were saved.
You actually weren’t though, so this is exclusively for Algalon. Also know as an oversight when they removed the timer from it.
Cause they’re flailing.
What you mentioned there is indeed a bug, but a completly different thing than Algalon.
Getting saved when engaged to Algalon is not a bug, opening his door and activating algalon is part of changing the instance, thus it require a instance ID.
What we do not know, is wether it is intended by design that you should be saved when attempting algalon, or if they forgot to remove it / its too much work to remove it.
bro name me 1 good change happened in the game, a decent change that made the experience better
same bugs of tbc / wotlk in 2006 did happpen again at classic launch
its like they found an old CD in the dust and executed it with the same idiocy , just milking money
like i said , this game is not worth the time or the sub anymore
this is embarrassing !!!
Whats that got to do with anything?
At least stay somewhat on topic in your own thread
The change that made Alliance unable to skip horde in AV by walljumping was really good in Classic. Too bad TBC made that change pointless with that stupid reinforcement counter.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.