Skip to content
Maintankadin

3.0 Addon Survival Guide

_Chloe
Tue Oct 14, 2008 1:12 am

3.0 Addon Survival Guide

Find your 3.x compatible mods on these lists below.

http://www.wowinterface.com/survivalguide.php
http://www.wowinterface.com/downloads/index.php?cid=110
http://wowui.worldofwar.net/?p=browse&x=wotlk&pg=1&sb=newrating&so=down

Note: Since this is a full Client upgrade I HIGHLY suggest deleting your Addon Directory, and also your WTF files. This should clear up any old saved variables and file conflicts with the 3.0 client.
_________________

MainTankadin UI/Addon Forums Moderator
_Chloe
Tue Oct 14, 2008 1:15 am
Installing Addons

The UI & Macros forum on the WoW site can be a great help as well. Here is a guide written by Lopeppeppy (edited by Troodi) that is plastered all over that forum.

Where is my addons menu!!? Lopeppeppy's Guide on Mod Installation

If the button doesn't appear on the WoW interface, it's because the mods aren't installed correctly, (or alternatively, none installed at all).

► First - Make sure you only have one copy of WoW installed, and your addons are in the correct directory. It has happened before that people have had two copies installed, and just been putting their addons into the wrong one!

► Second - Make sure you are unzipping/uncompressing your addons. WinZip, WinRar and StuffIt (for Mac) are three common unzipping programs.
● WinZIP users: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders as per the mod Authors structured directory paths.

► Third - Make sure that you aren't installing addons while WoW is running. WoW doesn't register addon changes until you logout and then back in, so save yourself some frustration and install while logged out and WoW is not running. Log in to check them, log back out as necessary to fix things.

► Fourth - Check the "Load Out of Date Addons" button on your Addons screen (when you install them properly, or if you already have some installed).

● If using the Windows VISTA system, there are peculiarities with needing to have Administrator privileges, and have all of the folders "visible." Check the Tech Support Forum for more info, there are threads there to help sort out how Vista and WoW interact. One recommendation given is to move the entire World of Warcraft folder to someplace other than C:\Program Files. Vista has security features where it doesn't allow programs to make changes to files inside the Program Files folder (unless they run as administrator).

● For Mac Users, check spelling. Make sure the AddOns folder is named and matches exactly the capital letters and spelling to be: AddOns (The "O" is a capital letter and not the number zero "0")

After that...

■ THE MOST COMMON ERROR is that the unzipper program embedded them into an extra folder layer. If you have any questions about whether your addons are embedded one folder too deep, post a path for the .toc file of each addon

CORRECT EXAMPLE:
C: \ Program Files \ World of Warcraft \ Interface \ AddOns \ MODFolder \ ModName.toc < --- would be a correct pathing

INCORRECT EXAMPLE:
C: \ Program Files \ World of Warcraft \ Interface \ AddOns \ MODFolder1.23.456 \ MODFolder \ ModName.toc < --- is NOT correct, and the addons will not load properly.

There should only be one path-step between the AddOns step and the .toc step, and it should be the name of the addon (most usually). Look very very closely at the directory structure, make sure that the addons folder is in the proper place. If you have any questions about whether your addons are embedded one folder too deep, post a path for the .toc file of each addon.

Standard Interface Guide
http://forums.worldofwarcraft.com/th...381215&sid=1#3
-----
Here's an excellent FAQ to read as well: http://www.wowinterface.com/forums/f..._howto_install
-----
Sample screen of file directory structure (Macs have same basic structure, though some minor differences)
http://www.wowinterface.com/storage/faq/correct.gif
-----

* * * *
_________________

MainTankadin UI/Addon Forums Moderator
_Chloe
Tue Oct 14, 2008 1:15 am
Vista Users - UAC and You - From WoWInterface

If you don't want to know all the background information on WHY this is necessary, and just want to get WoW to work, then scroll down "Making It Work" below.

Are you having trouble installing addons? Are you changing files or deleting your WTF folder, but somehow magically WoW ignores the changes? If you're on Windows Vista, a new security feature called "User Account Control" is likely to blame.

About User Account Control (UAC)
Microsoft's Windows Vista is the latest generation of their Windows operating system. Along with new eye-catching features, Vista also takes a new, hard stance on security. This new stance, however, caught some programmers off-guard. As a result, these new features have caused some programs to operate slightly differently than expected, and unfortunately, World of Warcraft is one of them.

The new feature in question is called "User Account Control" or "UAC." UAC is a great feature that provides users with the security that they are not running as administrators all the time. *nix users will be familiar with this system, as the overwhelming majority of them will agree that you should not be running as root, and only give permissions to programs as necessary.

One of the restrictions imposed by this is that the Program Files folder cannot be modified without "escalated" (administrative-level) permissions. WoW (by default) does not run escalated, so it does not have access to the Program Files folder. You may, however, be aware that WoW needs to write files there! It stores all of your configurations (in the WTF folder), it stores the cache data (in the Cache folder), and it even puts some default addon keys there.

