Razzue

Well... Used the way they're supposed to be you'll be well fed, or have tons of fun ;) But yes, this analogy works well ;) (Some) People who buy cheats are like drug addicts. They get pissy and emotional when they can't use it xD

This did it. I had to add the "wait:1000" between the path/code on the 2nd and 3rd door, along with a "wait:3000" between the code and running on the next path ( to give it time to actually interact) but it finally works perfectly! thank you for the help/advice! Now is there a way to make this look "prettier" with not as many steps? EVAC.xml

**Edit It worked for the first account, but not on any other. Gave me a error that i quickly closed (should've looked.. oops).. Hasn't given me that error since! However now it doesn't work at all, sometimes it gets stuck trying to pulse the last hot-spot rapidly, other times it just runs to the door and runs away mid "knocking" I've included the quest.xml as i've understood it.. maybe point out my flaw ? :) EVAC.xml

You sir. are my f**king savior. Thank you. I cannot rep you enough for what you've done <3 tried it, works perfect. this might also help with other profiles i'm stuck on !

Oh quit whining, you missed out on what.. 5 days? ( That's how long the red warning was there) so roughly 1.5 euros? FYI program was still usable while the warning was up, if you decided not to use it.. well that's on you.

Huh.. never had problems like that and 3/5 of my bots are druids :x Jensen's suggestion seems like the easiest fix :x

Will try this when i get home tonight. I just use the custom script function yeah? ( Total noob at questing profiles xD sorry)

Thank you for the suggestion Droidz! I tried what you wrote, and sadly the issue still occurs.. It will follow the path i set up, but still refuses to go to that last hot-spot, so it stays "out of range" 2018-03-04_12-08-12.flv *edit* I only used a custom path for the first door, but it still stopped one hot-spot short :x

Hello there community! I'm running into a problem with trying to map the quest [Evacuate the Merchant Square]. The bot runs up to the doors in Gather/InteractWithNpc no problem, but it stops at the base of the steps, which is out of range. The bot will still say its a successful farm even though nothing actually occured. Using InteractWithNpc works the same. Runs up to the door, but stops at the steps.. Iv'e tried Decreasing the range on IWN , not sure if that's possible on Gather.. anyone have a solution to somthing like this?

Run "RemoveFile" to remove wrobot, the rest you can delete normally afterwards

I too have had this issue with : Obsidian Nightwing, Leywoven carpet, long forgotten, sandstone Drake, and the Sky Golem. And occasionally on my druid, but that one is a very rare occurrence. All while using a multitude of personal profiles on the Broken shore (files in private forum)

Well.. they made some off whoever bought that token to sell ;) wrobot more than helps with my purchases.. heh

So maybe it's just pure dumb luck/unluckiness on my part but i wanted to share some thoughts xD Is it just me or does it seem blizz doesn't care about "starter editions" botting? Let me give some backround to this.. Ever since our first detection (this year) I've been Botting HARD on 5 starter accounts. One account was litterally running a profile that ran in a circle between 3 hotspots, just to see how long it would take to get banned ( accounts still active btw). However i tried upgrading 2 accounts to the base edition... And here's where shit goes south. AS SOON as i applied the upgrades, both accounts instantly got the "locked" symbol on bnet and seconds later had a couple emails from blizz. What's your opinion on this whole matter? XD Hope everyone else's endeavours are going better xD!!

You're the best! <3 thanks Droidz

Have been getting this error constantly,every time i click the "create fight class" button, ever since the update today! Have tried completely removing Wrobot and installing multiple times, but sadly that didnt help.. ;( Any help or a fix would be appreciated <3 Thanks :) *** Edit: Also occurs if i try launching through the fightclass editor shortcut :)

well since it's on a TRIAL i FEEL as if some features probably dont work the way they're supposed to...

What do you expect? It's not like blizz states what new obfuscation they push out does. Wrobot is the last of the "big3" ( Honorbuddy, ThenoobBot, and wrobot) that is still currently active. so i'd say Droidz is doing a mighty fine job.

you just admitted to running and using it? It doesn't matter if you used it for 5 minutes or 5 days. Blizzard has been pushing hard on bots. You knew the risk when you bought the bot, sucks but that's life mate. LOL

You know botting is against the ToS , and Droidz warns the ban chance is really high at the moment. Why would you get a refund? XD

Probably shouldn't keep using it for now

i have also encountered an issue like this, I mark black spots in my personal profile, but bot still tries to hit nodes inside the black spots. *edit* it only happens with SOME profiles i should add. i believe bot is intended to still go through black spot, just not interact with anything inside it

Truthfully, it COULD be stupid, dumb luck on my part. I've always fared on the better side of banwaves. I'm just making a observation from my experience..

Hmm, maybe I'll try to make a druid fight class and see if I can replicate this problem

Isn't humor supposed to be funny? Came across as quite rude to me as well >.>

Thank you for the response Droidz, but neither of those accomplish quite what I'm looking for.. I was more looking for a way to reduce the amount of spots produced while using the profile creation tool because going back and deleting spots this way is a large chunk of time And doing it this way ( IE : flying a little, switch windows, record on, then off, then fly a bit again etc..) is a large pain if you mess up a record.. I personally like using my second method because it gives me more control on WHERE my spots are generated.. but it would be kinda neat if you used the " ~ " as a hotkey to turn on/off the "Record path" button