Targeting 50/50

from Demigod Forums

It is just most annoying that your chasing DG back to its towers and then you do pounce / bite and think " yes his dead " but hmm, what just happened, it just didnt do the ability, you press 5 times again, and nothing happens. Same with sednas heal, mate asks can you heal me, i press bout 6 times the button and him, nothing happens he dies, GG..

Is the crappy targeting gonna be fixed in some point? Off course getting the multiplayer to work first is the #1 thing, but this makes alot of angry ppl, and affects in the ESL ladder matches and so, cause vs good players 1 death caused by this can mean loss.

demigod
6,223 views 14 replies
Reply #1 from Stardock Forums Top

This happened to me a LOT on Sedna last night. Trying to heal teammate and nothing. Same with Pounce. Very frustrating when they die before my eyes after I've been furiously clicking on them. Wasn't sure if it was connected with lag issues as there was a lot of lag in that game.

Reply #2 from Demigod Forums Top

This happened to me many times last night.  It seems to happen a LOT with Sedna, both with her heal and pounce.  You will click the ability and your hero will stop moving but no matter how many times you try it will never activate.

Moving appears to reset something and the ability might actually activate after that, but you just stood there for 3 seconds trying to cast something you desperately needed - the enemy already escaped or you're already dead.

This needs to be fixed.  I've also seen it happen with Torchbearer fireball, Oak Penitence, and Erebus bite.

The Political Machine 2024
Reply #3 from Stardock Forums Top

The powers that be are well aware of this issue but still, it's public enemy number one in this game as far as I'm concerned.

You have my sword.

Reply #4 from Demigod Forums Top

Mostly sednas pounce / heal and erebus bite, happens many times per one match. As you said it stops the char, then doesnt do anything, then u can click 1000 times and nothing happens, but if you move abit, then you can again do what you wanted, but huh.. too late.

Reply #5 from Demigod Forums Top

Yeah, I'm having the same problem. The same thing happens as well with QoTs bramble shield, when trying to use on team mates. Please fix this fast, nothing is as annoying as not skill being activated. But it's strange how it happens most with Sedna or when trying to cast on team mates.

Reply #6 from Stardock Forums Top

Did Frogboy say this was fixed and just unimplemented or was I just having a dream?

Reply #7 from Demigod Forums Top

you were dreaming.  Frogboy said it was FIXED and INSTALLED yet it still is a problem.  I've been having it happen all day long.

Reply #8 from Demigod Forums Top

This new patch has seemed to exacerbate this problem further. QoT would often times need TWO move orders for her shield to work. Seems to be really sensitive to being too close to the target.

Reply #9 from Demigod Forums Top

yes I am pretty sure it is related to issuing a targetted skill at a target that requires you to rotate.  For example, trying to pounce on someone behind you.  You do the rotation and just sit there....as if the movement engine thinks you had rotated enough but the actual skill code says you need to rotate a little bit more and so won't fire.  Moving or regular attacking seems to break the cycle.

It is almost as if there is a rounding issue:  Skill tells the movement engine "must rotate to be facing the 45 Degree heading"  and does a "while (direction != 45degrees) wait()".  So the movement engine gets all the way up to 44.99 degrees and says "eh, close enough" and stops rotating.  So the movement engine thinks you are rotated enough (because it is rounding up to 45) but he skill engine doesn't.  I think moving/regular attacking fixes things b/c it causes you to rotate abit in one direction or another so that the next time you issue the target order it all kinda lines up better.

Reply #10 from Demigod Forums Top

But it's strange how it happens most with Sedna or when trying to cast on team mates.
End of quote

I think it's because Sedna has two moves that need targeting so there's more chances for it to happen.

Reply #11 from Stardock Forums Top

QoT would often times need TWO move orders for her shield to work.
End of quote

Yeah, that was the one that got me last night.

What's funny is that it only really seems to happen when my target is about to die.  If we're just wandering across the map towards a fight, it's generally very reliable.

It's like the targeting mechanics completely fall apart as soon as someone goes critical.

Reply #12 from Stardock Forums Top

Saw this in the patch notes from today:

  • Fixed bug that occurred if you used an ability after issuing an attack command. This is the "won't chase the demigod I clicked" bug.

Is this the same thing as what we're talking about in this thread or something different?

Reply #13 from Demigod Forums Top

Quoting Charvel1, reply 12
Saw this in the patch notes from today:


Fixed bug that occurred if you used an ability after issuing an attack command. This is the "won't chase the demigod I clicked" bug.

Is this the same thing as what we're talking about in this thread or something different?
End of Charvel1's quote

 

I'm pretty sure this is different. They DID fix the follow bug, as stated. This was most obvious with Erebus when, after performing a bite (often after a teleport), and the opponent began to run, Erebus would start attacking the nearest grunt (attack order lost with skill triggering). Sedna's pounce was also subject to this alot. The bug that still remains is a skill not triggering in the first place. As far as I know, Frogboy has not mentioned when this will be addressed.

Reply #14 from Demigod Forums Top

I have this problem doing grasp/spit combos on UB now. =(

 

Many lives have been spared... (at least for another couple minutes mwahahaa) }:)