I love LiteMount but it caused some wipes for me on Dawnbreaker once I started using it.

In this dungeon on the first boss you need to mount a flying mount even though you are in combat.

As a result, on my paladin I used Divine Steed and died, and on my shaman I used ghost wolf and died.

Is there a way to set up the rules etc. to always try to mount a mount first?

Advice given, no reply, closing.

If you enable the combat actions (which you have) it will do what you told it. If you don't it will summon a mount.

https://github.com/xod-wow/LiteMount/wiki/In-Combat-Actions

There's no way for it to know which one you have decided you want at any particular time. You can't use one keybinding to cast divine steed versus summon a mount depending on what's in your head. :)

Happy adventuring, X.

Hi @mbattersby,

Thanks for the reply. I understand that LiteMount can't read my mind (though that would be a killer feature, no pun intended). My frustration isn't with the addon not being psychic, but rather that its robust rules system made me think there could be a way to tweak behavior in specific scenarios like this.

For example, is there a way to set up a rule to detect when we're in The Dawnbreaker and prioritize mounting over combat actions? Or perhaps some macro-level trickery to achieve this?

I love LiteMount and definitely want to keep using it, but I’d like to avoid situations like this where the combat actions become unintentionally deadly.

Thanks for your time,
Rai

The main problem is that Blizzard prevents addons from changing what spell they will cast while in combat. This is to stop automation of gameplay (like decursive back in vanilla where sometimes a healer's role in a fight was to put a drinking bird on the smart decurse button and go afk).

So what LiteMount is doing is just before combat starts it decides what the button will be, and it's stuck like that until combat ends. In The Dawnbreaker it has some smarts to make that action an appropriate mount, unless you have personally overridden it.

So while I agree, I don't think there's any way to do what you want. Blizzard prevent it with their addon restrictions. If you can find a way to do it in your macro you can put it in there (and please let me know), but I can't do anything smarter than that.

I would probably recommend not using the combat macro, to be honest. Blizzard have it in their gunsights, it already doesn't work if you call LiteMount from another macro, and I'm expecting they will break it completely at some point.

Also (out of interest), assuming it's not reading your mind what criteria would it use to know when to cast the mount?

Instead of locking into one action pre-combat, could LiteMount try a "mount-first" approach dynamically? For example:

When the key is pressed, attempt to summon a mount first.
If the mount casting fails (e.g., due to combat restrictions, no usable mount, or an error), check after a very short delay (say, 0.25 seconds) whether a mount is actively being summoned.
If no mount is being summoned, then fallback to the combat action like Ghost Wolf or Divine Steed.
This way, it prioritizes mounting without requiring mind-reading. I’m not sure how feasible it is to detect if a mount summon has started or failed (maybe checking for a casting state or error message?), but it could offer a smoother experience while staying within Blizzard’s restrictions.

When the key is pressed, attempt to summon a mount first.

This is unfortunately exactly the kind of thing you can't do. You get one chance (per keypress) to do one action immediately, and you have to decide what it'll be. And in-combat you can't change what that action is (at least amongst the set of protected actions like casting spells).

Gonna close this off again. Sorry, the kind of smarts you're hoping for are just not possible.