This project is read-only.

2.2.27 Shadowpriest error

Topics: Rawr.ShadowPriest
Nov 15, 2009 at 7:06 AM
Edited Nov 15, 2009 at 7:08 AM

The last version of Rawr I used prior to downloading v2.2.27 was v2.2.19. I've notice some major differences for shadow priests. In v2.2.19, if I upload my character and select only to use self buffs, Rawr tell me that I should be able to sustain around 4.6k dps, while in v2.2.27, it says I am only able to sustain around 3.9k dps. I have made absolutely sure that all gems, enchants, and buffs were the same in each version.

On a heroic boss dummy, I am able to easily sustain around 4.6k dps self buffed, so obviously the 3.9k dps from v2.2.27 is wrong. There are a couple of things I noticed that may be the cause of this error:

1. Devouring Plague higher than Mind Blast in the Spell Priority list. I realize that in WotLK 3.3, with enough haste, this may become a reality. However, the fact of the matter is that right now, the spell power coefficient for Mind Blast is more than twice that of Devouring Plague (per tick). Mind Blast is far superior.

2. In v2.2.27, I noticed that the castlist did not include Shadow Word: Pain, I don't know if that's because the castlist doesn't include the opener, but if SW:P really is being left out, that's definitely a major contributor to why the new version of Rawr's calculation for shadow priests is so off.


Another thing I noticed that Rawr calculates incorrectly is that it stacks buffs which do not stack in the game. For example, Moonkin Aura (5% crit increase) and Focus Magic (3% crit increase) or Improved Scorch (5% crit increase) and Heart of the Crusader (3% crit increase). I don't know if this "error" was actually intentional for some reason, as it hasn't been changed after many versions, but I thought I'd bring up just in case.



Nov 15, 2009 at 2:51 PM
Edited Nov 15, 2009 at 2:52 PM

Did you remember to set the slider for Movement DPS loss to 0?


There are 2 new sliders under options that lets you tell how often you move and for how long you move each time. Setting the time you move to 0 will be more realistic to a training dummy. Also you can change the Priority list yourself if you wish to do so.


Also note that the model does not currently include the DPS gain from using ShadowFiend. On the todo list.

Nov 15, 2009 at 6:45 PM

Also, two other things... First, your expectations about buff stacking are way off. The correct categories that involve spell crit are: [5% spell crit to raid, Moonkin Aura/Elemental Oath], [3% spell crit to single character, Focus Magic], [3% all crit taken by target, Heart of the Crusader, Master Poisoner, Totem of Wrath], and [5% spell crit taken by target, Improved Scorch, Improved Shadow Bolt, Winter's Chill]. Note that that's exactly how they stack in Rawr.

Second, just curious, I sometimes hear of cases such as yours, where you keep using old versions of Rawr, long long after new versions are released (waiting til .27 to upgrade from .19). We'd really like to improve this situation. Can you comment on why this is? Why don't you upgrade as soon as it tells you there's an upgrade (or does it not tell you there's an upgrade)? Do you expect that upgrades don't matter? Is it too much inconvenience to upgrade? etc? Again, just want to understand why people do that, so that we can help try to solve that problem.

Nov 15, 2009 at 8:35 PM

Here is my own personal reason for not upgrading sometimes to the latest Rawr version; maybe it will help you out as to why some others don't upgrade as well. I only upgrade when I see in the change log that the modules I use are updated, otherwise I wait until i'm 5 or more revisions behind usually. This is because I personally like to edit or create items either from the PTRs or to test some ideas out. The issue with PTR items could be potentially fixed if Rawr could grab item stats from mmo-champion's database as well since they're almost always the first to find new items, whereas wowhead requires people to actually see the item firsthand before adding it to their database.

Nov 15, 2009 at 9:14 PM

If you wish to simply preserve your existing item data cache, you can upgrade to the new version, and then simply copy over your pre-existing item cache into location of the new Rawr, replacing the premade cache that comes with the new version.

We've discussed importing MMO-Champ's database in the past. but the issue is that there isn't any data to be had from there.  While the Armory and Wowhead store each line of data about an item, MMo-Champ only stores an image (.jpg) of the stats, so there are no stats to grab from MMO-Champ.  Now, this may have changed, but I don't believe that's the case.

Nov 16, 2009 at 6:24 AM

Err, that's incorrect about MMO-Champ's db. They have full data, I believe there's a way to get xml data, and their dev has even posted here, saying to let him know if we needed any changes. We simply haven't gotten to building an MMO-Champ import, since it's low priority at the moment.

Nov 16, 2009 at 6:47 AM

I'm very sorry -  stand corrected!

Nov 18, 2009 at 11:13 AM

I'm an MMO-Champion Administrator I'll have a chat with Boubouille about their database and how we might get data from it. It would give me something to do at work as work machine can't have Silverlight stuff on it at present due to need to maintain old code for work purposes. Thus all my Rawr3 work is laptop or home PC.

Nov 18, 2009 at 3:24 PM
Astrylian wrote:

Second, just curious, I sometimes hear of cases such as yours, where you keep using old versions of Rawr, long long after new versions are released (waiting til .27 to upgrade from .19). We'd really like to improve this situation. Can you comment on why this is? Why don't you upgrade as soon as it tells you there's an upgrade (or does it not tell you there's an upgrade)? Do you expect that upgrades don't matter? Is it too much inconvenience to upgrade? etc? Again, just want to understand why people do that, so that we can help try to solve that problem.

I'll chime in on the "why not update every version" question.

Personally, I only use the Feral modules.  So each time there's a new version, I check for relevant updates, and if I don't see any I generally skip it.  Since the cat and bear models are updated frequently, I'm not usually very far behind.  The main reason for not upgrading more often is that it takes too long.  The download is fairly quick, but upzipping the archive takes a long time mainly because of all the item images.

