|
Welp I kept searching and eventually found an answer although I haven't tried it yet. Seems it was much easier to find when I actually used Google instead of DuckDuckGo. Here is what I found just in case someone else sees this with a similar issue:
If an addon is loaded on the BCC client, the client will first look for a TOC file whose name is suffixed by “-BCC” (eg. “MyAddOn-BCC.toc”) and load that if present. If not, the client will fall back and load “MyAddOn.toc”.
If an addon is loaded on the Classic client, the client will first look for a TOC file whose name is suffixed by “-Classic” (eg. “MyAddOn-Classic.toc”) and load that if present. If not, the client will fall back and load “MyAddOn.toc”.
If an addon is loaded on the Retail client, the client will first look for a TOC file whose name is suffixed by “-Mainline” (eg. “MyAddOn-Mainline.toc”) and load that if present. If not, the client will fall back and load “MyAddOn.toc”.
|