Step 1: Confirm portable mode works first

Test XivAlexander in portable mode, following How to Install XivAlexander on Windows and How to Check If XivAlexander Is Working. If portable mode fails, fix that first, starting with patch compatibility in XivAlexander Not Working After a Patch. If portable mode works but autoload does not, you have isolated the fault to the autoload configuration, which is a much smaller problem to solve.

Step 2: Check the DLL name, location, and game folder

Autoload depends on a DLL in the game folder with the exact name the game will load, d3d11.dll or dxgi.dll, depending on your setup. Check that the file exists in the game folder you actually launch from, not in an old installation, a backup folder, or the extracted XivAlexander folder. If you use Steam, XIVLauncher, or a standalone launcher, each may use a different game folder, and autoload configured for one will not affect the other. See XivAlexander Loader Cannot Find Game for the multiple-installation problem, which is also the most common autoload problem. After any install, update, or uninstall step, restart a running game; autoload changes do not apply to a game that was already open.

Step 3: Check for chain-loading and launcher overwrites

If you use ReShade or GShade, the DLL name collision described in XivAlexander with ReShade and GShade may mean the visual tool occupies the file name and XivAlexander is not chained through it, or vice versa. Check which tool occupies the name and whether a chain is configured. Separately, a game update or a launcher repair can replace files in the game folder, removing a manually placed DLL without warning. After any game update, re-check the game folder for your autoload DLL before assuming the tool broke. Antivirus software can also quarantine a DLL in the game folder; see XivAlexander Antivirus False Positive if a file disappears after a scan.

Step 4: Reset autoload cleanly and reconfigure

If checks do not reveal the fault, reset autoload completely: turn off automatic loading in the loader, delete any manually placed DLL you added for XivAlexander, restart the game to confirm it launches cleanly without the tool, and then set up autoload again from scratch, following the loader’s own option rather than copying files by hand. Test immediately after reconfiguring, and note exactly which game folder and which file name you used. A clean reset is preferable to layering a second autoload configuration on top of a broken first one, which is how duplicate and conflicting DLLs accumulate.

Frequently asked questions

Is autoload required?

No. Portable mode gives you the same latency feature, with an extra manual step each session. Autoload is convenience, not capability.

Why did autoload stop after a patch?

A patch can change the game folder contents, invalidate the build, or both. Turn autoload off, test the base game, and follow How to Update XivAlexander After a Patch before reconfiguring.

Can I use autoload with XIVLauncher?

Yes, if the game folder XIVLauncher uses is the folder you configured. See How to Install XivAlexander with XIVLauncher.

Autoload failures are configuration failures far more often than tool failures: wrong folder, wrong file name, missing chain, or a file removed by an update or a scan. Confirm portable mode, check the actual game folder, check the chain, and reset cleanly. When autoload works, it should be as boring as portable mode, just automatic.

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.

Step 1: Does the base game start without the tool?

Launch FFXIV through the official launcher with no third-party tools, and confirm it starts. If the base game crashes, the problem is not XivAlexander, even if the tool was present when you first noticed the crash. Fix the game, update your graphics driver, or repair the installation first. If the base game starts, turn autoload off, as described in How to Uninstall XivAlexander Completely, and test the tool in portable mode. A crash that disappears when autoload is off but the tool is still used portably points to the autoload configuration, covered in XivAlexander Autoload Not Working.

Step 2: Check patch compatibility and other injection tools

If the crash began right after a FFXIV patch, patch incompatibility is the leading suspect. See XivAlexander Not Working After a Patch and do not force an old build onto a new patch. If you use Dalamud, ReShade, or GShade, test XivAlexander alone, without those tools, before concluding anything. The isolation method in XivAlexander and Dalamud Conflict and XivAlexander with ReShade and GShade applies here: a crash with two injection tools active is not evidence against either tool alone.

Step 3: Check antivirus, drivers, and the installation folder

• Antivirus: if the loader or DLL was quarantined, a partial installation can crash on startup. Verify the hash and handle quarantine as described in XivAlexander Antivirus False Positive.
• Graphics driver: update the driver from the manufacturer’s site, not only through Windows Update, and test again. A driver that works for the base game can still fail when an additional DLL is loaded.
• Installation folder: extract a fresh copy of v1.14.9.3 to a new folder, verify its hash, and test from there. A corrupted extraction or a folder with restricted permissions can produce a startup crash that looks like a tool bug.
• Configuration: restore a default configuration, as described in the XivAlexander Config File Guide, and test before reapplying custom settings.

