www.ClassicTW.com
https://mail.black-squirrel.com/

Determining Current Prompt
https://mail.black-squirrel.com/viewtopic.php?f=15&t=18338
Page 1 of 4

Author:  LoneStar [ Mon Jan 01, 2007 4:37 am ]
Post subject: 

Does anyone know if sending #145 to redisplay the current prompt has been made an official Global cmd (as mentioned in http://www.eisonline.com/twgs/beta/ Section: TWGS Revision 58 - February 23, 2004 'New: Added experimental global...')?
I've tried it, and it seems to work just fine.
 
Lone

Author:  Singularity [ Mon Jan 01, 2007 5:10 am ]
Post subject: 

Does seem to work in most cases, yes. But they say not to implement them so... heh. I use / or just *, seems to work fine. Benefit to / being that for the same latency you also get stats... mmm.

Author:  ElderProphet [ Mon Jan 01, 2007 5:11 am ]
Post subject: 

Well, incidently, #145 doesn't work through SWATH, but #128 does.

I think it has its uses... though I can't really think of a time I've used it, other than in testing.

Still, I doubt it's going away, so make use of it.

+EP+

Author:  RexxCrow [ Mon Jan 01, 2007 7:22 am ]
Post subject: 

Why even bother using that though? Like Sing stated either / or * is fine and productive, or even #27 if good to keep the screen clean as Billie Jean... well until I get ahold of her newayz!

Author:  the reverend [ Mon Jan 01, 2007 12:15 pm ]
Post subject: 

this #145 feature was added at my request.

TWGS Revision 58 wrote:
New: Added an experimental global to help scripts and helpers verify the active prompt. Using the extended character ascii 145, a script or helper can tell TW to redisplay the active prompt, followed by the same ascii character, #145. The result of issueing a #145 will be two newlines, followed by the prompt, followed by ascii 145 and a backspace. In some cases, there will be additional dynamic information following the ascii 145, so it is not guaranteed that the 145 will be at the end of the prompt line.


if you read it carefully, it says that it will issue a #145 + backspace after the prompt. basically, what this allows you to do, is know the current prompt by waiting for #145 in your script and trapping that line.

if you are using '/' or '@' or '#' to redisplay the current prompt, you get the same effect, but you have to know - to a certain degree - what you are looking for after the /@# display. with #145, all you do is wait for #145 to be repeated back, then grab *that line* - and you are done.

Author:  the reverend [ Mon Jan 01, 2007 12:19 pm ]
Post subject: 

ElderProphet wrote:
Well, incidently, #145 doesn't work through SWATH, but #128 does.

I think it has its uses... though I can't really think of a time I've used it, other than in testing.

Still, I doubt it's going away, so make use of it.

+EP+


this is probably due to some code page translation that swath is doing. you send swath #128 and it gets translated into #145 before going to the twgs. someone could test that theory with a short script in twx. hint hint.

Author:  LoneStar [ Mon Jan 01, 2007 2:08 pm ]
Post subject: 

the reverend wrote:
this #145 feature was added at my request.

if you read it carefully, it says that it will issue a #145 + backspace after the prompt. basically, what this allows you to do, is know the current prompt by waiting for #145 in your script and trapping that line.

if you are using '/' or '@' or '#' to redisplay the current prompt, you get the same effect, but you have to know - to a certain degree - what you are looking for after the /@# display. with #145, all you do is wait for #145 to be repeated back, then grab *that line* - and you are done.

That's awsome. I knew there was a reason fot its implementation; just couldn't put my finger on it. Thanks for the great insight!
 

Author:  the reverend [ Wed Jan 24, 2007 7:28 pm ]
Post subject: 

TWGS Revision 58 wrote:
New: Added an experimental global to help scripts and helpers verify the active prompt. Using the extended character ascii 145, a script or helper can tell TW to redisplay the active prompt, followed by the same ascii character, #145. The result of issueing a #145 will be two newlines, followed by the prompt, followed by ascii 145 and a backspace. In some cases, there will be additional dynamic information following the ascii 145, so it is not guaranteed that the 145 will be at the end of the prompt line.


hmm i finally got around to actually testing this feature - and i can't see the "145 + backspace" in the echo'd prompt. does anyone else have this problem?

Author:  Parrothead [ Wed Jan 24, 2007 8:21 pm ]
Post subject: 

i am using it in my still beta bot to check against an array of available prompts to prevent getting stuck on a trigger/witon/waitfor as well as the usual redirect

Author:  Traitor [ Wed Jan 24, 2007 10:10 pm ]
Post subject: 

Don't send the backspace.

I use it all the time.

Author:  Vulcan [ Wed Jan 24, 2007 11:12 pm ]
Post subject: 

Traitor, what's with the new avatar? Kinda funny tho. laff

Author:  Slim Shady [ Wed Jan 24, 2007 11:24 pm ]
Post subject: 

the reverend wrote:
this #145 feature was added at my request.

TWGS Revision 58 wrote:
New: Added an experimental global to help scripts and helpers verify the active prompt. Using the extended character ascii 145, a script or helper can tell TW to redisplay the active prompt, followed by the same ascii character, #145. The result of issueing a #145 will be two newlines, followed by the prompt, followed by ascii 145 and a backspace. In some cases, there will be additional dynamic information following the ascii 145, so it is not guaranteed that the 145 will be at the end of the prompt line.


if you read it carefully, it says that it will issue a #145 + backspace after the prompt. basically, what this allows you to do, is know the current prompt by waiting for #145 in your script and trapping that line.

if you are using '/' or '@' or '#' to redisplay the current prompt, you get the same effect, but you have to know - to a certain degree - what you are looking for after the /@# display. with #145, all you do is wait for #145 to be repeated back, then grab *that line* - and you are done.


coincidentally, pods were added to the game because i dominated too many people and they wanted an extra chance.

true story.

...

Author:  Singularity [ Wed Jan 24, 2007 11:26 pm ]
Post subject: 

I thought pods were added to the game after you complained to K3 about being dead too often...

Author:  Traitor [ Thu Jan 25, 2007 1:34 am ]
Post subject: 

Vulcan wrote:
Traitor, what's with the new avatar? Kinda funny tho. laff

sorta sums up my feelings about EIS and these forums.

I'm the user...

Author:  RexxCrow [ Thu Jan 25, 2007 1:58 am ]
Post subject: 

lol, I think pods were made to give you a false sense of security... either that or just to make scripting out attack scripts a real challenge.

Page 1 of 4 All times are UTC - 5 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/