WUU FAQ

From WUUki

[edit] Main FAQ

Where do I find the WUU log and setting files?

On Windows: Everthing is in %USERPROFILE%\WUU

On OSX: Log files, traces, support files in $HOME/Library/Application Support/WUU, settings file in $HOME/Library/Preferences/WUU

On Linux: Everything is in ~/.wuu

When I "upload my addons list", where does it go?

You'll see a code in your combat event log (example: 19cc7d9403c48849966d011ef101bb5a) which can be used with File -> Import -> from addonpack to install the same set of addons.

http://wuu.vagabonds.info/addonpack.php?id=|code|&output=friendly gives a list of the addons: Example from earlier

All based on the example here: AddonPack:19cc7d9403c48849966d011ef101bb5a

What do I do with addons still marked as [Unknown] after I've updated with the master list?

See Manual addon setup

What are all these references I see to "Wurm"? (in the code/error logs/etc.)

The working title for WUU was "WoW UI Resource Manager", or Wurm for short - but, it was renamed, since there's some other project with a similar name ;) Most of the internal code still retained the Wurm name, and currently WUU is the GUI code, while Wurm is the library that "does the grunt work" of keeping your addons up to date

What's "Upd?"?

Short for "Update available?" - It'd look silly with a 40 pixel wide column for a single letter :P

'N' means "no update available", 'Y' means "update available", and 'E' is a special case for WoWace addons; it means the embedded libraries have been updated (and will trigger an update if you use Ctrl-U)

'U' means the addon has finished updating, and 'UE' means the addon has finished updating, but that the only change was the embedded libraries.

Why do all my local versions say "?"?

WUU uses its own version numbers for most addons, and can't reliably figure out the version of addons not updated thru WUU - please update all addons once inside WUU for it to have a chance to know which version you're running.

Why does WUU insist that some of my addons should be [Ignore]d?

WUU [Ignore]s folders that are checked out from svn by default (for mod authors - a folder containing a .svn folder is auto-ignored permanently, until the .svn folder is removed) - if you're not the author of the mod in question, you can safely delete the .svn folder.

Why did WUU suddenly stop working with CurseGaming/WoWace/WoWI/etc.?

WUU relies on the mod sites staying roughly the same design-wise to work - some small changes might not "break" WUU, but other (often "invisible" changes) can throw off WUU enough that the only way of getting it back on track is a new version updating the regular expressions used (from the Tools menu - added in 1.1.145).

Where does WUU store the downloaded addon files?

The "raw" ZIP and RAR files are stored in your temp directory - on Windows, this is typically "%TEMP%\Wurm", while on Linux and OSX it should be /tmp/Wurm/. Use the option "Tools -> Clean temp dir" (Ctrl-T) if you want to delete everything there.

Why doesn't WUU work with UIWoW anymore?

ui.worldofwar.net now blocks WUU "due to bandwidth concerns"

More details in this post and that post

How can I make WUU use a HTTP proxy server?

Set a system environment variable of HTTP_PROXY using the format "http://<ip>:<port>" substituting <ip> for the address or hostname and <port> for the port for your proxy server. For example "http://localhost:8080".

On Windows, WUU will use MS Internet Explorers proxy settings, if these are set.

What does '(WARN) Skipping forbidden file X' mean?

WUU has a whitelist of allowed file extensions (TOC, XML, LUA, TXT, TGA, GIF, JPG, JPEG, TTF, BLP, MP3 and no extension) - WUU will not extract other files from ZIPs/RARs (added in 0.7.32)

Starting with 1.7.533, the extensions HTM, HTML and M2 are also extracted.

Why do I get Read-only file system: 'WUU.log' when I try to run WUU on OS X?

WUU can't be run directly from the .dmg (yet) - you'll have to drag it to (for example) your WoW directory first

What are the different WUU versions?

WUU uses the version numbering system <major>.<minor>.<revision> (for instance, 1.4.320, the current stable, is major version 1, minor 4, and revision 320).

The revision is grabbed directly from the SVN revision number of WUU.py, so it's always higher than the previous release, regardless of major/minor (i.e. it's not reset to 0 for each minor version).

The minor version used to be changed when the format of the XML files changed, but after 1.0, it works more like Linux kernel version numbers; even for stable versions, odd for beta versions (1.2 was the last stable, then we had a lot of 1.3 betas, leading to 1.4 stable - the next beta cycle will be 1.5, leading to 1.6 stable) - our goal is to have a stable version that's usable until the betas are done.

Finally, the major version was set to 1 when WUU first turned stable, and will be upgraded again when WUU is significantly different from what 1.0 was (considering how little WUU has changed in appearance since 0.2, this might be "never" :P).

Why doesn't WUU work with CurseGaming as of v1.6.500 (2008.01.22)?

Curse had some minor changes to their page, that prevented WUU from working - it should work again now.

[edit] Issues that have been fixed

Kaspersky Anti-Virus/F-Secure/AVG Antivirus says WUU is infected with Trojan-Spy.Win32.KeyLogger.jm/PSW.Generic4.KTX

This is a false positive, due to some virus being written in Python and compiled with py2exe (which the WUU Windows release also is)

More details in this blog post, and the FretsOnFire forums (FOF also had the exact same positive, and they're also using Python/py2exe)

There is no keylogger compiled into WUU by any of the developers

Both F-Secure and Kaspersky released updates to their virus defintions on 2007-05-25, both of which no longer mark WUU as "infected"

Grisoft released an update to AVG's virus defintions on 2007-05-27, which is reported to no longer mark WUU as "infected"

The auto-updater doesn't work for me! It just downloads the new version and claims it's upgraded, but when I restart WUU it wants to upgrade again!

Yep, it's a bug :( Answer "no" and disable auto updates in the preferences - I'll change how the updates are done in a future version.

Should work for everyone starting from 1.1.139

Why doesn't WUU save my site IDs? (Mac OSX specific)

Short answer: I don't know - wxWindows seems to work differently on Mac, but I'll re-code much of the siteID stuff later. For now, the only workaround is editing \addons.wurm.xml manually and inserting the site IDs there :(

Fixed in 1.1.156

WUU won't download the latest version of a mod from CurseGaming!

WUU tries to download the latest release version of the mod, but that isn't available anymore (1.12 versions were removed, it seems) - the one you want is the latest beta, but WUU doesn't search those (yet - a "search betas"-flag will be added in a future version)

Support for Curse beta mods added in 1.1.165

Will WUU support ctmod.net?

CTMod.net isn't very fun to work with; their "high bandwidth" UI has you selecting by means of radio boxes which addons you want, after which you download a generic "CTMod.zip" (which doesn't work in, among others, ICEOWS or the default Windows unzipper - so there's a good chance the python Zipfile module might choke on it, too) tailored to what you want. Of all the "specific mod sites", I'd say ctmod is the worst to work with programatically (for now, at least - I'll look into it when they're back up).

Supported since 1.1.185

Why won't WUU work with ClearFont?

WUU only works with addons that extract all their files to Interface\AddOns - ClearFont, and some other addons, need files directly in the WoW directory, which WUU doesn't support (yet - support is planned in 1.2 or so)

Most addons should work without changes now - and ClearFont recently got a "cleaner" version with no funny placements of files

I get the error "WUU crashed on startup! Error, module object has no attribute HTTPCookieProcessor"

Mac OSX 10.4.8 ships with Python 2.3 - you need Python 2.4 or higher to run WUU

Newer versions of WUU have a workaround that may or may not make this work even on Python 2.3