<?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: Too Many Chiefs&#8230;</title>
	<atom:link href="http://www.guildmasterpiece.com/too-many-chiefs.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.guildmasterpiece.com/too-many-chiefs.html</link>
	<description>friendly guildmasters here to help you run a fabulous guild</description>
	<lastBuildDate>Sat, 27 Feb 2010 01:13:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: rusha</title>
		<link>http://www.guildmasterpiece.com/too-many-chiefs.html/comment-page-1#comment-145</link>
		<dc:creator>rusha</dc:creator>
		<pubDate>Sun, 23 Mar 2008 03:18:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.guildmasterpiece.com/too-many-chiefs.html#comment-145</guid>
		<description>I LOVE the idea of the key bind.  Do you feel like letting us know how to set that up?  No drama if you cbf.</description>
		<content:encoded><![CDATA[<p>I LOVE the idea of the key bind.  Do you feel like letting us know how to set that up?  No drama if you cbf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eryn</title>
		<link>http://www.guildmasterpiece.com/too-many-chiefs.html/comment-page-1#comment-131</link>
		<dc:creator>Eryn</dc:creator>
		<pubDate>Tue, 18 Mar 2008 18:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.guildmasterpiece.com/too-many-chiefs.html#comment-131</guid>
		<description>Too many chiefs, not enough braves. Too many chefs spoil the soup. However you want to say it, this is always an issue with GOOD raiders. They are good enough to take a little initiative and start researching the fights. Unfortunately as you say, they also tend to want to give lots of input during raids.

They key is to channel these outbursts of insight. Talk to them about sending tells during raids (for strategy) rather than speaking over Ventrilo. If this fails, you can set up a key bind to silence all other members of the channel while you open your mic. So they&#039;ll hear you and nobody else. This will stop people from being able to give conflicting information and will also make it so that people can hear you (the raid leader) much more clearly. I have two separate binds, one for this &quot;silence&quot; mode and one for &quot;normal&quot; chat.

Also, mention to the people who are being troublesome that they need to trust the other members of the raid more. As they trust less, they tend to call out what they believe are necessary pieces of advice. &quot;Heal me!&quot; or &quot;1%!!! KILL THE BOSS&quot; as if your dps had NO idea the boss was about to die. But when they see and know their guildmates, they tend to trust them more... and call out less.</description>
		<content:encoded><![CDATA[<p>Too many chiefs, not enough braves. Too many chefs spoil the soup. However you want to say it, this is always an issue with GOOD raiders. They are good enough to take a little initiative and start researching the fights. Unfortunately as you say, they also tend to want to give lots of input during raids.</p>
<p>They key is to channel these outbursts of insight. Talk to them about sending tells during raids (for strategy) rather than speaking over Ventrilo. If this fails, you can set up a key bind to silence all other members of the channel while you open your mic. So they&#8217;ll hear you and nobody else. This will stop people from being able to give conflicting information and will also make it so that people can hear you (the raid leader) much more clearly. I have two separate binds, one for this &#8220;silence&#8221; mode and one for &#8220;normal&#8221; chat.</p>
<p>Also, mention to the people who are being troublesome that they need to trust the other members of the raid more. As they trust less, they tend to call out what they believe are necessary pieces of advice. &#8220;Heal me!&#8221; or &#8220;1%!!! KILL THE BOSS&#8221; as if your dps had NO idea the boss was about to die. But when they see and know their guildmates, they tend to trust them more&#8230; and call out less.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bellemorte</title>
		<link>http://www.guildmasterpiece.com/too-many-chiefs.html/comment-page-1#comment-126</link>
		<dc:creator>Bellemorte</dc:creator>
		<pubDate>Sun, 16 Mar 2008 16:52:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.guildmasterpiece.com/too-many-chiefs.html#comment-126</guid>
		<description>Your hands aren&#039;t tied. Weather there a friend of someone in the guild or not the only whose got a right to yell at the raid is a raid leader gm, or mabe an officer. Anyone else gets a warning then they get globally muted in vent, and or Bound and gagged in guild. This is a rank in my guild chat that makes them able to see guild but not type in it. Make sure the warning is public, your people in guild that matter, know exactly what is expected of them. Warn them if there friend doesn&#039;t knock it off hes on the path to a gkick. Don&#039;t make exceptions just cause he knows someone thats unfair to your guild and annoying to you.</description>
		<content:encoded><![CDATA[<p>Your hands aren&#8217;t tied. Weather there a friend of someone in the guild or not the only whose got a right to yell at the raid is a raid leader gm, or mabe an officer. Anyone else gets a warning then they get globally muted in vent, and or Bound and gagged in guild. This is a rank in my guild chat that makes them able to see guild but not type in it. Make sure the warning is public, your people in guild that matter, know exactly what is expected of them. Warn them if there friend doesn&#8217;t knock it off hes on the path to a gkick. Don&#8217;t make exceptions just cause he knows someone thats unfair to your guild and annoying to you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

