Agreed...and if we know in the log what is going on...(teleported, Gm whisper, disconnect) we can have a story ready if we need appeal. "Playing on an old computer - crashed" "Screen is too small, so I don't have my chat up.." "Brother downloading porn while playing - lagged and disconnected (I swear it's not MY porn!!!)" Ya know, roll the dice with a story that is hard to refute. Using this example it would be better to straight disconnect rather than hearth...it would support the story.
My brain was working on overload yesterday again (yes I have a medical condition that I have hyper active brain activity, due to a bike accident when I was a child). As I don't want to mess with your plugin Giwin I have a few sugestions. Make a timer (optinal, don't know how much memory it would take without it) Compare your 'Me.Location' to your last location. If it differs more than 50, 100 or whatever yards, do some checks. Save Me.Location to Last location. Checks : Have we entered/left an instance, ignore as it's most likely false possitive. Have we entered/left an battleground, ignore as it's most likely false possetive. Have we used hs (dunno how to make a check for that, we can't really check if it's on cd as the cd for some ppl is 30 mins, for other 15 mins) Maybe it's possible to have a check if spell heartstone is being cast and in that case save a variable and then check with that variable for a false possitive. If none of above cases then disconect.
What are the other tools you are talking about? Oh and btw - does this plugin work or is it more a beta?
It works but I prefer to use the styx. Me. Location so it is profile independent. And btw tales of the past ftw
You use styx.Me.Location? How can i use that too? I dont understand exactly what u mean :/ TotP is great
Changing the pulse method Code: public override void Pulse() { if (StyxWoW.IsInGame) { if (StyxWoW.Me.IsAlive) { var distancenew = StyxWoW.Me.Location; var tempX=distancenew.X-distanceFromWaypoint.X; var tempY=distancenew.Y-distanceFromWaypoint.Y; var tempZ=distancenew.Z-distanceFromWaypoint.Z; if (tempX > MIRsettings.Instance.LeashDistance || tempY > MIRsettings.Instance.LeashDistance || tempZ > MIRsettings.Instance.LeashDistance) { Teleported(); } distanceFromWaypoint.X=distancenew.X; distanceFromWaypoint.Y=distancenew.Y; distanceFromWaypoint.Z=distancenew.Z; } } } also you need to declade distanceFromWaypoint which i haven't renamed cause i am bored to compare the two.Basically compare X,Y,Z axis every second.
Plugin seems to fail, when 2 WoW are open everytime i have HB with Plugin running on Acc1 and I log into Acc2 without HB, it says "teleported" and kills both wow.exe
I get the feeling that the way they teleport now, it's too avoid triggering my plugin (or they just changed it)... they never just teleported a few yards away before, when the bot starts to work I can work on updating this to include multiple methods and see whats best.
How do you avoid a false positive due to lag "rubber banding" then? Or is that not even an issue due to how it's coded (never coded anything beyond some vbasic macros in excel).
Updated to 1.3, Changed Distance to Distance2D (bit lower in number)... The randomize hotspots is the cause of the false positives and does need to be turned off, I'm also going to try and find that hut where people say they are being teleported as it seems like a popular place to be teleported. Not sure about the perfect distance because of the distance of the vendor may run up to 300, although it's better than nothing ^^ I'll do more testing but now that I've found what was causing false positives (randomize hotspots option) it should barely trigger false positives.
Known Issues with TeleportDetector as it doesn't turn off if teleported because the bot doesn't understand some functions like IsFalling (Version 540)... can't do anything until they fix their stuff (bot issue).
Two questions: 1. Any chance I can use this with a profile that does not contain any hotspots (like some crafting/shuffler profiles), so I can leave them alone crafting without having to fear they continue after being ported? If not, can you add this? There is an Anti-Teleport in Bengans Shuffle for example but I am not able to extract it due to my bad grasp of programming. 2. How can I check if it works properly? Can I try by using a warlock port? Thanks for your work so far.
hey thanks for this, I think it will definitely help. had a few ideas though. would it be possible to add 1) a log of what happened, when it triggered, any further info 2) an option to not log out after the teleport. Due to the fact that blizzard reads these forums, they would probably figure that every botter will logout after a teleport. Would be ideal if the bot would hearth, log out, or just say random stuff in guild chat 3) an option to say a message in guild chat/whisper random person/in /1 channel, in /say command? I feel like implementing these will give more randomness and not every bot will respond the same way.
1. already implemented 2. no, because they look for hearthing as i have another person's report of being teleported... plus what happens if GM teleports when trying to hearth. 3. already implemented but it's in say only in case of false positives and only gm can see
1. it would crash anyway with null reference exceptions anyway, so it won't work if there no hotspots lol 2. while farming, grab and put it somewhere else (like a teleport) and see what happens.
got some questions 1) Does the plugin logg you of then he detect a teleport ? 2) if yes how could you see waht u have writt in /s say etc ? 3) the plugin main reason was made for gather like mining herb ye ?
I think this would be a great plugin for campers / stationary fishers but as far as gatherbuddy n grinds concerned it shouldn't matter because No matter how many times they walk the same pattern it still looks like a person looking for more mobs/nodes/herbs to get.
