this is a followup on:
heres the requested bug video replication:
in the end at about 28 secs, i attack the archer, my attack doesnt quite start, then i try to move away but my hero is stuck completely froozen for about 3/4th of a second(0.75sec.) sometimes this occurs at other situations involving the attackcommand where the hero doesnt quite get to start the attack and then gets frozen for about 0.5-2 secs.
[S2]ElementUser plz reply or someone else confirm it.
Oh ok I'll confirm it.
Note that I can only replicate this 100% of the time at 25% gamespeed with fast clicking, so I guess it's possible to replicate it at 100% gamespeed with very low probability.
Of course if the gamespeed is set even lower than 25%, it gets easier and easier to reproduce.
S2 Games: Dedicated employees serving dedicated gamers. Continuous development. Never-ending improvement.
Tech Support and Customer Support: https://www.heroesofnewerth.com/support/
Look for my highlighted text (important information) and grey text (interesting but not required information).
This is a followup on
it is regarding a bug that freezes your hero after an attack command and then a move command you issue while the hero is about to attack. i got it confirmed in the previous thread, but i thought i would just post a replay where it is very easy to spot, and it might help you get data to fix the bug.
match id: 63206508
please watch Edwardcull's forsaken archer(from hellbourne) pushing the top lane, from about 17:50. You will be able to see that the hero is completely unresponsive for about 6.5 seconds, from 17:55 to 18:03.
Even though the hero gets puppet show on it, it does not even attack.
the hero is effectively frozen for about 6.5 seconds.
the commands issued to the archer was to attack the tower and then after that command was issued, the hero was ordered to move back, but instead it just froze...
Others must have expirienced this bug aswell, but i'm sure most people just think that it is lag.
Last edited by KaR0X; 10-01-2011 at 02:49 PM.
i feel like that this post doesnt really get a lot of exposure, as it is in the "confirmed" section.
If anyone actually clicks into this thread, please watch the replay like i request, i would like some feedback from it.
this bug was confirmed in 12-30-2010. The first time i bothered posting about it was 06-18-2010. And that was because it had been bugging me for a long time, so i noticed it a long time before this.
i have been talking to some friends who came to check out the thread, and i have just been informed that noone else can post in this thread..
that is in my oppinion not very constructive towards solving this bug...
to me, it just looks like S2 have taken the bug, pushed it under the carpet and are now just shrugging it off, hoping people wont get too annoyed with it...(or that they will just believe that it's mini disconnects.)
i get this bug about once every two games, but it's not always as clear as this(and sometimes it's just for less than one second.). If i just post other replays where i get it, and i'm not in the middle of getting puppet showed. it will just look like i pushed "hold position" for no reason and then start moving again after some seconds.
I'm very sad that S2 don't take this bug seriously.
I don't know how much exposure this thread gets, as it is in the confirmed section, but Evil_Andrex told me it would be seen by the staff.
he might be right about that, but the bug was confirmed more than a year ago, so i hope the staff have seen it soon, and are working on fixing it. Even though they've spent more than a year with no visible results.
to anyone entering this thread, please dont just look at the video in the first post, please check out the replay with Forsaken Archer: the bug is much more clear there!
I just want to thank any bug fixers working on this, and wish them good luck! me and the few others i know who've expirienced this bug will be very happy and satisfied when you've fixed it!