Protocol Negotiation Issues
- Ornir
-
Topic Author
- Offline
- New Member
- Posts: 3
- Thank you received: 0
Thanks!
- Ornir Elunari
Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
What's the quickest way to reproduce this issue? I tried creating a character and roaming around but couldn't get to a place where background colors were used.
Luminari will now show in the app Game Center. it won't show up in listings until you add a description and image.
Please Log in or Create an account to join the conversation.
- Ornir
-
Topic Author
- Offline
- New Member
- Posts: 3
- Thank you received: 0

The wilderness is still in development and there is no easy way to get there from the mud proper.
- Ornir Elunari
Please Log in or Create an account to join the conversation.
- hawgpadre
-
- Offline
- New Member
- Posts: 6
- Thank you received: 0
Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
Luminari is doing <ANSI Foreground Color><ANSI Invert> instead of setting the background color directly.
I wasn't able to reach a wilderness on Wayfar but it looks like it could be the same issue.
Please Log in or Create an account to join the conversation.
- hawgpadre
-
- Offline
- New Member
- Posts: 6
- Thank you received: 0
One other thing I've noticed:
#-5457 from (mudportal websocket proxy) > client mudportal.comclient_version 1.0client_ip 63.233.133.4E[**Vco swampdog ******
This first line sent by the web client is not terminated with a newline, so the first time you try to login (co swampdog *****) the client identifier line is all jumbled up with your login and the login fails.
Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
For the ANSI background map, try setting the background colors without using the invert code (7). Invert doesn't make it clear what you want the foreground color to be. This may have the result you expect on some clients, but not on others.
You can set background colors by sending codes #40-47, as per: en.wikipedia.org/wiki/ANSI_escape_code
The Portal app also supports 256-color codes, including background colors. The wiki link above covers those as well.
Please Log in or Create an account to join the conversation.
- Tijer
-
- Offline
- Senior Member
- Posts: 41
- Thank you received: 0
Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
Tijer wrote: that change has made the 256 colors stop working entirely on my test mud!! And my main mud also!!!
When you're reporting issues, please remember to share the quickest way to reproduce.
Please Log in or Create an account to join the conversation.
- Tijer
-
- Offline
- Senior Member
- Posts: 41
- Thank you received: 0
using the portal app...
Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
Please Log in or Create an account to join the conversation.
- Tijer
-
- Offline
- Senior Member
- Posts: 41
- Thank you received: 0
Please Log in or Create an account to join the conversation.
- Tijer
-
- Offline
- Senior Member
- Posts: 41
- Thank you received: 0
looks as if the actual protocols are not being negotiated by the mudportal plugin, used to work...

Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
Here's what you should be getting as TTYPE on connect:
"mudportal.com", "ANSI-256COLOR", "MTTS 141", <user IP>
The second and the third entry both should declare 256-color support. Let me know if you think the issue is on my end.
Please Log in or Create an account to join the conversation.
- Tijer
-
- Offline
- Senior Member
- Posts: 41
- Thank you received: 0
will point out that the negotiation works on zMUD, cMUD and Mushclient... just hasnt since the first response on this thread by me (if that gives you a little idea as to when the issue started)
if you connect to my mud.. and type finger (on your own character) it should show the following if protocols are supported:
Client: MUSHclient (Version: 4.91).
Protocols: NAWS, TTYPE, 256 Colours, MXP (0.5), MCCP.
Screen Size: 271 characters wide and 60 characters high.
Please Log in or Create an account to join the conversation.
- Tijer
-
- Offline
- Senior Member
- Posts: 41
- Thank you received: 0
never get past password entry screen...
Please Log in or Create an account to join the conversation.
- RahjIII
-
- Offline
- New Member
- Posts: 13
- Thank you received: 0
IAC WILL TELOPT_ECHO,
IAC WILL TELOPT_SGA,
IAC DO TELOPT_TTYPE,
IAC DO TELOPT_NAWS,
IAC DO TELOPT_NEW_ENVIRON,
IAC WILL TELOPT_MSSP,
And all it gets back from the client is:
IAC WILL 201
IAC DO 69
IAC DO 86
(LO doesn't support those protos and they aren't in arpa/telnet.h so I don't have a decode for what they are.)
The Last Outpost
last-outpost.com:23
Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
Also, now it should be sending client info via MSDP as well on connect, including the user IP.
Please Log in or Create an account to join the conversation.
- Tijer
-
- Offline
- Senior Member
- Posts: 41
- Thank you received: 0
Please Log in or Create an account to join the conversation.
- plamzi
-
- Offline
- Administrator
- Posts: 285
- Thank you received: 42
Please Log in or Create an account to join the conversation.