AutoTerror Question

[jinxdojo]

I know you technically aren't supporting AutoTerror anymore, but I've written most of this script already in AutoIT and now simply wish to adapt it slightly to make use of a few pieces of data from FFACT.

There used to be a list of AutoTerror functions in a section somewhere, but it's now lost deep within the archive. I'm hoping that you can inform me of how to access item data within AutoTerror. Specifically, this data from the FFACT Debug window:

Name: Ginger Cookie
Selected: 3
Max: 12
ItemCnt: 1
ItemCntAvail: 49

On the FFACT template, some functions are available, including ffact_ItemInfoItemName, but I have tried placing those in a similar format and it does not seem to retreive the data. Thank you very much for any assistance,

Jinx

[TinyTerror]

Not all info from ffact was supported in Autoterror. I just didn't have time to add it all. Iteminfo was one of the things that never made it. What you can do is use the FFACT debug text mode, and getwindowtext in autoit to grab the info from FFACT. From there, you search the string until you get to the stuff you want, and you should be good to go. Also, I checked the archive for the autoterror comamnd list, and it looks like it was lost when I reorganized the forum. You should be able to do what you want to do with getwindowtext and FFACT though. If not, you can always wait for lunar. It already does a hell of a lot more than autoterror ever did. I want to release it asap, but its not quite done yet.

[jinxdojo]

Heh. Boo... Tiny how could you leave out functions? Though it seems like it would have been simple, I guess since I don't know to acheive data from FFACT, I shouldn't be complaining as it might have been quite difficult. Anyway, your solution is quite viable. While not ideal, it should suffice. Thank you very much.

Yeah, I looked for the post but was unable to find it. Believe it or not, I try not to waste your time.

I'm looking forward to Lunar, but at the same time I'm somewhat angry that virtually all my scripts in the past are going to be rendered non-working or obsolete. For example, I once created a great ACTool script that would reference 4 text files: UserDB / FlagDB / CommandDB / ResponseDB, allowing the use of a dynamic set of input commands via /tell and a dynamic output (including limited output taken from the incoming /tell). Some of my close friends loved this as an idea since it would allow them to remotely control me: more specifically for teleports, for which it was designed originally. Unfortunately, it never really got to be used, primarily because of an awful error in AC Tool's handling of "x[y]" where x and y are any string. Perhaps it was my inability, but the method I used continually produced an error whenever text was found in that format, which halted the script. Arguably, I should be discussing this in their forums, but I never got around to it. Anyway, the point is that this script was rendered useless by a failure in the script engine, and worse: the script engine is not updated, so there it sits.

I understand not updating AutoTerror to attempt to make use of the DLL again (although, for all I know that might have been easier). I do think it would have been nice to keep the engine up though: including its forums. Of course, it would also be fantastic if you could add those few functions as well (despite the workaround) if it doesn't take much time: simply so the hordes of scripts from the past don't require a complete re-write to gain their full potential or even usage.

Of course, I'll be looking forward to Lunar, and I hope you can tune that up as fast as you're able. I'm sure I'll eventually hop on the Lunar bandwagon as well; it's just, for now, I'd like to see AutoTerror come to a final and successful close, so that these scripts don't sit here uselessly. My apologies for the long post; I have that tendency. Thank you for your time, and thanks again for the workaround.

[TinyTerror]

Trust me when I say autoterror was a real mess. I stopped maintaining it because adding new features was a fucking nightmare. Even if I did keep working on it, there are alot of things that just couldn't be done. Not worth the time in my mind. I know alot of people still used it when I discontinued autoterror, but I think it will be better in the end. Lunar is shaping up to be something really special. I was looking at code just today that would allow a user to hook up a second usb keyboard up and use it as a macro pad. Each key on the second KB could be scripted. Want access to 100+ macros without switching macro blocks? No problem. Want those macros to be able to be hundreds of lines long with conditional logic and access to extensive game data? No problem. This is exactly the kind of thing that would not be possible in autoterror. So as much as I know it would be useful to some people, I'm not going to spend any more time on autoterror. If there wasnt any other way to get game data into autoit scripts, I would consider another update, but the getwindowtext thing should be more than enough to get the job done.

[jinxdojo]

Disappointed, but understood. Thank you.