 |
| ReedN |
Posted: Sat Mar 07, 2009 12:19 am
[3.04] Responses from MUD are displayed on the prompt line |
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
 Posted: Mon Mar 09, 2009 11:39 pm
|
| Zugg wrote: |
ReedN, that still isn't enough information. Why don't you just post the XML for this? You still haven't told me if your function is getting called by a normal trigger, a prompt trigger, an ATCP trigger, a Oninput trigger, a macro, an alias, or anything else? I can't read your mind. The timing of this is crucial...I need to be able to replicate *exactly* when your "gut guard" is sent to the MUD.
|
Apologies for the lack of information. One never knows exactly how much information will eventually be needed to track down a bug. I was attempting to summarize what you had asked for in as succinct a space as possible in order to maximize your efficiency in not needing to wade through gobs of my code to find what you wanted. In this case my best intents hindered your efforts, so sorry it took you extra time.
Edit: In reality it really surprised me when you said you were having difficulty replicating this. When I fired up the new version it took me about 2 seconds after connecting to the Mud to immediately see that something was wrong and about 5 minutes to capture the appropriate text in the debugger. I guess it just goes to show you never know how complicated something will turn out to be.
| Zugg wrote: |
Also, this is yet another case where you should be using #SEND instead of #EXEC. Unless "gut" is some sort of alias you want to "execute", then you should be doing:
|
Noted. Yet another case of old Zmud code hanging around that hasn't been looked at closely.
| Zugg wrote: |
| Edited: Actually, it shows the error even without the #WAIT. The key was to create a trigger that interrupts in the middle of the text input stream. |
Superb! I'm glad you found it and that my theory from a previous post about it interrupting the text input was somewhat on mark. Thanks for spending the time to track this down. |
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Thu Mar 12, 2009 12:53 am
|
Confirmed fixed. Thanks!
|
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Fri Mar 13, 2009 5:23 am
|
| Zugg wrote: |
Also, this is yet another case where you should be using #SEND instead of #EXEC. Unless "gut" is some sort of alias you want to "execute", then you should be doing:
#SEND $attack @target
Use EXEC when you want to "execute" a command (which causes it to get parsed, compiled, and executed as a script). Use #SEND when you just want to send commands back to the MUD. But that shouldn't have any effect on this particular bug. |
Your explanation of the differences between #send and #exec was very helpful. Something to that effect should be added to the help files.
| Quote: |
EXECUTE
Syntax: #EXE {commands}
Executes the specified command. Since the command can contain variables which are expanded, this command can be very powerful.
Note: Use this command at your own risk!
If you use this in a trigger, you open yourself up to abuse from other players that will try to set off your triggers themselves.
EXEC example
#TRIGGER {^Zugg tells you '(*)'} {#EXEC %1}
Wow, what a trigger! Whenever Zugg tells you to do something, you will do it. Note the importance of using the ^ character to anchor the pattern to the beginning of the line. Without this precaution, somebody could say 'Aurora tells you 'Zugg tells you 'drop all'' which would cause you to inadvertently drop everything you are carrying!
|
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