Nov 18, 2009 at 4:35 PM

Seriously? 2-3 minutes to unzip on the *very high end* for a *really slow* machine is too much for you? o.O

The biggest argument against updating 'only when the model you use has notes on it' is that the base code ALWAYS has updates and those updates can and will affect every module. That and Astry of course doesn't every single note from every single commit, he just kind of throws a summary up there. He does this as DPSWarr's notes alone are sometimes several pages for a single version, not to mention the other models.

Nov 18, 2009 at 6:38 PM
Edited Nov 18, 2009 at 9:10 PM

Jothay, I personally think that it takes far too long to unzip Rawr as well. The biggest problem is there are over 4000 files in the Rawr folder due to the large nunber of 1-2k image files, the OS is a major bottleneck in creating this large number of small files (especially using the zip file decompression built into windows). Every time I download a new release of Rawr I get frustrated due to this.



Nov 18, 2009 at 7:14 PM

The images never change; you don't need to extract them.  In fact, all you really need to extract from the data files are the DLLs.

And Jothay, it's not 2-3mins to unzip on the high end for a really slow machine.  It takes me 5mins to unzip on my gaming machine while WoW is running.  Admittedly, it's not super-high end, but it's enough that I get 50-60fps in 25man raids with graphics set mid to high.

I do agree that people really should be updating at least the dlls for every release.  We could have a "full download" and a "patch", where the full download is what we've currently been releasing, and the patch is just the DLLs and changed xml files.

Also, since people are worried about their custom items or filters, we could have separate xml files for user changes versus base.  Have a ItemFilterBase.xml and an ItemFilterCustom.xml, ItemCacheBase.xml and ItemCacheCustom.xml (where custom overwrites base whenever there are conflicts).

Nov 18, 2009 at 7:19 PM

Even so, I really don't understand the complaint. You start the unzip, it does its thing, it finishes. Even if it took an hour how is that frustrating? You can still run the previous version until it's done unzipping the new one if you have to have something on screen right that second. This is also kind of a moot point when it comes to Rawr3 since that will be out of a browser (with optional system install).

Nov 18, 2009 at 7:34 PM

If you really want me to make a list about all the reasons why this is bad, I can...but this is Software Engineering 101.

  1. The user loses interest while waiting
  2. It takes resources to unzip all these files, which can affect game experience if running while playing
  3. If you are unzipping to the same directory, you can't have the old version running or you'll mess up the update when in-memory and on-disk doesn't match
  4. If you are unzipping to a different directory for some weird reason, you need to wait for it to finish unzipping before updating your shortcut to the new directory, and by the time it's done you've likely forgotten
  5. Updates should be patched into existing directories, and should only patch in things that have changed.  What if blizzard made us download and install the entire contents of Vanilla and TBC, all the Naxx/Ulduar/ToC files for every patch?  Even if it let us login while we wait, it doesn't make sense to force the user to download and install things that haven't changed.


Nov 18, 2009 at 8:00 PM
Edited Nov 18, 2009 at 8:11 PM


Nov 18, 2009 at 10:08 PM

I was finding that the Windows unzipping was very slow on my work PC (which is a bit old).   I switched to 7-zip ( and it unzips in about 30 secs now.   There are plenty of free unzipping programs which are probably more efficient for older PC's to use.



Nov 19, 2009 at 7:56 AM

Unzipping a fresh copy of Rawr 2.2.17 into a fresh directory runs between 10-13s for me, using 7-Zip, over the course of three test extractions.

Nov 19, 2009 at 8:18 AM

Most users will not be using 7-zip, the vast majority of them will be using the windows built-in zip extraction.



Nov 19, 2009 at 8:35 AM

Would be nice if download was only assemblies, config, modules, etc (everything not in the images directory).  Upon unzipping and running Rawr.exe, the program compared local ancillary files (images) and downloaded missing ones from server.

Nov 19, 2009 at 8:35 AM

I'm not concerned about things that we already have solved in Rawr3, like images, or unzip time. Keep em coming though!

Nov 19, 2009 at 10:45 PM

Is there an "Under Development" page where we can read and salivate over all the cool new things coming in Rawr3?  I searched around but failed to find anything.

And actually, I forgot the other thing that prevents me from updating more often... the gem templates.  These appear to be saved separately from your character, which means that when I create my new Rawr 2.2.28 folder, it comes with the default templates, not my modified templates.  So I have to go in and update them to make sure all my options are covered.  This is much better now that the defaults use the Epic gems, but it's still extra time.

Just for your reference, here's the steps I take when I decide to update:

0) press the "get new version" button in Rawr

1) download the file to my Downloads folder

2) navigate to the Downloads folder, open the zip file, CTRL-C to copy the compressed file

3) navigate to my Programs folder, hit CTRL-V to uncompress the file to the correct location

4) edit my desktop shortcut to refer to the new location

5) open the new Rawr, open my Bear saved character (using the Open menu, since the "recent character" list has been cleared)

6) check the gemming templates

7) make sure nothing else changed that would cause Rawr to give me bad results (meaning new options I need to check, not Rawr bugs)

8) repeat steps 5-7 for my Cat saved character

Each individual thing doesn't take long, but I'd estimate it takes me about 10-15 minutes to switch versions, and it's a bunch of steps, not a start it up and come back later thing.  It's not a big deal when there's updates I think are meaningful to my characters, but I'm not going to do it if the only changes are to models I don't use.  In an ideal world, steps 0 and 7 would be all would be required.

To be perfectly honest, as a user this doesn't really concern me much.  The program is great and I don't mind being a few versions behind.  But you asked, so there you are.