World of Warcraft
| Release dates
November 23, 2004
November 23, 2004
|Warcraft: Orcs & Humans||1994|
|Warcraft II: Tides of Darkness||1995|
|Warcraft II: Beyond the Dark Portal|
|Warcraft III: Reign of Chaos||2002|
|Warcraft III: The Frozen Throne|
|World of Warcraft||2004|
|The Burning Crusade|
|Wrath of the Lich King|
|Mists of Pandaria|
- Mod friendly (Mods pertains to UI addons)
- Very active community
- Currently the largest MMORPG around
- Updated frequently
- Runs well on low end machines
- Expansions must be bought to play in active endgame areas and activities
- Game requires $15 per month subscription fee
- Official Blizzard community site
- WoW Insider - A news site dedicated to all World of Warcraft news.
- WoWWiki - A huge wiki for everything World of Warcraft related. Also handles anything Warcraft universe related.
- Thottbot - A old but expansive database on anything that can be found or used in-game.
- Wowhead - An expansive database on anything that can be found or used in-game. Has a clean interface.
- Statista - A ranking on the distribution of characters across EU and U.S. realms. Other statistics on World of Warcraft accessible.
- 1 Availability
- 2 Game data
- 3 Video settings
- 4 Input settings
- 5 Audio settings
- 6 Network
- 7 Issues fixed
- 8 Other Information
- 9 System requirements
- 10 References
|Official website||First 20 levels are free to play. Base game purchase includes the Burning Crusade, Wrath of the Lich King, Cataclysm and Mists of Pandaria expansions.|
- The playable characters from all expansions are available, even if the player has not bought any expansion packs.
Downloadable content (DLC) and expansions
|The Burning Crusade||Available for free. Included with all full versions of the game.|
|Wrath of the Lich King||Available for free. Included with all full versions of the game.|
|Cataclysm||Available for free. Included with all full versions of the game.|
|Mists of Pandaria||Available for free. Included with all full versions of the game.|
|Warlords of Draenor||Can be bought from the Battle.net store.|
Configuration file(s) location
- Progress and stats are saved automatically by Battle.net
|Field of view (FOV)||Zoom can be increased beyond the default. See Field of view (FOV).|
|Borderless fullscreen windowed|
|Anisotropic filtering (AF)|
|Vertical sync (Vsync)|
|High frame rate||Frame rate is capped at 200 FPS.|
|Color blind mode||Default shows text when mouse is over the unit (Friendly, Neutral or Hostile). Even further modes are available see Color blind mode.|
The maximum distance you can zoom out the camera can be increased using this command:
/console cameraDistanceMaxFactor 40
Enable color blind mode
|Keyboard and mouse||Native||Notes|
|Mouse input in menus|
|Mouse Y-axis inversion|
|Separate volume controls|| Master, sound, music, ambience. |
A selected number of optional sounds can also be fully disabled
|Surround sound||5.1 and 7.1|
|Mute on focus lost|
|EAX support|| EAX 3. XP compatiblity mode is also required from Vista onwards (besides DirectSound3D restoration).
|Spanish||Latin American only.|
|Protocol||Port(s) and/or port range(s)|
|TCP (outbound)||3724, 1119, 1120, 4000, 6112, 6113, 6114, 80, 6881-6999|
|UDP (outbound)||3724, 1119, 1120, 4000, 6112, 6113, 6114, 80, 6881-6999|
- UPNP support status is unknown.
Windowed mode (OS X)
OS X - Windowed mode
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:
FPS performance issues (OS X)
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.
- For more information on how to install a Windows partition on a Mac see this official guide.
Sound issue (OS X)
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.
Mature Filter Options Not Saving
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.
- To increase the various graphical settings further than the sliders allows, use these commands:
/console farclip 777
/console horizonfarclip 2112
/console groundeffectdensity 256
/console groundeffectdist 140
/console smallcull 0
/console skycloudlod 3
- A comparison of each setting is shown in this video.
DirectX 11 Rendering
- DirectX 11 can significantly boost performance in some scenarios
Enable DirectX 11
If World of Warcraft is installed on an SSD, this will drastically decrease the load times for zoning.
Move SSD Cache
The World of Warcraft cache folder is required to hold uncompressed files and hotfix data. To save space on the SSD, it is possible to junction link the cache folder to a different drive. This should save approximately 7.5 GB of space on the SSD, although it may incur a minor performance hit.
mklink /j "C:\Games\World of Warcraft\Data\Cache" "D:\Games\Blizzard Stuff\World of Warcraft\Data\Cache\"
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.
Blizzard's AddOn policy
With the release of Patch 3.1, Blizzard Entertainment introduced a new UI AddOn development policy. Here is a summary below:
- AddOns must be free of charge.
- AddOn code must be completely visible.
- AddOns must not negatively impact World of Warcraft realms or other players.
- AddOns may not include advertisements.
- AddOns may not solicit donations.
- AddOns must not contain offensive or objectionable material.
- AddOns must abide by World of Warcraft ToU and EULA.
- Blizzard Entertainment has the right to disable AddOn functionality as it sees fit.
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."
Creating an AddOn
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 "
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)
- Tip: Make sure you do not have any extra spaces at the end of the line with the filename specified. If you do, the extra space is taken as part of the filename and will cause your AddOn to silently fail to load.
- Tip: The .toc file is not reloaded when you reload the user interface; if you make changes to it, you will need to quit all the way to the desktop before they take effect.
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.
- <API_LatestInterface> is the current interface number.
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.
Other keywords in the toc file
Please check out The TOC Format for a more detailed list.
Troubleshooting an AddOn
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"
|Operating system (OS)||XP||Vista, 7, 8, 8.1|
|Processor (CPU)|| Intel Core 2 Duo E6600
AMD Phenom X3 8750
| Intel Core i5 2400|
AMD FX 4100
|System memory (RAM)|| 1 GB (XP)
2 GB (Vista, 7, 8, 8.1)
|Hard disk drive (HDD)|| |
|Video card (GPU)|| Nvidia GeForce 8800 GT
ATI Radeon HD 4850
Intel HD Graphics 3000
512 MB of VRAM
| Nvidia GeForce GTX 470 |
ATI Radeon HD 5870
1 GB of VRAM
|Operating system (OS)||10.8.x||10.9|
|Processor (CPU)||Intel Core 2 Duo||Intel Core i5|
|System memory (RAM)||2 GB||4 GB|
|Hard disk drive (HDD)|| |
|Video card (GPU)|| Nvidia GeForce 9600M GT
ATI Radeon HD 4850
| Nvidia GeForce GT 750M |
AMD Radeon HD 6750M