XivAlexander and Dalamud Conflict: How to Run Both
XivAlexander and Dalamud can run together, and many players do so. When they conflict, the symptoms are familiar: the game crashes on startup, a plugin fails to load, the loader cannot attach, or weaving behaves unpredictably. Because both tools inject code into the game process, a conflict can look like a fault in either tool, and the only reliable diagnosis is isolation. This guide shows how to isolate, what the common conflict patterns are, and how to choose a stable arrangement.
Isolate before you change anything
Start with the base game through the official launcher, with neither tool active, and confirm it works. Then run the game with Dalamud alone, through XIVLauncher, and confirm it works. Then run the game with XivAlexander alone, in portable mode, and confirm it works. Then run both together. The step that reintroduces the problem is where the fault lies. If you change three things at once, reinstall both tools, and update a plugin in the same session, you will not know what fixed or broke anything. Isolation is slower than reinstalling, but it is the only method that gives you an answer you can trust. The same method is described for XIVLauncher setups in How to Install XivAlexander with XIVLauncher.
Common conflict patterns
Two latency tools at once
The most serious pattern is running XivAlexander together with NoClippy or another animation-lock plugin. Both adjust the same timing, and the result is unpredictable weaving and impossible diagnosis. Choose one latency tool and disable the other completely, not just visually, but so that it does not load at all. Test the remaining tool alone before concluding anything about it.
A single Dalamud plugin, not Dalamud itself
Dalamud is a framework; its plugins are separate code. A crash with Dalamud active may be caused by one plugin, not by Dalamud or by XivAlexander. If the game works with Dalamud alone but fails with both tools, disable Dalamud plugins in groups, then one at a time, until you find the plugin that triggers the failure with XivAlexander present. Report that specific combination to the relevant project, rather than reporting a vague conflict between the two tools.
Load order and autoload interaction
If XivAlexander autoload is configured, its DLL loads at game startup, in the same phase as Dalamud’s injection. That shared phase is where order matters most. Portable mode for XivAlexander avoids that shared phase, because the loader attaches after the game and Dalamud are already running. If both tools work alone but fail together in autoload mode, switch XivAlexander to portable mode and retest. If portable mode resolves the conflict, you have a workable arrangement, even if it is not the arrangement you originally wanted.
A stable arrangement to aim for
For most players, the stable arrangement is: XIVLauncher starts the game, Dalamud loads a minimal, tested set of plugins, XivAlexander attaches in portable mode, and no second latency tool is active. Keep plugin counts low while testing, add plugins one at a time, and keep a note of which plugins were active when a problem occurred. After a FFXIV patch, retest this arrangement from scratch, following How to Update XivAlexander After a Patch, because a patch can break either tool independently.
Frequently asked questions
Does Dalamud make XivAlexander unnecessary?
No. Dalamud is a plugin framework, not a latency tool. Only a latency plugin inside Dalamud, such as NoClippy, addresses animation lock, and running that alongside XivAlexander is the double-tool mistake described above.
Should I blame XivAlexander or Dalamud for a crash?
Neither, until you isolate. Test each alone, then together, then with plugins disabled in groups. The faulty combination, not a brand name, is the answer.
Can I use XivAlexander without XIVLauncher at all?
Yes. XivAlexander is standalone and works with the official launcher. XIVLauncher is only relevant if you also want Dalamud plugins.
Conflicts between injection tools are diagnosed, not guessed. Base game, one tool, the other tool, both together, plugins in groups. That sequence turns a frustrating crash into a specific, fixable cause, and it keeps you from discarding a working tool because of a single bad plugin.
Important: Final Fantasy XIV prohibits third-party tools that inject code into the game client or alter its network behaviour. XivAlexander is an unofficial, community tool, not affiliated with Square Enix. Using it carries a risk of account restriction. This guide is for information only; decide for yourself whether that risk is acceptable, and never use a third-party tool on an account you are unwilling to risk.
