<?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: Jason&#8217;s favorite games of 2012</title>
	<atom:link href="http://www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/</link>
	<description>The Adrenaline Vault is an independent site providing uninfluenced and unbiased video game information.</description>
	<lastBuildDate>Tue, 14 May 2013 10:40:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: MSpears</title>
		<link>http://www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/comment-page-1/#comment-118257</link>
		<dc:creator>MSpears</dc:creator>
		<pubDate>Tue, 12 Mar 2013 19:28:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.avault.com/?p=77153#comment-118257</guid>
		<description>I have been an off-and-on game reviewer (mostly &quot;off&quot; these days; I just don&#039;t have the time anymore) for more than a decade.  When I first started reviewing games, I would review the game as I received it, straight out of the box; no patches unless they were needed to make the game run on my PC (or at least to make it stop crashing so often).

A good example of this would have been Outpost.  I never reviewed this one, but I&#039;ve played it, and when it shipped it was missing nearly half of the features in the manual.  This was a combination of two factors: First, manuals have to be sent to print before the game is actually ready for release, so they&#039;re ready to ship.  That&#039;s the reason why you sometimes see mistakes in the manual... something changed after the manual was sent to the printers, but before the game shipped.  Second, they lost their lead programmer and management basically said &quot;take what you&#039;ve got, get it working, and ship it.&quot;  Eventually Sierra came out with patch 1.5, which added some (but not all) of the missing features to the game.

Now, assuming I *had* reviewed Outpost, and Sierra asked me to review it again with the 1.5 patch installed, I would&#039;ve refused.  &quot;Nope... too little, too late.  I&#039;ve already reviewed the game I received.  I&#039;m not going to waste my time reviewing the game it should have been.&quot;

These days, I&#039;m starting to come around to the &quot;second pass&quot; point of view.  Here&#039;s the quid pro quo... I would only consider second pass reviews *if* the DLC adds a significant amount of content or alters gameplay in a significant way.  I think we can all agree that you wouldn&#039;t do a second pass of a game just because they added some new costumes.  Adding another 10-20 hours of play, however... well, that&#039;s different.  But unless the reviewer kept his saved games, or has continued to actively play the MMO, or whatever, his avatar may not be experienced enough to access the new content; and that&#039;s where you run into the problems Jason mentioned.  There&#039;s simply no way to guarantee your &quot;second pass&quot; would be first AND be in depth, because another reviewer that DID keep his saved games, or continued to actively play the MMO, could get to the new content first.</description>
		<content:encoded><![CDATA[<p>I have been an off-and-on game reviewer (mostly &#8220;off&#8221; these days; I just don&#8217;t have the time anymore) for more than a decade.  When I first started reviewing games, I would review the game as I received it, straight out of the box; no patches unless they were needed to make the game run on my PC (or at least to make it stop crashing so often).</p>
<p>A good example of this would have been Outpost.  I never reviewed this one, but I&#8217;ve played it, and when it shipped it was missing nearly half of the features in the manual.  This was a combination of two factors: First, manuals have to be sent to print before the game is actually ready for release, so they&#8217;re ready to ship.  That&#8217;s the reason why you sometimes see mistakes in the manual&#8230; something changed after the manual was sent to the printers, but before the game shipped.  Second, they lost their lead programmer and management basically said &#8220;take what you&#8217;ve got, get it working, and ship it.&#8221;  Eventually Sierra came out with patch 1.5, which added some (but not all) of the missing features to the game.</p>
<p>Now, assuming I *had* reviewed Outpost, and Sierra asked me to review it again with the 1.5 patch installed, I would&#8217;ve refused.  &#8220;Nope&#8230; too little, too late.  I&#8217;ve already reviewed the game I received.  I&#8217;m not going to waste my time reviewing the game it should have been.&#8221;</p>
<p>These days, I&#8217;m starting to come around to the &#8220;second pass&#8221; point of view.  Here&#8217;s the quid pro quo&#8230; I would only consider second pass reviews *if* the DLC adds a significant amount of content or alters gameplay in a significant way.  I think we can all agree that you wouldn&#8217;t do a second pass of a game just because they added some new costumes.  Adding another 10-20 hours of play, however&#8230; well, that&#8217;s different.  But unless the reviewer kept his saved games, or has continued to actively play the MMO, or whatever, his avatar may not be experienced enough to access the new content; and that&#8217;s where you run into the problems Jason mentioned.  There&#8217;s simply no way to guarantee your &#8220;second pass&#8221; would be first AND be in depth, because another reviewer that DID keep his saved games, or continued to actively play the MMO, could get to the new content first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Pitruzzello</title>
		<link>http://www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/comment-page-1/#comment-113199</link>
		<dc:creator>Jason Pitruzzello</dc:creator>
		<pubDate>Thu, 03 Jan 2013 19:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.avault.com/?p=77153#comment-113199</guid>
		<description>I&#039;ve been giving it some thought, and it occurs to me second pass (or second chance) reviews carry some interesting pros and cons. 

On the one hand, some games, and MMOs especially, are so dynamic in terms of new content and changes that they are practically a different animal within six months. We would all agree on that.

On the other hand, this industry thrives on hype. And hype isn&#039;t just about talking up a game. It&#039;s also about being first with a news scoop or first with something neat. So, you can&#039;t be first AND be in depth AND see if a game ages well.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been giving it some thought, and it occurs to me second pass (or second chance) reviews carry some interesting pros and cons. </p>
<p>On the one hand, some games, and MMOs especially, are so dynamic in terms of new content and changes that they are practically a different animal within six months. We would all agree on that.</p>
<p>On the other hand, this industry thrives on hype. And hype isn&#8217;t just about talking up a game. It&#8217;s also about being first with a news scoop or first with something neat. So, you can&#8217;t be first AND be in depth AND see if a game ages well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Solo4114</title>
		<link>http://www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/comment-page-1/#comment-113187</link>
		<dc:creator>Solo4114</dc:creator>
		<pubDate>Wed, 26 Dec 2012 17:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.avault.com/?p=77153#comment-113187</guid>
		<description>I&#039;ve been thinking for a while about the notion of review timing.  I think there is -- or ought to be -- a market for the &quot;second pass&quot; review.  

For example, when a game first launches, much of the time you get the sense of &quot;This is great!  It&#039;s new and shiny and wonderful!&quot;  But play it a month or two more and suddenly the shine is off and you start seeing the real flaws in the game which have yet to be addressed.  Or, a patch has been released which dramatically alters gameplay.

I don&#039;t know about other folks, but generally speaking when I buy a game, it&#039;s gonna be one I intend to play for a while.  I take my time on single player games, frequently, because my gaming time is limited, and split between games usually.  Multiplayer games are a different kettle of fish, in that they typically don&#039;t reveal all that&#039;s good or bad right out of the gate.  It takes time playing with stuff (particularly games with obnoxious &quot;unlock&quot; systems) to really see that, for example, the USAS-12 plus 12G frags and an IRNV is a clearly broken unbeatable combo in BF3....until it got patched.  

So, I&#039;d say it might be worthwhile to institute a new column.  Something like &quot;One/Two Month(s) Later...&quot;  This might not work so well with review schedules, since that&#039;d require longer-term gameplay (which might be difficult if you&#039;ve got a deadline for that other review), but seeing as how you guys do admit to playing games in the meantime, maybe have folks write their post-shiny-phase impressions of the game.

Frankly, for all the breathlessly excited and positive reviews I see on other sites about the latest AAA title to come out that same day, after playing a lot of them for a month or so, I can&#039;t help but wonder what those reviewers would say (well, if they weren&#039;t shills, that is...) if they wrote another review after the fact.


Particularly in a changing gaming industry chock full of microtransactions, ongoing DLC packs, patches, etc., perhaps the gaming review industry needs to adapt to a more longitudinal approach to reviews.  &quot;Here&#039;s my Day-0 review.  And here&#039;s my Day-60 review.&quot;  We also often complain about company support (or lack thereof) with games, so given that you&#039;re almost buying a SERVICE now rather than just a PRODUCT, maybe some reviews of how well a game&#039;s being supported would influence people&#039;s decisions.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been thinking for a while about the notion of review timing.  I think there is &#8212; or ought to be &#8212; a market for the &#8220;second pass&#8221; review.  </p>
<p>For example, when a game first launches, much of the time you get the sense of &#8220;This is great!  It&#8217;s new and shiny and wonderful!&#8221;  But play it a month or two more and suddenly the shine is off and you start seeing the real flaws in the game which have yet to be addressed.  Or, a patch has been released which dramatically alters gameplay.</p>
<p>I don&#8217;t know about other folks, but generally speaking when I buy a game, it&#8217;s gonna be one I intend to play for a while.  I take my time on single player games, frequently, because my gaming time is limited, and split between games usually.  Multiplayer games are a different kettle of fish, in that they typically don&#8217;t reveal all that&#8217;s good or bad right out of the gate.  It takes time playing with stuff (particularly games with obnoxious &#8220;unlock&#8221; systems) to really see that, for example, the USAS-12 plus 12G frags and an IRNV is a clearly broken unbeatable combo in BF3&#8230;.until it got patched.  </p>
<p>So, I&#8217;d say it might be worthwhile to institute a new column.  Something like &#8220;One/Two Month(s) Later&#8230;&#8221;  This might not work so well with review schedules, since that&#8217;d require longer-term gameplay (which might be difficult if you&#8217;ve got a deadline for that other review), but seeing as how you guys do admit to playing games in the meantime, maybe have folks write their post-shiny-phase impressions of the game.</p>
<p>Frankly, for all the breathlessly excited and positive reviews I see on other sites about the latest AAA title to come out that same day, after playing a lot of them for a month or so, I can&#8217;t help but wonder what those reviewers would say (well, if they weren&#8217;t shills, that is&#8230;) if they wrote another review after the fact.</p>
<p>Particularly in a changing gaming industry chock full of microtransactions, ongoing DLC packs, patches, etc., perhaps the gaming review industry needs to adapt to a more longitudinal approach to reviews.  &#8220;Here&#8217;s my Day-0 review.  And here&#8217;s my Day-60 review.&#8221;  We also often complain about company support (or lack thereof) with games, so given that you&#8217;re almost buying a SERVICE now rather than just a PRODUCT, maybe some reviews of how well a game&#8217;s being supported would influence people&#8217;s decisions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Davis</title>
		<link>http://www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/comment-page-1/#comment-113176</link>
		<dc:creator>Ian Davis</dc:creator>
		<pubDate>Sun, 23 Dec 2012 18:10:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.avault.com/?p=77153#comment-113176</guid>
		<description>&quot;I also have to consider that it’s becoming increasingly meaningless to talk about games as if they’re static titles that get patched, but never really change their content.&quot;

Very true. Especially in the ephemeral PC realm, this can make reviews utterly meaningless. Does a launch review of Team Fortress 2 hold any meaning anymore? Does a review of a MMO offer any help after the first patch of many? Even more, how can we best post reviews for things like this? Update with a later review? Emphasize the time-stamp? Post everything on a scrolling twitter-feed that eventually erases itself?</description>
		<content:encoded><![CDATA[<p>&#8220;I also have to consider that it’s becoming increasingly meaningless to talk about games as if they’re static titles that get patched, but never really change their content.&#8221;</p>
<p>Very true. Especially in the ephemeral PC realm, this can make reviews utterly meaningless. Does a launch review of Team Fortress 2 hold any meaning anymore? Does a review of a MMO offer any help after the first patch of many? Even more, how can we best post reviews for things like this? Update with a later review? Emphasize the time-stamp? Post everything on a scrolling twitter-feed that eventually erases itself?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: psycros</title>
		<link>http://www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/comment-page-1/#comment-113175</link>
		<dc:creator>psycros</dc:creator>
		<pubDate>Sun, 23 Dec 2012 18:02:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.avault.com/?p=77153#comment-113175</guid>
		<description>So they&#039;ve patched up Warlock, have they?  I remember being intrigued by that one when I first heard about it and then disappointed when the reviews said it fell way short.  I know what you mean about patches and DLCs, and mods make it an even fuzzier call on what constitutes a &quot;last year&#039;s game&quot;.  This is why I stick with the PC - with consoles, what you get is what you get 99% of the time.</description>
		<content:encoded><![CDATA[<p>So they&#8217;ve patched up Warlock, have they?  I remember being intrigued by that one when I first heard about it and then disappointed when the reviews said it fell way short.  I know what you mean about patches and DLCs, and mods make it an even fuzzier call on what constitutes a &#8220;last year&#8217;s game&#8221;.  This is why I stick with the PC &#8211; with consoles, what you get is what you get 99% of the time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  www.avault.com/blogs/pitruzzello/jasons-favorite-games-2012/feed/ ) in 0.10812 seconds, on May 18th, 2013 at 12:21 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 18th, 2013 at 12:51 am UTC --