Kiashien Newbie
Joined: 13 Apr 2003 Posts: 1 Location: USA
|
Posted: Sun Apr 13, 2003 5:38 pm
#echo and vt102 |
I'm having a few problems. I found a new mud, and they use VT102. Now, although this gives -them- lots of cool features, it totally screws me up.
1) The only triggers I've dared to put in are #CW/#color triggers.
The major problem is that even -these- triggers are causing trigger loops, and I have no clue how. I can only guess that it's due to VT102 in some way. I've done extensive scripting before, and checked the triggers back from one end to the other and can not find the issue.
2) I can't seem to trigger off of the VT102 prompt (or highlight.. or cut/paste...)
3) It won't echo commands normally, and this is a big problem as I tend to use #say and #echo alot for multiple windows. It has a small line under the prompt, which it will echo into, but the moment a line comes back from the MUD, it dissapears. Its driving me nuts.
I realize that disabling VT102 might work, except that if I do that, the MUD has no other way for me to get HP/Mana/Ect, which are rather essential to know. If #3 is fixed, I can deal with 1 and 2....
I'm running 6.40. A friend is running 4.62, and has none of these problems, so it seems to be version dependant. I'd prefer -not- to run a beta, as I don't use the automapper at all and it would give no real benefit as of the moment to risk it, when I don't even know if it'd fix it... Anywho, thanks to anyone who has a solution. |
|