telopts, print, next output line

Posted by Bast on Mon 30 Aug 2010 02:15 AM — 7 posts, 31,904 views.

#0
I have a scenario:

Receive some input from a telnet option protocol (GMCP, ATCP, Aardtelopts) and then print or ColourNote something during the OnPluginTelnetOption (or anything called from that, such as printing from a broadcast from that function).

The next line sent to output after printing or colournote is not categorized correctly. It doesn't trigger any trigger even if it should. Sometimes it is in the same colour as the previous print, sometimes not.

It is especially annoying when I am on the test port on aard and printing all the new GMCP stuff and half my other triggers aren't working because of it.

Can you take a look at it Nick?

Thanks,
Bast
Australia Forum Administrator #1
Is that this issue?

Template:post=10535
Please see the forum thread: http://gammon.com.au/forum/?id=10535.


You could also try using the new plugin Messages_Window which was published here and also just released in version 4.59.

This lets you send messages to a miniwindow, so the output doesn't interfere with the MUD output.

It wouldn't surprise me that if you mixed up Note calls with standard MUD output (especially in the middle of a line, which might happen with GMCP) that it will get confused.

Either using a notepad window, or a miniwindow, solves this.

Messages_Window plugin here:

Template:post=10515
Please see the forum thread: http://gammon.com.au/forum/?id=10515.

Amended on Mon 30 Aug 2010 05:37 AM by Nick Gammon
USA Global Moderator #2
An Aardwolf player reports that this has happened to him too just recently. Same description.
Australia Forum Administrator #3
I thought that was fixed in version 4.99:

http://www.gammon.com.au/scripts/showrelnote.php?version=4.99&productid=0

What version of the client does this player have?
USA Global Moderator #4
5.06-pre
USA Global Moderator #5
The user reports that the echo print from a Send (as opposed to SendNoEcho) triggered on receipt of a GMCP message both color bleeds into the next output line from the server and also causes a trigger that should be hiding that next output to not fire. Did the change in 4.99 also apply to the echo from Send?
Amended on Thu 21 Dec 2017 09:23 PM by Fiendish
Australia Forum Administrator #6
No it doesn't apply to using Send. The deferred sending is for "note" lines, not echoing of sent text.

I suggest the user does a SendNoEcho and also a ColourNote which will make the sent text appear at the appropriate moment. However it will be tagged as a "note" line and not a "sent" line.