Before I begin, I must mention a few things. First ([b]1[/b]), the goal of this post is to resolve the issues involving Code of the Devastator in order to improve and/or fix PvE and PvP issues and viability. Second([b]2[/b]), this post is an extended version of my previous post on this subject, since the first was mostly rushed. Third ([b]3[/b]), some may not know that the throwing hammer's ability to activate health regeneration requires the hammer to have hit an enemy before you retrieve it. Fourth ([b]4[/b]), I'm not taking exotics into account since all subclass trees should be at least decent in both PvE and PvP. Fifth ([b]5[/b]), any combination and/or modifications of my suggestions would be fine as long as Code of the Devastator's PvP viabilty is improved, where it is most sorely lacking. [u]Issues with Code of the Devastator[/u] [b]Roaring Flames[/b]: In PvP, it is rare you'll get an ability kill to get a 1x stack and even more so to stack it to 3x. Even if you reach that point, you'll only have an abysmal upgrade to ability damage as a reward (even though the tree is built around it). Then you have only 15 seconds, which runs out a lot faster than you think, so it doesn't have and see nearly as much effectiveness and utility as you'd think. [b]Throwing Hammer[/b]: First ([b]1[/b]), the hammer can be very difficult to keep track of since it'll bounce wherever it wants, especially in the middle of a chaotic battle. The hammer's direction and distance from the bounce will be practically unpredictable, so it could end up off the map, in an unreachable nook, or in the middle of enemies. Second ([b]2[/b]), once your hammer explodes after you scrambled around to find it, you'll have been crippled since your subclass tree is practically built around it since you won't be able to easily use Roaring Flames, since grenades are the next best choice but have a long cooldown. Third ([b]3[/b]), in PvP, it's not very rewarding getting a kill with it since you'll have to retrieve it where it'll likely be in a place an opponent will easily gun you down or just be straight up lost. Fourth ([b]4[/b]), when a bunch of thrall or warbeasts charge and chase you, you'll throw your tiny hammer into the crowd only to kill 1, maybe 2 if you're lucky, and immediately after which you'll be reminded as to why this subclass tree is undeserving of its title of "Code of the Devastator" (to which Code of the Fire-forged is more deserving). [b]Super[/b]: In PvE, I believe the the super's damage and its overhead slam is fine as it is, but most of its issues are in PvP and tthe spin move. First ([b]1[/b]), in PvE and somewhat in PvP, the overhead slam's fire tornado will launch most enemies in the air (large enemies, such as ogres, won't be affected), where you'll have your combo broken and have to chase after your bouncing foe while wasting your super. Second ([b]2[/b]), in PvP, the burning maul super has no way to attack in-air targets, with the slam having no melee lunge and tracking and the spin having almost no range, sad damage (a giant two-handed warhammer can't even kill a normal guardian in 1 hit, instead 3 - 5), no tracking, and no melee lunge. In PvP, all enemies have to do is just spam jump and stay above you as you waste your super and look like a fool, since spin is unreliable and a waste and the slam is ground-based and slow. Third ([b]3[/b]), the spin itself is a detriment to the super. It's a useless move that does the same job as the slam but worse, since it consumes more super energy, can't be used for mobility since you get barely any boost, and as mentioned before, the spin has terrible damage, no tracking, very short range, and no lunge. [u]Solutions to Code of the Devastator's Issues[/u] My presented solutions will numerically correspond with the issues above. [b]Roaring Flames[/b]: Increase the timer from 15 to 20 seconds to allow players the time necessary to get proper benefits out of it and increase its effects in PvP, since only 30 more damage to your hammer at 3x Roaring Flames is ridiculously bad. [b]Throwing Hammer[/b]: First ([b]1[/b]), add an indicator pointing to your hammer and (optional) allow the ability to see your hammer through walls. Second ([b]2[/b]), increase the time it takes for hammer to explode and the pick-up range. Third ([b]3[/b]), include the ability to summon your hammer from anywhere but only after getting a throwing hammer kill (after recalling, either allow health regen to still proc or give only a bump of health). Fourth ([b]4[/b]), have enemies killed by the throwing hammer explode (similar to dragonfly/firefly). [b]Super[/b]: First ([b]1[/b]), replace the fire tornado's ability to vertically launch enemies with the ability to pull in nearby enemies, as a tornado would typically do. Have the pull be stronger the closer you are to it. This wouldn't be OP as long as the pull-in range it has isn't ridiculous, since the fire tornado itself already doesn't last long and is incredibly noticeable and avoidable. Plus, it would help in getting Roaring Flames activated. If it's still too much, then just get rid of the launching mechanic and we'd be fine. Second ([b]2[/b]) and third ([b]3[/b]), replace the spin move with an uppercut dash move, similar to Suncharge of D1, just with not as insane tracking/lock-on and damage (Suncharge could OHK supers). The only exception would be if 3x Roaring Flames is active, in which supers could be OHK. Normally, this uppercut dash should have enough damage to OHK normal guardians (as a melee super should have), medium range (as much as Suncharge), reliable lock-on/tracking (as a melee super should have), at least the same super energy cost as the spin, and get rid of the ability to spam and chain it back to back like the spin. This would allow some form of mobility and a counter to in-air targets, while not replacing the slam and being able to inherently OHK or overpower supers (except if at 3x Roaring Flames).