Addons for Retail will in most cases work on Classic with removal of any non-Classic API.
See also Patch 1.13.2/API changes.
Globe can tell you which API functions/events in an addon have been removed in Classic, if the TOC is set to the Retail version and with
## Interface: 90002 ## Globe: check-classic
local isClassic = (WOW_PROJECT_ID == WOW_PROJECT_CLASSIC)
- Texture:SetTexture() can no longer set color textures in Patch 7.0.3, use Texture:SetColorTexture(r, g, b [, a]) instead.
- PlaySound() only accepts SoundKitIDs in Patch 7.0.3
old: PlaySound("igMainMenuOptionCheckBoxOn") new: PlaySound(SOUNDKIT.IG_MAINMENU_OPTION_CHECKBOX_ON)
old: PlaySoundFile("Sound/Spells/LevelUp.ogg") new: PlaySoundFile(569593)
Maps were reworked in Patch 8.0.1 and the stateful API was changed to be stateless.
The combat log was reworked in Patch 2.4.0
- Parameters like
this, event, arg1, arg2, arg3are no longer globals for the script handler. This was changed in Patch 4.0.1
They are now passed like so
OnEvent(self, event, ...)or
OnEvent(self, event, someVar1, someVar2, someVar3)
thisparameter was unique to WoW frame scripts. It can generally be replaced with
There are multiple ways to handle frame scripts in XML. For simplicity's sake we will only describe a quick fix in blue text.
function SomeAddon_OnLoad(self) self:RegisterEvent("ADDON_LOADED") end function SomeAddon_OnEvent(self, event, addon) print(self, event, addon) end
<Frame name="SomeAddon"> <Scripts> <OnLoad> SomeAddon_OnLoad(self) </OnLoad> <OnEvent> SomeAddon_OnEvent(self, event, ...) </OnEvent> </Scripts> </Frame>
It's also possible to create a frame and handle the scripts in Lua without use of XML, depending on how simple the addon is.
local function OnEvent(self, event, addon) print(self, event, addon) end local f = CreateFrame("Frame") f:RegisterEvent("ADDON_LOADED") f:SetScript("OnEvent", OnEvent)