Autoit bot(Craft/Fish) - Simple bot

Hi,

First of all, thank you for this bot =)
But i have one suggestion, can you build in a "Stop" Button for Fish and Crafting bot, i always have to kill the App to shut it down.

Thx in Advance

End key on keyboard is stop. works well for me. then hit end again to unstop. after you unstop, click fish again.

Thank you for your Tip, i try it out today when i get home :)

Anyone tried dualboxing so far? Does it work to have one window fish and the other does crafting?

Regards

Quote:

Originally Posted by Aionimus Thank you for your Tip, i try it out today when i get home :) Anyone tried dualboxing so far? Does it work to have one window fish and the other does crafting? Regards

The only way it would work with duel boxing is to change the window name of FF XIV and match the name within the bot.

Cant the bot simply record the instance of it instead (PID in windows) of the current winhandle it uses (for dualbox support) this way you dont need to fiddle with anything other then make sure you record resolution and make sure you have the right window up atm when setting it.

atm if you use the fisher, it will just try use it actions on the ffxiv with last focus on regardless of what you recorded resolution of.

Dual-boxing is absolutely possible without changing any window names.

Lucid care to tell me how? beacuse if I active one window, and then open next (2screens 1 on each) it will just try to use the actions on the one I open next.

The bot needs to be written for it and I am not sure AutoIt supports it (though I suspect it does). The programming considerations are similar to that which go into writing threaded applications but at the process level instead of the thread level.

I don't think autoit can multitask to duel box. You would need to open the program X amount of time equal to the number of windows you are running. You would then have to make sure all at least the left top part of the screen is visible for pixels. The downside to overlapping windows is that you cannot run bait changer.

With that in mind, I would also have to add a function to change the window name of each FF window, then add a input for the user to type the name of the window they want to run the bot on. Something along those lines.

It would not be to difficult to add multibox support for Shadow 13ot.

Quote:

Originally Posted by 13ouncer I don't think autoit can multitask to duel box

It can.

Quote:

Originally Posted by 13ouncer You would need to open the program X amount of time equal to the number of windows you are running.

That is one option, but not necessarily.

Quote:

Originally Posted by 13ouncer You would then have to make sure all at least the left top part of the screen is visible for pixels.

Sorry, this is not correct. You don't even *need* to necessarily read pixels at all.

Quote:

Originally Posted by 13ouncer The downside to overlapping windows is that you cannot run bait changer.

Again, this may be true for the way your bot works but it is not necessarily true of all bots (even those written in AutoIt)

Quote:

Originally Posted by 13ouncer With that in mind, I would also have to add a function to change the window name of each FF window

This would be detectable and potentially dangerous

I am talking about my bot specifically.

You would need to learn more about the Windows API and make several changes, I can't just say "add this line of code"

5.4h working great.
aside from the shift/cap bug so far i haven't ran into any other issues if i leave the bot untouched. though if i am surfing, typing emails or something on a second screen, the bot sometimes stops. Not exactly sure of the reason and it happens without a specific set of conditions.

in my experience, the crafting bot always stops when u hqéd an Item.
it seems that the bot trying to go to a "location" after hit finish button,
but while ur chara is moving up his hand in the air (Hqíng) it delayed and bot cannot find craft board yet.
my guess, just change the openwindow to like 5000 to fix the issue

Good chance it is because the delay after the enter/finish keypress is too short. I think the HQ animations take an extra half second or so.