Matenia

Best available is hit and miss. It tries to read spells from the game. 
You might find a helpful plugin here: https://wrobot.eu/files/category/177-plugins-multiversion/

You need to use Lua to iterate your debuffs and get their debuff type, then cast Purify if it's poison. 

https://github.com/droidzfr/WRobot_Packages/blob/fccc740c611b6447361d401c2aa35bb401d6f638/Old paid files/akuros/PriestDiscipline By Akuros v1.2.cs#L302

You also need to find the correct parameters for your Wow version. They're different between 1.12.1, 2.4.3, 3.3.5a, 4.3.4, etc

14 hours ago, Zer0 said:

No worries.

After looking again at your log, I think I know what's going on. The issue that appears is the time it takes for your WRobot to calculate a path. WRobot uses a distant server for pathfinding (which is one of its biggest flaws in my opinion) and the AQ uses pathfing a lot, and often. Even very short paths seem to take at least 340ms for you, which is really a lot. VPN, slow internet connection, I don't know. As a comparison, mine takes 40ms max on short paths.

[N] 07:41:04 - [Path-Finding] FindPath from -11074.75 ; 898.3192 ; 40.03555 ; "None" to -11129 ; 936.59 ; 36.8307 ; "None" (Azeroth)
[N] 07:41:05 - [Path-Finding] Path Count: 5 (133.2519y, 345ms)
[N] 07:41:05 - [Path-Finding] FindPath from -11074.75 ; 898.3192 ; 40.03555 ; "None" to -11096.38 ; 886.2285 ; 41.5276 ; "None" (Azeroth)
[N] 07:41:05 - [Path-Finding] FindPath from -11074.75 ; 898.3192 ; 40.03555 ; "None" to -11067.94 ; 899.621 ; 38.16179 ; "None" (Azeroth)
[N] 07:41:05 - [Path-Finding] Path Count: 3 (24.90453y, 341ms)
[N] 07:41:06 - [Path-Finding] Path Count: 2 (7.178874y, 469ms)
07:41:06 - [Wholesome Auto Quester] Defending against Riverpaw Taskmaster

As you can see here, even a 2 nodes, 7 yards path took 469ms. This + the Line of sight checks I do on enemy detection might just be enough to make your bot too slow to react, which is what I observe from your gif. But I can't guarantee that this is your issue.

Try caching. This is what I had to do for HMP. In HMP, there's a similar functionality where I attempt to recognize mobs in your path by scanning vectors around where I know the bot is intending to walk to. 
I found that caching approximate distance somewhat alleviated these issues. As a further backup, I tried creating a square around the character and periodically check for colission of enemies within that square. It's by no means pretty or efficient, but it doesn't have pathing overhead. Maybe this is something you might wanna try for the Wholesome Plugins too.

Additionally, regarding OP's request to rezz away from mobs -  this is something I've tried with HMP too. I know Droidz has his own code, but generally speaking it's not actually that easy. If you're trying to do the math, you may end up with no safe spot at all, simply because there aren't any within rezz distance. Some servers will also allow for rezzing from further apart than would normally be the case and all you can do is guesstimate and choose what should be "safe" values for most servers.

Personally, I place myself on top of the corpse, calculate the angle to the closest mob, check 180° in the opposite direct (so further away from that mob) in a cone for spots that aren't within x yards of a mob. There's only so much you can do.

PS if you message me on my Discord, I'll give you a 24h trial to HMP to see if this will alleviate your issues at all. If it does, I can pass some of the code on to Droidz and he can see if it helps him at all.

Here's my take on this as a software developer:

• yes, but the traffic they can check is usually not very useful, only your WoW client communicates with their server
• I doubt they actually collect THAT much data. Most pserver owners don't have the infracstructure. Pserver are already running at their physical hardware limit and data warehouse costs extra $$$
• It's long been rumored, that they found an exploit in the WoW 1.12 warden that lets them execute abitrary commands on your PC, so they can do a traceroute and see if any of the IPs matches - this was never confirmed
• again, see point number 2. They obviously have logs, but definitely not to the extent you mention. They absolutely do not log the positions of 5000 players every tick (100ms) - where do you even store that amount of data? Yes, inventory logs and gold transactions as well as mail traffic are OBVIOUSLY monitored. Similar thing for combat routines.
• browser fingerprints have been known for a while - use Brave in icognito mode BEHIND A PROXY/VPN to create new accounts, this doesn't need to be said twice

If they can tell what games you have running on your computer, you either downloaded additional software or that exploit that lets you execute any code through Warden is real. I doubt it's that. It would be highly illegal and is essentially the same as turning the WoW client into a trojan for as long as you are connected to their server. They could just use the code to download an ACTUAL trojan. If you strictly monitor traffic on your own system, I'm sure you'll find this is not it.

Use the TRIAL key and find out on an account you don't care about. If you don't get banned within 10 minutes, it's safe.

