WoW:API UnitClass: Difference between revisions

From AddOn Studio
Jump to navigation Jump to search
(Clarified that englishclass omits spaces.)
m (→‎Result: Typo)
Line 24: Line 24:
=== Result ===
=== Result ===
Prints the player's class to the chat frame, e.g.
Prints the player's class to the chat frame, e.g.
  Your player is a : Warrior; WARRIOR'.
  Your player is a : Warrior; WARRIOR.


== Details ==
== Details ==

Revision as of 01:38, 27 August 2010

WoW API < UnitClass

Returns the class (Mage, Warrior, etc) of the specified unit.

localizedClass, englishClass = UnitClass("unit");

Parameters

Arguments

unit
String - the unitId to query, e.g. "player"

Returns

localizedClass, englishClass
localizedclass
The localized class of the specified unit as a string. e.g. "Mage", "Warrior", "Guerrier", etc.
englishclass
The fully capitalized english class name with no spaces, e.g. "MAGE", "WARRIOR", "DEATHKNIGHT", etc.

Example

local playerClass, englishClass = UnitClass("player");
ChatFrame1:AddMessage('Your player is a : ' .. playerClass .. '; ' .. englishClass .. '.');

Result

Prints the player's class to the chat frame, e.g.

Your player is a : Warrior; WARRIOR.

Details

For any type of data tracking, use the second parameter, since it is guaranteed to stay the same in different-language clients. This is especially important in europe, where it is not uncommon for people with e.g. german or french client software to play on english servers. You can keep track of mappings for display by remembering the output pairs in a table, e.g.:

localizedClass, englishClass = UnitClass("target");
MyAddOn_Classes[englishClass] = localizedClass;

.. do data tracking stuff with englishClass..