Matenia

He already said: Any version currently officially supported by Blizzard will not receive WRobot support. You're asking him to get in legal trouble.

https://github.com/tomrus88/BlizzardInterfaceCode/tree/wrath/Interface/FrameXML Figure it out. Time to read some code and figure out how that frame is created. Look into mail frame. From having a quick look it seems to open some MailFrameCOD. You can see literally all the functionality in place that causes this frame. Everything is statically name.

https://github.com/tomrus88/BlizzardInterfaceCode/blob/wrath/Interface/FrameXML/CoinPickupFrame.lua CoinPickupLeftButton:Click(); -- maybe?

Maybe contact the creators on their Discord, if you're looking for help.

Currently, it's almost impossible to find this section, for someone who doesn't know about it: https://wrobot.eu/files/category/174-wrobot-files-supported-by-multi-version/ The problem is, that it's not showing up in the main menus and you have to click your way through. There's still many useful plugins hidden there. It should be more visible.

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

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.

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.

For now, I can't reproduce it anymore (5 minutes ago, It was possible - idk!). If I can reproduce it again, I will put the values of Ticks checked and unchecked here.

I did the same test yesterday (exact same in development tools). Maybe it was a bad seed or something. My computer had already been running all day. Edit: Just did it again and it still always reports 1 - this is WRobot 32758. I can get it to work if I execute it before even starting the bot (Quester). If I use it while the bot is running without ever using it before, it will ALWAYS result in 1. For now, I just made my own implementation in my quester profile to work around.

I'm sure this worked on TBC back in the day. Currently definitely broken on Vanilla.

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: