This project is read-only.


Topics: Rawr.Base
Sep 5, 2010 at 2:59 AM

We're getting a rash of people that apparently can't follow the Posting Guidelines:

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, 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 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
  7. If you are requesting a feature, follow the feature request format found here: Feature Request Format Guide
  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.




Sep 5, 2010 at 3:44 AM

Seriously. People, the posting guidelines are for your own benefit. Even if it's your first time here, and you just want to let us know about something, or ask something, or think you're being helpful or reasonable... You're not, if you don't follow the posting guidelines. We really do need you to follow them, in order to help you.

Sep 5, 2010 at 10:34 PM

In case you guys don't believe me, here's an example of what we're talking about:

Shadow Priests in the current version have an issue with the Spell Hit Calculations. The percentage is wrong due to a formula change. Now we've already fixed this but here are each of the tickets that have been created regarding this issue:

That's 5 separate tickets because people didn't search both open and closed tickets for the same issue. The original (18564) was marked as fixed on the 26th, but they just kept on coming.

Remember, the more time we spend going through stuff like this, the less time we have for actual development and issue resolution.

Sep 6, 2010 at 12:52 AM
Edited Sep 6, 2010 at 12:54 AM

Maybe it would be a good idea to keep an upcoming fixes log?  You know, besides looking at the Source Code page and having to search through that...or something :P  I dunno..yeah, there is the Source Code page that says what's getting fixed/changed/etc, but since it's called the "Source Code" page, it's not really the go-to place for those things.

Also, I don't know how hard it is, but maybe doing weekly compiles and releasing a new version would help calm things down.  The last version was released on 8/23 (Mon), bug fixed on 8/26 (Thur), and those four dup. reports all came out after 8/29, which would have been one week after the last full build release.

There's no denying that the program is popular, but some bugs really do make the program useless until we get the next version.  The Priest spell hit thing being sense in trying to Optimize for the proper hit gear and maximizing DPS if the thing's broke.  You can't limit pushing out immediate updates just on program crashing bugs alone...if a module is broken in such a way that it defeats it's purpose, there should be an almost immediate turn around on pushing out a fix and releasing it.

Sep 6, 2010 at 2:09 AM

We pretty typically release every 2 weeks.