The original poster may have an issue with most proposed warrior stat priorities. I have an issue with the assumption that shield block is a go-to ability that we should use a lot.
Tengenstein is correct in the stat value posted in #39, but though it has been voiced a couple of times in this thread it seems most commenters are happy to completely ignore the question: Should you be using shield block?
Consider it please - what does shield block do? What does it not do?
Consider this also - feel free to go back to http://sacredduty.net/2012/09/18/l90...tion-followup/ and read through the entire thing. One thing I'm pretty sure you will not find is any consideration that the damage scenarios that are being theorycrafted are anything other than 100% blockable. In other words, the conclusions are pretty good in the scenario where 100% of dmg coming at you is possible to reduce with blocks and crit blocks.
This is not really how raid fights work out these days. I don't have an issue with Theck deciding to take a limited view of things - because the assumptions and restrictions you make is what makes the modelling possible - and it's such a valuable thing to have that I'm happy to read it. But when you want to use these kinds of theorycrafting results to make decisions about how to gear your tank it's necessary to understand the limitations of the model.
So the first thing I do when facing an encounter is ask myself this: Is this one fight where the damage is overwhelmingly (near 100%) physical and blockable? Because if it is - this would be a fight where I should consider being fully mastery speccing and using shield block on cooldown. I'm not saying it's a given - in that fight I might STILL choose to use shield barrier over shield block - but a 100% blockable fight I should at least consider using shield block on cooldown.
If the fight is not 100% blockable - why should I even consider using shield block?
Ok, that's being a bit too direct. Shield block is a tool, and there are times and places where the tool is the right tool for the job. But the point is - due to the relatively large amount of non-blockable damage we have to at least question whether a DEFAULT choice to use shield block is correct.
The most interesting point made in this thread so far was made in post #21 by Tengenstein. The specifics of his point aside it partially addresses the "Why you should ignore magic dmg and consider only the physical damage" argument in SOME situations (the why to use shield block argument). There may be times when there is raid wide magic damage which healers are assigned to top up - where the tanks part of the raid wide magic damage is ignored in the healing/survivability stakes - because it's being automatically alleviated.
This is why I'm skeptical when I see suggestions to run simulations with "some" magic damage to see if it skews the value of certain tanking stats. The situations are never quite as simple as that.
To the specific point raised by Teng - I unfortunately do not have the logs from when I tanked Stone Guard 10m, but when I tanked it 25m I took 40k per rend flesh tick as he said and 20k per melee hit. Yes, 20k. Not 200k (or 180k). I'm not sure this is actually a good example of a place to use shield block, but as said - I completely accept that there may be fights where the survivability challenge is predominantly blockable and for those situations it's worth considering if shield block should be used (and reforged for).
It is possible to have a fight with 90% blockable and 10% magic dmg where the challenge to the tanks survival is predominantly from the blockable damage and shield block is in play. It is possible to have the same fight with 9 times the magical damage - where the challenge to the tanks survival from blockable damage is the same - the blockable and magic split is 50/50 and the increased vengeance makes shield barrier so powerful that shield block is again no longer really valuable enough to use.