- Home
- Downloads
-
Addons & Mods
Featured
World of Warcraft
5,105 Addons
-
Popular Downloads
- Top World of Warcraft Addons
- Top Minecraft Server Mods
- Top Rift Addons
- Top Skyrim Mods
- Top World of Tanks WoT Mods
- Top Starcraft II Maps
- Top Terraria Maps
- Top Runes of Magic Addons
- Top Warhammer Online Addons
- Top Age of Conan Addons
-
- Curse Client
- Premium
- News
- Giveaways
- Videos
- Forums
TuckBindings
Login to Add Favorites
- 0 Likes
- World of Warcraft
- 15 Monthly Downloads
- Supports: 4.0.3a
- 865 Total Downloads
- Updated 2/7/2011 4:12:48 PM
- Created 1/20/2011 4:12:32 AM
- 4 Favorites
- Project Site
- Comments
- Release Type: Release
- License: TuckLicense
- Newest File: v4
About TuckBindings
This addon allows players to define their key bindings offline in a text file. The bindings are defined per class/spec combo and will work with any character you log on.
Introduction
- This addon is aimed at power users who have a basic understanding of wow addons and are not afraid of editing their configuration in text files. If this scares you, this addon is not for you.
- Key bindings are defined per-class
- You can create bindings that depend on your actual talents, and they will update automatically when switching talents.
- Any WoW macro can be bound to any key. There are functions to simplify the setup of commonly used macros and spell casts.
Quick Start
- Download and install the addon
- If you are updating the addon, read the next section
- Open the folder containing the addon
- Open the file TuckBindingsPriest.lua in any text editor
- Notepad will do, although I recommend SciTE
- Right under the line telling you to 'Add your key binding configuration here', add the following line
- TB:Cast('4', "Heal")
- Start WoW and log in as a priest (if you're already online, reload your interface by typing '/reload')
- Press 4 to cast the spell Heal
Updating the addon
- Always manually update the addon.
- Download the addon and only overwrite the TuckBindings.lua file. I will never make any changes to the class-specific files, these are your own configuration.
- For really advanced users, install git and update from curseforge
Details
- The configuration is reloaded every time you switch your talents
- You can force the configuration to reload by reloading your interface, or logging out and in
- The configuration will remove any actions previously bound to the same keys
- After the configuration was loaded, there will be a short summary of your key bindings in the default chat frame
- Edit the file TuckBindingsCommon.lua to define key bindings that are common to all characters
- Edit the file TuckBindingsXYZ.lua to define key bindings for all characters of class XYZ
- If you specify multiple spells/macros for some key, they will be concatenated and executed in the order you specified them
Example and documentation
- Have a look at the following reference or full example
tag v4
f65fc8843e88b3816d54cf7ea29ad20224d46c9f
root <root@db06.curselive.local>
2011-02-07 22:12:46 +0000
Clean up initial configuration
--------------------
TuckOfArthas:
- Remove old key bindings for the default configuration
- add warning for overlength macros
Top Downloads
-
- Bagnon
- Bags & Inventory
- 359,243 Monthly Downloads
-
- Deadly Boss Mods
- Combat and Boss Encounters
- 297,158 Monthly Downloads
-
- Recount
- Combat
- 295,968 Monthly Downloads
-
- SpellFlash
- PvP, Buffs & Debuffs, Quests & Leveling, Action Bars, and Combat
- 284,254 Monthly Downloads
-
- GatherMate2_Data
- Achievements
- 208,828 Monthly Downloads
Comments
Fantastic addon, it seems!
There is only one issue that bugs my OCD greatly.
If I use TB:Cast('1', 'Mortal Strike') or any variant thereof, and then press that button, I do not get the "I need a target" error -- this is the same even if I specify harm, exists and similar. The output text if I define this in-game is "/cast [@target]Mortal Strike", which also does not produce the error -- evidently because of the [@target].
I've tried even using TB:Macro('1', '/cast Mortal Strike'), but that has the same result -- even though actually running /cast Mortal Strike causes the desired error.
Do you know any way I might be able to preserve my errors and such, causing it to be more like casting actual spells? :)
Side note, any solutions for binding buttons 1-6 or so to actions, but use buttons when the Vehicle UI is up? I figured a macro might do it, [vehicleui] works as a condition, but not sure what to use as the "action".
The default target for all spells in my addon is [@target], meaning that you require a target even for aoe spells. A workaround is to explicitely specify the target in the fourth argument, as in TB:Cast("1", "Shadowfury", nil, ""). I probably should change this default behavior.
If I use TB:Macro, I do get errors, could you please check that again? Do you have other spells bound to the same key?
Vehicle UI:
Unfortunately this won't be easy. You can cast vehicle spells by name (like /cast [vehicleui] Afterburner), but that is of course not a general solution. Vehicle spells are just the first few action bar buttons. Personally, I have therefore bound action bar buttons 1-9 to CTRL-1 - CTRL-9, which I don't use for key bindings.
if GetActiveTalentGroup() == 1 then
TB:Cast("1", "Lifebloom")
TB:Cast("2", "Regrowth")
-- etc
elseif GetActiveTalentGroup() == 2 then
TB:Cast("1", "Moonfire")
TB:Cast("2", "Wrath")
-- etc
end
As for the conditional bindings, there is a section in the reference that shows how to create bindings that are only active if the character knows a certain spell. Since each talent spec has a unique core spell (starsurge/magle/swiftmend for you), you could use that. See here: http://wow.curseforge.com/addons/tuckbindings/pages/reference/#w-conditional-bindings
However, there might be situations where you really want different bindings even if you have the same spec, so I will add your suggestion.