Intimidate - Bugged?

[ddo.rsmo.pt]

Greetings,

I posted a bug, but wanted to know if anyone else has this problem, and if someone has a workaround.

This is happening to my TR character, but I also created a new character and the problem is still the same: When I login and start a quest, Intimidate is working normally for a few minutes / usages. After a few usages (always 6), it no longer works - it's not failing the roll, it doesn't even roll. The animation for intimidate is executed, but no roll nor fail/success message appears.
Even trying to intimidate monsters that are usually immune (for example, spiders), doesn't show the "cannot be influenced" message.

After relogging inside a quest, intimidate works for 6 more usages - as if it was using charges, then it stops working again. Shrining doesn't work; only relogging.

I don't use Autoattack; I tried using different hotbars too, and either clicking using a number or using the mouse.

Anyone has a clue?

Check out this vid I made showing this bug, and as a bonus, the freezing problem
https://www.youtube.com/watch?v=uZLLrYYXSrk

Carry on.

[Cordovan]

We'd love some more info on this. Are others also experiencing an issue with Intimidate suddenly failing to work?

[Annihilyght]

We'd love some more info on this. Are others also experiencing an issue with Intimidate suddenly failing to work?

I would like to add that intimidate randomly does not work when I have a mob hard targeted as well.

[Miahoo]

I also found intimidate very unreliable.
I see the animation and the skill go into cd, but I don't see the icon above the mobs (nor the save), nor the mobs reacting to my intimidate.

Did anyone try diplo/bluff? I'm pretty sure I had the same problem with those on my rogue last night.

[ddo.rsmo.pt]

We'd love some more info on this. Are others also experiencing an issue with Intimidate suddenly failing to work?

Just want to add that a friend of mine constantly uses intimidate as well, with no issues. Maybe an account issue, even if that sounds odd?

Carry on.

[JOTMON]

I had that the other day with intimidate.
figured it was a one off issue due to some lag bug or other animation that failed to finish properly and caused my intimidate to screw up and not work..

Try Tumbling.

There are some mechanics that get bugged out and one way I found that works (without having to restart the client) for me is to tumble.
I know it sounds stupid, but for whatever reason the tumble mechanic initiates and closes out its own routine that clears some problem issues I come across in the game like being stuck in place.

..keep in mind that tumble only works if you have at least 1 action point spent into it during the levelling process... otherwise you just hop..

[Lost_Leader]

Another possible culprit is auto-attack. I have found that having auto-attack on seems to interrupt intimidate and diplo, as well as scroll and spell casting even when using quicken spell.

[Ryan220]

I've been using Intim a extensively this last week and have had no issues that I have noticed.

[HuneyMunster]

Another possible culprit is auto-attack. I have found that having auto-attack on seems to interrupt intimidate and diplo, as well as scroll and spell casting even when using quicken spell.

Used intim on a Sorc a number of times and never have auto attack on so I doubt that has any effect. Still worth testing incase as could be many factors.

I think one of the main issue before, don't know if still case, but if you fail an Intim check it will stop working till u relog or something similar.

[ddo.rsmo.pt]

Video showing bug, and also freezing:

https://www.youtube.com/watch?v=uZLLrYYXSrk

[ddo.rsmo.pt]

Try Tumbling.

I'll try this, but if it works, it's going directly to my list of New and Exciting Bugs!

[StoddardSolomon]

If you're on a Barb, it's the Raveger tree, you can't put points into it. It's sickning how DDO bugs endure YEARS without fix, and yet they come and ask for 130 dollars for an expansion. Gtfo no love is unbreakable, Im utterly sick of this ****

Greetings,

I posted a bug, but wanted to know if anyone else has this problem, and if someone has a workaround.

This is happening to my TR character, but I also created a new character and the problem is still the same: When I login and start a quest, Intimidate is working normally for a few minutes / usages. After a few usages (always 6), it no longer works - it's not failing the roll, it doesn't even roll. The animation for intimidate is executed, but no roll nor fail/success message appears.
Even trying to intimidate monsters that are usually immune (for example, spiders), doesn't show the "cannot be influenced" message.

After relogging inside a quest, intimidate works for 6 more usages - as if it was using charges, then it stops working again. Shrining doesn't work; only relogging.

I don't use Autoattack; I tried using different hotbars too, and either clicking using a number or using the mouse.

Anyone has a clue?

Check out this vid I made showing this bug, and as a bonus, the freezing problem
https://www.youtube.com/watch?v=uZLLrYYXSrk

Carry on.

[monsoon22]

If you're on a Barb, it's the Raveger tree, you can't put points into it. It's sickning how DDO bugs endure YEARS without fix, and yet they come and ask for 130 dollars for an expansion. Gtfo no love is unbreakable, Im utterly sick of this ****