Collecting useful information before asking for help

If none of the above resolves the crash, collect the facts that will let someone else help you: game version and patch date, XivAlexander version, whether the base game starts, whether portable mode crashes, whether autoload is configured, which other tools were active, and whether the crash began after a patch, a driver update, or an antivirus action. A report that says only that the game crashes is difficult to act on. A report with those facts points directly at the remaining suspects.

Frequently asked questions

Should I reinstall Windows?

No. A startup crash with one tool is not a reason to reinstall Windows. Work through base game, patch, autoload, other tools, antivirus, driver, and fresh extraction first.

Does a crash mean my account is at risk?

A crash itself is not an account action. Account risk comes from using a third-party injection tool at all, which is a separate consideration from whether the tool crashes.

Can I keep playing with the tool crashing?

No. If the tool crashes the game on startup, remove autoload and play without it until you find the cause. Repeatedly crashing the client does not improve the odds of a fix.

Startup crashes reward method, not effort. Base game first, portable before autoload, one other tool at a time, patch checked, hash verified, driver updated, fresh folder tested. The cause is almost always on that list, and it is almost never the last thing you reinstalled.

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.

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.

How chain-loading works

Chain-loading means one DLL, when loaded by the game, loads the next DLL in the chain, which loads the next, and so on. The game itself only loads the first file, named d3d11.dll or dxgi.dll. That first file is responsible for passing control onward. XivAlexander, ReShade, and GShade all support chain-loading arrangements, but the exact configuration depends on which tool occupies the first file name and which tool is configured to load next. Do not assume that copying files in any order will chain correctly; an unconfigured chain is just a missing tool.

Recommended approach: portable mode first

The simplest way to avoid the entire DLL conflict is to use XivAlexander in portable mode while ReShade or GShade handles the visual layer through its own autoload file. In portable mode, XivAlexander does not need a DLL in the game folder, so there is no file-name collision at all. Start the game with your visual tool active, then attach XivAlexander with the portable loader, as described in How to Install XivAlexander on Windows. Test that both tools work together in this arrangement before attempting a full autoload chain. If portable mode works, you have a working setup, and you do not need to solve the chain-loading puzzle at all.

If you need full autoload chain-loading

• Back up your game folder’s DLL files and your visual tool’s presets before changing anything. A preset you lose to a careless overwrite is difficult to reconstruct.
• Decide which tool occupies the game’s d3d11.dll or dxgi.dll name, and configure that tool to chain-load the other, following the documentation of the tool that occupies the first name. Do not configure both tools to chain-load each other in a loop.
• Test with the game alone, then with the visual tool alone, then with the chain. If the chain crashes but each tool works alone, the fault is in the chain configuration, not in either tool by itself.
• If you use GShade, remember that GShade is a community fork with its own update history. Do not apply ReShade instructions to GShade blindly, and do not assume a GShade preset will behave identically under ReShade.

Isolating a crash

If the game crashes with both tools active, remove the chain and test each tool alone, in the same way you would isolate a Dalamud conflict in XivAlexander and Dalamud Conflict. If XivAlexander alone crashes, check patch compatibility in XivAlexander Not Working After a Patch. If the visual tool alone crashes, check its own compatibility with the current game version and graphics driver. Only when both work alone should you rebuild the chain, one link at a time, testing after each link. A chain that is built all at once and crashes tells you nothing about which link failed.

Frequently asked questions

Can I use XivAlexander autoload and ReShade at the same time?

Yes, with chain-loading, but portable mode for XivAlexander is the simpler and more reliable arrangement for most players.

Which file name should I use, d3d11 or dxgi?

Use the name your visual tool already uses, and chain the other tool through it, unless that tool’s documentation directs otherwise. Consistency matters more than the specific name.

Do visual presets affect latency?

No. A preset changes rendering, not network timing. A heavy preset can affect frame rate, which can feel like lag, but that is a graphics problem, not a network or animation-lock problem.

