How to Install XivAlexander with XIVLauncher

XIVLauncher is an alternative launcher for Final Fantasy XIV that can load Dalamud, the plugin framework. XivAlexander is a separate, standalone tool that is not a Dalamud plugin and is not installed through Dalamud. That distinction matters, because players often look for XivAlexander inside a plugin list, fail to find it, and assume it is broken. It is not missing; it simply lives outside that system. This guide shows how to run both side by side, what start order to use, and how to tell which tool is responsible when something goes wrong.

First, install each tool on its own terms. Install XIVLauncher and Dalamud as their own projects document, and install XivAlexander using the portable method in How to Install XivAlexander on Windows. Download the stable release, v1.14.9.3, from the download page, extract it to its own folder, and verify the SHA-256 hash before you run it. Do not place XivAlexander files inside the XIVLauncher or Dalamud folders, and do not try to load XivAlexander64.dll as if it were a Dalamud plugin. Keeping the folders separate makes every later diagnosis much easier.

Start order that works for most players

  • Start the game through XIVLauncher as you normally would, with Dalamud loading as usual.
  • Once you are in the game, run XivAlexanderLoader64.exe and apply it to the running game, following the loader prompts.
  • If you prefer, run the loader first and then log in through XIVLauncher; the important point is that you use one clear order and stick to it while testing.
  • After any install, update, or uninstall step for either tool, restart the game. A game that was already running will not reliably pick up the change.

Why they can coexist

XivAlexander and Dalamud work at different layers. XivAlexander adjusts animation-lock timing by handling game network packets locally. Dalamud loads interface and quality-of-life plugins. In principle they do not do the same job, so running both is a common community setup. In practice, both inject code into the game process, so a crash or a failure to start can come from either one, and the only reliable way to find out is to test them separately. That is why portable mode is recommended here: you can run the game with Dalamud alone, then with XivAlexander alone, then with both, and compare.

If something breaks, isolate before you reinstall

If the game crashes on startup with both tools active, do not reinstall everything at once. First run the game through the official launcher with neither tool, to confirm the base game works. Then add XIVLauncher and Dalamud alone. Then add XivAlexander alone in portable mode. Whichever step reintroduces the problem is where your fault lies. If the problem only appears with both together, read XivAlexander and Dalamud Conflict, which covers load order, plugin conflicts, and the specific mistake of running two latency tools at once. If the loader cannot find the game at all, see XivAlexander Loader Cannot Find Game, since XIVLauncher installations are a common cause of a wrong game path.

Two latency tools at once is a mistake

Do not run XivAlexander together with NoClippy or any other animation-lock tool. Both tools try to adjust the same timing, and running both does not double the benefit; it creates unpredictable behaviour and makes diagnosis impossible. Choose one latency tool, disable the other completely, and test. The same rule applies to testing: if you are comparing tools, test one at a time on the same rotation and the same connection, otherwise you cannot attribute any change you observe.

Frequently asked questions

Is XivAlexander a Dalamud plugin?

No. It is standalone. If you search Dalamud plugin lists for it, you will not find it, and that is expected.

Can I use autoload with XIVLauncher?

Portable mode is safer for testing. If you later set up autoload, remember that the game folder XIVLauncher uses must be the folder you configured, and you must know how to turn autoload off again. See XivAlexander Autoload Not Working.

Does XIVLauncher make XivAlexander allowed?

No. Both are third-party tools. Square Enix prohibits third-party injection tools, and using either carries account risk regardless of which launcher you use.

A clean XIVLauncher plus XivAlexander setup is deliberately boring: XIVLauncher starts the game, Dalamud loads its plugins, the portable loader attaches, and you test weaving on a dummy. If you keep the tools in separate folders and test one change at a time, most problems resolve themselves into a single, identifiable cause.

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.

Similar Posts