I saw a thread about this on Reddit and I thought I would bring the discussion to Diablo Fans.
It has recently been discovered that the simple act of clicking quickly versus holding your mouse down can significantly increase the attack speed with certain abilities.
I think it will be need to be fixed, not because of this example but because its very easy to get a script that sends 1000's of mouse clicks per click. So you would be attacking a lot faster than a normal "clicker".
God I hope this is fixed. Top youtube comment for that ended with "It doesn't affect Starcraft because the next attack is determined by a timer, not the end of an animation." If that's the case then why the **** didn't they do that with Diablo? Gameplay being preserved > drop in aesthetic quality from prematurely cancelled animations based on timers. SC2 clicking is godlike fast compared to Diablo so why didn't that game get a benefit from it? They should be making both games follow the same rules with attack speed as it pertains to clicking.
There's no skill involved in simply wearing out your fingers and mouse quicker so no additional combat benefit should be coming from this.
i only hold when i move, never when in combat so i never noticed this, but it is an interesting subject especially if it can sway the outcome of a fight (prob pvp).
would fixing it to where its like sc2 require a giant amount of work though? that seems like a fundimental mechanic and if it delays release i vote no lol.
Rollback Post to RevisionRollBack
D3anonymous
@Upgradez I could've faceplanted on the keyboard and still killed everything in act 1.
Yeah, I saw this bug when it was originally reported. I'm very worried that it STILL hasn't been fixed. This would be game breaking for me. You should not gain an advantage by clicking faster (or using a script). I'd prefer not to destroy my hands (and mice) playing this game.
It was reported, and sent to the Dev team to fix. This blue post was on march 23rd ... so 1 month ago... I overstated... sorry lol.
Aha, well apparently it has not been fixed yet, which I find quite surprising.
It's not game breaking... From what the metrics say.. its less than 10%
And it may have been fixed in the retail build.
As Sabvre says, it will be fixed in the retail build. The reason it probably hasn't been fixed yet is because you're playing a Beta which is there to test for these sorts of things. They then take the information gathered from the Beta build (which is probably many builds behind the release one) and correct the final build.
MAY be fixed. MAY.
We were told only a small patch at release. Don't expect a monster bug fix patch.
The beta is for testing. If they had a fix for this issue it'd be in there.... that way we could verify that it's fixed. How many times have they said a bug is fixed only for us to find out that is not the case? I highly doubt this issue is fixed atm.... it wouldn't make any sense NOT to include it in the beta.
The beta is for testing. If they had a fix for this issue it'd be in there.... that way we could verify that it's fixed. How many times have they said a bug is fixed only for us to find out that is not the case? I highly doubt this issue is fixed atm.... it wouldn't make any sense NOT to include it in the beta.
Not particularly. Now that the bug has been brought to their attention, and there are many reports and videos detailing it, the development team can now reproduce it and work on it behind closed doors with their advanced build. They don't have to change things in the beta at all, especially not in the Open Beta. The recent Open Beta Weekend was to test network infrastructure and server load, and to fish out smaller bugs which may not have been found previously.
Have faith in the Blizzard Development team that this will be fixed for launch. If not, it'll be in the first patch that they release.
Sorry, I don't have blind faith in Blizzard. How many builds have they said they fixed the multiplayer quest queue issue? The past 4 or 5 patches? Each time we report that it's still broken (aka, level 1's are put into lvl 13 games). Obviously the beta testers are more reliable than the internal guys. They'll put the fix in the beta when they have it.
I fully expect it to be fixed (and will be fairly outraged if they release with such a major known issue). The fact that it was reported a month ago and still no word on it worries me quite a bit personally.... but I worry about things The D3 development team has been.... pokey at best.
Beta is several versions behind what Blizzard is actually working with. They're not retarded contrary to popular belief. This won't be in release.
Not retarded but pretty much all of their games have suffered things gamebreaking in the live version. So I wouldn't put it past them to have this show up. It's a lot less jarring than the game crashing when you use a certain skill or everyone rubberbanding so they could have easily overlooked this by then or simply did not have it high enough in the priority list to have it fixed by 5/15. This is one of those things you have to pay attention to closely to notice (since it's only around 10%). It's still unintended (otherwise Blizzard wouldn't have said they were going to submit the report to their teams) thankfully, but most certainly could end up @ launch. It's not even in their Known Issues thread.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
It has recently been discovered that the simple act of clicking quickly versus holding your mouse down can significantly increase the attack speed with certain abilities.
This video demonstrates it:
http://www.youtube.com/watch?v=fgBt2e3905w
So, is this a bug? And if it is, is it significant enough to need to be patched? What are your thoughts?
There's no skill involved in simply wearing out your fingers and mouse quicker so no additional combat benefit should be coming from this.
Also nj on the vid OP
It was reported, and sent to the Dev team to fix. This blue post was on march 23rd ... so 1 month ago... I overstated... sorry lol.
It's not game breaking... From what the metrics say.. its less than 10%
And it may have been fixed in the retail build.
I bet there may even be people on this site who would consider 10% to be game-breaking.
Some people care only for the metrics.
--Jack Handy
would fixing it to where its like sc2 require a giant amount of work though? that seems like a fundimental mechanic and if it delays release i vote no lol.
@Upgradez I could've faceplanted on the keyboard and still killed everything in act 1.
-Funny troll tweet
MAY be fixed. MAY.
We were told only a small patch at release. Don't expect a monster bug fix patch.
Beta is several versions behind what Blizzard is actually working with. They're not retarded contrary to popular belief. This won't be in release.
They've pointed out several times their beta is an actual beta, not a demo.
Sorry, I don't have blind faith in Blizzard. How many builds have they said they fixed the multiplayer quest queue issue? The past 4 or 5 patches? Each time we report that it's still broken (aka, level 1's are put into lvl 13 games). Obviously the beta testers are more reliable than the internal guys. They'll put the fix in the beta when they have it.
Not retarded but pretty much all of their games have suffered things gamebreaking in the live version. So I wouldn't put it past them to have this show up. It's a lot less jarring than the game crashing when you use a certain skill or everyone rubberbanding so they could have easily overlooked this by then or simply did not have it high enough in the priority list to have it fixed by 5/15. This is one of those things you have to pay attention to closely to notice (since it's only around 10%). It's still unintended (otherwise Blizzard wouldn't have said they were going to submit the report to their teams) thankfully, but most certainly could end up @ launch. It's not even in their Known Issues thread.