"Idle" the bot or break from grind after a certain point
Posted: Sun Dec 10, 2017 6:20 am
First off love the bot. I had the bot farm several thousand ash for this past week. Shame I didn't figure the configuration a lot sooner as SSG will be killing ash farming coming 12/11/17 raid update.
So I've decided to refocus my botting efforts into grinding gold.
Currently, I have a nice little setup where I bot parts of an instance and use AHK to convert ash, vendor and repair. Which seems to fly complete under SSG's radar because I never complete and I never exceed max instances (hour or day) and I have log out durations scripted in as well.
Seeing as I have been caught landscape farming before I'm very wary of it and wish to remain using instances.
However, more complex instances require more grind spots to navigate it as oppose to the single grind location I use to navigate my current instance of choice. (Bot has to go over a bridge and then loop back underneath it later on)
In my current setup, the bot has no where to go after reaching it's single grind location and it will stay "idle" and not go AFK or move from location and then the time looped AHK script can perform the rinse and repeat.
What I'm looking to get out of my next iteration is to have the bot go into this "idle mode" after the 20th grind spot and wait for my time looped AHK script to take over. (Random Grind Order Deactivated)
Is there anyway to not have the bot proceed to the "next" grind spot? (20 back to 1).
I'm thinking something like adding a "21st" grind node in the data file that would "idle" it for me.
Any ideas, suggestions, or different approaches would be greatly appreciated.
So I've decided to refocus my botting efforts into grinding gold.
Currently, I have a nice little setup where I bot parts of an instance and use AHK to convert ash, vendor and repair. Which seems to fly complete under SSG's radar because I never complete and I never exceed max instances (hour or day) and I have log out durations scripted in as well.
Seeing as I have been caught landscape farming before I'm very wary of it and wish to remain using instances.
However, more complex instances require more grind spots to navigate it as oppose to the single grind location I use to navigate my current instance of choice. (Bot has to go over a bridge and then loop back underneath it later on)
In my current setup, the bot has no where to go after reaching it's single grind location and it will stay "idle" and not go AFK or move from location and then the time looped AHK script can perform the rinse and repeat.
What I'm looking to get out of my next iteration is to have the bot go into this "idle mode" after the 20th grind spot and wait for my time looped AHK script to take over. (Random Grind Order Deactivated)
Is there anyway to not have the bot proceed to the "next" grind spot? (20 back to 1).
I'm thinking something like adding a "21st" grind node in the data file that would "idle" it for me.
Any ideas, suggestions, or different approaches would be greatly appreciated.