mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

I haven't confirmed this yet, but it might be invalid data as per JSON,
they didn't escape something. Best to put it through a json validator
(several of those on the web) to check that, and then we'll go from there.

We aren't using a home-made JSON parser but a quality library (
http://lloyd.github.io/yajl/), so JSON parsing issues are unlikely to
happen. Still, it can't be ruled out and would need more detective work to
narrow down the issue.

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1165620

Title:
  GMCP chokes on ANSI

Status in Mudlet the MUD client:
  New

Bug description:
  Mudlet 2.1, Win7 x64

  I don't believe this is a duplicate of #1110243.

  It appears that mudlet fails to capture certain GMCP messages when
  ANSI sequences are embedded. An easy place to test this is on Aardwolf
  MUD. Create a new character, and from the starting room (the "recall"
  location) head 4 south. Note that this room sends gmcp.room.info just
  fine (as will all rooms with the default room name color). Now, step 1
  west. Note that the room name has a different color. Looking at
  gmcp.room.info, you will still see the info from the _previous_ room -
  Mudlet's GMCP has failed to capture the ANSIfied roomname string ( I
  confirmed with folks using other clients that the gmcp data is in fact
  being sent correctly).

  On this particular mud, there is a workaround available by doing a
  sendGMCP("rawcolor on"), and then parsing out the in-game custom color
  codes with a bit of string manipulation. However, others on the mud
  mentioned coming across similar issues on other muds that embed ansi
  sequences.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1165620/+subscriptions