Not moving when clicking (or using skill)

"
SirGuySW a écrit :
"
Vaelishaan a écrit :
only moving the mouse over a completely different target changed the target is the real issue.
Well ... that's how it should work, but we can see in your video that it didn't (you only changed targets twice (from Piety to Wandering Eye then back) from the start of that clip (?t=00h13m51s) until you died).


But it shouldn't work that way. Once off the target I should be targeting nothing, i.e. the ground. So clicking should have done the move action. Only just before I died did my mouse move over another target and show that i was not holding an attack on Piety.

So since I was not holding an attack, since the highlight was able to change to another target eans that my clicks should have been off piety as they werne't actually on her, EXCEPT for the fact that she was performing a field wide attack... And that's the only thing that it could be.

"
SirGuySW a écrit :
I'm pretty sure unique mobs have a larger click box so they're easier to target when in a horde of mobs. Again, you were instructing the game to attack, the game found what it thought was the most appropriate target.

I have not found that to be the case at all. I find that their hit box's are the same ratio as them. So the click box would only be larger if they are actually larger than one you are comparing to.

The most appropriate? But I wanted to move, and all it did was a continuous attack when I was not using any attack buttons or even hovering over any target.

If my char had have even taken one step, that would have changed everything. But it didn't. One step would have meant I would have lived instead of dying. Because moving one step when I had my mouse not targeting her would have meant that there was no bug. Which in the past, I have not had an issue with it, it is a bug, not always present.

Thus it isn't a coding error, it's just a bug.
"
Vaelishaan a écrit :
But it shouldn't work that way. Once off the target I should be targeting nothing, i.e. the ground. So clicking should have done the move action.
Not at all. Again, you have 'Attack' bound to your left click. Clicking a mob with this skill instructs the game to attack the mob, thus changing the target to the mob. You need to use a move-only option if you want to click without targeting clicked mobs.

"
Vaelishaan a écrit :
The most appropriate? But I wanted to move, and all it did was a continuous attack when I was not using any attack buttons or even hovering over any target.
Same as above: If you want to move, use a move command. You have default attack assigned to left mouse button. If that's the button you were clicking you were requesting an attack action *not* a move action.

Why confuse the game and yourself by requesting attack actions when you want to move? Just use 'move only'. I don't know why your character continued to attack Piety, that might indeed be a bug but your video doesn't prove this bug, your video just looks like you namelocked Piety.