Visual tools and latency tools can coexist, but only if you respect the file-name collision that autoload creates. Portable mode sidesteps it entirely. Full chain-loading requires a deliberate order, a backup, and one-link-at-a-time testing. Either path works; the one that fails is the one where both DLLs are copied in with the same name and nobody checks the chain.

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.

Step 1: Confirm the tool is actually working

Before diagnosing anything else, confirm the loader is attached and the tool is working, using How to Check If XivAlexander Is Working. Test on a training dummy, compare with the tool off on the same connection, and confirm that weaving improves with the tool. If there is no difference at all, the tool may not be attached, may be incompatible with the current patch, or may be conflicting with another latency tool. See XivAlexander Not Working After a Patch and XivAlexander and Dalamud Conflict before blaming your network.

Step 2: Measure your ping and route honestly

Check your ping to the data centre you play on, and check whether it is stable or spiking. A stable 180 ms connection and a connection that swings between 80 ms and 400 ms are very different problems, even if their averages look similar. Packet loss and jitter hurt weaving more than a stable, moderately high ping, because unpredictable delays cannot be compensated by a fixed timing adjustment. Test on a wired connection before judging a wireless one, and test at a different time of day to rule out peak-hour congestion. If your ping is unstable or lossy, a network fix is needed, and no animation-lock tool can substitute for it. That network fix may involve your home network, your internet provider, or a game-specific routing service, which is a separate decision from using XivAlexander.

Step 3: Check rotation and job factors

Some clipping is not a network problem at all. If you are late pressing an off-global ability, if your skill speed pushes your global cooldown below the window your rotation assumes, or if you are weaving three abilities where only two fit, the tool cannot rescue the rotation. The project documentation makes this point directly: the tool helps with weaving, but it cannot help if you are not pressing your buttons. Test with a simple, known rotation on a dummy, with abilities you can press on time, before concluding the tool has failed. Record which abilities clip, and whether they clip consistently or only under specific conditions, such as during heavy mechanics or on a particular job.

A practical diagnosis table

If weaving improves with the tool but still clips occasionally, you likely have a network stability problem on top of animation lock. If weaving does not improve at all, suspect attachment, patch compatibility, or a second latency tool. If weaving is clean on a dummy but clips in duties, suspect mechanics, movement, and network load during content rather than the tool. If weaving is clean at one time of day and bad at another, suspect route congestion. Each of those conclusions points to a different fix, which is why a single test in a single dungeon is not a diagnosis.

Frequently asked questions

Should I add a VPN or routing service on top of XivAlexander?

A routing service changes your network route; XivAlexander changes animation-lock timing. They address different problems and can complement each other, but neither removes the account risk of using a third-party injection tool, and neither guarantees a result on your specific route. Test one change at a time.

Does a higher ping always mean worse clipping?

Generally yes, but stability matters as much as the number. A stable high ping is more predictable than a spiking lower ping.

Is double weaving impossible above a certain ping even with the tool?

There is no single threshold that applies to every job, rotation, and connection. Test your own setup on a dummy rather than relying on a claimed cutoff.

Still clipping after XivAlexander is a prompt to diagnose, not a verdict on the tool. Confirm attachment, measure ping and stability, check rotation, and fix the layer that is actually failing. Players who do that end up with a setup that is stable for their connection, rather than a stack of tools that mask each other’s faults.

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.

A quick note on why this guide sits on a latency site at all. New players often arrive here while troubleshooting, and the edition question comes up alongside connection questions: a new account, a new platform, and a new connection all at once. The connection rules do not change with the edition you buy. Ping is still the round-trip time to the data centre, and animation lock is still the roughly half-second lock after most actions, which a late server reply can re-extend. XivAlexander adjusts packet timestamps locally so the lock is not re-extended by the full round trip; it does not lower your ping, and buying a different edition does not change your ping either.

What Complete Edition usually means — and what to verify

In general, a Complete Edition bundles the base game with its expansions up to a stated point, while a Starter Edition covers the base game and early expansions only. The exact cut-off is the single most important detail, and it changes when new expansions release, so never assume it from an old guide. On the listing, check the expansion list line by line: which expansions are named, whether the newest expansion is included or sold separately, and whether any bonus items are actually part of the bundle or just pictured. If the listing is vague, treat that vagueness as a reason to ask the seller or choose a clearer listing, not as a detail to guess at.

