The maximum distance you can zoom out the camera can be increased using this command:
/console cameraDistanceMaxFactor 40
/console colorblindshader X
For a long time there was a bug where the player was unable to drag the screen after having gone into windowed mode which meant that the player couldn't decide on the screen size except for the defaults. In later patches this was fixed but in some rare cases the issue still persists. Follow these steps if you're still having the problem:
World of Warcraft might run sluggishly on older-model Macs (despite having the required specs). A workaround is installing a Windows partition using Boot Camp.
This is a known issue that only seems to occur on older MacBooks (PowerBook series, early MacBook series). The problem is that the computer isn't powerful enough to run the game with sound on (my hypothesis anyway) which causes it to distort the sound and make it unbearable to listen too. This happens when the computer gets too hot (Macs have a tendency to do that) from running the game because it takes a lot of the computers power to run it. The sound distortion then causes the in-game fps to fall dramatically causing unplayable lag. The only real solution to this problem, that works (experience) is shutting off the sound. Not just the speakers but going into the settings and removing Master volume. This will enable you to play the game without the excessive lag, on an old, although hot, MacBook.
Known issue with mature filter options not saving properly once set in the game menu. In order to force a save to the server side, open the options menu, change the setting (whether on or off), then use Alt+F4 to forcibly close the game. Re-open the game and new setting should be saved properly.
/console farclip 1300
/console horizonfarclip 2112
/console groundeffectdensity 256
/console groundeffectdist 140
/console smallcull 0
/console skycloudlod 3
/console gxTextureCacheSize <VALUE in MB>
World of Warcraft\WTF\Config.wtf
SET gxTextureCacheSize <VALUE in MB>
If World of Warcraft is installed on an SSD, this will drastically decrease the load times for zoning.
World of Warcraft's UI is developed via LUA scripting, and XML data.
AddOns are generally self-contained User Interface (UI) modification components. However, some AddOns can be dependent on other AddOns to work, and some AddOns are actually collections of other AddOns. There is no size restriction on AddOns, some can grow to be quite massive.
In plain English, an AddOn is just some files you can put in the installation folder that can (theoretically) improve your interaction with the World of Warcraft game (i.e. make it easier to play, or give you more information about what's going on in the game).
Often the name modification (or "mod" for short) is used interchangeably with AddOn. More specifically, a mod is a third-party AddOn that alters or enhances some aspect of World of Warcraft's interface. Mods can perform a wide variety of tasks, including adding new buttons to the screen, altering the built-in player and party frames. In extreme cases, mods completely supplant the standard WoW interface, usually offering more advanced functionality.
Some mods are standalone, able to run without any additional software. Others are built on libraries such as Sea or Ace. Still others are compilations of many individually-developed mods.
With the release of Patch 3.1, Blizzard Entertainment introduced a new UI AddOn development policy. Here is a summary below:
It isn't exactly clear how Blizzard plans to enforce this policy, but developers should follow the policy or risk some sort of exclusion of their AddOns from the game. The following sentence ends the introductory paragraph of the policy: "failure to abide by them may result in measures up to and including taking formal legal action."
First of all, you need to create a new folder in Interface\AddOns. The name of this folder is kind of important, as it is what other AddOns use to refer to your AddOn (in dependencies). Therefore, using version numbers in your AddOn folder name can be a bad idea; you will run the risk of having other AddOns "break" when you change the version. This will probably lead to people either not depending on your AddOn or, worse, that they'll keep using an old version.
Major version numbers as part of AddOn folder names might work, though.
.toc is short for "table of contents".
A functioning AddOn will need a file named <YourAddOnDirectoryName>.toc in "Interface\AddOns\YourAddOnDirectoryName\".
This file needs to have two things - an interface keyword with a correct interface number, and the name(s) of one or more files to load. However, Blizzard asks that you include at least these five client recognized tag lines:
## Interface: <API_LatestInterface>
## Title: My Add On
## Version: 1.0.0
## Notes: A short description of my AddOn
## Author: Your name or memorable descriptor (e.g. LuckyLuke)
To get the latest interface number, see #Getting the current interface number. The number in the .toc file must match the current build or the add on will not be loaded/active, unless the user has explicitly told WoW to load out-of-date Addons. If the .toc file declares an interface number prior to 2.0.0 (i.e. pre-The Burning Crusade), the AddOn can not be loaded, regardless of the load out of date AddOns setting.
If you include a Bindings.xml file, it does not have to be included in your .toc list of files to load - WoW loads this file automatically. This file is used to set key bindings specific to the AddOn.
Please check out The TOC Format for a more detailed list.
As of Patch 2.3, if you get a message "Interface action failed because of an AddOn", this means that an AddOn interfered with the Blizzard UI in some way. To diagnose this, enter the following into chat "/console taintLog 1" and restart the game and try to reproduce it. If you reproduce it, you can quit the game and search through the file Logs\taint.log for the word "blocked" and mail the log to the author of the AddOn listed there. Once you have done this you can turn off logging by entering the following into chat "/console taintLog 0"