Supersnake_Lx wrote: »I play Templar and I think that is a good thing. It bugged me because gap closers should be dodgable.
david.haypreub18_ESO wrote: »The latest PTS patch notes don't have much for Templars, but they do have this gem:
•Focused Charge: The damage from this ability and the Toppling Charge morph can now be dodged.
No fix to the Global Cool Down on the skill, of course, or any of the other bugs afflicting it; but they did at least have time to apply a nerf to the skill!
No one here understands the concept of low hanging fruit?
If this change was simpler to perform and test than the other changes, or they were already changing related objects, they could have tackled this change as a easy win. In software development this often happens; has little to do with prioritization. A complex but more critical change will take a while to properly fix and test, if during that time there is opportunity to quickly and surgically clean up small easy changes (the low hanging fruit), there is no reason not to do so.
Arm chair developers need to relax; they obviously don't understand the processes involved.
No one here understands the concept of low hanging fruit?
If this change was simpler to perform and test than the other changes, or they were already changing related objects, they could have tackled this change as a easy win. In software development this often happens; has little to do with prioritization. A complex but more critical change will take a while to properly fix and test, if during that time there is opportunity to quickly and surgically clean up small easy changes (the low hanging fruit), there is no reason not to do so.
Arm chair developers need to relax; they obviously don't understand the processes involved.
WalkingLegacy wrote: »They do not know how to fix the code for this ability. Copying and pasting from 2handded charge is too difficult.
No one here understands the concept of low hanging fruit?
If this change was simpler to perform and test than the other changes, or they were already changing related objects, they could have tackled this change as a easy win. In software development this often happens; has little to do with prioritization. A complex but more critical change will take a while to properly fix and test, if during that time there is opportunity to quickly and surgically clean up small easy changes (the low hanging fruit), there is no reason not to do so.
Arm chair developers need to relax; they obviously don't understand the processes involved.