I just tested the Piety fight for about 20 more minutes trying to emulate your play style (on an Ancestral Bond character so can't damage Piety, but used a golem to whittle her down to about the same HP level as in your vid). I still wasn't able to replicate any targeting issue but did notice that it is annoyingly easy to accidentally namelock with default attack on left mouse (even when holding lmb: use any movement skill while cursor is over an enemy --or if cursor passes through enemy during character movement-- and suddenly namelocked, use any other skill while cursor is over an enemy and char will attack enemy but will break namelock when cursor leaves enemy). But that's not really relevant to your issue if you were indeed clicking lmb in the lower right of your screen in the second or so before your character's death.
Once you namelock, even with default attack, it stays namelocked until you cease using what you namelocked with. Simply moving the cursor to a free space while continuing to use the attack doesn't release the namelock.

You may not have intended to namelock her with your default attack, but you did. You were very clearly holding down your default attack in an attempt to move, but doing so is precisely what prevented you from moving. It has no built-in "free move" function, so it had no option but to continue trying to attack your locked target from where you were standing.

Even putting an actual skill there can cause similar problems. If you had it set to move only though, you would have moved without any issue at all and (probably) wouldn't have died.

Like it or not, and there have been complaints about it over the years, it's working as intended.
I have a pretty good sense of humor. I'm not German.
Dernière édition par aggromagnet#5565, le 19 août 2020 à 07:25:03
"
aggromagnet a écrit :
You may not have intended to namelock her with your default attack, but you did. You were very clearly holding down your default attack in an attempt to move, but doing so is precisely what prevented you from moving.


You obviously never listened to the audio and heard the mouse clicking.

Please, think before you speak, or I will report you again.
"
SirGuySW a écrit :

Why confuse the game and yourself by requesting attack actions when you want to move? Just use 'move only'. I don't know why your character continued to attack Piety, that might indeed be a bug but your video doesn't prove this bug, your video just looks like you namelocked Piety.

I just tested the Piety fight for about 20 more minutes trying to emulate your play style (on an Ancestral Bond character so can't damage Piety, but used a golem to whittle her down to about the same HP level as in your vid). I still wasn't able to replicate any targeting issue but did notice that it is annoyingly easy to accidentally namelock with default attack on left mouse (even when holding lmb: use any movement skill while cursor is over an enemy --or if cursor passes through enemy during character movement-- and suddenly namelocked, use any other skill while cursor is over an enemy and char will attack enemy but will break namelock when cursor leaves enemy). But that's not really relevant to your issue if you were indeed clicking lmb in the lower right of your screen in the second or so before your character's death.


As I said, it doesn't ALWAYS happen.
I have done EXACTLY the same thing multiple times in the past. It happened a couple of times in total. But the exact style of what happened has happened to me on many more bosses than just Piety Act 4.

The issue is when they are using a field attack. Pietys beam, merveils water spouts. They both are field attacks and have the same bug. Merveil is the easiest one to get to, and the fastest to get to, so that is the best one for testing if you really want to test it.

I've had it happen multiple times recently on merveil, so i know it still happens. The fact that it "name locks" when I have not set any lock is worrying. If you are talking about just holding an attack, then that is not what was happening. As I had said, and as the video shows, I just did what I did.

I have written a little application for my future streaming to show what keys and clicks I am doing, that way, bugs can be confirmed and you will actually be able to visually see what I am doing, that will avoid these thinkings of "i am holding the attack mouse button", when I'm actually using the middle mouse button trying to use a movement skill, as well as clicking the left mouse button on the ground far enough away that the creature should not be targeted as I have not got any attack selected or locked.

This is why I say it is a bug and needs to be looked into by the developers. I'm just a mere bug tester, and I don't have the debug edition of the game to be able to do my bug testing more than I already have by doing multiple tests on the same creatures to verify that things are happening at times, the same way.

So I do what I can, and I have verified that it does happen. Last time on Merveil tonight, I did encounter it again, but when she teleported, the layers fixed up and I was able to not target her and was able to move. And she teleported from the left side of the map to the right, which took her from across the gorge, to standing next to me.

And I was able to move again even very close to her without targeting her and attacking her while I had the basic attack skill on my LMB.

If I was name locked to piety and I was using MMB then I should have blinked. The skill was available after all.

As you can see, it is a bug, not a coding issue. (by default) just a random event that causes the one performing the field wide attack to have their targeting layer sometimes appear over the ground.

There has to be a reason for it. There may be something spawn in the area at the same time (Merveil and Piety both have minions spawning) which would cause the layer to rise to the spawning layer for mobs above ground, then the targeting layer gets set instead of having the attack targeting layer set below the ground but the animation above.

So there is something in the code that is having an abnormal event occur to cause that to happen. It's not something that is there on purpose or designed to do.

This is the common factor. Dominus, I don't have the same issue. He has no summons, but he does have a field cast.

Just food for thought. Yes, trying to work the bug out too.
So want to preface that I've never had this happen, and I couldn't get it to happen in either mervail or the shown piety fight despite multiple attempts. (may want to validate your files, maybe somethings messed up)

Though your given video isn't divisive proof, even on full volume with a head set on I can't hear your mouse so you'd need a video with inputs shown to help show it better.

With the clip no matter where you moved your mouse piety's nameplate was there and she was highlighted which only happens if 1) you mouse over them (which supports your claim) or 2) you namelock them (which goes against your claim)

Unfortunately you were using frostblink in the clip which will let a namelock persist even after use (which something like leap slam handles differently) and it doesn't help that there's no real way to test if frostblink will aim at/go through a target you are hovering over since there's no way to hover over an enemy while aiming it somewhere else(while it does for sure behave like that while namelocking)

So unfortunately since I can't recreate it you'd probably want a better clip of it happening for you showing button inputs.


As an aside from the validity of the bug, it's not worth ever having auto-attack on the hot bar after killing the first zombie on twilight strand, even more so in hardcore. So in the future after validating the bug or not I'd recommend swapping auto attack for move only after the first zombie. Even outside of possible bugs auto attack can only ever cause issues for you being on your bar.
Okay.. Here we go...

I died again...
I have my things active so you can see what is clicking and all.

I tried to do what I had been doing many times in the past, and it did not work, DURING an AOE attack.

In the time leading up to it, you can see me doing the thing many times over and it was always doing what I told it to do... then, it did not, and I died...

Here is IRREFUTABLE proof.


https://www.twitch.tv/videos/717938311?t=02h11m06s

Looking back in the stream you will see when I had done it in the past.
If you want I can mark them all. But there was so many you would not have to look for long...

Name Locking + movement skill...

Works all the time, then suddenly it doesn't....

Sadly I can't make heads or tails of that, unlike an input program like speed runners use where it shows each button being pressed and how long each input is held I can't really tell if you are or aren't holding down left click, also your flood of inputs come in after you die.

Even after running through the clip multiple times all I can see you doing is walking in mousing over the enemy then holding left click (no clue why you used auto attack on the enemy rather than your double strike in the first place or at least you can't see any right click inputs) but anyway you name lock the boss with left click hold, kill him with it then immediately namelock the new boss that spawns, auto attacking him till you are dead then a flood of middle clicks come into your input program post death. Watched it like 15 times on .25 speed and that's what I see every time.
Same btw. I wasn't sure about the button display on the right side but looking at the input display in the bottom left it looks like you don't hit Middle Mouse Button until just as your character dies (ie: too late).
Dernière édition par SirGuySW#7930, le 22 août 2020 à 09:22:52
"
SirGuySW a écrit :
Same btw. I wasn't sure about the button display on the right side but looking at the input display in the bottom left it looks like you don't hit Middle Mouse Button until just as your character dies (ie: too late).


Yes, the one in the top right missed some clicks. the one in the lower left shows it though.

As for holding an attack, in the lower left you will see..

Yes I had name lock, and yes it should have worked fine. I have proof of it working the way it is meant to work, in the past. Just look back in the stream.

As I said in my post "Name Locking + movement skill" so why would you ask if I was locking when I even told you I was?

The one in the top right seems to be a bit laggy, like it detects one but not the other. It detected the click but not the middle click, where the lower left detected the middle clicks perfectly.




"
IonDrako a écrit :
Sadly I can't make heads or tails of that, unlike an input program like speed runners use where it shows each button being pressed and how long each input is held I can't really tell if you are or aren't holding down left click, also your flood of inputs come in after you die.


I don't know what professional speed runners use, wish I did.

And yes I was still clicking even after I died.... even just for a second because I had that many inputs queued up in my system. (i.e. my brain) EDIT: {Not to mention the frustration so I just kept clicking a few times}

"
IonDrako a écrit :
Even after running through the clip multiple times all I can see you doing is walking in mousing over the enemy then holding left click (no clue why you used auto attack on the enemy rather than your double strike in the first place or at least you can't see any right click inputs) but anyway you name lock the boss with left click hold, kill him with it then immediately namelock the new boss that spawns, auto attacking him till you are dead then a flood of middle clicks come into your input program post death. Watched it like 15 times on .25 speed and that's what I see every time.


Are you sure it was left click? Look in the lower left one. No matter what it was that I was targeting, my movement should have occurred. the proof is there. Clip it and download it from twitch if you want. then you can watch it on something better that doesn't have the overlay.

I watched it 4 times, and saw that middle clicks in the lower left program saying that I was clicking, before my HP hit 0.

As I said just before, the one in the top right seems to miss some clicks.

I can replicate it easily now that I know how and why it happens.

{Admins}/{Devs}, can you please send me a bug report form so that I can fill it out including all technical data that I have?

Yes, I have done plenty of testing on other games in the past, and I know how it works, so please send me the form you require and I'll post it in with the required data that I have already collected. (Would be easier if I had access to the debug console.)
Dernière édition par Vaelishaan#6370, le 22 août 2020 à 10:02:36

Signaler

Compte à signaler :

Type de signalement

Infos supplémentaires