WoW:TOC format: Difference between revisions

731 bytes added ,  24 October 2022
No edit summary
Line 69: Line 69:
#: There are differences big enough between two editions of WoW, that it would be easier to use two or more different coded or XML files, and need a different .toc files to load different sets of code for an edition.
#: There are differences big enough between two editions of WoW, that it would be easier to use two or more different coded or XML files, and need a different .toc files to load different sets of code for an edition.
# The 'Interface' version numbers
# The 'Interface' version numbers
#: Each edition has its own series of interface version numbers. Because of this and because you only have one '## Interface:' line to specify the number, you will actually need a .toc file for each supported edition. Otherwise, users will have to click the 'load outdated' checkbox to load your addon.
#: Each edition has its own series of interface version numbers. Because of this and because you only have one '## Interface:' line to specify the number, you will actually need a .toc file for each supported edition. Otherwise, users will have to click the 'load outdated' checkbox to load your addon.
 
=== Edition names ===
Known and current name postfixes (show in full name context) are:
* MyAddon.toc - the default .toc file. Any edition will load this file, including retail.
* MyAddOn_Wrath.toc - used for WolLK
* MyAddOn_Vanilla.toc - used for Classic
 
Other known name postfixes (show in full name context) are:
* MyAddOn_Mainline.toc - can be used for Retail. Highly suggested just use default instead.
* MyAddOn_TBC.toc - was used for TBC. There is no longer a way to load TBC
* MyAddOn-Wrath.toc - the older deprecated postfix for WotLK
* MyAddOn-TBC.toc - the older deprecated postfix for TBC
* MyAddOn-Classic.toc - the older deprecated postfix for Classic
* MyAddOn-Mainline.toc - the older deprecated postfix for Retail


== Details ==
== Details ==