zoloFighter WOW grinding bot

[kanadin]

Nice job Panda! I love this bot,only thing is,some times when I set a waypoint path,it just runs in a circle and wont attack anything. Any ideas?

[l8flip]

I know this is sort of a double post but I just wanna check with wowpanda so I'm pasting what I said on the last page here:
"Yeah the thing is it never actually started, I never actually launched the bot.I just had the exe file running. I never pressed "fight" or "ok". So
So I doubt it did any injection or memory reading or even interfered with WoW.
Would that mean any difference?"

[minifss]

l8flip; Shouldnt be that big of a deal then, but would change the exe name of the bot, just to be sure :P

kanadin; Youve got to add the mobs to the profile!

[l8flip]

Phew, cheers. Thats the answer I needed. The file name was already changed when I ran it luckily.

[dmc22]

blizz can detect this as well as glider innerpspace etc now. It basically makes a check list and sends it to an employee to whack the banhammer.

[wowpanda]

@dmc22 no, this is not detectable as long as you follow the rules. I am boting right now, and botted through the ban wave, and my wave of anti warden is generic enough that I don't need to do much at all every time there is a new update.

@l8flip you might still be at risk, because you did everything backward. The only thing that could save you is Blizzard has put a lot of resource on the ban wave and didn't have time to track my new fighter updates. I would suggest you to stay low and don't bot afk, in case a GM tries to check on you

[dmc22]

care to explain what setting and updates your talking about.

[l8flip]

well does the bot actually do anything if you just run the program without pressing any buttons? I dont see how warden would detect it but then again thats just me.

[wowpanda]

@dmc22 the settings are well documented on my post and my site. The updates I was talking about is the wow patch.

@l8flip WOW scans your computer from time to time for loaded processes. In your case you started fighter as guest so it is powerless to even defend itself, WOW could have scanned it. However if you started as guest, the bot should have complained and let you know, so most likely you hit the "exit" button right away, which leave the exposed time to be short. anyway, it is possible that you were exposed. So take my warning and always watch your bot.

[minifss]

I did too bot through the ban wave, nothing to worry about as long as you follow the security instructions.

[Demonicas]

I botted through the banwave also, was not afk botting though but I didnt get messed with once.

I did give it a break yesturday though but I might run it for a few today and see how things go.

[wowpanda]

Break or not is not important, the important one is not to bot afk.

[wowaddict605]

Thank you for the bot!! +rep

[l8flip]

Heres exactly how I did it:
1. Switch to guest
2. Start bot, tried to run wow but did not work, then forgot to close the bot.
3. Switched to administrator
4. Ran wow on administrator
5. Few hours later, switch back to guest. Realized the exe file was running.
6. Closed it.
I mean, I never started wow from the bot. I didnt even bot. Didnt press fight or ok, just tried to press "Start wow". when it didnt work i swtiched to admin and ran it from there.
So final question do you still think I could be at risk? I understand if you just say yes no long explanation needed mate.

[wowpanda]

That was really bad. The bot should have realized that it is not logged on as admin account and warn you. I need to check if that feature is still there or not.

Yes you are at risk.