You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often times when trying to mount up, mounting may fail due to being in combat, or being in a non-mountable area. The game provides 'some' feedback in these situations, i.e. "Not enough space to mount", but more-often-than-not the game gives you zero feedback and you're left wondering why your mount isn't working.
I'm not sure if there is any backend messaging provided when mounting fails to work, but it would be a great help to have some on screen message to indicate 'why' mounting didn't work. This could even be as simple as a notification stating that the command was received but failed due to 'unknown reasons", which would at-least inform the player that the command was successfully submitted. Because right now, with zero feedback, we don't know if the command failed to go through, or the command was outright rejected, and that leaves us just blindly spamming the mount until it eventually works.
The text was updated successfully, but these errors were encountered:
Often times when trying to mount up, mounting may fail due to being in combat, or being in a non-mountable area. The game provides 'some' feedback in these situations, i.e. "Not enough space to mount", but more-often-than-not the game gives you zero feedback and you're left wondering why your mount isn't working.
I'm not sure if there is any backend messaging provided when mounting fails to work, but it would be a great help to have some on screen message to indicate 'why' mounting didn't work. This could even be as simple as a notification stating that the command was received but failed due to 'unknown reasons", which would at-least inform the player that the command was successfully submitted. Because right now, with zero feedback, we don't know if the command failed to go through, or the command was outright rejected, and that leaves us just blindly spamming the mount until it eventually works.
The text was updated successfully, but these errors were encountered: