Curse client addons not showing up in wow

broken image

Honestly the best thing to do is to install buggrabber/bugsack

broken image

Original by Omegal (Tech Support MVP) - saved here in case the forums are shut down: Here are some good reasons for why you should consider this. Note: If you'd like to collect and report script errors more easily to help addon authors out and/or get your addon problems fixed quickly, I recommend using specific addons to do so. The more I know about the specifics of a potential issue, the faster I'll be able to fix it, and the more likely it is to become a higher priority for me to do so. Please understand that you're making it extremely difficult, if not impossible, for me to help you if you don't give me all the information that you can. Important: There is no confirmation after typing these commands, and you'll need to reload your interface or restart/relog to see the relevant error messages if Rarity failed to load. Once you're done reporting a problem, and no longer wish to see error messages, feel free to disable them with this command: /console scriptErrors 0 You can, however, enable them using this command: /console scriptErrors 1 These are disabled by default in the most current client versions. In order to troubleshoot potential issues, particularly when the addon isn't loading correctly, you'll need to post any error messages Lua will display in the game.