Platform: the mistake that costs the most time

Final Fantasy XIV accounts are platform-sensitive in ways that surprise new players. A Windows licence, a Steam licence, a Mac licence, and a PlayStation licence are not freely interchangeable for expansion purchases, and buying an expansion on the wrong platform is a common and frustrating error. Before buying, confirm three things on the listing and in your account: the platform the code is for, the platform you already play on, and whether the bundle is a code, a physical item, or a direct account purchase. Our Final Fantasy XIV Complete Edition listing on Amazon (affiliate link) is a place to start comparing, but the platform line on that listing is what you must read, not the product title alone. Check the exact edition, platform, and price on Amazon before buying, and confirm the region matches your account.

New account, existing account, and free trial

If you have never played, check whether the listing mentions any included game time and whether it applies to new accounts, since trial and new-account rules differ from existing-account rules. If you already play, check whether the edition adds expansions to your existing account or whether it would create a separate account you do not want. Players coming from the free trial should check the trial’s current limits on the official site before buying, because trial limits and the point at which a purchase becomes necessary change over time. When in doubt, the official account pages outrank any guide, including this one.

Hardware and storage: the boring check that saves a reinstall

Final Fantasy XIV is a large game, and a slow or nearly full drive makes patch days painful. Before buying, make sure you have room for the full installation plus patch headroom, and consider an SSD if you are still on a spinning drive. An SSD for Final Fantasy XIV (affiliate link) is a sensible upgrade for load times and patching, though it does not affect ping or weaving. Our mouse and keyboard guide and ping-checking guide cover the other two halves of a comfortable setup once the game itself is installed.

Buying checklist

• Confirm the exact expansion list on the listing, including whether the newest expansion is included.
• Confirm the platform matches the platform you play on, and the region matches your account.
• Confirm whether any included game time applies to your account type, and what happens after it ends.
• If you already play, confirm the purchase adds to your existing account rather than creating a new one.
• Check the exact edition, platform, and price on Amazon before buying, and keep the order confirmation until the code is redeemed.

Frequently asked questions

Is Complete Edition always the best value?

Not necessarily. If you already own some expansions, or only want to try the game, a smaller edition or the free trial may fit better. Value depends on what you already own, not on the size of the bundle.

Can I buy on Steam if I play on standalone Windows, or vice versa?

Treat them as separate platforms for expansion purchases and check the listing carefully. Do not assume a code works across them.

Does buying Complete Edition change my connection or weaving?

No. Edition, platform, and connection are separate. Fix connection problems with the network guides on this site, and animation-lock problems on their own terms.

Third-party tools and account risk. XivAlexander is not made, endorsed, or supported by Square Enix, and Final Fantasy XIV’s rules prohibit third-party tools that modify the game client. Using any such tool carries a risk of account action, and no guide can remove that risk. This article is educational: read the risks, make your own decision, and never use a tool on an account you are not willing to risk.

Buy the edition whose expansion list, platform, and account effect you have actually verified, not the one with the most attractive title. That single habit prevents the most common and most annoying purchase mistake in Final Fantasy XIV, and it costs nothing but a few minutes of reading before checkout.

Disclosure: this post contains affiliate links. If you buy through one, we may earn a commission at no extra cost to you. See our affiliate disclosure for the full explanation.

Step 1: Make sure the game is actually in a state the loader can see

Start FFXIV and log in to the character selection screen or into the game world, then run the loader and use its option to apply to a running game, as described in How to Install XivAlexander on Windows. If you run the loader before the game has started, and you have not configured a game folder, there may be nothing for it to attach to yet. If several game clients are running, select the correct one in the loader’s running games list. Close any extra clients you do not intend to use, because multiple instances are a common source of selecting the wrong one.

Step 2: Use Find game folder

If the loader does not detect your installation automatically, use its Find game folder option and point it at the folder that contains the game executable and data, not at a parent folder, a shortcuts folder, or the launcher folder alone. Steam installations, standalone installations, and XIVLauncher installations all place the game in different locations, and the loader’s automatic detection may only cover the most common one. After pointing it at the correct folder, restart the loader and try again. If you use XIVLauncher, see How to Install XivAlexander with XIVLauncher, because the game folder XIVLauncher uses is the one the loader needs.

