Introduction
Addon conflicts are one of the least understood problems in WoW Classic troubleshooting. When Questie icons disappear, display incorrectly, or cause UI errors, another installed addon is frequently the underlying cause rather than Questie itself.
Conflicts occur when two addons attempt to control the same UI element, load in an incompatible order, or carry outdated code that interferes with how modern Questie builds initialize. Identifying and resolving them requires a structured approach rather than randomly disabling and reinstalling.
Quick Answer about Questie & Other Addon Conflicts Diagnosis & Resolution
- What an addon conflict is: Two or more addons interfering with each other’s ability to function correctly within the same UI session
- Questie conflicts most commonly involve map addons, minimap managers, and full UI replacement frameworks
- Who this affects: Any WoW Classic player running Questie alongside other addons, particularly UI overhauls or map enhancement tools
- Conflicts do not always produce visible error messages and can silently suppress icon display or cause partial functionality
- The fastest diagnostic method is disabling all addons except Questie and re enabling them one at a time
- Who should prioritize this guide: Players whose Questie icons disappeared after installing a new addon rather than after a game patch
- Resolving conflicts rarely requires uninstalling either addon permanently and usually involves a settings adjustment
- Key risk: Randomly disabling addons without a structured method can mask the actual conflict source and prolong resolution
- Expert insight: Most Questie conflicts stem from addons modifying the same Blizzard map frame that Questie uses to render its icons
What Causes Addon Conflicts with Questie?
Questie renders its icons by hooking into WoW Classic’s map and minimap frames. Any addon that also modifies, replaces, or heavily customizes those same frames creates a potential conflict zone.
The conflict is not always intentional or the result of poor code. It often reflects two well maintained addons making legitimate but incompatible assumptions about how the shared UI space should behave.
How WoW Classic Addon Conflicts Work
WoW Classic’s addon system loads all enabled addons sequentially during the login process. Each addon registers functions, hooks into game events, and modifies UI elements as it loads.
When two addons attempt to hook the same event or modify the same frame, the second one to load may overwrite or block the first. In Questie’s case, this means map icons that were correctly registered during Questie’s load phase become invisible or non functional after a conflicting addon finishes its own initialization.
This explains why the conflict appears as missing icons rather than an obvious error. Questie loaded successfully, but a subsequent addon altered the rendering environment in a way that suppressed the visual output.
The Most Conflict Prone Addon Categories
Not all addon types carry equal conflict risk. The following categories produce the highest frequency of documented Questie conflicts:
- Full UI replacement frameworks: ElvUI, Tukui, and similar packages replace large portions of the default Blizzard UI including map and minimap elements
- Map enhancement addons: Leatrix Maps, Cartographer, and Atlas modify the world map frame directly, the same frame Questie uses for icon placement
- Minimap managers: Sexymap, MBB, and ButtonBin reposition or restyle the minimap in ways that can clip or hide Questie’s minimap icon layer
- Quest tracking addons: Any addon that also reads quest data or modifies the quest tracker can produce data layer conflicts with Questie’s objective tracking
- Outdated or abandoned addons: Addons that have not been updated for the current Classic patch can carry deprecated API calls that destabilize Questie’s initialization
What to Do When You Suspect a Conflict
Suspecting a conflict and confirming one are different steps. Before making changes, confirm that the issue is conflict related rather than a version mismatch or settings problem.
A conflict is the most likely cause when Questie icons disappeared specifically after a new addon was installed or updated, and not after a game patch.
Running the Isolation Test
The isolation test is the definitive method for confirming and identifying an addon conflict. It removes all variables except Questie, confirms baseline function, then reintroduces addons systematically to find the source.
Complete the isolation test in this order:
- Exit WoW Classic fully and open the character select screen
- Click the AddOns button and disable every addon except Questie
- Log in to a character in a leveling zone and open the world map
- Confirm whether Questie icons are now visible with all other addons disabled
- If icons appear, a conflict with one of the disabled addons is confirmed
- Return to the character select screen and re enable addons in small groups of two or three
- Log in after each group addition and check the world map for icon display
- When icons disappear, the most recently enabled group contains the conflicting addon
- Disable that group and re enable its addons individually to isolate the specific source
- Once the conflicting addon is identified, proceed to the resolution steps below
If icons do not appear even with all other addons disabled, the issue is not conflict related. Return to version checking, saved variable clearing, and clean reinstallation steps.
Reading the Lua Error Output
WoW Classic has a built in error reporting system that surfaces addon errors as pop up messages. These messages are suppressed by default on many setups, particularly those running error filter addons like BugSack or Swatter.
Enable Lua error display by typing /console scriptErrors 1 in the chat window. This forces raw error messages to appear as pop ups during gameplay.
After enabling this, reload the UI and log back in. If a conflict is producing code level errors, they will appear as pop up messages identifying the addon and function responsible. Screenshot or note any error messages that reference Questie Wow Classic alongside another addon name, as this directly identifies the conflict source.
Common Problems and Solutions for Lua Error Diagnosis:
- No errors appear but icons are still missing The conflict is a silent rendering suppression rather than a code error. Continue with the isolation test method
- Errors reference a deprecated API function An outdated addon is calling a function no longer supported in the current Classic patch. Update or remove that addon
- Errors mention both Questie and ElvUI or another framework A framework level conflict exists requiring a settings adjustment within the framework rather than in Questie
- Multiple errors appear simultaneously on login Disable addons in the error messages one at a time to establish which produces the conflict in isolation
- Errors appear only after zoning or reloading The conflict is triggered by a specific game event rather than initial load order, narrowing the source to event handling code
How to Resolve Specific Addon Conflicts
Once the conflicting addon is identified, resolution depends on which addon is involved. Most common conflicts have established fixes within the community that do not require permanently removing either addon.
Work through the resolution specific to your identified conflict before considering addon removal as a final option.
Resolving Conflicts with ElvUI and UI Frameworks
ElvUI is the most frequently cited source of Questie conflicts due to its comprehensive replacement of default Blizzard UI elements including the minimap and map frames.
Resolution steps for ElvUI conflicts:
- Open ElvUI configuration by typing /elvui in the chat window
- Navigate to the Map and Minimap section within the ElvUI config panel
- Look for a Questie compatibility toggle or a setting labeled Enhanced Map or Map Overlay
- If a compatibility option exists, enable it and reload the UI
- If no compatibility option is present, reduce ElvUI’s map customization level by disabling its map skin or map enhancement features
- Navigate to the Minimap section and confirm ElvUI is not set to hide third party minimap icons
- Save settings and reload the UI, then check for Questie icon display
If ElvUI’s map skin is the direct cause, disabling only the map skin within ElvUI while retaining all other ElvUI features resolves the conflict without sacrificing the broader UI framework.
For Tukui and other framework addons, the same approach applies. Locate the map and minimap customization sections within the framework config and reduce their control over those specific elements.
Resolving Conflicts with Map and Minimap Addons
| Addon | Conflict Type | Resolution Method |
| Leatrix Maps | World map frame override suppressing Questie icon layer | Disable Leatrix map skin or adjust Questie icon scale upward |
| Cartographer | Shared map frame hooks causing icon layer conflict | Update Cartographer or disable its map overlay features |
| Atlas | Dungeon map overlay clipping Questie world map icons | Disable Atlas world map integration, keep dungeon map only |
| Sexymap | Minimap restyling hiding Questie minimap icon layer | Adjust Sexymap icon layer settings or disable Questie minimap icons |
| MBB or ButtonBin | Minimap button consolidation removing Questie minimap presence | Exclude Questie from the button consolidation list in MBB settings |
| Handy Notes | Shared map pin system conflicting with Questie icon registration | Update both addons to current versions and reload |
For map addons not listed above, the general resolution principle is consistent. Locate that addon’s map or overlay settings and reduce its level of control over the world map frame. Questie’s icons render within the map frame layer, and any addon that replaces or heavily modifies that layer risks suppressing Questie’s output.
Resolving Conflicts with Quest and Objective Tracking Addons
Quest tracking addons that read the same game quest data Questie uses can create data layer conflicts resulting in incomplete or missing objective markers.
Addons in this category include older versions of QuestGuru, MonkeyQuest, and similar quest log replacement tools. These addons were built for earlier game versions and their quest data hooks can interfere with how Questie registers active objectives.
Resolution steps for quest tracking conflicts:
- Confirm the conflicting quest tracking addon is updated to a current Classic compatible version
- If no current version exists, the addon is likely abandoned and should be removed
- Check whether the quest tracking addon has a compatibility mode or a setting to disable its map integration while retaining its log features
- If compatible settings exist, enable them and test Questie icon display after a UI reload
- If no compatibility option exists and the addon cannot be updated, removing it is the most reliable resolution given that Questie provides equivalent or superior quest tracking functionality
Advanced Conflict Scenarios and Edge Cases
Some conflicts are not resolved by standard isolation and settings adjustments. These advanced scenarios require deeper investigation but remain solvable without expert knowledge of addon development.
Understanding why these edge cases occur helps identify them faster when standard methods do not produce results.
Load Order and Initialization Conflicts
WoW Classic loads addons in a sequence determined partly by addon dependencies declared in each addon’s .toc file. When Questie loads before a conflicting addon and that addon overwrites Questie’s map hooks during its own initialization, icons registered by Questie become inaccessible.
This type of conflict is not visible through standard testing because Questie appears to load successfully in the AddOns panel. The issue only manifests at the rendering stage after all addons have completed initialization.
Identifying a load order conflict requires noting whether icons appear briefly on login before disappearing, which indicates Questie initialized correctly but was subsequently overwritten by another addon completing its load sequence after Questie.
If this pattern is observed, the conflicting addon is one that loads late in the sequence. Addon managers like CurseForge and WowUp do not provide direct load order control, but dependencies declared in .toc files influence sequence. Removing and reinstalling the suspected late loading addon to reset its dependency chain occasionally resolves persistent load order issues.
Saved Variable Conflicts Between Addons
Some addons write to shared SavedVariables namespaces or use variable names that overlap with Questie’s own saved data. This is rare but produces highly inconsistent behavior where Questie functions correctly on some characters but not others, or works after a fresh login but fails after a reload.
If Questie icon display is inconsistent across characters on the same account, navigate to the WTF folder and clear saved variables for both Questie and the suspected conflicting addon simultaneously. Allow both addons to rebuild their saved data from defaults on next login.
This resets configuration for both addons. Document any important settings in either addon before clearing their saved variable files.
Frequently Asked Questions
How do I know if my issue is a conflict or a version mismatch?
If icons disappeared after installing or updating a specific addon rather than after a Blizzard game patch, a conflict is the likely cause. Version mismatches follow game patches rather than addon changes.
Can two well maintained and updated addons still conflict with each other?
Yes. Conflicts can exist between fully current addons when both legitimately modify the same UI element. Maintenance status determines code quality but not compatibility, which depends on how each addon interacts with shared game frames.
Is it safe to run Questie without ElvUI’s map skin enabled?
Yes. Disabling only ElvUI’s map skin leaves all other ElvUI features fully functional. The map skin is a cosmetic overlay and its removal does not affect ElvUI’s performance, action bars, unit frames, or any other element.
Why does disabling an addon on the character select screen not always fix the conflict?
Some addons write persistent data or hooks that survive a UI reload within the same session. A full exit to the login screen or game restart ensures all addon code is completely unloaded before testing with a modified addon list.
Can addon conflicts cause WoW Classic to crash rather than just missing icons?
Yes, though crashes from conflicts are less common than icon suppression or UI errors. Crashes are more likely when a conflict involves deprecated API calls or memory errors in older abandoned addons rather than simple frame hook competition.
Does reinstalling Questie fix conflicts caused by another addon?
No. If another addon is the source of the conflict, reinstalling Questie does not change the behavior of that addon. The conflicting addon must be updated, reconfigured, or removed to fully resolve the issue.
Should I report conflicts to the Questie team or the conflicting addon’s team?
Both are reasonable. The Questie GitHub issues page is a good starting point as the team actively tracks compatibility reports. The conflicting addon’s issue tracker is equally appropriate. Providing both teams with your addon list and Classic version helps them coordinate a compatibility fix.
What is the best long term approach to avoiding Questie conflicts?
Keep all addons updated consistently, remove addons that are no longer actively maintained, and after each game patch confirm both Questie and any map or UI framework addons have current compatible releases before logging in.
Latest Post: