WoW:MACRO dump: Difference between revisions
Jump to navigation
Jump to search
(New in 3.2) |
(added historical note about protected exploit (now that it's fixed)) |
||
Line 4: | Line 4: | ||
Displays the value of a global variable | Displays the value of a global variable | ||
/dump value | /dump value | ||
== Aliases == | == Aliases == | ||
Line 51: | Line 52: | ||
:Output is color coded for easier reading | :Output is color coded for easier reading | ||
:Tables display up to 30 values, the rest are skipped and a message is shown. | :Tables display up to 30 values, the rest are skipped and a message is shown. | ||
:Prior to patch 3.2a, /dump compiled and executed its argument as secure code, thereby permitting arbitrary code to be run in secure mode. This led to widespread use of "dump macro" exploits to circumvent the Blizzard addon secure code restrictions. The command was fixed via urgent client patch 3.2a and is no longer exploitable in this way. |
Revision as of 23:26, 19 August 2009
Displays the value of a global variable
/dump value
Aliases
- None
Arguments
- value
- The name of the global variable, table value, or function result you wish to show.
Example
- /dump MAX_CHARACTER_NAME_BYTES
Dump: MAX_CHARACTER_NAME_BYTES MAX_CHARACTER_NAME_BYTES=48
- /dump SlashCmdList
Dump: SlashCmdList SlashCmdList={ GUILD_MOTD=<function>, FOLLOW=<function>, (28 more lines follow, not shown in this example) <skipped 57> }
- /dump ChatTypeGroup["CHANNEL"]
Dump: value=ChatTypeGroup["CHANNEL"] [1]={ [1]="CHAT_MESSAGE_JOIN", [2]="CHAT_MESSAGE_LEAVE", [3]="CHAT_MESSAGE_NOTICE", [4]="CHAT_MESSAGE_NOTICE_USER", [5]="CHAT_MESSAGE_LIST", }
- /dump UnitName("player")
Dump: UnitName("player") [1]="Shalune"
- /dump
Dump: value= empty result
- /dump NOTAVALIDNAME
Dump: NOTAVALIDNAME NOTAVALIDNAME=nil, empty result
Notes
- Added in patch 3.2
- This utilizes the new Blizzard_DebugTools interface.
- Output is color coded for easier reading
- Tables display up to 30 values, the rest are skipped and a message is shown.
- Prior to patch 3.2a, /dump compiled and executed its argument as secure code, thereby permitting arbitrary code to be run in secure mode. This led to widespread use of "dump macro" exploits to circumvent the Blizzard addon secure code restrictions. The command was fixed via urgent client patch 3.2a and is no longer exploitable in this way.