A few alternative ways to tweek CWDT
We all know the gem is in kind of an awkward spot and is more than likely still being altered with different iterations. I have given this gem and avenues of balancing it much thought. Here are my two cents, which could be combined or taken separately with current given variables adjusted accordingly.
1. Calculate the damage taken before mitigation is applied. (This is my favorite i.e Thornmail from League of Legends.) This could be armor/endurance charges, but not dodge/blind as they are avoidance and not mitigation. 2. Less scaling on the damage required to proc at all ranks. 3. Increase the amount of time between procs as the gem levels up. 4. Allow the skill linked to be used, but excluded from the que for next proc if that skill has been used since the previous proc. 5. Edit the level requirement of the gem restriction to be the gems 1-20 level instead of the level required to use it. (I know this may lead to balance problems in the gems current form but this may be an option available if other variables were changed.) 6 (Make Cast on Melee Kill not required to be linked to the skill you kill with and then please apply similar restrictions and guidelines to it, because as it stands its uses are VERY limited.) 7. Keep up the fantastic work, your game is what D3 wishes it was. This thread has been automatically archived. Replies are disabled.
|
![]() |
Stop trying to change the trigger gems and make them OP again.
|
![]() |
I'm not, they are in an awkward place atm.
|
![]() |
I believe if you apply the damage taken before mitigation and change the values required this gem could easily be balanced for tanky players to use it at higher levels, and that would seemingly be what it was intended for. CWDT is after all a strength gem so many characters lacking in str would seek to not level it anyway for this reason, and these characters are usually also not allocating stacked mitigation into their priorities. I just seek a more balanced approach to this gem because it feels gimmicky to not level it up when I feel my build should support it at a high level.
|
![]() |
Nevermind this thread. I figured something out.
|
![]() |