<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet title="XSL_formatting" type="text/xsl" href="includes/rss/rss_20.xsl" ?>

<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title></title>
<link>http://www.deluxegaming.net</link>
<description>DELUXEGAMING</description>
<copyright></copyright>
<generator> Evo RSS 2.0 Parser</generator>
<ttl>60</ttl>

<image>
<title></title>
<url>http://www.deluxegaming.net/images/evo/minilogo.gif</url>
<link>http://www.deluxegaming.net</link>
<width>94</width>
<height>15</height>
<description>Nuke-Evolution Powered Site</description>
</image>
<dc:language>en-us</dc:language>
<dc:creator>deluxegaming@y7mail.com</dc:creator>
<dc:date>2012-05-20T04:19:02-04:00</dc:date>

<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2012-05-20T04:19:02-04:00</sy:updateBase>

<item>
<title>Diablo III Problems - Servers Overloaded Battle.net Tempory Taken Offline</title>
<link>http://www.deluxegaming.net/modules.php?name=News&amp;file=article&amp;sid=49</link>
<description><![CDATA[Just before the launch of Diablo 3 Blizzard was forced to take battle.net offline in order to add additional servers to handle the overwhelming demand of traffic for the game. If you are logging in and experiencing a greeted error code that prevents you from logging in your account, Blizzard has provided some information on error codes. The general error code which was displayed by players were &quot;Error 37&quot; which indicated that the Diablo 3 server has reached its max capacity. Players have also experience failure of a creation of a character at the character list but according to Blizzard most of these issues should of been completed at the previous patch 1.0.1. Blizzard is now working to resolve the issue and error codes can be found on the technical support forum.<br />
<br />
Blizzard has demonstrated that they're aware of the problem and is stating for fans to be patient as the rush to fix the issues as fast as possible.]]></description>
<guid isPermaLink="false">49@http://www.deluxegaming.net</guid>
<dc:subject>evolution</dc:subject>
<dc:date>2012-05-15T08:52:13-04:00</dc:date>
<dc:creator>Posted by net0451</dc:creator>
</item>

<item>
<title>Diablo 3 , Australian/Aussie Lag issues at Launch</title>
<link>http://www.deluxegaming.net/modules.php?name=News&amp;file=article&amp;sid=48</link>
<description><![CDATA[It seems Diablo 3 has become very laggy at launch with many Australian players experiencing 400ms by connecting to the U.S servers. Blizzard is working on it to resolve the issue but we don't know how long it will take. The only solution to take is to run a tunneling service such as LowerPing to improve the latency of the game. By running a tunneling service you can reduce your ping to about 200ms which will possible make Diablo 3 playable. Australian Customers are upset with no Australian servers supplied at launch, which may hurt blizzard ASIA/Pacific Fan base due to the latency. With all the hype of the game across the world it seems Australian gamers are getting disadvantage with the single player experience and even the multilayer against U.S players. When a zombie delays for 5 seconds then it breaks the Diablo 3 experience. The only two options are for blizzard to resolve the latency issue or to try a tunneling services which may reduce lag. <br />
<br />
<br />
The game is great but should we be forced to experience lag on a single player element of the game? Post your comments below]]></description>
<guid isPermaLink="false">48@http://www.deluxegaming.net</guid>
<dc:subject>evolution</dc:subject>
<dc:date>2012-05-15T08:18:07-04:00</dc:date>
<dc:creator>Posted by net0451</dc:creator>
</item>

</channel>
</rss>

