Yes, it's an accurate reflection, you copy/paste it as-is. It is indeed something that gets split up into separate commands, that's why command separator being the default is important.
I don't think messing with the command separator is the fix here, the command separator doing it's job is not the issue. The issue is either Mudlet or the game 'hang' on such input provided! -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1674601 Title: Mudlet or game output hangs with crafted input Status in Mudlet: Confirmed Bug description: Steps to reproduce: * ensure your command separator is set to ; * connect to an IRE game like Lusternia.com and log in * do: lua display([1;33;44m(Polaris): You say, "Test."[0;37m) What happens: any input you enter is not reflected by the game. Mudlet still sends the input (confirmed by Wireshark) and Mudlet still receives output from the game (confirmed with ambient effects still showing). It makes it really hard to tell if it's Mudlet or the MUD with the issue since Mudlet is still sending and receiving data as far as I see. Reported by Pharanyx on Discord. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1674601/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : mudlet-makers@lists.launchpad.net Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
