camelot10

Seems like blizzard avoid/fear to scan hardware ids or ip. There are huge amount of proofs that each WoW instalation have unique ID, and if one account catched in botting (see algorythm below) others account used in same wow instalation in danger.
This mean: all accounts who interact (trade, mails, guild banking, leveling) with catched account and have same WoW ID goes to ban with catched account.
RULE #1: DIFFERENT WOW INSTALLATION FOR EACH ACCOUNT. IF ACCOUNT COMPROMISED REMOVE THAT WOW FOLDER AND INSTALL NEW FROM FRESH
How they catch botting?
1. Client Side Detection.
If bot doesnt have enought protection then wow/blizzard detect it. Nothing you can do about it. Account flagged, all linked account flagged too (see rule #1)
 
2. Server Side Detection
Everyone should google about AI and heatmaps. Here brief example: youtube
blizzard doesnt ban/catch/watch by ip or hardware id. when you have millions of users, you can get heatmaps of users interactions. and when some part of your userbase start acting like on alghorythm, and you can predict what and when they do and what they gonna do next. this is main problem with popular bots/profiles: 100 000 users go to X,Y get quest AA or gather node BB, then all of them go to X2,Y2 and get quest CC or node DD and so on. after few hours/days/weeks blizzard have heatmap algorythm. and if someone: even if that player login for 20min, but in this 20min that player do same steps/action that other botts do -> blizzard mark your character for banwave and all linked accounts (see rule #1).
that why banwaves apprear once per 6-12 months. Its a gigantic job to calculcate bots heatmaps, its like a trump ace on your hands, you gonna rise till max and only then reveal it.
RULE #2: AVOID PUBLIC GATHER/GRINDER PROFILES
no public profiles -> even if someone posted good profile -> mimic it: download profile, run for 1 secs, make screenshot from radar, delete profile, make own profile according to screenshot. event that method i would't suggest. make all profiles by hands. its a 2-5min to make good route
never make profiles with one lap (loop/circle): made something like olympic rings, 2-5 circles
 
grinding only on "hotspots" - > no path
Each time you got banned-> remove and forget profiles used
RULE #3: RUN DIFFERENT TASKS/PROFILES
especialy actual content. i mean do: reputations, daily, dungeons, timewalking, lfr, mythics, darkmoon. everything that breaks your farm heatmaps routine (grind/gather)
 
TINFOIL HAT RULE: Differect PC/Virtual PC + IP/Provider/VPN
that doesnt help much. but! BUT!

discord banned our channel. lets move to telegram.
here link: https://t.me/wrobot_eu
 

you can't just quit botting

you can't just quit botting

fixed. thanks alot

just set " Check if know spell" = false, and add check pet distance to target <= 5 and now my felguard use it as intendet. thanks

Hello,
Yes of course I'll add 64 bit support (and I'm going to start working on it before release, it's a lot of change)

тут политика: меньше народу больше кислороду. то бишь за количеством никто не гонится. главное сильно не отсвечивать. 

you can't just quit botting

pm me

everything possible with wrobot except stormheim first scenario

@Droidz
hi
attached xml and cs encrypted, put both in Profiles\Quester\
Testing.xml have custom script Testing.cs
run Testing.xml. when i run i got errors:
[E] 17:46:53 - Compilator Error : c:\Users\ssrazor\AppData\Local\Temp\shwennwk.0.cs(13,1) : error CS0116: Пространство имен не может напрямую включать в себя такие члены, как поля или методы [E] 17:47:01 - Compilator Error : warning CS1685: Заранее определенный тип "System.Runtime.CompilerServices.ExtensionAttribute" определен в нескольких сборках в глобальном псевдониме; используется определение из "c:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll" c:\Users\ssrazor\AppData\Local\Temp\krmb4xas.0.cs(16,7) : error CS0246: Не удалось найти имя типа или пространства имен "EciegidOuNyBtBwYiftjnvCVwpPUNPtxfeGOGXje" (пропущена директива using или ссылка на сборку?) wrobot doesnt support "custom script" encryption? tryed both variants: shorten (serverside) and not shorted (client side)
or im doing something wrong?
 
p.s. if cs is not ecrypted, then encrypted xml loads and run successfully
Testing.cs
Testing.xml

search "how to post logs"

search "how to post logs"

search "how to post logs"

return wManager.Wow.Helpers.Bag.GetContainerNumFreeSlots &lt; 4;

ObjectManager.Me.IsFalling
        ObjectManager.Me.IsFallingFar
 

http://bfy.tw/Eope

ObjectManager.Me.BuffStack(12345) >= 5

wManager.Wow.Helpers.CVar.SetCVar("autoDismount", "1"); wManager.Wow.Helpers.CVar.SetCVar("autoDismountFlying", "1"); wManager.Wow.Helpers.CVar.SetCVar("autoLootDefault", "1"); wManager.Wow.Helpers.CVar.SetCVar("autounshift", "1"); u welcome

never scammed anyone. he ask, i reply. i dont know what wrong: he cant use search, he doesnt like your or droidz plugin. next time try answer not in rude way. mkay?

Seems like blizzard avoid/fear to scan hardware ids or ip. There are huge amount of proofs that each WoW instalation have unique ID, and if one account catched in botting (see algorythm below) others account used in same wow instalation in danger.
This mean: all accounts who interact (trade, mails, guild banking, leveling) with catched account and have same WoW ID goes to ban with catched account.
RULE #1: DIFFERENT WOW INSTALLATION FOR EACH ACCOUNT. IF ACCOUNT COMPROMISED REMOVE THAT WOW FOLDER AND INSTALL NEW FROM FRESH
How they catch botting?
1. Client Side Detection.
If bot doesnt have enought protection then wow/blizzard detect it. Nothing you can do about it. Account flagged, all linked account flagged too (see rule #1)
 
2. Server Side Detection
Everyone should google about AI and heatmaps. Here brief example: youtube
blizzard doesnt ban/catch/watch by ip or hardware id. when you have millions of users, you can get heatmaps of users interactions. and when some part of your userbase start acting like on alghorythm, and you can predict what and when they do and what they gonna do next. this is main problem with popular bots/profiles: 100 000 users go to X,Y get quest AA or gather node BB, then all of them go to X2,Y2 and get quest CC or node DD and so on. after few hours/days/weeks blizzard have heatmap algorythm. and if someone: even if that player login for 20min, but in this 20min that player do same steps/action that other botts do -> blizzard mark your character for banwave and all linked accounts (see rule #1).
that why banwaves apprear once per 6-12 months. Its a gigantic job to calculcate bots heatmaps, its like a trump ace on your hands, you gonna rise till max and only then reveal it.
RULE #2: AVOID PUBLIC GATHER/GRINDER PROFILES
no public profiles -> even if someone posted good profile -> mimic it: download profile, run for 1 secs, make screenshot from radar, delete profile, make own profile according to screenshot. event that method i would't suggest. make all profiles by hands. its a 2-5min to make good route
never make profiles with one lap (loop/circle): made something like olympic rings, 2-5 circles
 
grinding only on "hotspots" - > no path
Each time you got banned-> remove and forget profiles used
RULE #3: RUN DIFFERENT TASKS/PROFILES
especialy actual content. i mean do: reputations, daily, dungeons, timewalking, lfr, mythics, darkmoon. everything that breaks your farm heatmaps routine (grind/gather)
 
TINFOIL HAT RULE: Differect PC/Virtual PC + IP/Provider/VPN
that doesnt help much. but! BUT!

u welcome

wManager.Events.MovementEvents.OnSeemStuck += OnSeemStuck;

no need for such coding
/cast [@cursor] Far Sight