This might also be why I only see ranged characters die to this, since they go far away and mene goes after them and moves them, while melees will go near him and he won't move, therefore not moving the player
I think you'd see more ranged being hit simply because they're the only ones who are still trying to hit the boss before accel bomb. Melees inherently would be peeling away from the aoe, making that movement their last action before it goes off, so unless they use shield lob, throwing daggers, piercing talon etc then it's impossible for them to get tripped up by the autoface interaction.
i haven't exploded in the menenius duel yet, but the acceleration bombs in the diablo armament fight have constantly been blowing me up despite de-targeting and stopping movement well before the timer expires. i've never had an issue with accel bombs before (o4s, ozma, susano ex, etc; i think my general approach is also 'finish whatever i'm doing, move slightly away and cancel targeting') but i've succeeded in dalriada maybe twice, total. it seems like the delay between client and server in areas of large player activity is causing more problems than the mechanic traditionally would?
Edit : only sheathing weapon will not stop you from face rotate so you need to manually moving a bit after cast a spell (Sheath is still good for stop auto attack so do that too especially if you are RDM) Sheathing your weapon work for this too if you want to make sure, the default button for this is "Z" click it once and it will cancel all your action including auto attack.
I don't think it's the case. There was a clip where someone targeted themselves (so no face moving around): ua-cam.com/video/ZFKOX3KEQ4Y/v-deo.html With friends we debated that it could be your character moving from... Taking the auto-attack. I have 2 Menenius clip in which the bomb explode exactly when Menenius auto-attacks. Since Melees tends to be closer, they take it earlier and might not trigger the bomb. But sometimes it does, sometimes it doesn't.
Hi, your current target is irrelevant when it comes to this interaction. If you look in my second clip in Limsa I'm also targeting myself but my character is still rotating to face my previous target. The player in your video cast Dia, then did not move again. He still has autoface on during the boss movement, which I believe caused him to be hit. Thanks
@@vimapostrophe8737 Wait you're right. Why the hell is it working... Like that? Anyway, thank you for your answer, I did not understood it this way. EDIT: We tried and it definitely "works"! It's probably an oversight from the devs, a feature from a very long time ago. Most bosses don't move at all when they use this mechanic. Also, it means we can kill half the party by moving Susano.
@@Shinnouryu This was a change made sometime in late ARR/early HW I don't remember to help casters keep their target in their frontal line of sight. What would happen is casters could start casting, then the target would move around and they could lose LoS unless they spun their character manually or spammed a /facetarget macro constantly. So now we just spin with the target all the time instead. Though yeah I agree it seems like an oversight that it's not only specifically when casting a spell.
This seems like it would explain my 2 stillness deaths on my clear ua-cam.com/video/HMeZ0w5N3fA/v-deo.html I thought that standing still and dropping target completely would have worked but this explains it perfectly. I didn't need to drop target, but I did need to move to disable auto facing if I'm understanding correctly. Thanks!
This might also be why I only see ranged characters die to this, since they go far away and mene goes after them and moves them, while melees will go near him and he won't move, therefore not moving the player
I think you'd see more ranged being hit simply because they're the only ones who are still trying to hit the boss before accel bomb. Melees inherently would be peeling away from the aoe, making that movement their last action before it goes off, so unless they use shield lob, throwing daggers, piercing talon etc then it's impossible for them to get tripped up by the autoface interaction.
i haven't exploded in the menenius duel yet, but the acceleration bombs in the diablo armament fight have constantly been blowing me up despite de-targeting and stopping movement well before the timer expires. i've never had an issue with accel bombs before (o4s, ozma, susano ex, etc; i think my general approach is also 'finish whatever i'm doing, move slightly away and cancel targeting') but i've succeeded in dalriada maybe twice, total. it seems like the delay between client and server in areas of large player activity is causing more problems than the mechanic traditionally would?
Edit : only sheathing weapon will not stop you from face rotate so you need to manually moving a bit after cast a spell (Sheath is still good for stop auto attack so do that too especially if you are RDM)
Sheathing your weapon work for this too if you want to make sure, the default button for this is "Z" click it once and it will cancel all your action including auto attack.
Sheathing weapon doesn't work, I have multiple clips proving it where I put the weapon away and still explode.
@@Shinnouryu Ah I see ,double check it with walking sabotender and my character still moving(by continuing to rotate face) toward that sobotender.
Does disabling autoface via command not fix this?
It fix the face rotating problem but it will also create another annoying problem that you have to manually face the target to cast a skill
ty very cool
I don't think it's the case.
There was a clip where someone targeted themselves (so no face moving around): ua-cam.com/video/ZFKOX3KEQ4Y/v-deo.html
With friends we debated that it could be your character moving from... Taking the auto-attack. I have 2 Menenius clip in which the bomb explode exactly when Menenius auto-attacks. Since Melees tends to be closer, they take it earlier and might not trigger the bomb. But sometimes it does, sometimes it doesn't.
Hi, your current target is irrelevant when it comes to this interaction. If you look in my second clip in Limsa I'm also targeting myself but my character is still rotating to face my previous target. The player in your video cast Dia, then did not move again. He still has autoface on during the boss movement, which I believe caused him to be hit. Thanks
@@vimapostrophe8737 Wait you're right.
Why the hell is it working... Like that? Anyway, thank you for your answer, I did not understood it this way.
EDIT: We tried and it definitely "works"! It's probably an oversight from the devs, a feature from a very long time ago.
Most bosses don't move at all when they use this mechanic.
Also, it means we can kill half the party by moving Susano.
@@Shinnouryu This was a change made sometime in late ARR/early HW I don't remember to help casters keep their target in their frontal line of sight. What would happen is casters could start casting, then the target would move around and they could lose LoS unless they spun their character manually or spammed a /facetarget macro constantly. So now we just spin with the target all the time instead. Though yeah I agree it seems like an oversight that it's not only specifically when casting a spell.
You're welcome.
This seems like it would explain my 2 stillness deaths on my clear ua-cam.com/video/HMeZ0w5N3fA/v-deo.html I thought that standing still and dropping target completely would have worked but this explains it perfectly. I didn't need to drop target, but I did need to move to disable auto facing if I'm understanding correctly. Thanks!