<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Using telnet negotiation to control MUD / Client Interaction.</title>
	<atom:link href="http://www.aardwolf.com/blog/2008/07/10/telnet-negotiation-control-mud-client-interaction/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.aardwolf.com/blog/2008/07/10/telnet-negotiation-control-mud-client-interaction/</link>
	<description>Aardwolf MUD General News and Updates.</description>
	<pubDate>Sun, 14 Mar 2010 16:12:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Hyena</title>
		<link>http://www.aardwolf.com/blog/2008/07/10/telnet-negotiation-control-mud-client-interaction/#comment-452</link>
		<dc:creator>Hyena</dc:creator>
		<pubDate>Thu, 16 Jul 2009 13:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.aardwolf.com/blog/?p=12#comment-452</guid>
		<description>Hi Lasher. I would like to have a chat with you about this topic. You see, I'm building a whole new mud client for two years now and I was learning IAC telnet options when I discovered this blog. You decided to use option 102 but why 102? 
MSSP uses 70
MCCP uses 85 (COMPRESS) and 86 (COMPRESS2)
How can you make sure that other protocols won't use 102 later? How to make it a standard so that everybody knows 102 is MUP / MCP (mud update protocol / mud client protocol). Btw mud client protocol is already done but I don't like its standards, it doesn't use IAC sequence (http://mcp.cubik.org/).

I am also a mud developer and looking for some good solution to create about the same thing you are talking here in your blog but I don't know what option number to use - should I use 102 too?</description>
		<content:encoded><![CDATA[<p>Hi Lasher. I would like to have a chat with you about this topic. You see, I&#8217;m building a whole new mud client for two years now and I was learning IAC telnet options when I discovered this blog. You decided to use option 102 but why 102?<br />
MSSP uses 70<br />
MCCP uses 85 (COMPRESS) and 86 (COMPRESS2)<br />
How can you make sure that other protocols won&#8217;t use 102 later? How to make it a standard so that everybody knows 102 is MUP / MCP (mud update protocol / mud client protocol). Btw mud client protocol is already done but I don&#8217;t like its standards, it doesn&#8217;t use IAC sequence (http://mcp.cubik.org/).</p>
<p>I am also a mud developer and looking for some good solution to create about the same thing you are talking here in your blog but I don&#8217;t know what option number to use - should I use 102 too?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lasher</title>
		<link>http://www.aardwolf.com/blog/2008/07/10/telnet-negotiation-control-mud-client-interaction/#comment-110</link>
		<dc:creator>Lasher</dc:creator>
		<pubDate>Thu, 10 Jul 2008 20:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.aardwolf.com/blog/?p=12#comment-110</guid>
		<description>Excellent, I didn't know CMUD could do this, that makes it even more useful for spellup writers etc to use these telnet options.</description>
		<content:encoded><![CDATA[<p>Excellent, I didn&#8217;t know CMUD could do this, that makes it even more useful for spellup writers etc to use these telnet options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davos</title>
		<link>http://www.aardwolf.com/blog/2008/07/10/telnet-negotiation-control-mud-client-interaction/#comment-109</link>
		<dc:creator>Davos</dc:creator>
		<pubDate>Thu, 10 Jul 2008 20:30:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.aardwolf.com/blog/?p=12#comment-109</guid>
		<description>Hmm I wish I could edit my own comments.  Anyways I meant the option displayed in the origional post for ZMUD will work for CMUD as well, but the #SENDSB command might work better for you.</description>
		<content:encoded><![CDATA[<p>Hmm I wish I could edit my own comments.  Anyways I meant the option displayed in the origional post for ZMUD will work for CMUD as well, but the #SENDSB command might work better for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davos</title>
		<link>http://www.aardwolf.com/blog/2008/07/10/telnet-negotiation-control-mud-client-interaction/#comment-108</link>
		<dc:creator>Davos</dc:creator>
		<pubDate>Thu, 10 Jul 2008 20:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.aardwolf.com/blog/?p=12#comment-108</guid>
		<description>Also, the option displayed above will work for CMUD as well, as far as sending these telnet commands from client to mud, but CMUD users might also want to check out #SENDSB command to do the same thing in a simpler fashion.</description>
		<content:encoded><![CDATA[<p>Also, the option displayed above will work for CMUD as well, as far as sending these telnet commands from client to mud, but CMUD users might also want to check out #SENDSB command to do the same thing in a simpler fashion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davos</title>
		<link>http://www.aardwolf.com/blog/2008/07/10/telnet-negotiation-control-mud-client-interaction/#comment-107</link>
		<dc:creator>Davos</dc:creator>
		<pubDate>Thu, 10 Jul 2008 20:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.aardwolf.com/blog/?p=12#comment-107</guid>
		<description>BTW, in cMUD you can trigger off the telnet IAC,SB messages.

I copied this from CMUD help files:

Telnet 
Fires when specified Telnet Option subchannel text is received. When IAC SB OptionNumber Text IAC SE is received from the server, a Telnet trigger that matches the OptionNumber will fire and will compare the Text sent from the MUD with the pattern of the trigger state. (Added in v2.0)</description>
		<content:encoded><![CDATA[<p>BTW, in cMUD you can trigger off the telnet IAC,SB messages.</p>
<p>I copied this from CMUD help files:</p>
<p>Telnet<br />
Fires when specified Telnet Option subchannel text is received. When IAC SB OptionNumber Text IAC SE is received from the server, a Telnet trigger that matches the OptionNumber will fire and will compare the Text sent from the MUD with the pattern of the trigger state. (Added in v2.0)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
