Quote:
Originally Posted by Timemonkey
Not sure if it's just me, something I did or didn't do...
The bot was selecting an ability (I had 3 checked) and if another ability came up, it would try to select it right away before even finishing a normal synth. It would also randomly select "careful" when I had no careful checked but the bot said it was selecting normal. @.@
I removed 2 abilities and then it would randomly wait while claiming to be doing standard.
Is there a way to set a delay? Right now it's selecting standard and wait almost as fast as it loads it but it waits till about 1/2 down the bar when selecting finish on the synth.
Nice bot!
|
When wrong abilities are selected I need to see the debug log.
Some jobs have problems with certain ability IDs because the standard/rapid/careful IDs overlap the IDs of certain abilities, which causes undesirable behavior. To recognize these jobs I need to see the log and make the corrections for the specific jobs these errors occur on.
The bot will operate as fast as possible on synths. Since the timing of the bot is based from memory reads it would not be of any help to allow the user to select their own timings. I'll see if I can speed up the bot for finishes, but I am not sure if I can speed that section up.
Quote:
Originally Posted by sl295
i cant get the guild support to wotk for me really either doesnt get the right support or when it does and i go to craft in the debug shows something like -5168 minutes til support wears
|
I have corrected an error with the timer for guild support (mainly the timer is not initialized until the second synth, small oversight on my part. When I release the newest version it will initialize properly. I also slowed the guild support selections down because some people noticed it was tripping itself up getting guild support.
Are you initializing the support NPC by highlighting him in game, then hitting the support button? This initializes the NPC ID, and on the first synth the bot will exit the crafting menu, reselect support, and timer will actually initialize. (Note: this is only true for the old and current versions, this will not occur in any new versions)
Quote:
Originally Posted by Mingatsu
Bot never uses 'wait' option for me, anything I should do?
|
post a debug log from the bot, it will let me know if wait is given the wrong ID.
Also, if you have 5+ abilities available to the bot there is a good chance it wont wait because the bot gives priorities to abilities over wait.
You may notice in the bot that 3-5 times it will say scanning for wait/abilities, and that each time it will select an ability. In this case the bot is using wait, but because there are so many abilities it never actually gets to use wait.
The bot used to wait frequently, but I changed it to use abilities if they were up because sometimes the abilities would only come up for that one time the bot was going to wait.