Subject: Echoing the echo-issue
Author: Massaria
Posted: 02/23/2006 06:18AM

---

I know we've covered this before, but I believe the solution you provided is no longer valid due to the re-contruction of the engine in later versions.
I'm still on 2.7.0

The problem is with the commands being echoed back at me, like:
>say hi
say hi
You say, "hi".

How, once again, do I get rid of that?

Thanks
Tobias

---

reply

Subject: Echoing the echo-issue
Author: Tyche
Posted: 02/23/2006 10:36AM

---

Massaria wrote:
>
> I know we've covered this before, but I believe the solution you provided is no longer valid due to the re-contruction of the engine in later versions.
> I'm still on 2.7.0
>
> The problem is with the commands being echoed back at me, like:
> >say hi
> say hi
> You say, "hi".
>
> How, once again, do I get rid of that?
>

Yes configuration of the network moved to the config.yaml file.
Which now would be commenting out :echo under server_negotiation.

server_negotiation:
  - :sga
#  - :echo
  - :naws
  - :ttype
  - :zmp

The thing is I so far can only duplicate the behavior you decribe in Mushclient when NOT attempting to negotiate echo. Which while echo negotiation is broken in Mushclient, it produces the desired behavior of not echoing commands.

I started a page ClientData. I'd appreciate any data and comments on clients using the default configuration (:echo on) and with logger 'DEBUG' in TelnetFilter? set on. I have mostly tested against Telnet clients and only a handful of mud clients.

The trick here is to come up with a configuration and recognition code that handles most clients that will log into your mud.

--
Tyche

Late Addendum:
I was able to duplicate your problem with the Mudmagic 1.8 client. I sent Kyndig a list of issues and comments about his ECHO support and some other things.

---

reply