WoW:TOC format - Revision history

Bear: /* Names and values */

2025-08-23T18:44:56Z

Names and values

← Older revision		Revision as of 18:44, 23 August 2025
Line 251:		Line 251:
	** zhCN		** zhCN
	** zhTW		** zhTW
	** ... (or whatever other text localization code ~~the wow client is set to~~)		** ... (or whatever other text localization code)

	; File path markup names, with replacement values		; File path markup names, with replacement values

2025-08-23T18:26:16Z

Names and values

← Older revision		Revision as of 18:26, 23 August 2025
Line 245:		Line 245:
	** mists		** mists
	** mainline		** mainline
			* AllowLoadTextLocale
			** enUS
			** frFR
			** ruRU
			** zhCN
			** zhTW
			** ... (or whatever other text localization code the wow client is set to)

	; File path markup names, with replacement values		; File path markup names, with replacement values

2025-08-22T23:46:43Z

Edition names

← Older revision		Revision as of 23:46, 22 August 2025
Line 102:		Line 102:
	* MyAddOn-Classic.toc - older deprecated postfix for Classic		* MyAddOn-Classic.toc - older deprecated postfix for Classic
	* MyAddOn-Mainline.toc - older deprecated postfix for Retail		* MyAddOn-Mainline.toc - older deprecated postfix for Retail
			* MyAddOn_PlunderStorm.toc - used for a PlunderStorm game mode

	=== Edition precedence ===		=== Edition precedence ===

2025-08-22T23:45:22Z

Edition names

← Older revision		Revision as of 23:45, 22 August 2025
Line 81:		Line 81:

	=== Edition names ===		=== Edition names ===
	Known ~~and current~~ name postfixes (shown in full name context) are:		Known main-use name postfixes (shown in full name context) are:
	* MyAddon.toc - the default .toc file. Any edition or game mode will load this file, including retail.		* MyAddon.toc - the default .toc file. Any edition or game mode will load this file, including retail.
	* MyAddOn_Classic.toc - used for any Classic edition		* MyAddOn_Classic.toc - used for any Classic edition

2025-08-22T23:35:56Z

Edition names

← Older revision		Revision as of 23:35, 22 August 2025
Line 88:		Line 88:
	Other known name postfixes (shown in full name context) are:		Other known name postfixes (shown in full name context) are:
	* MyAddOn_Mainline.toc - used for Retail. Highly suggested to just use default instead		* MyAddOn_Mainline.toc - used for Retail. Highly suggested to just use default instead
	* ~~MyAddOn_Cata~~.toc - used for Cataclysm. Suggested to use 'Classic' instead, and differentiate with 'Vanilla' if necessary		* MyAddOn_Mists.toc - used for Cataclysm. Suggested to use 'Classic' instead, and differentiate with 'Vanilla' if necessary
	* MyAddOn_Standard.toc - used for any standard mode, version or edition. will be ignored when non-standard mode is loaded.		* MyAddOn_Standard.toc - used for any standard mode, version or edition. will be ignored when non-standard mode is loaded.
	* MyAddOn_WoWLabs.toc - used for a non-standard game mode		* MyAddOn_WoWLabs.toc - used for a non-standard game mode

	Deprecated or unused (shown in full name context) are:		Deprecated or unused (shown in full name context) are:
			* MyAddOn_Cata.toc - used for Cataclysm. There is no longer a way to load Cataclysm
	* MyAddOn_Wrath.toc - was used for WotLK. There is no longer a way to load WotLK		* MyAddOn_Wrath.toc - was used for WotLK. There is no longer a way to load WotLK
	* MyAddOn_TBC.toc - was used for TBC. There is no longer a way to load TBC		* MyAddOn_TBC.toc - was used for TBC. There is no longer a way to load TBC

2025-08-02T21:16:49Z

2023-08-15T04:49:00Z

Move page script moved page TOC format to TOC format without leaving a redirect

← Older revision	Revision as of 04:49, 15 August 2023
(No difference)

2022-10-24T06:43:28Z

Edition names

← Older revision		Revision as of 06:43, 24 October 2022
Line 74:		Line 74:

	=== Edition names ===		=== Edition names ===
	Known and current name postfixes (~~show~~ in full name context) are:		Known and current name postfixes (shown in full name context) are:
	* MyAddon.toc - the default .toc file. Any edition will load this file, including retail.		* MyAddon.toc - the default .toc file. Any edition will load this file, including retail.
	* MyAddOn_Wrath.toc - used for WolLK		* MyAddOn_Wrath.toc - used for WolLK
	* MyAddOn_Vanilla.toc - used for Classic		* MyAddOn_Vanilla.toc - used for Classic

	Other known name postfixes (~~show~~ in full name context) are:		Other known name postfixes (shown in full name context) are:
	* MyAddOn_Mainline.toc - can be used for Retail. Highly suggested just use default instead.		* 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_TBC.toc - was used for TBC. There is no longer a way to load TBC

2022-10-24T06:42:13Z

Why multiple .toc files

← Older revision		Revision as of 06:42, 24 October 2022
Line 69:		Line 69:
	There are two big reasons:		There are two big reasons:
	# Code differences		# Code differences
	#: If there ~~are~~ big enough differences between two editions of WoW for an addon, that it would be easier to just use two or more different sets of some of the code or XML files, then the addon would need different .toc files to load the different sets of code for each edition.		#: If there were big enough differences between two editions of WoW for an addon, that it would be easier to just use two or more different sets of some of the code or XML files, then the addon would need different .toc files to load the different sets of code for each 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.

2022-10-24T06:41:48Z

Why multiple .toc files

← Older revision		Revision as of 06:41, 24 October 2022
Line 69:		Line 69:
	There are two big reasons:		There are two big reasons:
	# Code differences		# Code differences
	#: If there are big enough differences between two editions of WoW for an addon, that it would be easier to just use two or more different code or XML files, the addon ~~then~~ would need different .toc files to load the different sets of code for each edition.		#: If there are big enough differences between two editions of WoW for an addon, that it would be easier to just use two or more different sets of some of the code or XML files, then the addon would need different .toc files to load the different sets of code for each 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.