I have a few aliases that set some mushclient variables that I use in my scripts and in version 3.32, the alias would call a routine and simply set the variable without sending anything to the mud. I just upgraded to version 3.34 and when I used the same alias, it still called the routine and performed as expected, but then a newline was also sent to the mud... even though that particular routine sends nothing. Is there a way I can disable this newline being sent when I don't want it to be? Thanks.
New line being sent to mud via aliases
Posted by Sleeve on Mon 24 Mar 2003 07:17 AM — 8 posts, 29,946 views.
I have the same problem with 3.34 actually. Didn't realize what it was exactly but now I think that script calls from aliases are indeed the source of the problem. I've tried a few aliases that don't call any script procedures and those work as usual, but aliases which do rely on a script (such as targetting for example) do their job and then send the newline. And it doesn't depend on whether the script sends anything to the world or not, the newline is sent in either case.
I am also experiencing this bug. To be clear, it's not simply a blank line that is created, but rather a "return" character is sent to the mud.
Ach! It seems like the code to set a variable from an alias has had an undesired side-effect. Sorry. Will look at it.
Fixed in 3.35.
I just tried this out in 3.35 and still have the same problem. Just to make sure that my plugin isn't doing anything really wierd, I tried this out with the MudDatabase plugin as well. For example, using the MudDatabase plugin, if I type "addmud test test 4000 description" it will send a newline to the mud after processing the addmud alias.
Yes, I see what you mean. I did say "fixed" didn't I? What I meant was, "almost fixed". ;)
I thought I had it nice and simple, but it seems it is too simple, and this case slips through and sends a blank line.
For a start, you can work around it. Set the alias to "send to speedwalk". An empty speedwalk sends nothing, not even one line. I just tested that.
In version 3.36 I have tightened the code up a bit. Now the "send to" code does absolutely nothing if the "send" text is empty. That fixes it. You can still send a blank line to the MUD if you actually type it in (or have an alias with a non-empty send box).
I thought I had it nice and simple, but it seems it is too simple, and this case slips through and sends a blank line.
For a start, you can work around it. Set the alias to "send to speedwalk". An empty speedwalk sends nothing, not even one line. I just tested that.
In version 3.36 I have tightened the code up a bit. Now the "send to" code does absolutely nothing if the "send" text is empty. That fixes it. You can still send a blank line to the MUD if you actually type it in (or have an alias with a non-empty send box).
Thanks for the workaround and the information about 3.36 Nick. :) It's not really a big deal, it's just that I have a lot of aliases that send nothing to the mud and noticed it happening again.