Please stop using ZOLO for 3.0.9

[wowpanda]

Hi all,
This is the author of zoloFighter and zoloFisher.

As of this morning (2009-02-10), I found wow has installed a driver alone with the new patch. This means WOW can no longer be restricted by the original guest account mode, and only users who take time to read and understand instructions can run it safely.

For now I will disable the bot, and I will analyze what ever blizzard has done, and see if there are ways to automatically detect it with a legit third party tool to warn users. If it can be done, the bot will stay open. If not, the only way will be put the bot private and anyone who want to use it has to confirm with me that he/she has follow the proper steps.

Of course there could be the time when blizzard just forces this on any computer and won't run WOW without the driver. At that time the bot will have to go private all the way.

As of now, please stop all donations, it won't do you any good.

Thank you
Panda

[Robske]

I really doubt running WoW as guest stopped anything though.

Can the green texted charma... nazgul confirm this awkward theory?

[wowpanda]

Yes it works. else you will see headlines about how windows got a huge hole etc. You can only do so much at a restricted level, since the x386 days.

However WOW did something different. they might be on the device driver level now and unless you knowing avoid that there is not much I can do.

[Hootiie Pwnz]

Comfirmative Truley Blizzard shows more care now.

[wowpanda]

And it is not only zolofighter. all public bots (and popular private ones) are in danger. I am sure the next step for them will be they will check to make sure their "supervisor" driver is there before you can play.

[UnknOwned]

Not just bots ^^


Im currently trying to figure what is going on and see what this new thing does and "can do".

[EDIT]

Couldnt find it, but found something strange in the hearbeat.
A new flag? hmmm....

[UnknOwned]

And it is not only zolofighter. all public bots (and popular private ones) are in danger. I am sure the next step for them will be they will check to make sure their "supervisor" driver is there before you can play.

I heard someone managed to spoof the OS type, making WoW on windows apear as WoW on mac and in that way avoid warden and what not.
Since i don't know anything about the diffrences in clients i can't verify this, but it does sound interesting.

[dynamics]

Well this was pretty much bound to happen eventually, although I didn't expect it so soon. Thanks for the heads up anyway when are you going to release the unlocked version again for those that want to keep running the bot safely until the device is actually forced to be ran like you mentioned?

[Mango Jerry]

Thank you for the sad News, WoWPanda.
Its really bad that Blizzard will stop the Ultimate Bot after the 3.0.9 Patch!

[Hamut]

There is no Driver in this patch.
*think before you post.

Hamut

[Lucifarius]

holy SHIT at all the FUD in this thread.

Shameful

[rezinous]

Thanks for the update, hope to hear of a fix soon

[ramey]

LOL. There is no driver.

[UnknOwned]

There is no Driver in this patch.
*think before you post.

Hamut

Btw Hamut
Did you check the upcodes?
Tinus found something there...

[wowpanda]

OK, I got several messages from people who told me they didn't have to reboot. I came home this noon and didn't find any extra drivers from blizzard, however there is a windows update taking place at the time when blizzard's patch come in.

I didn't turn on that computer for a while now (since the last update) and it is most likely a windows update that forced me to reboot, not from WOW.

I am reinstalling wow now, and I will try the updates again tonight to make sure.

Sorry, you will see more opps like this from me in the future. It is better safe than sorry and I don't have much time in the morning to verify if blizzard has pulled something or not.