Hacking World of Warcraft
Part I: Simple Hacks: Addons, Macros, and More.
Chapter 1: Introduction to WoW Modding.
Chapter 2: Combat Addons.
Chapter 3: Map Addons.
Chapter 4: Miscellaneous Addons.
Chapter 5: Loot Addons.
Chapter 6: Chat Addons.
Chapter 7: Raid Addons.
Chapter 8: Class-Specific Addons.
Chapter 9: Addon Compilations.
Part II: Advanced Hacks: Creating Your Own Addons.
Chapter 10: Addon Anatomy.
Chapter 11: XML, Frames, and Event Handlers.
Chapter 12: The Lua Side.
Chapter 13: Expanding the Whereabouts Addon.
Chapter 14: The Whereabouts Options Panel.
Chapter 15: Hacking an Advanced Addon.
Chapter 16: Creating Advanced Macros.
Dan recently graduated from Hampshire College in Amherst, MA where he studied film production. For his thesis project (or Div III) he created a film called The Nightingale Princess with his co-conspirators, Christopher Dreisbach and Owen Granich-Young. The three of them have websites at thenightingaleprincess.com and ocdproductions.net. So far the movie hasn’t gotten into any festivals, but Dan has his fingers crossed. He currently lives in Northampton, MA. In his spare time, he enjoys sleeping.
Jim Whitehead has been an active member of the UI
community since December 2004. He initially became an active
developer on WatchDog unit frames, and eventually created
PerfectRaid and Clique, and spearheaded the creation of the Dongle
addon framework.When he’s not developing addons for World of
Warcraft, he can be found playing the game with one of his many
characters on the Stormrage server.
Jim is a graduate of Syracuse (NY) University, holding an MSc in computer science. Although he has been a resident of cubicle-land for the past few years, he will soon retreat to the halls of academia to pursue his PhD in computer science. He lives in Syracuse, where he spends a disproportionate amount of his life’s savings on keeping his house warm.
Do you think you've discovered an error in this book? Please check the list of errata below to see if we've already addressed the error. If not, please submit the error via our Errata Form. We will attempt to verify your error; if you're right, we will post a correction below.
|245||Error in Reference
like it is everywhere else. This error doesn't break anything though, since either will work. It's just a bit inconsistent.
|317||Error in Code
The code should read:
elseif ( event == "UNIT_MANA" or event == "UNIT_RAGE" or
event == "UNIT_ENERGY" or (event == "UNIT_FOCUS" and
arg1 == "focus")) then