Nax

not gonna lie, would be awesome if @DroidzAdd a Asm DetourHook class to wrobot so we can hook functions and have more control over wow. but i know he is using Break points and i dont know if having asm hook will mess with break points.
 
@Pudgei wrote my own packet sniffer for wow in c++ (its not public) if you want to message me, i can let you use a copy of it. 
 

No.
 

looks like a socket problem
 

Dear community,
I just found, I still have access to some workspaces via bitbucket (where I barely ever log in).
Therefore, I'm sharing the original source as it was last commited by him here. I don't know if it's different from what was already uploaded or anything. That's why I'm sharing it in the developer forums and not plugins/quester.
Last commits are from early 2018.
mxsbt-vanillaflightmaster-dbcc4a5bd0e7.zip fnv316quester-quester-1-40-71d751b8482d.zip

Simple google search : https://www.google.com/search?q=wrobot+Face+target&rlz=1C1CHBF_enUS1022US1022&oq=wrobot+Face+target&aqs=chrome..69i57.3199j0j7&sourceid=chrome&ie=UTF-8
 

Yes.

Im patently wait to see if anyone is gonna tell this guy he is using c# and not lua?

i found this, Might help. use google next time. https://github.com/Talamin/Wholesome-Dungeon-Crawler/blob/master/States/AvoidAOE.cs, also i do not know if wrobot ObjectManager has this type of info but Aoe ability's and ground effect can be found as Dynamic Game Objects. Here is the code for creating your own function using wrobot Descriptors, https://www.ownedcore.com/forums/world-of-warcraft/world-of-warcraft-bots-programs/wow-memory-editing/300463-wow-3-3-5-12340-info-dump-thread.html
 

The  reason your character only moves a little step is because you're still on the fight thread, so your code only executes for one fight loop iteration. The next iteration, you're back on the normal fight loop which forces you to get in your fight class range.
There are two ways I know to prevent this.
1 - Lock the thread in your method. Which in your case would mean calling MovementManager.Go(pathList); and the next line, lock the thread in a while (MovementManager.InMovement) loop. I wouldn't necessary recommend this, because you're blocking the entire fight loop and you will need mutliple conditions to set it right.
2 - Cancel the fight event. This is my preferred option, but it's more complicated to set up. The code Nax has linked you is one I've written. It uses a manager that listens to multiple events.
On the ObjectManagerEvents.OnObjectManagerPulsed event, I check and record a list of all the AOEs present in the object manager range.
On MovementEvents.OnMovementPulse and MovementEvents.OnMoveToPulse I make sure I don't walk into an AOE, and make sure I never cancel an escape
On FightEvents.OnFightStart, I make sure I don't start any fight during an escape
This code doesn't really fit your need, because it avoids AOEs that stand on the ground (like a puddle of poison), and uses a "grid" to look for a safe position. In your case, you react to a single action.
What you need to do is:
- Detect the moment you need to escape.
- Cancel the current fight, using cancelable.Cancel = true;
- Calculate a safe route.
- Turn an escape flag to true (a simple boolean)
- Make sure you don't start a new fight during the escape using your flag
- Turn back the flag to false when your safe condition is met

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