Surprise, I've already implemented Trim and point 4 in my original post, they're actually in the beta build Sing posted a month or so ago, but still undocumented. They'll likely change before a final release though.

I'm working on point 2, escaping from a long variable dump. It's mostly done.

In a previous working build, I implemented point 3, being able to break out of a runaway loop, but it had too much of a performance impact so I didn't commit it. It's something that I've wanted for a long time though, I just need to implement it in a way that doesn't impact performance.

speaking of variable-dumps.. Would it be possible to dump variables from a specific script, in the same fashion as killing a script?

Alternatively. the one feature request I believe many would appreciate would be a variable dump to a text file; perhaps in the Logs folder.


Thanks

These are reasonable requests, I'll see how easy they are to implement.

I've completed and committed the code to abort a variable dump.

If there's interest, I can attach these interim builds for people to play with.

I'm interested.

Okay, keep the feature requests coming.

I realize I need to publish a full beta build, but here at least an interim build (just the twxproxy.exe) is attached. So make a copy of your TWX folder, call it something like TWX2.05.70, and overwrite its twxproxy.exe with the unzipped attached file. And you should probably delete any game data too.

The following is not a list of changes since 2.04, but rather since the last interim build.
Commands Added:
Trim $var // remove left and right white space
Truncate $var // truncate a decimal number (round down)
* I'll add the ability to truncate at a specified decimal place later
** Also, in all 2.05 builds, you can do inline commenting, using // as above.

Improvements:
It has the ability to ESC (by pressing ESC) from a long var dump.

Bug Fixes:
Fixed a potential bug when sending really large amounts of data.

Right now its possible to make a client deaf, that is, not receive game update but only what TWX is saying.

I would like to be able to do the opposite, that is, receive only what comes from the game and not see output generated by TWX.

Another way of saying it would be to allow TWX to proxy dirrectly to the game without interfering with ouput.

This would allow for helper to do lots of TWX call without messing the game output.

Am I making any sense?

If its hard to implement I could always setup a second proxy layer using something else than TWX, but I'd rather not

$ = that will toggle deaf mode on/off

Help for option '=':

Deafs clients are telnet terminals that don't receive anything
from the remote server. This option will turn your connected
terminal into a 'deaf' terminal. This is great if you have
a fast-paced script running in the background and you want to
query your database.

You didnt read my post correctly it seems. I know that, I said on the very first line that its possible to do it right now. What I asked is the oposite: don't receive from TWX, but see the remote server.

Hey EP, if you happen to have a little time again and you want more suggestions about additions to TWX Proxy, I thought of one. Don't know how hard it would be to implement but maybe you could give me an idea if it would be fairly easy or a lot of work.

I was thinking it would be nice if TWX could do a count of the lines in a text file and save it as a variable. Would make it easier for setting up static Array's.

If it would be a major undertaking that's cool, a little bit of code in a script and you can do it yourself. So no big deal. Just an idea.

Have you used readToArray?

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Thanks Pro, I have used it, I have found it to be a very handy command in the script arsenal. However, I was working under the mistaken understanding that it only worked in a file where each line only had one 'word' and that it wouldn't store a line with multiple words in an array element.

From a quick test script I see that I was mistaken on that. So I am going to have to play around with the command and learn some additional ways to work with the readToArray command.

Seeing that it can store a line with more than one word in it I am thinking, correct me if I'm wrong, that you could use this to build a static multi-dimension array.

So thanks for pointing out that readToArray is already set up as a static array, if I understand that correctly.

Yes, readtoarray is your friend. Want to know how many lines are in the file "bubbasfile.txt"?

readToArray bubbasfile.txt $array
echo "Line Count: " $array

Done. That was almost like the EASY button in those commercials.

another one of those undocumented features EP? That was like the easy button, you're good man

From script.html in the TWX folder:

Thanks Toyman, I had seen that in the description in scripts.html, so I knew about the variable of the same name as the array being the count of the array. As I said earlier, the reason I didn't use readToArray in some scripts was when I was wanting to get multiple words from a line in a file, and I had mistakenly thought it would only grab the first word from the line not a whole line. And I wasn't sure it was a static array, i like to work with them as they are faster I have heard. A more careful reading of the description would show one that it is a static array though.

Don't know where I got that assumption from, I think probably from one of my many scripting errors when I was working with the array. I probably wrote some code wrong, it only got the first word, and instead of checking it out more or asking about it in the forum, I probably just assumed it didn't grab the whole line when it populated the array.

Good looking out though, if anyone is wondering about that in a search in the future they should run across your post and learn something new or have a question answered. And it did cause me to take another read of the description and figure out that it is a static array.