<?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: Yu-Gi-Oh! Ban List Discussion: A Wonderful Format (Part Two)</title>
	<atom:link href="http://go-ygo.com/746/feed" rel="self" type="application/rss+xml" />
	<link>http://go-ygo.com/746</link>
	<description></description>
	<lastBuildDate>Sun, 25 Jul 2010 02:09:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: DesPro</title>
		<link>http://go-ygo.com/746/comment-page-1#comment-895</link>
		<dc:creator>DesPro</dc:creator>
		<pubDate>Wed, 06 Jan 2010 19:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://go-ygo.com/?p=746#comment-895</guid>
		<description>The main reason why KDE manipulates the banlist is not only to balance the game, but to FORCE players to BUY newer cards. M-Reborn returned with Premature (banning Callof) because of the release of DiskCommander. Malicious returned at X3 because of the release of  snchros=so players would buy holo synchros and E.Teleports in greater ammounts upon their release. 
Solemn has been maintech x3 since 08&#039;s GB&#039;s, Oppression Monarchs, and TELEDAD. including bottomless seeing x3 as maintech. they were the cards that CONTROLLING/CONSISTENT/FAST/AGGRESSIVE decks overused. Having Solemn and BTH at 3 means players will remain using the same cards despite of ANY CHANGES done to a banlist. Therefore, hitting them in a banlist makes new cards to make their debut.(until they wait for 2 YEARS to be at 3, the case with RAIZA)</description>
		<content:encoded><![CDATA[<p>The main reason why KDE manipulates the banlist is not only to balance the game, but to FORCE players to BUY newer cards. M-Reborn returned with Premature (banning Callof) because of the release of DiskCommander. Malicious returned at X3 because of the release of  snchros=so players would buy holo synchros and E.Teleports in greater ammounts upon their release.<br />
Solemn has been maintech x3 since 08&#8242;s GB&#8217;s, Oppression Monarchs, and TELEDAD. including bottomless seeing x3 as maintech. they were the cards that CONTROLLING/CONSISTENT/FAST/AGGRESSIVE decks overused. Having Solemn and BTH at 3 means players will remain using the same cards despite of ANY CHANGES done to a banlist. Therefore, hitting them in a banlist makes new cards to make their debut.(until they wait for 2 YEARS to be at 3, the case with RAIZA)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Swmystery</title>
		<link>http://go-ygo.com/746/comment-page-1#comment-754</link>
		<dc:creator>Swmystery</dc:creator>
		<pubDate>Fri, 18 Sep 2009 14:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://go-ygo.com/?p=746#comment-754</guid>
		<description>J: Limiting broken cards is unreasonable? No, it&#039;s not, it&#039;s neccessary. Which broken level 4&#039;s are left in the game, in your opinion? If a card is broken it should be banned. It really is as simple as that. Monk is not broken and does not need to be hit just so broken cards can stay.</description>
		<content:encoded><![CDATA[<p>J: Limiting broken cards is unreasonable? No, it&#8217;s not, it&#8217;s neccessary. Which broken level 4&#8242;s are left in the game, in your opinion? If a card is broken it should be banned. It really is as simple as that. Monk is not broken and does not need to be hit just so broken cards can stay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J</title>
		<link>http://go-ygo.com/746/comment-page-1#comment-704</link>
		<dc:creator>J</dc:creator>
		<pubDate>Mon, 07 Sep 2009 01:51:28 +0000</pubDate>
		<guid isPermaLink="false">http://go-ygo.com/?p=746#comment-704</guid>
		<description>@Swmystery, limiting the number of broken level 4s that can be searched out with Summoner Monk is just unreasonable. Level 4 is, by far, the level that, in my mind, has some of the most broken monsters available. Rather than limit the selection, why not limit the incredibly easy way of finding them all whenever you want?</description>
		<content:encoded><![CDATA[<p>@Swmystery, limiting the number of broken level 4s that can be searched out with Summoner Monk is just unreasonable. Level 4 is, by far, the level that, in my mind, has some of the most broken monsters available. Rather than limit the selection, why not limit the incredibly easy way of finding them all whenever you want?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: K.T.</title>
		<link>http://go-ygo.com/746/comment-page-1#comment-686</link>
		<dc:creator>K.T.</dc:creator>
		<pubDate>Fri, 04 Sep 2009 17:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://go-ygo.com/?p=746#comment-686</guid>
		<description>&quot;Yes I might be a bit biased because I have been playing plants ever since I saw the potential of Lonefire, but the best plants have done competitively is probably 24th place at Chicago Shonen Jump (that was me) during Tele-DAD format.&quot;

lol...Wasn&#039;t there an article about a Plant/Skill Drain deck winning some Japanese championship?</description>
		<content:encoded><![CDATA[<p>&#8220;Yes I might be a bit biased because I have been playing plants ever since I saw the potential of Lonefire, but the best plants have done competitively is probably 24th place at Chicago Shonen Jump (that was me) during Tele-DAD format.&#8221;</p>
<p>lol&#8230;Wasn&#8217;t there an article about a Plant/Skill Drain deck winning some Japanese championship?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ShadowQueen</title>
		<link>http://go-ygo.com/746/comment-page-1#comment-674</link>
		<dc:creator>ShadowQueen</dc:creator>
		<pubDate>Thu, 03 Sep 2009 05:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://go-ygo.com/?p=746#comment-674</guid>
		<description>It&#039;s not like it&#039;s hard to get Lonefire into your hand...</description>
		<content:encoded><![CDATA[<p>It&#8217;s not like it&#8217;s hard to get Lonefire into your hand&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
