Bug? Sending invalid characters on connection

Start
Prev
1
Next
End

Zeno
Topic Author
Offline
Junior Member

01 Nov 2013 01:16 #1 by Zeno

Bug? Sending invalid characters on connection was created by Zeno

When you first connect to my MUD on here, enter any name it'll say invalid character name. Seems to be related to the client sending some extra characters?

This doesn't happen on any MUD clients like MUSHclient.

Screenshot: i.imgur.com/Ce8VDGP.jpg

Please Log in or Create an account to join the conversation.

plamzi
Offline
Administrator

01 Nov 2013 02:45 #2 by plamzi

Replied by plamzi on topic Bug? Sending invalid characters on connection

This is fixed--thanks for reporting.

Please Log in or Create an account to join the conversation.

Zeno
Topic Author
Offline
Junior Member

01 Nov 2013 02:58 #3 by Zeno

Replied by Zeno on topic Bug? Sending invalid characters on connection

Hmm. It looks like the 2nd string sent was fixed, but I'm still having an issue with the first string sent: i.imgur.com/C5UEe7l.jpg

Please Log in or Create an account to join the conversation.

plamzi
Offline
Administrator

01 Nov 2013 14:43 #4 by plamzi

Replied by plamzi on topic Bug? Sending invalid characters on connection

Try now.

Please Log in or Create an account to join the conversation.

Viriato
Offline
New Member

07 Nov 2013 22:42 #5 by Viriato

Replied by Viriato on topic Bug? Sending invalid characters on connection

Had same problems earlier but now are fixed. Wanted to say something earlier because figured out what the problem was: mudportal client sends GMCP and TTYPE negotiations at startup (some weeks ago also sent MXP), so servers that do not "consume" those chars will keep them waiting on stream. Due to this, when player sends his first input (a bunch of characters ending with some EOL char) server will read the non negotiated characters concatenated with the true first input. With the stream flushed, further inputs work as supposed.

The other problem that stills a mistery for me is MXP tags defined in entities not being recognized by MUD portal yet...

Please Log in or Create an account to join the conversation.

plamzi
Offline
Administrator

08 Nov 2013 05:49 - 08 Nov 2013 05:50 #6 by plamzi

Replied by plamzi on topic Bug? Sending invalid characters on connection

Viriato wrote: Had same problems earlier but now are fixed. Wanted to say something earlier because figured out what the problem was: mudportal client sends GMCP and TTYPE negotiations at startup (some weeks ago also sent MXP), so servers that do not "consume" those chars will keep them waiting on stream.

Gradually sorting out these issues. Should be almost there.

Viriato wrote: The other problem that stills a mistery for me is MXP tags defined in entities not being recognized by MUD portal yet...

Some of them should work (the ones with empty FLAG attribute). For example, <buy>bread</buy> should send "buy bread" on click.

How is this supposed to be handled: <!ELEMENT RExits FLAG="RoomExit">

I improved the handling of the MXP FONT tag.

Last edit: 08 Nov 2013 05:50 by plamzi.

Please Log in or Create an account to join the conversation.

Zeno
Topic Author
Offline
Junior Member

08 Nov 2013 13:34 #7 by Zeno

Replied by Zeno on topic Bug? Sending invalid characters on connection

I'm still getting this issue:

Zeno wrote: Hmm. It looks like the 2nd string sent was fixed, but I'm still having an issue with the first string sent: i.imgur.com/C5UEe7l.jpg

Please Log in or Create an account to join the conversation.

plamzi
Offline
Administrator

08 Nov 2013 17:35 #8 by plamzi

Replied by plamzi on topic Bug? Sending invalid characters on connection

This is sorted out now, with some help from KaVir @ mudbytes.

Please Log in or Create an account to join the conversation.

Viriato
Offline
New Member

09 Nov 2013 02:32 #9 by Viriato

Replied by Viriato on topic Bug? Sending invalid characters on connection

From MXP specs by Zuggsoft:

Tag Properties

MUD Clients can define properties tags to be used by the server in !ELEMENT definitions. The syntax is FLAG='value'. The following special flags are defined in zMUD:

RoomName
The text for the element is parsed by the automapper as the name of a room.
RoomDesc
The text for the element is parsed by the automapper as the description of a room.
RoomExit
The text for the element is parsed by the automapper as exits for the room
RoomNum
The text for the element is parsed by the automapper as a room number
Prompt
The text for the element is parsed by as a MUD Prompt
Set
The text for the element is stored into the named local variable within the client. For example:
<!ELEMENT Hp FLAG="Set hp">
<Hp>100</Hp>
would set the @hp variable in the user's session to 100.

So some of those elements are ok to be ignored by MudPortal. The ones useful but not working are like those (at least for me):

<!ELEMENT Ex '<SEND "&text;|look &text;" EXPIRE="ime">

I guess you took the "bread" example from the specs, so some lines below there's the following example too:

<!EL Itm '<send "buy &text;">'>
<Itm>bread</Itm>
<Itm>water</Itm>

I checked that using "<send>" directly it works as supposed, but above "shortcuts" no. Can mudportal be breaking setup entities when finds one of those elements with FLAG attributes?

Please Log in or Create an account to join the conversation.

Start
Prev
1
Next
End