Step 3: Check for multiple installations

Many players have more than one FFXIV installation without realising it: a Steam installation and a standalone installation, an old installation on another drive, or a copy left over from a drive migration. The loader may be pointed at an old installation while you are playing from a new one, or vice versa. Search your drives for the game installation, identify which one you actually launch, and point the loader at that one. Remove or clearly rename old installations you no longer use, so future detection does not pick the wrong one again. Do not delete a game folder while the game is running from it.

Other causes to check

• Antivirus quarantine: if the loader was quarantined, it may run partially or not at all. See XivAlexander Antivirus False Positive and verify the hash before restoring anything.
• Outdated build after a patch: if the loader cannot attach after a patch, the cause may be opcode incompatibility, not path detection. See XivAlexander Not Working After a Patch.
• Running the wrong architecture: v1.14.9.3 is 64-bit only. A 32-bit game installation or system is not supported by this release.
• Permissions: do not run the loader from a protected system folder or a network drive. Keep it in a normal user folder with write access, so it can save its configuration.

Frequently asked questions

Why does the loader find the game sometimes but not others?

That usually means the game folder detection depends on which launcher or client instance started first. Use an explicit game folder setting rather than relying on automatic detection each time.

Should I reinstall the game?

No, not for a detection problem. Reinstalling the game is a last resort for a broken game installation, not a fix for a loader pointing at the wrong folder.

Does Steam vs standalone matter?

Only for the folder path. The loader does not care which store you bought the game from; it cares where the game files actually are.

Game detection failures are almost always path failures. Confirm the running game, point the loader explicitly at the correct folder, eliminate duplicate installations, and test again. If the loader still cannot find a running, correctly pathed game, the next step is to check for a patch incompatibility or a quarantined file, not to reinstall the game.

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.

The connection split still applies, and it is worth stating before any buying advice. Ping is the round-trip time to the data centre. Animation lock is the roughly half-second lock after most actions, which a late server reply can re-extend so your second weave clips. XivAlexander adjusts packet timestamps locally so the lock is not re-extended by the full round trip. It does not lower your ping, and a new mouse does not lower it either. Gear helps your hands; network fixes help your packets; animation-lock tools help the lock. Confusing those three is how players buy a mouse for a routing problem.

The MMO mouse: buttons you can actually find blind

The case for an MMO mouse is not the number on the box, but whether you can press each side button without looking and without mis-pressing its neighbour. A 12-button side grid suits players who want a full second hotbar under their thumb, while a smaller grid suits players who only need their most urgent off-global abilities close at hand. Try to judge by your hand size and grip: a grid that is perfect for someone else may be unusable for you. An MMO mouse (affiliate link) is worth considering if your current mouse forces you to stretch for abilities you press every few seconds. Put your most time-critical off-global abilities on the buttons you hit most reliably, and leave rarely used actions on keys you reach deliberately. If a button is regularly mis-pressed in raids, move the ability, not your expectations.

The keyboard: layout beats switches

Keyboard marketing focuses on switches, but for weaving, layout matters more. Your movement keys, your main rotation keys, and your most urgent off-global abilities should all be reachable without moving your left hand off its home position. Many players keep their core rotation on easily reached keys and put defensive and utility abilities on a second row they can find by feel. A mechanical keyboard (affiliate link) can offer a more consistent key feel and durability than a membrane board, but no switch type will improve your weaving on its own, and no keyboard deserves a promise of better damage output. Comfort over long sessions matters more than any specification: if your wrist hurts after a raid night, fix ergonomics before anything else.

A practical setup checklist

• Map your two most urgent off-global abilities to your two most reliable mouse buttons, and practise them in easy content first.
• Keep movement, main rotation, and urgent utilities on keys your left hand reaches without looking.
• Use the same layout for at least a few weeks. Constantly rebinding destroys the muscle memory that weaving depends on.
• Test the setup under raid pressure, not just on a training dummy. Stress reveals mis-presses that calm practice hides.
• Fix your connection in parallel: our wired vs Wi-Fi guide and ping-checking guide cover the network half of weaving.

