Heimdall Studios
World of Warcraft / Retail

Your edition.
Your addons.

A separate home for Retail. Keep the right files with the right client.

LIVE CLIENT · _retail_

Find the right folder ↓

Know your client

What makes Retail different?

Current live game; choose Retail files. Classic downloads do not belong in this client.

Heimdall identifies this environment from _retail_ and a matching game executable. A folder alone is not an installed game. It does not infer your realm, character, or subscription.

In Battle.net, choose this game version and use the install-location option to verify the folder. Check the actual game build before choosing addon files. Expansion names and test branches change; the client folder is the routing boundary.

Addon setup

Keep this installation separate.

  1. Close this WoW client before installing or changing addons.
  2. Download a file explicitly supporting Retail and its current build.
  3. Extract each addon folder directly into the path below. Keep its files and dependencies together.
  4. Start this edition and check its AddOns list. Enable the addon for the intended characters.
World of Warcraft/_retail_/Interface/AddOns/AddonName/AddonName.toc

A package can contain multiple addon folders. Avoid an extra wrapper folder between AddOns and the folder holding the .toc file.

Where to find addons

Sources for this environment.

CurseForge

Choose the file flavor and game version matching Retail. A project may offer several incompatible downloads.

Browse addons ↗

Website only in Heimdall today; this definition does not imply an API connection.

WoWInterface

Choose the file flavor and game version matching Retail. A project may offer several incompatible downloads.

Browse addons ↗

Website only in Heimdall today; this definition does not imply an API connection.

Wago Addons

Choose the file flavor and game version matching Retail. A project may offer several incompatible downloads.

Browse addons ↗

Website only in Heimdall today; this definition does not imply an API connection.

No unrelated Minecraft or BepInEx catalogs are queried. Test-build support depends on the individual author; inclusion of a website is not a compatibility guarantee.

Keep your setup

Back up local settings.

_retail_/WTF holds local configuration and addon saved variables. Back it up with the game closed. Interface/AddOns holds the installed addon code. Keep backups labeled with the edition and date.

Characters and progression are maintained by Blizzard. A local settings backup cannot restore lost character progress. Do not overwrite another edition’s WTF folder without checking compatibility.

When something is wrong

Check the route before reinstalling.

The addon is missing from the list.

Confirm Battle.net opened Retail, then inspect _retail_/Interface/AddOns. Look for an extra ZIP wrapper folder and ensure the addon’s .toc file is directly inside its own folder.

The addon is marked out of date or throws errors.

Check its supported flavor, interface version and dependencies. An out-of-date toggle does not repair changed APIs. Get the author’s compatible release before enabling it.

My settings appear in one edition but not here.

This edition has its own WTF directory. That separation is expected. Use the addon’s supported profile export/import when available instead of copying all settings blindly.

Does this detect Hardcore or my realm?

No. Discovery identifies installed clients, not the currently selected realm or ruleset. Choose realm-specific addon options yourself and verify the author’s instructions.

Other installations

Choose another WoW environment.

Sources & review

Reviewed October 13, 2026. Directory and executable mappings checked against WowUp’s published implementation; catalog availability checked on provider websites. No live addon compatibility test is claimed.