EXILE

Log attached. Keeps getting me killed cause it'll run into 2-3 mobs trying to loot another one T_T

24 Jan 2019 10H06.log.html

This thread existing doesn't make it any easier for them to detect "us" or botting. Anyone with that mindset must be new to the botting scene.

The methods used to detect botting haven't changed. They may have some things that are unique to their anticheat/bot detection strategy, but generally it comes down to:

1. Player reports (leaving your bots on too long, bots doing stupid things/dying a bunch of times, bots not answering whispers, bots running "bot trains")

Once the original report happens, it gets investigated and they ban you, then:

1. Your IP is flagged
2. Your HWID is flagged

After that it falls on the botter to take the measures to protect themselves. Both my IP and my HWID are flagged, so if I start a new bot it gets canned by level 10 if I'm lucky, usually by around level 5. That's why you need to run VMs + Proxies or VMs + VPNs.

If anyone's interested I can make a guide explaining how to set all this shit up so you can feel more secure and not worry about people posting on the forums ?

There's definitely some form of detection running on Northdale now. It's pretty good at catching lower level characters, not as good at getting higher levels, so it seems.

Definitely bot at your own risk, and make sure you're using proxies and private profiles if you do. Being on a public profile right now is asking to get banned.

Seems like I found the fix. Turned off "Locked frame' in my fightclass' settings.

Just started an alliance warrior and it seems to be crashing everytime the fightclass casts Heroic Strike. It's weird though cause I have a horde warrior running the same profile and that hasn't crashed at all.

Log file is attached

20 Oct 2018 13H19.log.html

Gotcha, thanks

Bot is working now, but spams another error and clutters up the log

16 Oct 2018 20H12.log.html

7 hours ago, BetterSister said:

i did

No troll ?? Is there somewhere I can get the most updated profiles in that case?

I had bought them last year and know he had given over the project to someone else. Seemed like the developer was making good progress but I lost access to the discord and have no way of finding my way back.

If anyone could point me in the right direction I'd appreciate that.

Logs are attached. Get an error anytime I try to run quester profiles

16 Oct 2018 01H10.log.html

16 Oct 2018 01H18.log.html

On 2/6/2018 at 11:31 AM, FNV316 said:

You dont have to change your monitors settings. Just lock WoWs frame rate:

 

 

thanks bruh

I've been running the bot on 60hz so it works properly, so I'm not sure if the logs will show you anything. But here's the two I've been running for the past few days:

I can switch my monitor to 144hz and let them run for an hour or so if that'd be more helpful to diagnose the problem. As far as I've seen when I put the monitor to 144hz the bot has problems facing mobs and using pathfinding.

6 Feb 2018 09H16.log.html

6 Feb 2018 09H18.log.html

EDIT: I probably should've specified I'm playing on a vanilla server/using the vanilla version of WRobot

Bot doesn't function properly while using a 144hz monitor and wondering if there was any plan to add functionality/support for 144hz monitors. I want to have my bots running in the background but in order to do that I have to keep my main monitor on 60hz instead of 144hz and it really ruins the quality of the game I'm playing while the bots run in the background