Frequently asked questions

Will an MMO mouse improve my damage?

Not by itself. It can make abilities easier to reach, which helps consistency, but damage still depends on rotation, timing, fight knowledge, and connection. Any product promising damage gains is overselling.

Do I need 12 side buttons?

No. Some excellent players use far fewer. Buy the number of buttons you will actually use reliably, not the largest number available.

Should I copy a famous player’s keybinds?

Use them as a starting point, not a prescription. Hand size, mouse grip, and job all change what works, and a layout that fights your hand will always lose to a layout built around it.

Third-party tools and account risk. XivAlexander is not made, endorsed, or supported by Square Enix, and Final Fantasy XIV’s rules prohibit third-party tools that modify the game client. Using any such tool carries a risk of account action, and no guide can remove that risk. This article is educational: read the risks, make your own decision, and never use a tool on an account you are not willing to risk.

Buy for reach and reliability, arrange for muscle memory, and practise under pressure. Then check the other halves of weaving — connection and animation lock — on their own terms. If you decide to try XivAlexander, get it from our download page and verify its hash first.

Disclosure: this post contains affiliate links. If you buy through one, we may earn a commission at no extra cost to you. See our affiliate disclosure for the full explanation.

Why the flag happens

Antivirus software uses two kinds of detection. Signature detection matches a file against known malware. Heuristic detection watches behaviour, such as injecting code into another process, and flags behaviour that is commonly malicious even if the specific file is unknown. XivAlexander’s core behaviour, DLL injection into FFXIV, triggers heuristic detection by design. The project’s source code is open under the Apache License 2.0, which lets anyone inspect what it does, but openness of the source does not automatically prove that a particular downloaded binary matches that source. That is why hash verification matters more than reassurance.

The correct response, in order

• Do not run the file yet. If your antivirus quarantined it, leave it quarantined while you check.
• Confirm you downloaded the stable release, v1.14.9.3, from the download page, using the GitHub release as the main channel. A file from an unknown re-upload deserves more suspicion, not less.
• Verify the SHA-256 hash exactly as described in How to Verify XivAlexander SHA-256 After Download. The expected value is c17be29dc81cf4c5a43954832a47133d4f3929688a2304ebb1525c15526de03a. If the hash does not match, delete the file and do not proceed.
• If the hash matches and the file is still flagged, you are looking at the known heuristic pattern for this kind of tool. You may then decide, with the account risk in mind, whether to restore it from quarantine.
• Only after a hash match should you consider an exclusion, and only for the specific folder containing the verified tool, not for your whole drive or your downloads folder.

What not to do

Do not disable your antivirus entirely, do not disable real-time protection permanently, and do not add a broad exclusion for a folder that also contains unverified downloads. Do not restore a quarantined file before checking its hash, and do not assume that because one version was flagged as a false positive, every future version will be too. Each new release should be verified again. If a different antivirus product flags the file with a specific malware family name rather than a generic heuristic label, take that more seriously, check the hash again, and consider reporting it to the project rather than overriding it.

If the flag appears after a patch

A flag that appears only after a FFXIV patch is usually a new binary being scanned for the first time, or a new heuristic rule, rather than a sign that the patch itself infected the tool. Still, follow the same routine: base game first, hash check second, exclusion last. If the tool also stops working after the patch, the patch explanation in XivAlexander Not Working After a Patch is more likely than an antivirus explanation, and you should not use an exclusion to mask a compatibility failure.

Frequently asked questions

Does a flag mean XivAlexander is malware?

Not by itself. A generic heuristic flag for a DLL injection tool is expected behaviour for this category. A hash mismatch, or a specific malware signature, is a different and more serious signal.

Should I submit the file to my antivirus vendor?

You may, if your vendor offers a false-positive submission process. That helps future detection, but it does not change the account risk of using the tool.

Can I avoid flags by using a different download source?

No. A mirror does not change how the tool behaves, and an unverified mirror adds risk. Use the GitHub release and verify the hash.

Handle antivirus flags with a fixed routine: quarantine first, hash second, decision third, narrow exclusion last. That routine protects you from both overreaction and carelessness, and it works for every future release, not just this one.

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.

