As of the last week, and I'm not sure if it's the 8.2.5 patch or a hotfix, but SexyMap no longer loads ingame. It's back to the default map, and it won't even show up in my addons menu ingame. It's listed in my addons before you login, and it's checked off for all my characters. I even tried to do a reinstall with the Twitch/Curse client, but that didn't do anything. I haven't installed any new addons, and the only common denominator atm is the 8.2.5. patch. Should I go and delete the addon completely as well as all my settings for it, and install it fresh?

This is the issue in having I've tried everything I can think of. It is showing in my ingame addons list however even though its clicked on it still wont work.

You're trying to use the retail version of SexyMap on classic WoW when you should be using the classic specific version (or the other way around). You should install the Twitch client to manage this for you.

If you're already using the Twitch client, try restarting your PC and loading it up again. If it still doesn't offer you the correct version, you will need to uninstall SexyMap and reinstall it.

I have been using the Twitch client since it was the Curse client - and that is all I use to update the addons for WoW. I will try removing and reinstalling fresh when I get home from work - but I have had SexyMap installed for a few years now, since before Classic was even put into Beta. So if there is any sort of mixup, it's on the Twitch client side.

You're trying to use the retail version of SexyMap on classic WoW when you should be using the classic specific version (or the other way around). You should install the Twitch client to manage this for you.

If you're already using the Twitch client, try restarting your PC and loading it up again. If it still doesn't offer you the correct version, you will need to uninstall SexyMap and reinstall it.

Ok, so it looks like somehow, the Classic one DID get installed - even though I never installed it, simply updated SexyMap with the Twitch Client when there was a new update. So looks like it was a problem with either Twitch or the Twitch client, or the file that was uploaded int he last week or two.