So why doesn't WoW just crash when it can't write there? Well, Microsoft was intelligent. They foresaw that older programs consistently used this folder to store configuration information, even though it has been strongly discouraged by Microsoft for years in favor of the %APPDATA% folder. So they invented this idea of "virtualization." If a program does not indicate to Vista that it is "UAC Aware" (via a "manifest"), Vista assumes that the program is not aware of the permissions restrictions. So, instead of denying access, it "fakes" write access. Anything the program tries to write or create in the Program Files folder then gets actually written to the "Virtual Store" which is located at C:\Users\[username]\AppData\Local\VirtualStore. If you go there and don't properly have WoW set up, you may even see that there is a Program Files\World of Warcraft folder there with various files that have been virtualized away.

Making It Work

So, how do we stop this? There are actually several solutions, though some are preferred over others due to simplicity.

* Option 1: Install in an Unprotected Location

This option is best for people whom haven't yet installed or aren't worried about installing again and losing their settings. The idea behind it is quite simple: If you don't install in the Program Files folder, WoW won't be restricted by Vista. Many people recommend creating a C:\Games folder or something similar. Thus, your program would be installed in

C:\Games\World of Warcraft

So long as you don't use the "Windows" or "Program Files" folders, you should be OK.

You can also use another drive for World of Warcraft. If you do so, it is perfectly acceptable to create a "Program Files" folder on that drive and install it there, like the screenshot below. In such a case, Vista realizes that this is not the "real" Program Files directory, so it is not protected by UAC.

Click this bar to view the small image.


(Note that the folder is called "Program Files (x86)" because this is a 64-bit copy of Vista and a 32-bit program.)


* Option 2: Provide Administrative Permissions

This isn't always the easiest option because it requires a bit of moving, especially if you've already played WoW for a while and your settings are currently virtualized away. It does, however, avoid the need for a new installation. Giving WoW administrative permissions provides a means for WoW to write directly to the Program Files folder, so it doesn't get virtualized anymore.

If you right click on "WoW.exe" in your Program Files directory, you will find an option "Properties." Clicking on this will bring up the Program Properties window. Click on the "Compatibility" tab. You will see the following pane:



Check the box next to "Run this program as an administrator."

Next, do the same for "Launcher.exe" in the same folder. Open the "Compatibility" tab and check "Run this program as an administrator."

If this is done correctly, the next time you run WoW, you will get a UAC escalation popup, which looks like this:



This popup asks for escalated permissions for the program shown. If it does not say "Blizzard Entertainment" and "Blizzard Launcher" or "WoW.exe," double-check that it's the right program before giving permissions.

However you have another problem -- all your old settings! Now that WoW has administrative permissions, it will no longer consult the Virtual Store for settings, meaning all your settings have been lost! Fortunately, we can move them back to where they need to be.

Go to "C:\Users\[Username]\AppData\Local\VirtualStore\Program Files\World of Warcraft" and you will find all of your WTF folders, etc. Copy your WTF folder into "C:\Program Files\World of Warcraft" and your settings will be restored. If prompted, the files in your VirtualStore should overwrite the ones that may already exist in your Program Files directory. Keep in mind that if you are using a 64-bit Vista, "Program Files" will be named "Program Files (x86)."

* Option 3: Disable UAC
This is a last-resort option and probably should not be used, but I place it here for informational purposes anyway. UAC is a beneficial feature which protects you from malicious code being executed at an administrative level where it can do serious harm. If not given escalated permissions, most malicious code may cause a little harm, but nothing too severe (perhaps an annoyance more than anything).

However, it is possible to turn it off if you really want to, and that will stop all of these Virtual Store and permissions problems. You will, however, be turning off one of the most crucial security features that Vista has to offer, so be absolutely sure you want to do this before you do it.

Click on the "Start" button and then choose "Control Panel" on the right side. Find the "User Accounts" icon and double click it. This will open up the "User Accounts" control panel. At the bottom, you will see an option "Turn User Account Control On or Off." Click on this option. You will see a UAC box pop up; validate that it is from Microsoft and then accept it. (Naturally you must give administrative permissions to disable this!). Uncheck the checkbox in the window that appears, and then select OK. UAC is now disabled. You may wish to follow the instructions in option 2 above, now, to copy over your WTF folder to your WoW folder, as these settings will no longer be virtualized away.


Conclusion
UAC is a useful feature provided by Microsoft that enforces policies that have been encouraged a long time ago. Unfortunately, programs are still not up with the times, and thus these changes sometimes cause a few glitches along the way. UAC still can provide the security you desire and your programs can get along with it just fine, it just may take a little extra attention. With this attention you can be sure to have a secure user account while enjoying the world we all love.
_________________

MainTankadin UI/Addon Forums Moderator
_Chloe
Tue Oct 14, 2008 1:15 am
The realms are up and my addons are broken!
That's not a question, but you're panicking. First, DON'T PANIC. Second, go check for updates to all of your addons. Here are direct links to the "latest updates" pages of some big addon sites:
WoWInterface: http://www.wowinterface.com/downloads/latest.php?wotlk
Curse: http://wow.curse.com/downloads/Updated.aspx
Atlas/AtlasLoot: http://atlasmod.com
Auctioneer: http://auctioneeraddon.com/dl
Cosmos: http://cosmosui.org
CT Mod: http://ctmod.net
Deadly Boss Mods: http://deadlybossmods.com

