<?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: Gearbox issues update to fix Borderlands 2 character sabotage</title>
	<atom:link href="http://www.slashgear.com/gearbox-issues-update-to-fix-borderlands-2-character-sabotage-07256027/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slashgear.com/gearbox-issues-update-to-fix-borderlands-2-character-sabotage-07256027/</link>
	<description>Feeding Your Gadget and Tech Obsessions</description>
	<lastBuildDate>Wed, 19 Jun 2013 03:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Darth Nikon</title>
		<link>http://www.slashgear.com/gearbox-issues-update-to-fix-borderlands-2-character-sabotage-07256027/#comment-252823</link>
		<dc:creator>Darth Nikon</dc:creator>
		<pubDate>Thu, 08 Nov 2012 23:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=256027#comment-252823</guid>
		<description><![CDATA[Thing is, I&#039;ve contacted Chris Faylor directly on Twitter (@ZombiePancakes) and so far he hasn&#039;t answered as to why he alleges there was ever &quot;malicious&quot; intent.


Of course, Gearbox seems like it&#039;s less at fault if they can claim it was malicious, so they have something to gain from the allegation.]]></description>
		<content:encoded><![CDATA[<p>Thing is, I&#8217;ve contacted Chris Faylor directly on Twitter (@ZombiePancakes) and so far he hasn&#8217;t answered as to why he alleges there was ever &#8220;malicious&#8221; intent.</p>
<p>Of course, Gearbox seems like it&#8217;s less at fault if they can claim it was malicious, so they have something to gain from the allegation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darth Nikon</title>
		<link>http://www.slashgear.com/gearbox-issues-update-to-fix-borderlands-2-character-sabotage-07256027/#comment-252474</link>
		<dc:creator>Darth Nikon</dc:creator>
		<pubDate>Wed, 07 Nov 2012 23:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=256027#comment-252474</guid>
		<description><![CDATA[Man, I&#039;m just going to have to keep saying this over and over, aren&#039;t I? It would be nice if Gearbox stopped trying to shift the blame instead of accepting some responsibility. They have yet to respond to requests for any evidence at all that the flag getting set was intentional, much less malicious. It comes off more like they&#039;re lying about the malicious part to cover themselves, and hope everyone gets mad enough at &quot;teh haxxors!&quot; that they don&#039;t stop and think.

What spread virally (through Gearbox&#039;s online save code) was a flag that turns on hardcore mode code that Gearbox left in the release of the game. It was silently patched out on the PC, and PS3 owners never got a save editor to accidentally turn the flag on. It just took longer for Gearbox to disarm the hardcore mode on XBox because of the update certification process.

Saves on all platforms are still  susceptible to any flag-passing infection in online play, even if it&#039;s as simple as griefing players on playthrough 2 by selecting optional missions to lock the gear  rewards at the current level; even if you go back later to complete the missions at 50, the rewards will be locked at the lower level when they were selected.

That&#039;s the least-damaging, known danger of online play at the moment. Until Gearbox changes the save code, something just as bad as Graveyard.sav could still happen in the future.]]></description>
		<content:encoded><![CDATA[<p>Man, I&#8217;m just going to have to keep saying this over and over, aren&#8217;t I? It would be nice if Gearbox stopped trying to shift the blame instead of accepting some responsibility. They have yet to respond to requests for any evidence at all that the flag getting set was intentional, much less malicious. It comes off more like they&#8217;re lying about the malicious part to cover themselves, and hope everyone gets mad enough at &#8220;teh haxxors!&#8221; that they don&#8217;t stop and think.</p>
<p>What spread virally (through Gearbox&#8217;s online save code) was a flag that turns on hardcore mode code that Gearbox left in the release of the game. It was silently patched out on the PC, and PS3 owners never got a save editor to accidentally turn the flag on. It just took longer for Gearbox to disarm the hardcore mode on XBox because of the update certification process.</p>
<p>Saves on all platforms are still  susceptible to any flag-passing infection in online play, even if it&#8217;s as simple as griefing players on playthrough 2 by selecting optional missions to lock the gear  rewards at the current level; even if you go back later to complete the missions at 50, the rewards will be locked at the lower level when they were selected.</p>
<p>That&#8217;s the least-damaging, known danger of online play at the moment. Until Gearbox changes the save code, something just as bad as Graveyard.sav could still happen in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Good ol' JS</title>
		<link>http://www.slashgear.com/gearbox-issues-update-to-fix-borderlands-2-character-sabotage-07256027/#comment-252415</link>
		<dc:creator>Good ol' JS</dc:creator>
		<pubDate>Wed, 07 Nov 2012 19:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=256027#comment-252415</guid>
		<description><![CDATA[This is not a malicious issue.  It&#039;s been known for a while.  Someone was messing with a game save and flipped the flag for essentially &quot;hardcore&quot; mode.  Which means when your character dies, they&#039;re dead for good.  It would have stayed isolated but anyone playing with a person that has that flag set, will inherit the other person&#039;s flag and then when their character dies, they die forever as well. Gearbox should have either removed that code initially OR finished out the idea so those of us who would like to could have played that way.]]></description>
		<content:encoded><![CDATA[<p>This is not a malicious issue.  It&#8217;s been known for a while.  Someone was messing with a game save and flipped the flag for essentially &#8220;hardcore&#8221; mode.  Which means when your character dies, they&#8217;re dead for good.  It would have stayed isolated but anyone playing with a person that has that flag set, will inherit the other person&#8217;s flag and then when their character dies, they die forever as well. Gearbox should have either removed that code initially OR finished out the idea so those of us who would like to could have played that way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
