<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to write con scenarios the Gar Hanrahan way</title>
	<atom:link href="http://thatsnotmysquid.com/blog/?feed=rss2&#038;p=81" rel="self" type="application/rss+xml" />
	<link>http://thatsnotmysquid.com/blog/?p=81</link>
	<description>...so it is necessary that I keep labouring at it, until the figure is to my thinking to and to my desire...</description>
	<lastBuildDate>Wed, 09 Jun 2010 15:11:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gareth Hanrahan on Writing Convention Games &#124; Northeast Wars X</title>
		<link>http://thatsnotmysquid.com/blog/?p=81&#038;cpage=1#comment-1583</link>
		<dc:creator>Gareth Hanrahan on Writing Convention Games &#124; Northeast Wars X</dc:creator>
		<pubDate>Mon, 10 Aug 2009 17:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://thatsnotmysquid.com/blog/?p=81#comment-1583</guid>
		<description>[...] Gareth Hanrahan, contributor to a number of roleplaying game lines  &#8212; including Traveller, RuneQuest and Paranoia &#8211; has a five part series on his blog Figures of Text describing his methods for writing convention scenarios. The first article, &#8220;How to write convention scenarios the Gar Hanrahan way,&#8221; is here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Gareth Hanrahan, contributor to a number of roleplaying game lines  &#8212; including Traveller, RuneQuest and Paranoia &#8211; has a five part series on his blog Figures of Text describing his methods for writing convention scenarios. The first article, &#8220;How to write convention scenarios the Gar Hanrahan way,&#8221; is here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
