For Interface, what is the easiest place to look for the current number for the client?
- -- Generally, it can be found in parentheses in the lower left corner of the login screen when you launch WoW. The last patch was an exception to this, as the number there was not the correct one. --The Nerd Wonder 15:41, 22 Mar 2005 (EST)
After some digging it apears that number isn't correct for this patch either. I used the CustomInterfaceKit.exe provided by Blizzard and looked at the Interface\FrameXML\FrameXML.toc and it appears this version is 1300. Am I wrong about that? --Ehertlein 16:43, 22 Mar 2005 (EST)
- -- No, they pulled the same stunt on us again. 1300 is the working number... --The Nerd Wonder 22:49, 22 Mar 2005 (EST)
I'm concerned about the use of non-standard headers in this file, especially when they're not named in a way that clearly shows they're not provided by Blizzard.
As far as I can tell, these are the current standard header roots:
DefaultState: SavedVariables: RequiredDep OptionalDep Notes Title Interface:
Including user defined headers that have names that will potentially get used by WoW later is a bit risky, and passing them off in this document as 'standard' rather than as some extension for a specific tool is also a little bit misleading. I would hope this wasn't the intent, and enthusiasm just got in the way, but I would seriously consider:
- Renaming the extension ones with a common prefix, that'd at least reduce the possibility of collision.. Maybe the honored tradition of a leading 'x' - xURL xEmail etc..
- Making it clear in this document that those headers are *NOT* part of the standard .toc format, and are extensions used by a specific tool.
-- Flickering 11:51, 1 Apr 2005 (EST)
Am I wrong in assuming that if you mark your addon as dependent on another addon, your addon will always be loaded after the other addon? This article doesn't seem to say anything about that. --Zootsko 12:30, 3 May 2006 (EDT)
- If addon 1 is listed in the RequiredDeps, Dependencies, or OptionalDeps of addon 2, addon 1 should load first so that all the globals declared in addon 1 are available to addon 2. In other words, yes. :) (I know, I'm answering an old question, but I had nothing better to do)
I have recently been debating updating some addons that are now longer being updated, but I was not sure how to create a TOC file, could someone please help me out?
- You are aware that the article tells you exactly what to do, right? All it is is a plain-text file with ".toc" as the extension.
I wrote a PHP script that generates the basic files for an addon (1x .TOC, 1x .LUA, and 1x .XML files) and populates the .TOC with user defined info. Check it out.
I think the part telling that the .toc files are read only when the client initially starts up is no longer true as of 4.0.1. I commented out some referenced files (and didn't delete them) and after ReloadUI these files were no longer read (the code included in them clearly didn't run). Can one confirm? Mars85 (talk) 13:54, 6 November 2010 (UTC)
I've reorganized this into sections, and pulled in the body of Getting the current interface number to one of those sections. This makes for a slightly longer article, but I feel this prioritises the information from "most" to "least" relevant. (ie, game-changing things near the top like the basic rules and interface version numbers, versus unimportant things pushed to the bottom because they are only used by GetAddOnMetadata). If this sticks after a few days, then I will add a merge or delete tag to the other article that is no longer really necessary. DDC (talk) 16:05, 30 January 2020 (UTC)