Protect PiroX AFKBot against Warden

[LuBu]

First of all, this is not my work, i just added some links, comments and compiled some other Threads to this new one, hopefully more understandable


Safety tips against warden:

So at first, download the newest AutoIT Script from eScription - Home
2. Download the bot source (.au3)Download Here (7.2.7) Use Right click -> Save Target
3. Add some lines to the code to get a bigger filesize

example:

code:

Just Add beyond this line
Dim $asjdgas = "21zsb09218"
Global $muhmuhmuh = "asdajg"

Func wohoo()
sleep(1000)
sleep(2000)
sleep(7000)
EndFunc



The variables change your memory hash (i think, but i don't know)
The file hash does change because of the added code.


4. Change the AutoIt3Wrapper ResHacker Infos:
7.2.7.0 default:

code:

#AutoIt3Wrapper_Res_Description=HappyNewYear
#AutoIt3Wrapper_Res_Fileversion=7.2.7.0


to example

code:

#AutoIt3Wrapper_Res_Description=Outlook 2008 Professional
#AutoIt3Wrapper_Res_Fileversion=1.2.2.6


5. compile it

6. Copy the new *.exe to the Pirox AFK Bot Folder and replace the old pirox.exe, start as usual, have some fun

[Yeti]

first off, your never safe using pirox (running into av walls....yeah..right)

second i thought this was just a process guard for a sec and i was about say WOWWWWWW

[LuBu]

of course, your never sure of beeing reported or banned when using Pirox or any other bot program. But by adding these code to the sourcecode, you change the size of the *.exe, another way to reduce the risk of beeing banned by warden, of course you should rename the folder of Pirox and the *.exe itself, using Processguard is the same thing. But i think, thats common sense for botters, so i wanted to show some more security

[Yeti]

make sure thats not your code, since whats the point if everyone just takes the same code and hash size still =P

[Heggo]

Second off..

Warden doesnt ban you for using Pirox.

He bans you for having the "Lazy" buff more than 5 times.

Like if you get reported afk (like everyone gets while using pirox) and you get the Lazy buff more than 5 times, the Warden bans you for 24 hours (sometimes 3). Kinda the new and improved "Deserter" debuff :P

[Yeti]

yeah thats pretty much true..

[LuBu]

yeah, of course, afkbotting has been very risky in the last time because of the Lasy buff, but still you can get banned when using hacks/Bots etc. Pirox AFK Bot is not that different from Glider, it´s not u playing, it´s a programm, that is what warden scans for

[[Blaze]]

But, I haven't been perma-banned for Pirox's AFK Bot. Maybe cause Glider can be used for... gold farmers? I dunno but I'm willing to take 3 hours as a first offense.

Which I've already stopped using it cause I have full Glad gear cause of it

[PiroX]

1 by 1 copy of my forum
Link: PiroX AFK BG Bot Board - Safety Tips

i will soon release v7.2.8 where u can use profiles which u can make with macrogamer, a beta is already available in piroxafkbot forum

[Zaphry]

1 by 1 copy of my forum
Link: PiroX AFK BG Bot Board - Safety Tips

i will soon release v7.2.8 where u can use profiles which u can make with macrogamer, a beta is already available in piroxafkbot forum

And yet again i thank you ^_^

[gangbanger]

I am not changing anything :P never been caught :P

[khaled1994]

nice thx =)

[Heggo]

yeah, of course, afkbotting has been very risky in the last time because of the Lasy buff, but still you can get banned when using hacks/Bots etc. Pirox AFK Bot is not that different from Glider, it´s not u playing, it´s a programm, that is what warden scans for

Yes ofcourse, but if Blizzard perm banned everyone for using Pirox, they would lose many, MANY subscribers :P

[mmhelm]

LuBu is right, have you tried counting the average AV/bg botters in one battlegroup?

3 during prime hours for both factions
10 - 20 during nighttime
Look at it as fuzzard losing 15$ for each person if they took action
????
Profit.

[swollen]

I don't see the point of making macro's TBH.
Macro's don't always take you the same way as when you recorded them, if your FPS changes slightly, you have a tiny lagspike, or something similar, it change the whole course of a macro.

the best way to do it is memory reading with waypoints.
Enough said.