I doubt they can detect. TBC is similar to vanilla - the client is ass and doesn't have good anti-cheat. You need to develop server side pattern detection in hopes of finding bots.

8 hours ago, junger2017 said:

to day i just made another 11 accounts, going to buy 3 old laptops, with 3 character on each, with vm, 3 routers with different internet provide , and plus vpn, : D, botting , still have 50+ characters which i have stopped botting, 

Don't buy laptops. You can run vanilla on a used office PC with an iGPU (like Intel i5 4440 or i7 4770). Alternatively, you can get cheap X99 (QD4 or MR9A) from China and pair it with a bunch of RAM and an E5 2670 v3.

Put some cheap Quadro K600 or K2000 in there and you can run 4-8 WoW VMs in a single instance if you want/need. It does take up more space than 3 laptops tho, I guess.

First try on Everlook I forgot to fix my movement and got banned in the starting zone. Made a new account on the same IP 5 minutes later and got banned at level 38.

Running 12 hours a day unattended. There's something you're likely doing wrong. And if you're connecting several accounts (you care about) through the same IP, I'd start there.

That would mean automatic support for official servers (because you're supporting an official client) and it wouldn't at all be compatible with exisiting WRobot stuff for vanilla/tbc/wrath.

My best guess: Never, ever happening.

Finally got my test character banned in the mid 30s. No quests done, nearly no monitoring besides a few times to make a few fixes to my products for vanilla.

The last entry in the log was 

[Fight] Mob has moved more than 45 yards

So I suspect regular old GM check by teleporting a mob to see the bot's reaction.

Conclusion: No ban waves. It's safe to bot on Everlook if you use CTM with Rivatuner to limit FPS to 60 and use a semi-decent profile.

1 hour ago, w8plz said:

@Matenia also have your's paid profile and he uses S&D, but when 2+ mobs. How can i turn ON for 1st combo?

 

You can't and it's incredibly inefficient for leveling. If you use Rogue.cs you need to learn C# to change the conditions.

My guess: Respawn is too fast and the server is recycling GUIDs.
GUIDs are supposed to be unique and generated on every spawn. WRobot blacklists them for a while after killing them. 

Droidz offers a solution here: 

A plugin that basically does this (but also unblacklists pretty much everything in the current session - this is not ideal) can be found here: 

It's vanilla. Every spell needs to be on the action bars and you need to manually update the ranks as you get new ones. That's why I made the effort of writing a whole framework in C# that tries to automate everything.

If you're using CTM, get Rivatuner Statistics Server and limit your framerate to 60. I have not had issues with that. At least when disabling all kinds of smooth movement options or plugins.

Unless you write something completely custom in C#, you can't. WRobot isn't built around healing (or even raid rotations).
Also, expansions matter. 

There's a free shaman healing fightclass with source code attached here:

For Holy Pala there's something here:

3 hours ago, sanelb said:

I figured out by editing quest it and adding it to my quests

 

its strange if you manually take a quest the bot doesn’t seem to understand that 

That is not strange at all. Stop playing the game on botting character or only use grinders.

Vanilla (and even TBC) are incredibly old. There is no info from the server or game regarding which quests you've already done. It's literally impossible to figure out.

No log file, no clue which questers, no clue if WRobot is potentially trying to vendor and a cropped screenshot.

Figure out what WRobot is actually doing, maybe read your log

Been running 12 hours non-stop with no problem at all. Once you're out of the starting area and follow my advice above, you're mostly safe. 

Not using CTM has a high chance of getting you caught/banned. I recommend RivaTuner Statistics Server to lock your game to 60 FPS so CTM doesn't bug out.

18 hours ago, swishswish said:

Gm just turned Mob Green and controlled it so i couldnt attack it, i am in a starter area but he knew i was botting or saw weird behaviour.

Might work

Is it possible to add a new type, "IMPOSSIBLE" or something, with cost 2000?
There are scenarios where going around is the only way. BigDanger is good as is. It shouldn't be changed.

I think they analyze movement packets. Maybe CTM or "SmoothMove" option of some kind is spamming the server too much with movement packets of some sort that they can recognize. 

Quote

Q11: My character tries to pull from out of range and/or wRobot thinks it can't fight the target, then switches to another A: Go into advanced wRobot settings and disable "calculate distance by target size".

Server you're on seems to calculate distance differently from the client. This could be either because they specifically chose to do this (to mess with bots) or because their client is modified.

Additionally, WRobot's fightclass range works as specified. If you set it to 40yd, it will ALWAYS try to fight from 40 yd. If you set it to 30 yd but have a spell that works from further away, it might try to cast that spell and stop movement for a second. This is why people do a bunch of calculations themselves to prevent this as much as humanly possible.

If you know C#, I open sourced my framework that attempts top to take care of these problems.

Even with "only your current profile", it will automatically add new ones. You need to disable that option.

Your fightclass or something similar likely sets WoW to the minimum FPS required with a macro, like /console maxfps 20

Disable unstuck. It does nothing anyway if you ever get stuck.