I am working on a script, using an include, and it has really got me stumped. The include is executing correctly from the calling script. The include script is getting the variable I want, in this case "Command [TL". I did some testing, there are no leading or trailing blank spaces in the variable. It seems to be reporting the variable back to the calling script correctly, and when I did a test echo it echo's the variable correctly in the game. But the IF routine I am using to test the variable isn't recognizing it correctly.

I believe that the conditional I am using doesn't like checking against a text string, I believe this is the culprit :



I don't know if TWXProxy no longer likes a text string used in this way or what, and even though It's been a long time since I did much scripting and I'm a bit rusty, I could swear I have been able to use text strings for things like this in past scripts. Maybe I'm wrong? Is it something else? I'm throwing myself on the mercy of the LEET scripter's court on this one, be gentle with me :D

Here's the calling script code, as far as I've gotten with it :



This is the code for the prompt check include :



Here is the relevant screen cap from in the game, shows it seems to be getting the variable right :



So what am I doing wrong/missing here?

Edit : used quotes on the code, so the code wouldn't look like it was spill-over, the inline comments ARE all on one line in the script file.

1

did you do a variable dump to see what your $check variable reads? i'm assuming that it contains some ansi characters since you are using CURRENTANSILINE and are pulling your prompt from BOL to =

if that is the case, that is why your "Command [TL" is not matching $check

You hit the nail on the head Tweety. I was originally going to use this for some other checking too, but since I have no way of knowing what the ANSI characters are between "BOL " and Command, I can't think of how I could do that right now. But I am very tired and I have a debugging headache too so that might be playing a role.

I changed CURRENTANSILINE to CURRENTLINE in the scripts and it worked like a charm. Now I remember why I didn't use CURRENTANSILINE much in the past

Thanks Vid, I am assuming by your reply of 1 that I could use getWord to get the first word of a CURRENTLINE or any other line, which is true. I just remember reading somewhere, the Cabal's secret hideout or twxproxy.com support, that you could use CURRENTANSILINE in your code for spoof checking.

I believe Traitor et al were talking about it in their 'stupid ansi tricks' post but I would have to go look it up to be sure. CURRENTLINE will work for a prompt check in this case though, and getWord will involve less coding. So I may change my code to use getWord instead of getText.

and just a quick note.

if you use echo to display a string that has ansi characters in it, i believe it prints out with all the same colors and affects onto your screen.

if you use clientMessage. I think it sends it out on its own line, but keeps the ansi characters in the string. I may be wrong there, but i'm pretty sure clientMessage does not display the ansi colors. Its been a while since i've used the commands.

Yes if you echo a string with ansi characters, at least in the case of this script, it was displaying it in the helper terminal (I was using SWATH) the same way the game shows it. So what advantages would there be to using clientMessage as opposed to echo? Would it help on spoof checking, or are you just saying that it would show up as regular characters in the helper terminal? I can see how that would be helpful to know it was output from a script, but I'm drawing a blank on other uses for it. Not that I don't see the usefulness of it for that purpose alone of course.

for debugging purposes only. knowing what is in the string. characters and all.

but hmm, i should try it first to make sure that command does not automatically strip out all ansi characters haha...

its been a long time.