teleport protection plugin

[Farah]

Hello,
I need a plugin that can "pause" my bot when I get teleported by a gm.
I know there's Logmeout but that one just closes your wow upon teleport and this just does not suits my need.

I need something like the teleport protection embedded in the Bengan's Multiprofession profile.

 

[Giwin]

They used to teleport you when they had the staff, it's all automated nowadays by server side scripts.

 

[Farah]

They used to teleport you when they had the staff, it's all automated nowadays by server side scripts.

GB bans are automated yes, but I am not talking about GB.

The only way to ban AH bots, for example, is to teleport them around to make sure they're bots.

Trust me, I speak from my own experience, I witnessed to my bots being teleported behind walls, on cliffs etc, away from the auctioneer. 3 days ago was the last time that happened and I managed to save 2 out of 3.
I managed to save a few of my AH bots because I logged back in right away (I use logmeout) and started playing by hand. Unfortunately I am not always ready to take over and if you do not relog right away they figure out you're a botter using a disconnecter. So I need some kind of extra protection for my ah bots like the one in the Bengan's Multi Profile.

 

[Giwin]

I would agree with you when it comes to AH bots, I would say teleport detection is definitely needed but the TeleportDetector I made and posted on the forums wouldn't be suitable for an AHer as it simply closes the bot after sending a message (maybe might be enough).

 

[Farah]

Thanks man, I've tried your plugin just now and it's alright. Although it would be wonderful if you could add an option to your plugin so that it pauses (as HBToggle does) or even kill the HB instance (I do not use HBRelog so no problem) instead of killing the related WoW instance right away.

 

[BotOperator]

Trust me, I speak from my own experience, I witnessed to my bots being teleported behind walls, on cliffs etc, away from the auctioneer.

Post a log about this and DEVs will take a look.
Personally I have never seen this myself so I have to say as long as I do not see a logfile about this I don't believe in it

 

[Farah]

Post a log about this and DEVs will take a look.
Personally I have never seen this myself so I have to say as long as I do not see a logfile about this I don't believe in it

here you go

btw you should raise the 1mb cap on txt file, I had to delete half of the log.

 

[buzzkip]

Dude, you're running the bot way too long. I'd advise using HBRelog and add two wait time tasks with 2 idles.

Wait 1 = 3/4 minutes (this will be your main bulk of time required to carry out AH tasks)
Wait 2 = randomized between 0 and 5 minutes (this ensures there's no strict pattern of the logged in time that you're working the AH)
Idle 1 = 55 minutes (main/minimum logged out period)
Idle 2 = randomized between 0 and 35 minutes (again, to ensure there's no strict pattern)

Add more to vary your patterns, however once the Idle 2 has been completed, your bot will then log back in. This way, every hour - hour and a half, you're checking the auctions and not staying logged in for 45 odd minutes running the same waypoint loop. That's a sure way to get spotted by bored players and other pesky botters which don't want you working their undercuts.

Plugins are great, but don't rely on them to cover up bad botting practice.

 

[powa]

here you go

btw you should raise the 1mb cap on txt file, I had to delete half of the log.

zip the text file before uploading it

 

[Farah]

Dude, you're running the bot way too long. I'd advise using HBRelog and add two wait time tasks with 2 idles.

Wait 1 = 3/4 minutes (this will be your main bulk of time required to carry out AH tasks)
Wait 2 = randomized between 0 and 5 minutes (this ensures there's no strict pattern of the logged in time that you're working the AH)
Idle 1 = 55 minutes (main/minimum logged out period)
Idle 2 = randomized between 0 and 35 minutes (again, to ensure there's no strict pattern)

Add more to vary your patterns, however once the Idle 2 has been completed, your bot will then log back in. This way, every hour - hour and a half, you're checking the auctions and not staying logged in for 45 odd minutes running the same waypoint loop. That's a sure way to get spotted by bored players and other pesky botters which don't want you working their undercuts.

Plugins are great, but don't rely on them to cover up bad botting practice.

Dude, it's an ah bot, the online time does not trigger any flag. I have been running ah bots for 2 years now, I know this shit.

and btw, I am NOT complaning about getting banned on those accounts. I pay 5? for a battlechest and they last 40 days (30 + 10 mop trial) so it's all good. Of course if they lasted the full 40 days before running out of gametime i'd be happier than having them banned after 3 weeks or something.

I know that there's a way so they don't get banned at all (for example, I happen to run ah bots in Shrine during their mop trial period with movement deactivated through HBToggle - the mailbox is right beside the auctioneer so the bots never have to walk around), they never get banned because when a gm teleports them away they just stay there), and thats why I am asking for this plugin that would pause/stop the bot upon getting teleported instead of just quitting wow.


@Powa: I thought about doing that but you can not upload .rar file or .zip s for that matter.

 

[buzzkip]

I'm not suggesting you don't know what you're doing. I'm suggesting you run the bot for less periods of time. Your characters are not stood next to the mailbox, your characters is looping the same CHECK AUCTION and CHECK MAIL routine for 45 minutes. Don't come at me all defensive when I'm trying to help.

"it's an ah bot", which means you should be extra careful. Online time is obviously not the reason why I just made a suggestion to you, you entirely missed the point. GM's will only get involved with you if you've received reports.

Now why would you receive reports? And who by? Players. And for making a scene. That scene is most likely the 45 minutes of running back and forth between a Mailbox. That routine which can be prevented by taking my beautiful advice instead of acting like your intellectual experience with HB cannot be defeated.

I don't need to know your crazy-cool battlechest method. You just need to acknowledge the real issue here. If you're experiencing bans on a frequent basis to the point where you are actually prepared and waiting for it, I would highly suggest changing your botting method/practice.

Clearly just from that log we can see you're method is extremely repetitive. Here's some tips:

- Run a Guild for your AHBuddy
- Have a 'main' character who owns the guild but doesn't post auctions
- Have a banker character in that guild who posts auctions
- Delete and create a new banker every 2 days (this will prevent other players seeing an obtrusive 'undercutter' (and don't say you're not, look at your length of time running the bot)).
- Repeat

This way your Guild has less chance of being entirely lost to an account ban. This way other players don't see a trend with one character posting a ton of stuff. This way other players don't see some numpty repeating the same movements for nearly an hour.

Also bare in mind, when you say "they never get banned because when a gm teleports them away they just stay there" INCORRECT. Look at the log, your bot cannot create a valid path to return to the specified waypoint, this creates a jerky anti-stuck rotation which disconnects you and closes WoW. Doing nothing isn't very human when you've just been teleported is it? I'd panic if I was playing the game. Anti-stuck routines aren't very human are they? I'd jot that down on my pad if I were a GM.

Accept advice, even if you don't want to use it. Being defensive is a poor quality.