<?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: Nerdrage and How to Deal With It</title>
	<atom:link href="http://blog.cold-comfort.org/nerdrage-deal/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cold-comfort.org/nerdrage-deal/</link>
	<description>Guild Management and Leadership in WoW</description>
	<lastBuildDate>Fri, 13 Aug 2010 11:51:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Malevica</title>
		<link>http://blog.cold-comfort.org/nerdrage-deal/comment-page-1/#comment-119</link>
		<dc:creator>Malevica</dc:creator>
		<pubDate>Thu, 22 Oct 2009 11:42:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cold-comfort.org/?p=731#comment-119</guid>
		<description>Well, this is something I&#039;ve had to handle in the past, more frequently recently although I&#039;m not sure whether that&#039;s a guild thing or a game thing. It&#039;s something I&#039;m personally aware of because as a result of my occupation I&#039;m relatively good at constructing impressive-sounding, well-referenced arguments and I&#039;m not afraid of walls of text, which can intimidate people. So I&#039;ve learned to resist the urge to &quot;demolish&quot; people&#039;s points. 

A couple of examples then.
Having a close-knit guild we ran with a priority-based (main&gt;off, raider&gt;trial) roll system for loot with people often agreeing to pass for the greatest need. This worked well, but the nature of the rng and loot tables meant that some people had dry spells from time to time. One raider who was a long-time member got frustrated with this. A key part of managing this person&#039;s concerns was to PM him an extract of the EQDKP table for the guild listing drops per person, usually showing him on par with the others of his class. We never used the DKP scores, and never made the existence of the site public, but we still gathered and held the information so that if someone raised concerns we could check their validity and reassure them if needed. It was very tempting to write this person off as a &quot;lootwhore&quot;, but people have short memories and so returning to the facts helped in this case. 
The other example concerns a member who was hugely indignant about being accused of ninjaing blues in a PuG. This one didn&#039;t turn out very well, partly because of language issues, but when one of our officers approached the raider about the issue the phrase he kept using was &quot;I don&#039;t care if you did it or not, you just need to apologise&quot;. Exactly your early point, to the player the key issue was that they didn&#039;t believe they&#039;d done anything wrong, while the officer was looking at how to get a resolution. After this, we quickly pushed out a &quot;quick guide to dispute resolution&quot; to the officers, which seemed to help a bit. 

A general point about the generation of guild nerdrage is that leaders and officers often forget that members do not get to see officer chat or officer forums, so if you&#039;re not transparent enough it can appear that nothing&#039;s being done about the concerns of the membership. Moving from founding officer to member recently has definitely brought that home to me.</description>
		<content:encoded><![CDATA[<p>Well, this is something I&#8217;ve had to handle in the past, more frequently recently although I&#8217;m not sure whether that&#8217;s a guild thing or a game thing. It&#8217;s something I&#8217;m personally aware of because as a result of my occupation I&#8217;m relatively good at constructing impressive-sounding, well-referenced arguments and I&#8217;m not afraid of walls of text, which can intimidate people. So I&#8217;ve learned to resist the urge to &#8220;demolish&#8221; people&#8217;s points. </p>
<p>A couple of examples then.<br />
Having a close-knit guild we ran with a priority-based (main&gt;off, raider&gt;trial) roll system for loot with people often agreeing to pass for the greatest need. This worked well, but the nature of the rng and loot tables meant that some people had dry spells from time to time. One raider who was a long-time member got frustrated with this. A key part of managing this person&#8217;s concerns was to PM him an extract of the EQDKP table for the guild listing drops per person, usually showing him on par with the others of his class. We never used the DKP scores, and never made the existence of the site public, but we still gathered and held the information so that if someone raised concerns we could check their validity and reassure them if needed. It was very tempting to write this person off as a &#8220;lootwhore&#8221;, but people have short memories and so returning to the facts helped in this case.<br />
The other example concerns a member who was hugely indignant about being accused of ninjaing blues in a PuG. This one didn&#8217;t turn out very well, partly because of language issues, but when one of our officers approached the raider about the issue the phrase he kept using was &#8220;I don&#8217;t care if you did it or not, you just need to apologise&#8221;. Exactly your early point, to the player the key issue was that they didn&#8217;t believe they&#8217;d done anything wrong, while the officer was looking at how to get a resolution. After this, we quickly pushed out a &#8220;quick guide to dispute resolution&#8221; to the officers, which seemed to help a bit. </p>
<p>A general point about the generation of guild nerdrage is that leaders and officers often forget that members do not get to see officer chat or officer forums, so if you&#8217;re not transparent enough it can appear that nothing&#8217;s being done about the concerns of the membership. Moving from founding officer to member recently has definitely brought that home to me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
