I take it the site is down for everyone? Getting a 502 Gateway error here.

Is there any way to add the heroic version of the Obsidium Cleaver axe to the spreadsheet to see how much better it is than the regular Gatecrasher? It'd be nice to see some numbers to compare the benefit of doing that verses someone upgrading a relic etc.

Since both weapons have identical dps and differ only in the allocated stats, you can approximate the difference, by calculating your dps with a heroic Gatecrasher and then replacing Agility gems worth 200 Agi on your equip with Strength gems (Bold Inferno Ruby).

If I did it right, in your case, heroic Obsidium Cleaver is only about 110 dps better than normal Gatecrasher and thus really not worth wasting a firestone.

I have used the search function so my apologies if this has already been answered. I am questioning if Shadowcraft currently has the right calculations for the engineering tinker on gloves.

With my current gear set I have an estimated 34507 dps. When I replace the wrist enchant and lose 80agility I drop to 34171, a 336 drop. When I then tick the 'engineer box' on professions it goes up to 34341 an increase of 170dps. Considering it is 480 agility for 10s/60s it should, at worst, achieve an 80agility average, yet Shadowcraft is valuing the tinker close to half this value.

Am I doing something wrong or are the values incorrect?

Seems to be working for me, also running 6.0.2 - You possibly have an addon running that's blocking scripts?

The only bug in the talents that I'm aware of is that, when resetting talents, it will let you pick talents mid tree: the 5 talents per tier check is reset after the first talent is picked. Not beign able to edit talents is something that has never occured to me and, as pointed above, it might be a problem on your end. The exceptions, however, are a bit funky: cycle selection is something the front end won't let you do, because it should do it on its own (a cycle, for the engine, is a middle-man object as to say):

The engine has a variety of safety measures in place to ensure that the talents make some sense to the modeler. Some checks, like the 31 talents in a tree, are done only once, when the talents object is built, instead of every time we change talents: the reasoning behind this is that the engine needs to swap talents in and out to compute the ranking, so we use at some points specs that the game won't let you have, like having less than 31 talent points in a tree, or more than 41 total, or less than 5 talent points per tier, etc. Ultimately this leads to us only being able to throw the 'must specify cycle to match spec' exceptions (that's almost the last check before runing the modeler) instead of 'must have at least 31 talents spent', which would be a little more helpful. Now, we could refine it a bit, so we check spec consistency at certain key points, but I'd say the cycle exception has proved to be enough to let the user figure that something is not quite right.

The 'notices' section in the front-end is a log of exceptions, so you can browse what went wrong all through the sesion. It pops up every time the engine complains and won't go away until you perform a log related action, like running the optimizers (which add stuff to the log section), or choosing a stock or catched spec (which resets the log). If anything, I'd like the notices to be shown in reverse (last exception on top) but I don't particularly see that as much of an issue.

Weird. It appears to be a conflict with the "All-in-One Gestures" addon, I assume because that addon intercepts right mouse clicks for its own purposes.

As for the cycle error, now that I know what it is trying to communicate, it makes a little more sense to me. I agree, though, a better message might be less confusing, since the current one makes it seem like the user is supposed to select a cycle somewhere, rather than just that the user needs to continue selecting further talents until some internal threasholds get met. It's also a little hard to figure out when you've gotten to that threshold and are no longer throwing errors, because by this point your error list might be 30 lines long. Even if you did reverse order, it might not be easy to tell that you've stopping throwing new ones.

Nope. I haven't pushed any code changes recently.

I've found that when I switch to combat, then reload from armoury it doesn't change my glyphs. This would give roughly the damage swing you've seen (assassination with the wrong glyphs). So check your glyphs are correct in both specs when comparing dps. I can't think of anything else that could be causing this.

Perfect, that was the issue. When I refreshed from the armory it didn't refresh my glyphs properly and I didn't notice.

Thanks!

I find this may be a stat question moreso than an issue with Shadowcraft itself, but I received Matrix Restabiliser tonight and came across the following issue:

1. Un-equip Fluid Death and equip Matrix
2. Gain 300 odd dps
3. Auto-reforge (this then re-forged my Weaps, Cloak, Bracers and gloves to increase my hit back up to 1332)
4. Loss of approx 85 dps

Given that the spell hit stat weights appear to be static, shouldn't gaining this hit rating back up to the spell cap be a dps increase?
I don't understand how replacing crit and expertise on those items with hit would be costing me dps. If shadowcraft is correct, it's suggesting I run at below hit cap as optimum reforging.
If anyone could shed some light on this, it would be much appreciated!

Edit: After some further fiddling, it seems to be whenever I fall below a Mastery rating of approx 1466, it nets me a massive dps loss (approx 100 - perhaps not massive, but considerable in regards to reforging).
If this is true, is there a plateau of mastery I'm not aware of that we should be reaching before the spell hit cap?