100% correct. Spent about 3 hours trying to figure it out in various combinantions with a tank barb build figuring it was ritual scarring, but it is even the first core. You spend one point in ravager and your intim is borked. Spend none and my barb can intim all day long without issue.

[Lynnabel]

100% correct. Spent about 3 hours trying to figure it out in various combinantions with a tank barb build figuring it was ritual scarring, but it is even the first core. You spend one point in ravager and your intim is borked. Spend none and my barb can intim all day long without issue.

Beep boop we're looking into this, thanks for the info!

[Dragavon]

Beep boop we're looking into this, thanks for the info!

You know Lynn, you are always saying here we must send in bug reports, right?

A guildie sent in the first bug report about this 2 years ago, it has been bugged that long.

Since then he has bug reported it again and again many times.

So, no wonder people get disillusioned when they bug report things and nothing happens. On top of that the bug report page is a pita to use.

[Lynnabel]

You know Lynn, you are always saying here we must send in bug reports, right?

A guildie sent in the first bug report about this 2 years ago, it has been bugged that long.

Since then he has bug reported it again and again many times.

So, no wonder people get disillusioned when they bug report things and nothing happens.

You ever have that moment where you're thinking about something and then someone else says something unrelated and then suddenly your memories work again and you get this little "aha!" moment and fix the problem or solve the puzzle? That's what the forums help with. Sometimes we have 99.9999% of a puzzle with bug reports, and then someone on the forums goes "hey check the ED cores" and then you remember that there's this one thing in intimidate that checks for something unrelated and then a whole bunch of things connect and then you go on and win the big yo-yo championship or something.

On top of that the bug report page is a pita to use.

This is the millionth time I've heard this and I honestly just don't understand. I report bugs while I'm playing. It's 3 drop down menus (such as the game you're playing - Lotro or DDO!), and 5 required fields (Character name, account username, subject line, description of the bug, and an email address) - plus the check box to not be a robot. What's a pain in the butt? Am I looking at a different bug report page? Are you a robot?*

*if you are a robot, you've definitely fooled me, please send congratulations to your programmer and remember my kindness in the inevitable robot uprising!

[Tyrande]

You know Lynn, you are always saying here we must send in bug reports, right?

A guildie sent in the first bug report about this 2 years ago, it has been bugged that long.

Since then he has bug reported it again and again many times.

So, no wonder people get disillusioned when they bug report things and nothing happens. On top of that the bug report page is a pita to use.

Give her a break. She wasn't here two years ago. Unless she has a Flux capacitor and a hover car 2 years ago; she can't travel back in time and find that bug report that was probably closed a long time ago and their duplicates. If the bug report did not have detail reproduction steps and was reproducible, it was probably closed as NO-REPRO.

When I was a senior QE engineer I always had to write good bug reports so that even I can read it two years later.

Story description, Acceptance Criteria, Dependencies, STEPS TO REPRODUCE, OS, MEM, HARDWARE/VM, What else was running, etc.

[Dragavon]

This is the millionth time I've heard this and I honestly just don't understand. I report bugs while I'm playing. It's 3 drop down menus (such as the game you're playing - Lotro or DDO!), and 5 required fields (Character name, account username, subject line, description of the bug, and an email address) - plus the check box to not be a robot. What's a pain in the butt? Am I looking at a different bug report page?

Maybe it is easy for you, but for someone who is not very familiar with it is anything but easy and intuitive to use. And as options come up after you have chosen some options then it is easy to miss something. I have several times done my best, only to get smacked in the face with a message that something was missed when I click submit.

Then I usually say **** this **** and close the page.

The bug report tool should be in game, and collect all relevant char / quest data automatically, the only user input required should be a description of the bug.

[Drwaz99]

The bug report tool should be in game, and collect all relevant char / quest data automatically, the only user input required should be a description of the bug.

Bingo.

[janave]

This is the millionth time I've heard this and I honestly just don't understand. I report bugs while I'm playing. It's 3 drop down menus (such as the game you're playing - Lotro or DDO!), and 5 required fields (Character name, account username, subject line, description of the bug, and an email address) - plus the check box to not be a robot. What's a pain in the butt? Am I looking at a different bug report page? Are you a robot?*

I don’t find the report form as clunky as others, although they could experience some client side quirks due to browser ego. With that said I think for those logged in the forums should not ask for account, email fields. If someone clicks a bug report URL from ddo.com domain we can assume they also going to report a DDO bug, so that’s one less param.

Some bugs are clearly unrelated to character, eg: where something in some quest bugs out due to a quest item. (Although I expect a few of us can judge with 90%+ certainty, so the extra param would not hurt).