Guu
New Member
Posts: 7
|
Post by Guu on Oct 11, 2004 1:59:31 GMT -5
As posted above, what is the pros/cons of using different combination of these handy programs?
|
|
|
|
Post by TinyTerror on Oct 11, 2004 9:35:48 GMT -5
AC Tools and AutoIT are similar in many ways. AutoIT offers a syntax closer to that of C++ and Java, where AC Tools is different. You can use either one to do pretty much the same thing, but I would rather use AutoIT. FFACT is aparently built off of ACTools, and is designed primarily to be used in AC Tools macros. FFACT provides a debug window that contains all of its data in text form for people working in AutoIT. The problem with this is that getting the data from the debug window into a usable form in AutoIT is a little bit of a problem. I have written a script that will do this really quickly and easily. The current problem is that FFACT appears to be down at the moment. Hopefully it will be back in a working state soon.
If you are looking for a language that will be a good gateway into using other languages like C++ or Java, use AutoIT. AC Tools is popular, but i'm not a big fan of the language.
|
|
Guu
New Member
Posts: 7
|
Post by Guu on Oct 11, 2004 16:39:42 GMT -5
yah i'm a java-based consultant myself. so i guess i should stick with autoit. aeries' bot with ffact and actool does not depend on pixel and is more usuable it seems. perhaps once i get familiar with how the pixel works things would be different  |
|
|
|
Post by TinyTerror on Oct 11, 2004 16:48:41 GMT -5
I dont really like PixelGetColor. While it was once the only way of doing things, there are better ways around now like FFACT. Really the only use for looking at pixels is to check target and text data, things ffact is very good at doing. Pixel ops are also really slow and shouldnt be used in thight loops. If you can, I recomend avoiding pixel checking. None of this advice is valid unless FFACT is working, and currently it is not.
|
|
|
|
Post by Izlude on Jan 23, 2005 22:02:09 GMT -5
can you please explain how ffact works? and how i use it to help write a script
|
|
|
|
Post by TinyTerror on Jan 24, 2005 8:40:53 GMT -5
FFACT works by reading information directly from the game's memory. This gets you stuff like HP, MP, position, status, target name, and a whole lot more. Currently, FFACT is only truely supported for AC Tools. I wrote a script that would read debug info out of the FFACT window, but its a bit out of date and no longer works.
|
|
|
|
Post by TinyTerror on Jan 24, 2005 8:43:35 GMT -5
If anyone wants to play with the FFACT script, they can. Its under the FFXI_Helper subforum. The code is pretty advanced for autoIT, and will take a strong understanding to get anywhere. I will not assist you in this because of the complexity of the code. Its not that I don't want to help, I just don't have the time to deal with 100 code noobs PM'ing me about how to deal with arrays and parsers.
|
|
|
|
Post by Izlude on Jan 24, 2005 12:22:51 GMT -5
ok so how could i use autoIt and ffact all together to make a killer script?
|
|
|
|
Post by TinyTerror on Jan 25, 2005 8:36:51 GMT -5
To use FFACT with autoIT, you need a helper script that parses some info from the FFACT debug screen. Duke said he would post an updated version of FFXI helper soon. This script should let you get info from FFACT into your script. Unfortunately FFXI helper is a little bit complicated, so read the FFXI helper forum before trying to mess with it.
|
|
|
|
Post by Duke Newrise on Jan 25, 2005 17:07:56 GMT -5
If anyone wants to play with the FFACT script, they can. Its under the FFXI_Helper subforum. The code is pretty advanced for autoIT, and will take a strong understanding to get anywhere. I will not assist you in this because of the complexity of the code. Its not that I don't want to help, I just don't have the time to deal with 100 code noobs PM'ing me about how to deal with arrays and parsers. I'm not only fixing it I'm making it better |
|
|
|
Post by TinyTerror on Jan 25, 2005 19:13:12 GMT -5
Looks good duke!
|
|
Heffy
Junior Member
Posts: 62
|
Post by Heffy on Jan 26, 2005 2:59:06 GMT -5
I'm not only fixing it I'm making it better Really...really...really...slowly. |
|
