Have read through more threads/pages than I can count regarding the topic here and over at battlenet forums and can't find any concrete proof on whether it is acceptable or whether it isn't. Virtually every post seems to be speculation and no valid evidence to support claims. While I see even the most popular streamers using the trick and still not banned after all this time, it still doesn't put my mind at ease.
The builds I find really appealing (like the Tals Woh build) requires insane button mashing, and I just cant justify playing it for very long if I'm having to smash multiple buttons 20 times per second in order for it to work. The logitech gaming software can also replicate the Numlock trick, but I remain cautious concerning if it's truly allowed or not.
If only Blizzard had included Autocast options, it wouldn't be an issue.
Numlock appears to be legit, but as always, using those things at your own risk.
I think the bigger issue is... why should this even be allowed to exist? Skills like EB and Condemn requires an unhealthy amount of spamming to optimize it. I would be in favor of increasing their cooldown while also increasing the number of blasts (for EB).
Numlock appears to be legit, but as always, using those things at your own risk.
I think the bigger issue is... why should this even be allowed to exist? Skills like EB and Condemn requires an unhealthy amount of spamming to optimize it. I would be in favor of increasing their cooldown while also increasing the number of blasts (for EB).
So, something like the Logitech Gaming Software set to replicate the Numlock trick wouldn't be legit?
As for the issue, I totally agree. It brings me back to pre-expansion when the Wizard had that similar button mashing build, the one where Crits reduced the cooldown of all skills (I believe it was Unstable Anomaly before it was re-designed).
I don't use numlock. I think that part of the skill in playing is to remember stuff like cooldowns. Even when I played WoW, only macros I used were for repetitive tasks.
I don't use numlock. I think that part of the skill in playing is to remember stuff like cooldowns. Even when I played WoW, only macros I used were for repetitive tasks.
It's not the same thing. If someone is waiting for an ability that has, say, a 30 second cooldown, then yes there may or may not be some skill involved in using your mind to keep track of the time, but for something like Explosive Blast which virtually has no cooldown using the proper gear, then there is no timing involved as it's only a matter of mashing the button to cast the skill as many times as you can.
Setting up a macro to cast a skill at certain times specified by the user I can see being an issue, setting a macro to just repeatedly cast an ability with little or no cooldown so you're not forced to suffer from hand and wrist strain, no.
I don't use numlock. I think that part of the skill in playing is to remember stuff like cooldowns. Even when I played WoW, only macros I used were for repetitive tasks.
It's not the same thing. If someone is waiting for an ability that has, say, a 30 second cooldown, then yes there may or may not be some skill involved in using your mind to keep track of the time, but for something like Explosive Blast which virtually has no cooldown using the proper gear, then there is no timing involved as it's only a matter of mashing the button to cast the skill as many times as you can.
Setting up a macro to cast a skill at certain times specified by the user I can see being an issue, setting a macro to just repeatedly cast an ability with little or no cooldown so you're not forced to suffer from hand and wrist strain, no.
I get that. I would rather see the ability changed so it doesn't require you to mash it though. I hate mashing buttons too. It's intention is nice, but execution is a little off (for skills you have to mash).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Have read through more threads/pages than I can count regarding the topic here and over at battlenet forums and can't find any concrete proof on whether it is acceptable or whether it isn't. Virtually every post seems to be speculation and no valid evidence to support claims. While I see even the most popular streamers using the trick and still not banned after all this time, it still doesn't put my mind at ease.
The builds I find really appealing (like the Tals Woh build) requires insane button mashing, and I just cant justify playing it for very long if I'm having to smash multiple buttons 20 times per second in order for it to work. The logitech gaming software can also replicate the Numlock trick, but I remain cautious concerning if it's truly allowed or not.
If only Blizzard had included Autocast options, it wouldn't be an issue.
Numlock appears to be legit, but as always, using those things at your own risk.
I think the bigger issue is... why should this even be allowed to exist? Skills like EB and Condemn requires an unhealthy amount of spamming to optimize it. I would be in favor of increasing their cooldown while also increasing the number of blasts (for EB).
So, something like the Logitech Gaming Software set to replicate the Numlock trick wouldn't be legit?
As for the issue, I totally agree. It brings me back to pre-expansion when the Wizard had that similar button mashing build, the one where Crits reduced the cooldown of all skills (I believe it was Unstable Anomaly before it was re-designed).
I don't use numlock. I think that part of the skill in playing is to remember stuff like cooldowns. Even when I played WoW, only macros I used were for repetitive tasks.
It's not the same thing. If someone is waiting for an ability that has, say, a 30 second cooldown, then yes there may or may not be some skill involved in using your mind to keep track of the time, but for something like Explosive Blast which virtually has no cooldown using the proper gear, then there is no timing involved as it's only a matter of mashing the button to cast the skill as many times as you can.
Setting up a macro to cast a skill at certain times specified by the user I can see being an issue, setting a macro to just repeatedly cast an ability with little or no cooldown so you're not forced to suffer from hand and wrist strain, no.