<?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: Timing mechanisms: what&#8217;s not to like?</title>
	<atom:link href="http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like</link>
	<description>Inside the Mind of Thomas Robertson</description>
	<lastBuildDate>Tue, 31 Jan 2012 03:19:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Thomas Robertson</title>
		<link>http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like/comment-page-1#comment-776</link>
		<dc:creator>Thomas Robertson</dc:creator>
		<pubDate>Wed, 27 Sep 2006 13:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesmerf.com/blog/78-timing-mechanisms-whats-not-to-like#comment-776</guid>
		<description>Fred,

I think it&#039;s pretty highly dependent upon how you&#039;re defining &#039;game&#039;.  So, looking at Mike&#039;s HQ game, is a &#039;game&#039; a single session, a phase, the entirety of play (phases 1, 2, and now 3), all the play done by that group of players?

Because it seems obvious that you want a given session to end.  It seems obvious that each phase will come to an end if you&#039;re actually progressing your story (no story is infinite).  I would suggest that given enough play you&#039;d want the cycle of phases to end, eventually you&#039;ve told all the stories you want to tell with a given set of characters in a given world (though this is a theoretical thing, I&#039;m not sure how many hundreds of hours it takes to exhaust something like this).  I imagine that people are complex enough that you can play indefinitely with the same group.

Since you want some of these things to end (for they must eventually end if play is functional), it seems worthwhile to see if you can make them end satisfactorily and predictably.  The open-ended nature of traditional gaming (we play every week until the apocalypse) makes it difficult to get people involved.  I mean, I can&#039;t really maintain that sort of schedule, and I&#039;m a college student.

It seems much better to me to be able to do something like &lt;i&gt;Primetime Adventures&lt;/i&gt; where I can say &#039;We&#039;ll play this every other week for about three hours, and we&#039;ll be done in three months.&#039;  That&#039;s a commitment you can agree to in good conscience (or not, as the case may be).  You can evaluate it.

Even better, I&#039;d like to see something like the idea Tony was tossing around in the &#039;Social Footprint&#039; threads where I can say &#039;we&#039;ll play this for an hour or two&#039; and when we&#039;re done we&#039;re all satisfied.  We don&#039;t have that &#039;that was fun, but half of the game was spent building stuff up for the next session, if I don&#039;t get that next session I&#039;ll feel like my time was wasted&#039; feeling.  I hate that feeling, and it is one of the things that makes it hard for me to get involved in longer-term games.

