Posting Guidelines

In order to streamline the communication between you (the end user) and us (the Rawr developers), we've setup these posting guidelines. When posting to our Discussion board or Issue Tracker, we ask the following things from you:
  1. You put as much time and effort into searching previous issues and discussion topics as you want us to spend addressing your issue. A large number of the questions that are asked have already been answered when they were asked previously. Not only will it save us the time of readdressing the issue repeatedly, you can typically find the information in much less time.
  2. You make an effort to use proper English, including correct capitalization and punctuation. Avoid "leet speak", excessive non-traditional abbreviations, and other such nonsense. We understand that not all Rawr users are native-English speakers, and will do our best to understand you, when you do your best to be understood.
  3. You keep your conversation civil and polite. If you disagree with something that has been posted, support your point of view with analysis, extensive testing to prove you've put some time and thought into it.
  4. You only create a new post if you have something to discuss. If a topic has been spoken about previously, please post in the existing thread rather then starting a new one.
  5. If you are having general problems with Rawr, such as it not launching, Armory import issues, etc., please read this: Troubleshooting
  6. If you are reporting a bug, follow the bug report format found here: Bug Reporting Format Guide and only post it to the Issue Tracker, not Discussions.
  7. If you are requesting a feature, follow the feature request format found here: Feature Request Format Guide and only post it to the Issue Tracker, not Discussions.
  8. If you don't understand why Rawr is telling you to gem, enchant or gear a certain way, please read this: I Don't Understand Why...

Bug Reports go in the Issue Tracker!

We want the discussion boards here to be a forum for discussion on theorycrafting, programming and well, Rawr. By following the above guidelines, hopefully your questions will be answered quickly and effectively. Failure to abide by these rules will result in your posts being linked to this page as a response and being otherwise ignored by the staff of this project.

Last edited Apr 6, 2011 at 4:58 AM by Jothay, version 17

Comments

Rtsrman3911 Apr 11, 2011 at 3:19 AM 
Hello. When I open Rawr and use "load from battle.net" I get the following error message, just on two toons that I'm trying to bring up :[Arg_NullReferenceException]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.60129.0&File=mscorlib.dll&Key=Arg_NullReferenceException.

Also, this is what comes up in Stat trace:
at Rawr.DK.AbilityDK_Base.get_TotalThreat()
at Rawr.DK.Rotation.BuildCosts()
at Rawr.DK.Rotation.PRE_Unholy()
at Rawr.DPSDK.CalculationsDPSDK.GetCharacterCalculations(Character character, Item additionalItem, Boolean referenceCalculation, Boolean significantChange, Boolean needsDisplayCalculations)
at Rawr.UI.MainPage.character_CalculationsInvalidated(Object sender, EventArgs e)
at Rawr.UI.MainPage.set_Character(Character value)
at Rawr.UI.MainPage.bnetLoad_Closed(Object sender, EventArgs e)
at System.Windows.Controls.ChildWindow.OnClosed(EventArgs e)
at System.Windows.Controls.ChildWindow.Close()
at System.Windows.Controls.ChildWindow.set_DialogResult(Nullable`1 value)
at Rawr.UI.BNetLoadDialog._armoryService_GetCharacterCompleted(Object sender, EventArgs`1 e)
at Rawr.Rawr4ArmoryService._webClient_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)

I have looked everywhere and cannot find anything on this. Any help would be appreciated :-), thanks!

Astrylian Jun 28, 2010 at 7:20 AM 
We do not read comments on wiki pages. Please follow the Posting Guidelines, so that we have a chance to help you.