Sometimes right after I use ruin on an enemy, my auto attack will not work. After 3-4 seconds, for some reason ruin would take place again. The only way I would be able to use my auto attack right after the glitch/freeze would be to walk anywhere on the map and attack again. It's a bit hard to explain, but I'm hoping you could test it out yourself and understand what I'm trying to say. Btw, this glitch takes place around 50% of the time.
Annoying 'Ruin' Bug.
#1
Posted 03 January 2014 - 17:45
#2
Posted 03 January 2014 - 19:47
Yes it is extremely annoying
Reported it as bug a while ago now. Seems it is not just happening with Ruin.
http://forums.hunted...showtopic=60822
Visit my shop! Mongo's Emporium for emotes, pets, vanity and more!
#3
Posted 03 January 2014 - 20:49
Yes it is extremely annoying
Reported it as bug a while ago now. Seems it is not just happening with Ruin.
Nice to know that it's quite a common issue and I'm not the only one facing it. Hopefully the glitch will get sorted out soon enough.
#4
Posted 06 January 2014 - 17:59
I am unable to reproduce this at all, can I get some pointers/screenshots of this happening.
It sounds like it's breaking completely, so when it glitches out you cannot use any spells/abilities?
Is there a cast bar present while you are in this state?
Are you using a lot of potions while this happens?
Things to be aware off: If you trigger Ruin first you will not be able to queue up Auto Attack until the move is finished (Ruin hits twice as well don't forget). We will improve this for a future release so you can queue auto attack while still casting something else.
#5
Posted 06 January 2014 - 18:12
It isn't only ruin,i've witnessed it quite a few times on my mage and templar class as well.
with templar sometimes it happens after you Impale after a time of basic melee
and mages it happens actually often if your haste is to high to the point of spamming ignite between incins/basic ranged attack it will give you almost like a stun effect
Characters:
Guthix:
Level 40 Mage.
Chelsea's Man<3
#6
Posted 16 January 2014 - 16:47
This has since been fixed
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users