Thomas</description>
		<content:encoded><![CDATA[<p>Fred,</p>
<p>I think it&#8217;s pretty highly dependent upon how you&#8217;re defining &#8216;game&#8217;.  So, looking at Mike&#8217;s HQ game, is a &#8216;game&#8217; a single session, a phase, the entirety of play (phases 1, 2, and now 3), all the play done by that group of players?</p>
<p>Because it seems obvious that you want a given session to end.  It seems obvious that each phase will come to an end if you&#8217;re actually progressing your story (no story is infinite).  I would suggest that given enough play you&#8217;d want the cycle of phases to end, eventually you&#8217;ve told all the stories you want to tell with a given set of characters in a given world (though this is a theoretical thing, I&#8217;m not sure how many hundreds of hours it takes to exhaust something like this).  I imagine that people are complex enough that you can play indefinitely with the same group.</p>
<p>Since you want some of these things to end (for they must eventually end if play is functional), it seems worthwhile to see if you can make them end satisfactorily and predictably.  The open-ended nature of traditional gaming (we play every week until the apocalypse) makes it difficult to get people involved.  I mean, I can&#8217;t really maintain that sort of schedule, and I&#8217;m a college student.</p>
<p>It seems much better to me to be able to do something like <i>Primetime Adventures</i> where I can say &#8216;We&#8217;ll play this every other week for about three hours, and we&#8217;ll be done in three months.&#8217;  That&#8217;s a commitment you can agree to in good conscience (or not, as the case may be).  You can evaluate it.</p>
<p>Even better, I&#8217;d like to see something like the idea Tony was tossing around in the &#8216;Social Footprint&#8217; threads where I can say &#8216;we&#8217;ll play this for an hour or two&#8217; and when we&#8217;re done we&#8217;re all satisfied.  We don&#8217;t have that &#8216;that was fun, but half of the game was spent building stuff up for the next session, if I don&#8217;t get that next session I&#8217;ll feel like my time was wasted&#8217; feeling.  I hate that feeling, and it is one of the things that makes it hard for me to get involved in longer-term games.</p>
<p>Thomas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like/comment-page-1#comment-775</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Wed, 27 Sep 2006 12:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesmerf.com/blog/78-timing-mechanisms-whats-not-to-like#comment-775</guid>
		<description>So it sounds like there are two functions that timing mechanisms can have; one is to affect how long things take, in terms of &quot;turns&quot; or whatever, and the other is to affect the order in which things happen. Either, neither, or both may be in effect.

http://www.newciv.org/pos/infinitegames.html

I don&#039;t know if you&#039;ve ever heard of &quot;infinite games&quot; but a fellow by the name of James Carse wrote a book a while back about this topic that&#039;s worth reading with an eye towards roleplaying games.

I think one of the most fascinating things about roleplaying games is that they can become very infinite in character; the purpose of play is not to &quot;win&quot; and thereby end the game, but to keep playing.

It&#039;s for this reason that I&#039;m not as interested in timing mechanisms that bring a game to an end.  There&#039;s nothing special about that.</description>
		<content:encoded><![CDATA[<p>So it sounds like there are two functions that timing mechanisms can have; one is to affect how long things take, in terms of &#8220;turns&#8221; or whatever, and the other is to affect the order in which things happen. Either, neither, or both may be in effect.</p>
<p><a href="http://www.newciv.org/pos/infinitegames.html" rel="nofollow">http://www.newciv.org/pos/infinitegames.html</a></p>
<p>I don&#8217;t know if you&#8217;ve ever heard of &#8220;infinite games&#8221; but a fellow by the name of James Carse wrote a book a while back about this topic that&#8217;s worth reading with an eye towards roleplaying games.</p>
<p>I think one of the most fascinating things about roleplaying games is that they can become very infinite in character; the purpose of play is not to &#8220;win&#8221; and thereby end the game, but to keep playing.</p>
<p>It&#8217;s for this reason that I&#8217;m not as interested in timing mechanisms that bring a game to an end.  There&#8217;s nothing special about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Robertson</title>
		<link>http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like/comment-page-1#comment-774</link>
		<dc:creator>Thomas Robertson</dc:creator>
		<pubDate>Tue, 26 Sep 2006 22:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesmerf.com/blog/78-timing-mechanisms-whats-not-to-like#comment-774</guid>
		<description>Fred,

Having read the mechanic in question, I think that it&#039;s definitely a timing mechanism of a sort, if not quite the type I&#039;m focused on at the moment.  It&#039;s clear that it&#039;s a pacing mechanism.  It allows for players to specify that event X will be super-important and will happen after event Y.  And that event Z is cool, but not too cool, and will happen early on.  It &#039;times&#039; things in the sense that it tells you what order they will happen in, which is sort of like the Plot Arc mechanic in &lt;i&gt;Primetime Adventures&lt;/i&gt;, but more specific than that.

But it&#039;s not a timing mechanism in the sense that it controls how much time play takes.  Because clearly you could play for hours and hours without expending any of the pivotal scenes.  In fact you could finish a session with the same number in play (having never changed them at all).

Contrast that with something like &lt;i&gt;Uno&lt;/i&gt; where on your turn you &lt;i&gt;must&lt;/i&gt; play a card if you can.  Otherwise you&#039;re not playing &lt;i&gt;Uno&lt;/i&gt;, you&#039;re playing some crazy game with the &lt;i&gt;Uno&lt;/i&gt; deck.  Thus, eventually, you&#039;ll run out of cards.  And further you should be able to develop a nice bell curve regarding how much time it takes people to do so.

Thomas</description>
		<content:encoded><![CDATA[<p>Fred,</p>
<p>Having read the mechanic in question, I think that it&#8217;s definitely a timing mechanism of a sort, if not quite the type I&#8217;m focused on at the moment.  It&#8217;s clear that it&#8217;s a pacing mechanism.  It allows for players to specify that event X will be super-important and will happen after event Y.  And that event Z is cool, but not too cool, and will happen early on.  It &#8216;times&#8217; things in the sense that it tells you what order they will happen in, which is sort of like the Plot Arc mechanic in <i>Primetime Adventures</i>, but more specific than that.</p>
<p>But it&#8217;s not a timing mechanism in the sense that it controls how much time play takes.  Because clearly you could play for hours and hours without expending any of the pivotal scenes.  In fact you could finish a session with the same number in play (having never changed them at all).</p>
<p>Contrast that with something like <i>Uno</i> where on your turn you <i>must</i> play a card if you can.  Otherwise you&#8217;re not playing <i>Uno</i>, you&#8217;re playing some crazy game with the <i>Uno</i> deck.  Thus, eventually, you&#8217;ll run out of cards.  And further you should be able to develop a nice bell curve regarding how much time it takes people to do so.</p>
<p>Thomas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like/comment-page-1#comment-773</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Tue, 26 Sep 2006 19:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesmerf.com/blog/78-timing-mechanisms-whats-not-to-like#comment-773</guid>
		<description>Click my name.

http://vaxalon.livejournal.com/</description>
		<content:encoded><![CDATA[<p>Click my name.</p>
<p><a href="http://vaxalon.livejournal.com/" rel="nofollow">http://vaxalon.livejournal.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Robertson</title>
		<link>http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like/comment-page-1#comment-772</link>
		<dc:creator>Thomas Robertson</dc:creator>
		<pubDate>Tue, 26 Sep 2006 18:18:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesmerf.com/blog/78-timing-mechanisms-whats-not-to-like#comment-772</guid>
		<description>Got a link?

Thomas</description>
		<content:encoded><![CDATA[<p>Got a link?</p>
<p>Thomas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://blog.thomas-robertson.com/80-timing-mechanisms-whats-not-to-like/comment-page-1#comment-771</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Tue, 26 Sep 2006 18:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesmerf.com/blog/78-timing-mechanisms-whats-not-to-like#comment-771</guid>
		<description>Have you seen my &quot;Pivotal Scenes&quot; mechanic?  Does that count as a timing mechanism?</description>
		<content:encoded><![CDATA[<p>Have you seen my &#8220;Pivotal Scenes&#8221; mechanic?  Does that count as a timing mechanism?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

