Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Bug reports
➜ Odd characters showing up in output screen
Odd characters showing up in output screen
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
Posted by
| Krenath
USA (76 posts) Bio
|
Date
| Sat 22 Feb 2003 05:51 PM (UTC) Amended on Sat 22 Feb 2003 05:53 PM (UTC) by Krenath
|
Message
| Periodically, I see odd characters in the output screen replacing the text that should have been there. Fairly often, it happens when I type something that's sent to the world.
Nobody else sees the occ characters but be, so it's in what gets displayed on my screen, not what's sent to or from the MUSH.
Most often, the characters are 'http' but occasionally are high ascii characters. So far, all occurrances have been four characters long.
Most recent example:
sent to world: my cablemodem
received: m[ÁpÉblemodem |
- Krenath from
bDv TrekMUSH
ATS TrekMUSH
TNG TrekMUSE
TOS TrekMUSE | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #1 on Sun 23 Feb 2003 12:40 AM (UTC) |
Message
|
Quote:
Nobody else sees the occ characters but be
Seems to be happening on the forum as well! :)
Strange, is this happening to anyone else? Sounds like a MUD outputting problem, or transmission error. Try doing a packet debug if it happens often enough that you can reproduce it inside 5 minutes. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
Posted by
| Krenath
USA (76 posts) Bio
|
Date
| Reply #2 on Mon 24 Feb 2003 03:34 AM (UTC) Amended on Mon 24 Feb 2003 03:36 AM (UTC) by Krenath
|
Message
| Here's a packet where the problem showed up.
The name of the player speaking is supposed to be "Cerekk" but four characters in the middle of his name were changed to garbage.
Incoming packet: 3995 (78 bytes)
.[36mC....k says 1b 5b 33 36 6d 43 00 00 ac 13 6b 20 73 61 79 73
, ".[1;37mheh. o 2c 20 22 1b 5b 31 3b 33 37 6d 68 65 68 2e 20 6f
ne setr, drop 20 6e 65 20 73 65 74 72 2c 20 64 72 6f 70 20 32 30
0 function calls 30 20 66 75 6e 63 74 69 6f 6e 20 63 61 6c 6c 73
.[0m.[36m".[0m 1b 5b 30 6d 1b 5b 33 36 6d 22 1b 5b 30 6d
|
- Krenath from
bDv TrekMUSH
ATS TrekMUSH
TNG TrekMUSE
TOS TrekMUSE | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #3 on Mon 24 Feb 2003 04:44 AM (UTC) |
Message
| The packet debug is written out very early in MUSHclient's packet processing (right after decompression, if applicable) so if the junk is there it is very likely it arrived like that. I suggest the server has a bug where it is corrupting its output. Try a different client. I doubt MUSHclient is doing it. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #4 on Thu 01 May 2003 04:04 AM (UTC) |
Message
| A few versions back an obscure bug was fixed that might be related to this. A buffer was being shared between worlds, that might have accounted for this behaviour. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
14,702 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
top