Should I check "Load Out-of-Date"?

Yes, but only after you update all of your mods. Some mods don't need updates (such as RP/guild mods) and can probably be safely run using an old version.

What mods have been updated?

Many have. Any "Wrath beta" compatible mod will work in 3.0.2.

Random mods not loading/working?

There's a known bug with mods using disembedded libraries (Ace2/3, Rock... etc) which is going to be broken until 3.0.3. Use embedded libraries until then. http://forums.worldofwarcraft.com/thread.html?topicId=10971929880#8

What happened to files.wowace.com?

It's now part of curseforge. See http://www.wowace.com for the announcement and http://www.curseforge.com too. Release-version mods can be found directly on wow.curse.com and via the curse client.

What mods have been discontinued?

* Bongos (see Dominos http://www.wowinterface.com/downloads/info10197-Dominos.html)
* Omen 2 (see Omen 3!)


What mods need to be updated?

Check for updates to ALL of your mods!

The biggest classes of AddOns that may break in 3.0 are action bar mods (dominos, bartender, etc...) and unitframe mods (agUnitframes, perl classic, pitbull, x-perl, etc...). Many have already been updated and work for the wrath beta.

A slightly more technical perspective:

Q u o t e:
Patches are great, they just mean we authors have to do a TON of work and then the users have to do a little bit of work.

The things I suspect will most likely cause issues are:

* Changes in underlying FrameXML method signatures due to this -> self (The change improves performance and sanity overall)
* Changes in the button font handling (This improves performance and memory use)
* Unification on the TradeSkill API's (death of the Crafting API) (This is massively helpful to any tradeskill UI developers as it makes enchanting no longer a special case)
* Conversion of mounts and companions into spells (Everyone should be in support of this!)
* Removal of the 'PlayerBuff' API's (these were rather odd anyway, and buff information handling got better as a result)
* Replacement of the old state headers (The replacement is significantly easier to use and more flexible)
* Some settings functions were replaced with CVars so they could go server side (The change enabled new functionality)

-- Iriel @ http://forums.worldofwarcraft.com/thread.html?topicId=10972023311#13

Macros / settings saved on the server?
Yup. You can turn this setting off by running the command "/console synchronizeSettings 0" on each account/computer you have, or by adding the line 'SET synchronizeSettings "0" ' to your config.wtf file on each computer.

What should I use instead of the WoWAceUpdater?

WoWInterface: http://www.wowinterface.com/downloads/info8239-WoWInterfaceUIManager-Windows.html
Curse: http://www.curse.com/client/ (requires a curse login)
_________________

MainTankadin UI/Addon Forums Moderator
_Chloe
Tue Oct 14, 2008 1:15 am
Where's a guide for updating my addons?
View the handy install guide at http://www.wowinterface.com/forums/faq.php?faq=install#faq_howto_install or see above

Why does Blizzard break addons every patch?
All Blizzard cares about is making sure its own UI works properly. Anything third-party is explicitly unsupported. More info in the Mods FAQ sticky at: http://forums.worldofwarcraft.com/thread.html?topicId=442927843#9

What did this patch do for addons?
The technical details are at http://forums.worldofwarcraft.com/thread.html?topicId=8202271194

Other Questions?
The "Mods FAQ - READ" sticky has all the information you need: http://forums.worldofwarcraft.com/thread.html?topicId=442927843
_________________

MainTankadin UI/Addon Forums Moderator
DexterBelgium
Thu Oct 16, 2008 4:40 am
Thank you for this, saved my life. Especially with the "DON'T PANIC" comment...

Suggested addition: Bartender 3 is also Dodo-food with this patch, see Bartender 4.

Other suggestion (tho I don't know whether the choice to not include it was intentional): wowmatrix for addon updatage.

Once again, thanks very much for this great guide.
Stilgarr
Thu Oct 16, 2008 11:52 pm
Thanks for this, proved to be very helpful.

I did notice something last night while sorting addons out though.

In the addons section of the character select screen, a fair few of the new ones were listed in red instead of yellow (blue for DBM).
I guess it must be down to out of date ones so unchecked the box. Nope, according to the menu they were all upto date so re ticked the box.

Only thing I could think of is that the main addon is still listed in yellow text with the dependancies (spelling) listed in red to make then stand out a little perhaps.

Though it might be worth a mention as a guildy saw the red names and spent ages looking for "newer" versions when they did not need to. Unless ofc there is another reason.



oh, and anyone know how I can get my damn Ora2 button to show on the map again, it's gone walkies Sad
_________________
Gelnon
Fri Oct 17, 2008 7:46 am
Red addons there are now Load on Demand ones I believe.
_________________
Kaedan
Tue Nov 25, 2008 6:22 pm
Thank you! Worked great
_________________
Gelnon
Wed Dec 17, 2008 11:58 am
Yes, you can just drag the World of Warcraft folder from Program Files to anywhere else. WOW recreates registry entries when it is run.
_________________