First, the split that matters for weaving. Ping is the round-trip time to the data centre. Animation lock is the roughly half-second lock after most actions, which a late server reply can re-extend so your second weave clips. XivAlexander adjusts packet timestamps locally so the lock is not re-extended by the full round trip. It does not lower your ping, and it cannot fix a Wi-Fi connection that drops packets. If your problem is interference, fix the connection first; no animation-lock tool will rescue it.

Why Wi-Fi struggles at raid time

Wi-Fi shares the air with neighbours, microwaves, Bluetooth devices, and every other device in your home. That sharing shows up as jitter: most packets arrive quickly, but some arrive late, and a few never arrive. In a dungeon that is barely noticeable. In a Savage raid, a late packet at the wrong moment can clip a weave or delay a mitigation ability, and the inconsistency is worse than a stable but slightly higher ping. Wi-Fi also degrades with distance and walls, so a PC two rooms from the router is playing a different game from a PC in the same room. Evening congestion makes all of this worse, because that is when neighbours and household members are also online.

What Ethernet actually changes

A wired connection removes the shared-air problem. Your packets travel over a cable that nobody else is broadcasting on, so latency becomes steadier and packet loss falls. You may see a small average-ping improvement, but the real gain is consistency: fewer spikes, fewer late abilities, and raid evenings that feel the same from pull to pull. A Ethernet adapter (affiliate link) is the usual fix if your PC has no wired port, and a Cat6a cable (affiliate link) is a cheap, durable choice for the run itself. Neither purchase promises a specific ping drop, and any guide that quotes one for your home is guessing.

When Wi-Fi is acceptable — and how to make it better

Sometimes a cable is genuinely impractical: a rented room, a PC far from the router, or a household that will not allow drilling. In that case, Wi-Fi can still be workable if you treat it seriously. Use the 5 GHz band close to the router rather than a congested 2.4 GHz network, keep the router in the open rather than inside a cabinet, and reduce competing traffic during raid. A modern gaming router (affiliate link) can help with traffic handling on a busy home network, but it cannot repeal physics: walls and distance still cost you. Powerline adapters and mesh systems are middle options worth testing in your own home, because their performance depends entirely on your wiring and walls; buy from a place with a return policy and judge them on raid evenings, not on a box’s headline speed.

Head-to-head comparison

• Stability: Ethernet wins clearly. Wi-Fi can be good, but it is rarely as steady over a full raid evening.
• Average ping: Ethernet is usually slightly better, but the difference is smaller than most marketing suggests.
• Packet loss: Ethernet wins. Wi-Fi loss is the most common cause of abilities that feel randomly late.
• Convenience: Wi-Fi wins. No cable, no routing, no negotiation with housemates.
• Cost: a cable and adapter are among the cheapest upgrades in this whole setup, which is why they come first in our Oceania connection guide and our ping-checking guide.

Frequently asked questions

Will switching to Ethernet fix my double weaving?

It fixes the connection half of the problem. If your weaves clip because of Wi-Fi spikes, Ethernet helps a lot. If they clip because of a long round trip re-extending the animation lock, you still need to address the lock separately.

Is a long Ethernet cable worse than a short one?

No, within a normal home. A cable run across a house performs the same as a short one for gaming purposes; what matters is that the cable is undamaged and properly plugged in, not its length in metres.

Should I buy the fastest cable or adapter I can find?

No. For Final Fantasy XIV, a standard modern cable and adapter are already far beyond what the game needs. Spend on reliability and a sensible router, not on headline speeds you will never use.

Third-party tools and account risk. XivAlexander is not made, endorsed, or supported by Square Enix, and Final Fantasy XIV’s rules prohibit third-party tools that modify the game client. Using any such tool carries a risk of account action, and no guide can remove that risk. This article is educational: read the risks, make your own decision, and never use a tool on an account you are not willing to risk.

The verdict is boring and therefore useful: wire your PC if you can, make Wi-Fi as clean as possible if you cannot, and judge either option by stable raid evenings rather than by a single test. Then, and only then, decide whether animation lock is still your remaining problem — and get any latency tool from our download page with its hash verified.

Disclosure: this post contains affiliate links. If you buy through one, we may earn a commission at no extra cost to you. See our affiliate disclosure for the full explanation.