Matenia

For anyone wondering, this is pretty much the preferred method. You could set WRobot's settings to completely ignore fights after calling Fight.StopFight as well. 
But this is essentially what I use to escape mobs in HMP too. Unfortunately dynamic escape while avoiding new groups of mobs is quite complicated and will probably never be 100% perfect as you need to also make sure you won't just run in circles etc.
Mostly just came here to say Zer0's approach is the one I found to be working best and most reliably.

Try
Lua.LuaDoString("TradeSkillCreateAllButton:Click()") If that doesn't work, the problem seems to be that Wrobot executes secure calls and the button won't won't work when doing so. There might be an extra argument that allows disabling secure call.
Additionally, maybe the anti-cheat protection WRobot uses breaks some code.

Decompile the Resurrect state and have a look yourself

Thanks, I changed the OP. I honestly hadn't touched WoW in years and only vaguely remembered that in some expansions, it already returns in percentage

I added support to pathfinder server

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

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.

Happy New Year to all !

I'm excited to start another year and look forward to continuing to serve you with WRobot.

This year marks a special milestone for us as we celebrate the 10-year anniversary of WRobot. 
I'm grateful for your support and look forward to many more years of success together. 

Thank you for choosing WRobot, and I hope you have a happy, healthy, and prosperous new year!

View full article

Hi guys, I've created a video showing how to create a C# plugin from scratch. If you have questions or need more info, don't hesitate to ask.
 
 

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.

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.

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.

what means your's "yes" ? I mean POLYAREA_AVOID is good enough for avoid. But wManagerSetting.IsBlackListed() method doesn't take new POLYAREA_AVOID enum.
btw little bit more respect for author! take back your "fucks" and describe detailed your repeatable bug

damn wManagerSetting.CurrentSetting.UsePathsFinder was disabled !! Shame on me
New polyarea is awesome, dude, You can push it in production

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. 

POLYAREA_AVOID by default will blacklist on a great height.
I added method
Pather.ReportArea(Vector3 position, float radius, float height, RD.PolyArea areaType)  

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. 

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. 

unitCaster doesn't exist in TBC and owner doesn't work either
In TBC, if there's a timer it's yours.

ToTown.ToTownInProgress (although I've noticed that sometimes that boolean is set despite not actually going to town, so try Logging.Status.ToLower().Contains("town")).

I don't think you understand how detection works. Detection means the client tells the server the bot is injected.
If you use patterns, grind for hours on end, don't do quests, use non-human behavior etc they can track that statistically. It doesn't mean the bot is detected.

I've it for years on Warmane and it's been safe except when I got caught. It was only ever detected on an old version, but that was fixed. So if you are using the old cracked WRobot... go figure.

local creatureType = UnitCreatureType("target") return creatureType == "Elemental" or creatureType == "Mechanical" Hopefully makes it more readable

You're likely trying to a quester profile as a grinder or the other way around. Start it as Quester

Then the best you can do is read log events and react to your current target when it happens. That should do the trick for now. 
Don't use the regular blacklist either (wManager.wManagerSetting.AddBlackList - this isn't realiable), it has to be the property directly on the ObjectManager class as seen here.

I realize log events won't help much with identifying the mob correctly, but hopefully this will do the trick as your bot is still targeting the mob, so that you can blacklist it and then stop the fight manually afterwards.

I think blacklist events exist, but I don't recall if this case is covered by them. There is a blacklist of GUIDs (which in "real" wow are truly random and NOT re-used like on most p-servers) attached directly to the objectmanager iirc. It's either a list or a map that you can manually add those GUIDs to and they will never be considered in the OM, so for WRobot it's as if those mobs don't even exist. I believe I used this in my free AV plugin for blacklisting AV mobs too.