-
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ready Check Window layout broken in recent patch. #1467
Comments
Please follow all the troubleshooting steps and provide the requested information when opening a ticket.
|
You need to provide the troubleshooting steps when opening a ticket (and do the steps). This rules out if it is another addon, and if it is ElvUI - gives information to help fix the issue. It wastes people’s time opening tickets without doing this. |
Feel free to close this, but any dev could pick this up and see the issue based on the screenshot. I hate how you always say, "It's a waste of time to report bugs..." because clearly you rely on users to do QA. It's just rude how you behave here. I like Elv, but man... there's no other add-on that treats users as shitty as you guys do. |
It is the basic troubleshooting steps - this helps
It also gives the status panel so if the issue is with ElvUI - it gives information to help find out the cause of the issue. Some issues are only on cata, so if it isn’t shown what wow version you are on, and it gets checked in retail - then it won’t show. Also helps if there is a class / talent based issue. It isn’t that hard. The steps are very easy to do. You can just Ask the RL to do a ready check (you already said they did a lot) See if you have the issue Screenshot.
Done. |
Troubleshooting Steps
Ready Check Window is messed up with longer names. I noticed this since the last patch. Before last patch I don't recall seeing this, and this guy ready checks a lot. (=
Describe the expected behavior and what actually happened?
See above.
Reproducing the issue.
See above.
Lua Errors
Verification Steps
The text was updated successfully, but these errors were encountered: