Overview
AlwaysLFG joins the LFG channel automatically.
Just install AlwaysLFG, and type "/join LookingForGroup" if you haven't already. From then on, AlwaysLFG will make sure that you're signed in to the LookingForGroup channel whenever possible.
Details
What exactly does AlwaysLFG do?
WoW requires you to be in an LFG queue in order to have access the LFG channel, but it's often nice to be able to see LFG messages even when you're not specifically looking for a group.
AlwaysLFG solves this problem by automatically adding you to the LFG queue for the first item in the "Zone" category, which is typically unused. AlwaysLFG will add you to this queue (a) when you first log in, (b) when you leave a group, and (c) when you type "/alfg join".
As a result, just about the only time you'll be out of the LFG channel is when you're in a group that is not using the LFM tool--and in that case, there's not much you can do about it anyway.
By the way, you can also type "/alfg leave" if you decide you'd like to leave the LFG channel.
How do I customize the LFG comment?
By default, AlwaysLFG sets your LFG comment to say that you're just listening to the LFG channel, so that people who see you in the LFG tool know that you're not actually looking for a group for that zone.
If you'd like to change this comment, type "/alfg config" and enter a new comment. You can set up separate profiles for different characters if you'd like to have a different LFG comment for different characters.
------------------------------------------------------------------------
r33 | merialkilrogg | 2009-04-16 08:35:32 +0000 (Thu, 16 Apr 2009) | 3 lines
Changed paths:
A /tags/v2.0.1 (from /trunk:32)
Tagging as v2.0.1
Re-added profiles.
------------------------------------------------------------------------
r32 | merialkilrogg | 2009-04-16 08:34:39 +0000 (Thu, 16 Apr 2009) | 3 lines
Changed paths:
M /trunk/AlwaysLFG.lua
M /trunk/AlwaysLFG.toc
Re-added profiles.
Bumped version number to 2.0.1.
------------------------------------------------------------------------
r30 | merialkilrogg | 2009-04-16 08:25:48 +0000 (Thu, 16 Apr 2009) | 4 lines
Changed paths:
M /trunk/.pkgmeta
M /trunk/AlwaysLFG.lua
M /trunk/AlwaysLFG.toc
M /trunk/embeds.xml
Upgraded to Ace3.
Compatible with WoW 3.1.
Bumped version number to 2.0.
------------------------------------------------------------------------
r28 | MerialKilrogg | 2008-10-19 04:40:05 +0000 (Sun, 19 Oct 2008) | 3 lines
Changed paths:
M /trunk/AlwaysLFG.toc
AlwaysLFG:
- Incremented version to 1.1.
------------------------------------------------------------------------
r27 | MerialKilrogg | 2008-10-15 07:14:56 +0000 (Wed, 15 Oct 2008) | 4 lines
Changed paths:
M /trunk/AlwaysLFG.lua
M /trunk/AlwaysLFG.toc
AlwaysLFG:
- Updated to WoW 3.0.2.
- You can now customize the LFG comment using "/alfg comment ...".
------------------------------------------------------------------------
r26 | root | 2008-09-30 15:39:54 +0000 (Tue, 30 Sep 2008) | 1 line
Changed paths:
M /trunk/.pkgmeta
Hopefully fix .pkgmeta
------------------------------------------------------------------------
r25 | root | 2008-09-29 21:47:40 +0000 (Mon, 29 Sep 2008) | 1 line
Changed paths:
M /trunk
A /trunk/.pkgmeta
Facilitate WowAce-on-CurseForge transition
------------------------------------------------------------------------
r23 | root | 2008-09-29 20:57:32 +0000 (Mon, 29 Sep 2008) | 1 line
Changed paths:
D /tmp/trunk/AlwaysLFG
A /trunk (from /tmp/trunk/AlwaysLFG:22)
Importing old repo data under /trunk
------------------------------------------------------------------------
r20 | Merial | 2008-05-01 02:14:56 +0000 (Thu, 01 May 2008) | 3 lines
Changed paths:
M /tmp/trunk/AlwaysLFG/AlwaysLFG.lua
AlwaysLFG:
- Removed incorrect dependency on AceHook, which caused loading to fail.
------------------------------------------------------------------------
r18 | Merial | 2008-04-27 08:35:07 +0000 (Sun, 27 Apr 2008) | 3 lines
Changed paths:
A /tmp/trunk/AlwaysLFG
A /tmp/trunk/AlwaysLFG/AlwaysLFG.lua
A /tmp/trunk/AlwaysLFG/AlwaysLFG.toc
A /tmp/trunk/AlwaysLFG/embeds.xml
AlwaysLFG: initial commit
- Automatically joins the LFG channel when signing in and when leaving a group.
------------------------------------------------------------------------
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP has a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: 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 how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
