[EPIC] Run ToC(10) infinitely (soft reset bug)

[BiGDeE]

Im grabbing my lynching rope.

[Sayu]

posting in an epic thread!

[mrnobody]

this musta been you!

[Sayu]

tosting in an epic phread!

[Sodee]

lol Palumir
yeah there's no way Blizz would have let this slip with a "soft reset" as you say.
It's a raid... all raids save the same way (basically) I really doubt this one would be any different..
lol maybe you just cleared right before the Tuesday reset and went back in after 30 mins and were like O.o

Because blizzard has never before EVER made game-breaking mistakes before.

How about the bug where you could stack rampage, zone in, stack it, zone out, stack it over and over and over and get ridiculous attack power, during classic. A level 60 warrior could one shot bosses with that exploit. Not only did they take their time fixing it, but none of the loot won in the process was taken by, nor any action taken against the accounts in question.

ps - points if you can see note where I used sarcasm.

[celticking]

Blizz never made colosal mistakes? Well ofc they did, but they got fixed in a timely maner (1 week max)
How long has it been since ToC (with all bosses) has been out? If this worked I'm sure someone would have found it, abused it about 10 times, Blizz detected it, fixed it and woulda made the Blizz news/************ news for sure.
Plus really, Ensidia abused realm transfer to get 50 more tries at ToGC, slipping under Blizz's noses for a quick one, if there was simply a soft reset they woulda just used that

[Tagmonkey]

Let this thread be an example of why you shouldn't +rep someone without confirmation/proof from multiple people.

[CowsGoQuack]

Posting in epic thread FTW

[shorstuff910mc]

nice find, rlly like it

[shorstuff910mc]

nice find! i can use this !

[lakkano]

Hi people! I like hamburgers.

[Sayu]

Let this thread be an example of why you shouldn't +rep someone without confirmation/proof from multiple people.

well he got 0rep out of this thread anyway.
oh and, thread in an epic posting.

[condordanish]

i've figured out how this is done.

when you enter ToC10m you occasionally can not spawn Lord Jaraxxus due to a bug with the person you talk to. When this happens you are required to wait a soft reset to be able to spawn him.

IF this bug occurs, you can clear TOC10, wait for the soft reset, and clear it once again.

It comes down to finding a way to "bug" this every time, and i *believe* it can be done by DIing someone, iceblocking, vanishing, etc WHILE GETTING CHARGED BY ICEHOWL ON NB.

If the person is DI'd, iceblocked etc, icehowl bugs and doesnt have a target. I haven't confirmed if this bugs the guy who spawns jaraxx, so if someone can confirm it'd be great.

if not i will be running it again tomorrow to see if this works.

NOTE: jaraxxus has to be bugged on your original* clear, no others afterwards.

[wreq]

please screen shots

[Sayu]

i've figured out how this is done.

when you enter ToC10m you occasionally can not spawn Lord Jaraxxus due to a bug with the person you talk to. When this happens you are required to wait a soft reset to be able to spawn him.

IF this bug occurs, you can clear TOC10, wait for the soft reset, and clear it once again.

It comes down to finding a way to "bug" this every time, and i *believe* it can be done by DIing someone, iceblocking, vanishing, etc WHILE GETTING CHARGED BY ICEHOWL ON NB.

If the person is DI'd, iceblocked etc, icehowl bugs and doesnt have a target. I haven't confirmed if this bugs the guy who spawns jaraxx, so if someone can confirm it'd be great.

if not i will be running it again tomorrow to see if this works.

NOTE: jaraxxus has to be bugged on your original* clear, no others afterwards.

dude, fraps it or prove it otherwise. your damn theories aren't helping anyone and I really doubt that it would work even with this trick.