What is it?
LinkyLink automatically responds with links of your Tradeskills for people who request them. LinkyLink recognizes messages in plain english, and responds with the Tradeskill links that were requested.
How do you use it?
LinkyLink responds to whispers that contain the word 'link', and the name of a tradeskill. LinkyLink saves your tradeskill links when you open the window, and saves them for when they are requested. After you install the addon no action is required to enable it, other then opening your Tradeskill window for the Tradeskill you want to link.
LinkyLink also works in Party, Officer, Guild, and Raid chat. Any message in one of those channels must include: the 'link' keyword, your character name (or a custom nickname), and one or more tradeskills to link. For example, typing /raid Parthos link Enchanting and Blacksmithing would trigger the character 'Parthos' to link his Enchanting and Blacksmithing skills.
If your guildies call you a nickname, they don't have to type your full name in Party, Officer, Guild, or Raid chat. You can use the /linkylink nickname command (see the Slash Commands section) to set a nickname which LinkyLink will respond to.
Slash Commands
LinkyLink works out of the box, but there are a couple slash commands you can use.
- /linkylink enable (or /llink, /ll)
- LinkyLink is enabled by default. This command enables chat messages and chat frame notifications.
- /linkylink disable
- This disables chat messages and chat frame notifications, but LinkyLink still saves Tradeskill data.
- /linkylink barker enable
- This enables barking in trade chat.
- /linkylink barker disable
- This disables barking in trade chat.
- /linkylink keyword newKeyword
- This is the word that must be present alongside a tradeskill name
- Keywords are not case sensitive, but must be made of letters and numbers.
- /linkylink nickname newNickname
- This is an alternate name which will trigger LinkyLink in Party, Officer, Guild, or Raid chat.
- Example: If your name is Parthos, and people call you Parth, use /linkylink nickname Parth
To Do
I'm hoping to have these in the next release:
- Allow multiple keywords. Create setting to require one, or all.
- Save Tradeskills when new recipes are learned.
Changelog
0.9.2
- Fixed a bug which would cause warning messages to be displayed even though debug was turned off.
- Fixed a bug which would cause an error when the /linkylink enable command was used
0.9.1
- Added support for barking in trade chat.
0.9
- Added support for linking multiple tradeskills.
- Added support for linking tradeskills in Party, Officer, Guild, and Raid channels.
- Added support for setting a nickname to respond to in Party, Officer, Guild, and Raid channels.
- Added support for linking First Aid. Must use 'FirstAid' as the tradeskill (e.g. /tell <character> link firstaid)
- Fixed bug where requesting multiple tradeskills would cause an error.
0.8
- Inital Version
- Added auto-response to whispers.
- Added support for all tradeskills except first aid.
------------------------------------------------------------------------
r24 | t3rmv3locity | 2009-02-17 00:33:21 +0000 (Tue, 17 Feb 2009) | 1 line
Changed paths:
A /tags/0.9.2 (from /trunk:23)
added 0.9.2
------------------------------------------------------------------------
r23 | t3rmv3locity | 2009-02-17 00:28:12 +0000 (Tue, 17 Feb 2009) | 1 line
Changed paths:
M /trunk/LinkyLink.lua
Fixed a bug which would cause an error when the /linkylink enable command was used
------------------------------------------------------------------------
r22 | t3rmv3locity | 2009-02-17 00:11:51 +0000 (Tue, 17 Feb 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
fixed capitalization
------------------------------------------------------------------------
r21 | t3rmv3locity | 2009-02-17 00:07:39 +0000 (Tue, 17 Feb 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
Added manual changelog
------------------------------------------------------------------------
r20 | t3rmv3locity | 2009-02-17 00:07:21 +0000 (Tue, 17 Feb 2009) | 1 line
Changed paths:
M /trunk/Changelog.txt
Added 0.9.2 and bug fixes
------------------------------------------------------------------------
r19 | t3rmv3locity | 2009-02-16 19:24:33 +0000 (Mon, 16 Feb 2009) | 1 line
Changed paths:
M /trunk/LinkyLink.lua
changed debug to false
------------------------------------------------------------------------
r11 | t3rmv3locity | 2009-02-16 16:36:41 +0000 (Mon, 16 Feb 2009) | 1 line
Changed paths:
A /trunk/.pkgmeta
A /trunk/Changelog.txt
Added Initial Versions
------------------------------------------------------------------------
r10 | t3rmv3locity | 2009-02-16 16:24:01 +0000 (Mon, 16 Feb 2009) | 1 line
Changed paths:
D /trunk/LinkyLink
deleted
------------------------------------------------------------------------
r9 | t3rmv3locity | 2009-02-16 16:23:53 +0000 (Mon, 16 Feb 2009) | 1 line
Changed paths:
D /trunk/LinkyLink/LinkyLink.toc
A /trunk/LinkyLink.toc (from /trunk/LinkyLink/LinkyLink.toc:8
moved to trunk
------------------------------------------------------------------------
r8 | t3rmv3locity | 2009-02-16 16:23:46 +0000 (Mon, 16 Feb 2009) | 1 line
Changed paths:
D /trunk/LinkyLink/LinkyLink.xml
A /trunk/LinkyLink.xml (from /trunk/LinkyLink/LinkyLink.xml:7
moved to trunk
------------------------------------------------------------------------
r7 | t3rmv3locity | 2009-02-16 16:23:32 +0000 (Mon, 16 Feb 2009) | 1 line
Changed paths:
D /trunk/LinkyLink/LinkyLink.lua
A /trunk/LinkyLink.lua (from /trunk/LinkyLink/LinkyLink.lua:6
moved to trunk
------------------------------------------------------------------------
r6 | t3rmv3locity | 2009-02-16 16:09:44 +0000 (Mon, 16 Feb 2009) | 1 line
Changed paths:
A /trunk/LinkyLink/LinkyLink.lua
A /trunk/LinkyLink/LinkyLink.toc
A /trunk/LinkyLink/LinkyLink.xml
Inital Version: 0.9.1
------------------------------------------------------------------------
r5 | t3rmv3locity | 2009-02-13 10:47:31 +0000 (Fri, 13 Feb 2009) | 1 line
Changed paths:
A /trunk/LinkyLink
Created Initial Version
------------------------------------------------------------------------
r4 | t3rmv3locity | 2009-02-13 10:30:14 +0000 (Fri, 13 Feb 2009) | 1 line
Changed paths:
D /trunk/linkylink
Created Initial Version
------------------------------------------------------------------------
r3 | t3rmv3locity | 2009-02-13 10:29:45 +0000 (Fri, 13 Feb 2009) | 1 line
Changed paths:
D /trunk/asdf
A /trunk/linkylink (from /trunk/asdf:2)
Created Initial Version
------------------------------------------------------------------------
r2 | t3rmv3locity | 2009-02-13 10:29:29 +0000 (Fri, 13 Feb 2009) | 1 line
Changed paths:
A /trunk/asdf
Created Initial Version
------------------------------------------------------------------------
r1 | root | 2009-02-13 07:36:49 +0000 (Fri, 13 Feb 2009) | 1 line
Changed paths:
A /branches
A /tags
A /trunk
"linkylink/mainline: Initial Import"
------------------------------------------------------------------------
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)...
