Thanks for the feedback. I want to be sensitive to this. Would you mind testing it for me? Send #255 #241 on the shield prompt and tell me what happens.

i'm going to modify my design so that the keepalive timer only fires after user activity has gone quiet for N seconds - as opposed to every N seconds regardless of activity.

settextouttrigger one :_one #27

is completely different than

send #27

Which is why he talked about a keepalive. He's got another
program he's working on, and he wants it to auto keepalive.
Thus testing various send to make sure they actually keep
alive.

The problem? Anything he sends can get caught up by other
layers. Like if his program is running on top of TWXproxy, it
might catch whatever he sends out and screw stuff up.
It'd be easy to fix with a small script, but that requires ppl
to do more than he wants.

Thus he wants commands that do the keepalive, but don't
get trapped up by other layers, and are invisible to the user.

btw i also was hoping i could do in-game pings using telnet AYT command, but twgs does not respond to AYT.

sing confirmed that sending #255 #241 doesn't have unwanted side effects at the shield prompt. yay!