You can recode my plugin to fit into Grind Mode and AHBuddy, it's all open source and you are welcome to use any code.
It works for Grind Mode and AHBuddy now? Awesome then, thanks a lot if thats what u meant... i never used this before i would not like to make mistake and dont notice the teleport in case it happens, do you mind telling me how much leash distance would be good for ordinary grind profile and AHBuddy? And how can i test it?
I updated TeleportDetector to the latest version and now it doesnt show up in my plugins and gives me a message in my HB log. but when i get a fresh download and dont update, it works but no GUI option. The GUI would be in the folder or the settings in the HB plugin area?
tested again by accident... it seemed like only 400 yards but it was 1600, I think this really would detect teleports at least until they read this thread. again, you should adjust by your false positive, so increase it by 200 yards on every false positives... I reached 900 and it runs fine.
Updated but now doesn't work. \TeleportDetector.cs(85,21) : error CS0161: 'TeleportDetector.TeleportDetector.VendorDetour()': not all code paths return a value
Update 1.5: August, 2nd, 2013 - I will be updating this to a working teleportdetecter based on a method mentioned and one that I preferred to do, although I've discovered that the same method can be used to detect stucks (ever been stuck on the top of a tree?, infinite looping?) by using this same method but in reverse. on the stucks, it would use hearthstone because I've found some places where even a normal person couldn't get out of without using hearthstone, just need to test it a lot more... running 24/7 atm in a stuck friendly area (won't get reported by players). on teleport, it would kill wow and reloggers.
Saw one if my farmers by a Cliffside just flying back and forth in a 10yrd loop. It was randombuddy farming, but my guess it's a nav / gatherbuddy issue. So this update could be used for that kind of thing?
False Positive: When you go to logout it will sometimes trigger the stuck detection, since this requires manually intervention I won't be fixing this as programs which 'kill' wow don't need to go through the logout process.
