<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Troubleshooting &#8211; XivAlexander</title>
	<atom:link href="https://xivalexander.net/troubleshooting/feed/" rel="self" type="application/rss+xml" />
	<link>https://xivalexander.net</link>
	<description>Independent Animation Lock Optimization &#38; Standalone x64 Zip Download</description>
	<lastBuildDate>Sat, 24 Oct 2026 15:10:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://xivalexander.net/wp-content/uploads/2026/06/favicon-150x150.png</url>
	<title>Troubleshooting &#8211; XivAlexander</title>
	<link>https://xivalexander.net</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>XivAlexander Autoload Not Working: Fixes</title>
		<link>https://xivalexander.net/xivalexander-autoload-not-working/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:10:24 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-autoload-not-working/</guid>

					<description><![CDATA[Autoload is convenient when it works and confusing when it does not, because a failure can look identical to the tool simply not being installed. The game opens normally, nothing obviously errors, and weaving feels unchanged. That silence is the clue: autoload either did not load the DLL, loaded it from the wrong place, or...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">Autoload is convenient when it works and confusing when it does not, because a failure can look identical to the tool simply not being installed. The game opens normally, nothing obviously errors, and weaving feels unchanged. That silence is the clue: autoload either did not load the DLL, loaded it from the wrong place, or was disabled by a change you did not notice. This guide checks each of those possibilities in order, and it assumes portable mode already works, because if portable mode does not work, autoload is not your problem.</p><h2 class="wp-block-heading">Step 1: Confirm portable mode works first</h2><p class="wp-block-paragraph">Test XivAlexander in portable mode, following <a href="https://xivalexander.net/how-to-install-xivalexander/">How to Install XivAlexander on Windows</a> and <a href="https://xivalexander.net/how-to-check-if-xivalexander-is-working/">How to Check If XivAlexander Is Working</a>. If portable mode fails, fix that first, starting with patch compatibility in <a href="https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/">XivAlexander Not Working After a Patch</a>. 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.</p><h2 class="wp-block-heading">Step 2: Check the DLL name, location, and game folder</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/xivalexander-loader-cannot-find-game/">XivAlexander Loader Cannot Find Game</a> 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.</p><h2 class="wp-block-heading">Step 3: Check for chain-loading and launcher overwrites</h2><p class="wp-block-paragraph">If you use ReShade or GShade, the DLL name collision described in <a href="https://xivalexander.net/xivalexander-reshade-gshade-chain-loading/">XivAlexander with ReShade and GShade</a> 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 <a href="https://xivalexander.net/xivalexander-antivirus-false-positive/">XivAlexander Antivirus False Positive</a> if a file disappears after a scan.</p><h2 class="wp-block-heading">Step 4: Reset autoload cleanly and reconfigure</h2><p class="wp-block-paragraph">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&#8217;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.</p><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Is autoload required?</h3><p class="wp-block-paragraph">No. Portable mode gives you the same latency feature, with an extra manual step each session. Autoload is convenience, not capability.</p><h3 class="wp-block-heading">Why did autoload stop after a patch?</h3><p class="wp-block-paragraph">A patch can change the game folder contents, invalidate the build, or both. Turn autoload off, test the base game, and follow <a href="https://xivalexander.net/how-to-update-xivalexander-after-patch/">How to Update XivAlexander After a Patch</a> before reconfiguring.</p><h3 class="wp-block-heading">Can I use autoload with XIVLauncher?</h3><p class="wp-block-paragraph">Yes, if the game folder XIVLauncher uses is the folder you configured. See <a href="https://xivalexander.net/how-to-install-xivalexander-with-xivlauncher/">How to Install XivAlexander with XIVLauncher</a>.</p><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>XivAlexander Crashes on Startup: Fixes</title>
		<link>https://xivalexander.net/xivalexander-crashes-on-startup/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:10:06 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-crashes-on-startup/</guid>

					<description><![CDATA[A crash on startup is the least informative failure a tool can produce, because it tells you that something went wrong, but not what. With XivAlexander, startup crashes have a short list of usual causes: a patch incompatibility, a stale autoload DLL, an antivirus quarantine, a conflicting injection tool, or a graphics driver issue that...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">A crash on startup is the least informative failure a tool can produce, because it tells you that something went wrong, but not what. With XivAlexander, startup crashes have a short list of usual causes: a patch incompatibility, a stale autoload DLL, an antivirus quarantine, a conflicting injection tool, or a graphics driver issue that only appears when another DLL is loaded. Working through that list in order, rather than reinstalling at random, will find the cause in most cases.</p><h2 class="wp-block-heading">Step 1: Does the base game start without the tool?</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/how-to-uninstall-xivalexander/">How to Uninstall XivAlexander Completely</a>, 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 <a href="https://xivalexander.net/xivalexander-autoload-not-working/">XivAlexander Autoload Not Working</a>.</p><h2 class="wp-block-heading">Step 2: Check patch compatibility and other injection tools</h2><p class="wp-block-paragraph">If the crash began right after a FFXIV patch, patch incompatibility is the leading suspect. See <a href="https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/">XivAlexander Not Working After a Patch</a> 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 <a href="https://xivalexander.net/xivalexander-dalamud-conflict/">XivAlexander and Dalamud Conflict</a> and <a href="https://xivalexander.net/xivalexander-reshade-gshade-chain-loading/">XivAlexander with ReShade and GShade</a> applies here: a crash with two injection tools active is not evidence against either tool alone.</p><h2 class="wp-block-heading">Step 3: Check antivirus, drivers, and the installation folder</h2><ul class="wp-block-list"><li>Antivirus: if the loader or DLL was quarantined, a partial installation can crash on startup. Verify the hash and handle quarantine as described in <a href="https://xivalexander.net/xivalexander-antivirus-false-positive/">XivAlexander Antivirus False Positive</a>.</li><li>Graphics driver: update the driver from the manufacturer&#8217;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.</li><li>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.</li><li>Configuration: restore a default configuration, as described in the <a href="https://xivalexander.net/xivalexander-config-file-guide/">XivAlexander Config File Guide</a>, and test before reapplying custom settings.</li></ul><h2 class="wp-block-heading">Collecting useful information before asking for help</h2><p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Should I reinstall Windows?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Does a crash mean my account is at risk?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Can I keep playing with the tool crashing?</h3><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>XivAlexander and Dalamud Conflict: How to Run Both</title>
		<link>https://xivalexander.net/xivalexander-dalamud-conflict/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:09:48 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-dalamud-conflict/</guid>

					<description><![CDATA[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,...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">Isolate before you change anything</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/how-to-install-xivalexander-with-xivlauncher/">How to Install XivAlexander with XIVLauncher</a>.</p><h2 class="wp-block-heading">Common conflict patterns</h2><h3 class="wp-block-heading">Two latency tools at once</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">A single Dalamud plugin, not Dalamud itself</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Load order and autoload interaction</h3><p class="wp-block-paragraph">If XivAlexander autoload is configured, its DLL loads at game startup, in the same phase as Dalamud&#8217;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.</p><h2 class="wp-block-heading">A stable arrangement to aim for</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/how-to-update-xivalexander-after-patch/">How to Update XivAlexander After a Patch</a>, because a patch can break either tool independently.</p><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Does Dalamud make XivAlexander unnecessary?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Should I blame XivAlexander or Dalamud for a crash?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Can I use XivAlexander without XIVLauncher at all?</h3><p class="wp-block-paragraph">Yes. XivAlexander is standalone and works with the official launcher. XIVLauncher is only relevant if you also want Dalamud plugins.</p><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>XivAlexander with ReShade and GShade: Chain-Loading Guide</title>
		<link>https://xivalexander.net/xivalexander-reshade-gshade-chain-loading/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:09:30 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-reshade-gshade-chain-loading/</guid>

					<description><![CDATA[ReShade and GShade are visual overlay tools that, like XivAlexander&#8217;s autoload mode, can be loaded through a DLL placed in the game folder and named d3d11.dll or dxgi.dll. When two tools both want the same file name, only one can occupy it, and the other must be chain-loaded through the first. If you simply copy...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">ReShade and GShade are visual overlay tools that, like XivAlexander&#8217;s autoload mode, can be loaded through a DLL placed in the game folder and named d3d11.dll or dxgi.dll. When two tools both want the same file name, only one can occupy it, and the other must be chain-loaded through the first. If you simply copy both tools&#8217; DLLs into the game folder with the same name, one will overwrite the other, and you will end up with either a missing tool or a crash. This guide explains chain-loading, the correct order to test, and how to isolate a crash.</p><h2 class="wp-block-heading">How chain-loading works</h2><p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">Recommended approach: portable mode first</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/how-to-install-xivalexander/">How to Install XivAlexander on Windows</a>. 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.</p><h2 class="wp-block-heading">If you need full autoload chain-loading</h2><ul class="wp-block-list"><li>Back up your game folder&#8217;s DLL files and your visual tool&#8217;s presets before changing anything. A preset you lose to a careless overwrite is difficult to reconstruct.</li><li>Decide which tool occupies the game&#8217;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.</li><li>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.</li><li>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.</li></ul><h2 class="wp-block-heading">Isolating a crash</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/xivalexander-dalamud-conflict/">XivAlexander and Dalamud Conflict</a>. If XivAlexander alone crashes, check patch compatibility in <a href="https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/">XivAlexander Not Working After a Patch</a>. 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.</p><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Can I use XivAlexander autoload and ReShade at the same time?</h3><p class="wp-block-paragraph">Yes, with chain-loading, but portable mode for XivAlexander is the simpler and more reliable arrangement for most players.</p><h3 class="wp-block-heading">Which file name should I use, d3d11 or dxgi?</h3><p class="wp-block-paragraph">Use the name your visual tool already uses, and chain the other tool through it, unless that tool&#8217;s documentation directs otherwise. Consistency matters more than the specific name.</p><h3 class="wp-block-heading">Do visual presets affect latency?</h3><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>XivAlexander Still Clipping at High Ping: Diagnosis</title>
		<link>https://xivalexander.net/xivalexander-still-clipping-high-ping/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:09:12 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-still-clipping-high-ping/</guid>

					<description><![CDATA[XivAlexander is often installed with the expectation that it will fix all high-ping problems. It will not, because it only fixes one part of the problem. It adjusts animation-lock timing locally. It does not lower your ping, improve your route to the data centre, fix packet loss, or correct your rotation. If you are still...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">XivAlexander is often installed with the expectation that it will fix all high-ping problems. It will not, because it only fixes one part of the problem. It adjusts animation-lock timing locally. It does not lower your ping, improve your route to the data centre, fix packet loss, or correct your rotation. If you are still clipping with the tool running, the fault may be in any of those other areas, and treating every clip as a tool failure will lead you in circles. This guide separates the causes so you can find the real one.</p><h2 class="wp-block-heading">Step 1: Confirm the tool is actually working</h2><p class="wp-block-paragraph">Before diagnosing anything else, confirm the loader is attached and the tool is working, using <a href="https://xivalexander.net/how-to-check-if-xivalexander-is-working/">How to Check If XivAlexander Is Working</a>. 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 <a href="https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/">XivAlexander Not Working After a Patch</a> and <a href="https://xivalexander.net/xivalexander-dalamud-conflict/">XivAlexander and Dalamud Conflict</a> before blaming your network.</p><h2 class="wp-block-heading">Step 2: Measure your ping and route honestly</h2><p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">Step 3: Check rotation and job factors</h2><p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">A practical diagnosis table</h2><p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Should I add a VPN or routing service on top of XivAlexander?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Does a higher ping always mean worse clipping?</h3><p class="wp-block-paragraph">Generally yes, but stability matters as much as the number. A stable high ping is more predictable than a spiking lower ping.</p><h3 class="wp-block-heading">Is double weaving impossible above a certain ping even with the tool?</h3><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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&#8217;s faults.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>XivAlexander Loader Cannot Find Game: Fixes</title>
		<link>https://xivalexander.net/xivalexander-loader-cannot-find-game/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:08:54 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-loader-cannot-find-game/</guid>

					<description><![CDATA[One of the most common XivAlexander setup failures is also one of the simplest to describe: the loader opens, but it cannot find the game. The game may be installed and running, yet the loader reports no game, an empty game list, or a wrong installation. That usually means the loader is looking in the...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">One of the most common XivAlexander setup failures is also one of the simplest to describe: the loader opens, but it cannot find the game. The game may be installed and running, yet the loader reports no game, an empty game list, or a wrong installation. That usually means the loader is looking in the wrong place, not that the game is broken. This guide works through the causes in order, from the most common to the least, so you can find the fault without reinstalling everything.</p><h2 class="wp-block-heading">Step 1: Make sure the game is actually in a state the loader can see</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/how-to-install-xivalexander/">How to Install XivAlexander on Windows</a>. 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&#8217;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.</p><h2 class="wp-block-heading">Step 2: Use Find game folder</h2><p class="wp-block-paragraph">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&#8217;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 <a href="https://xivalexander.net/how-to-install-xivalexander-with-xivlauncher/">How to Install XivAlexander with XIVLauncher</a>, because the game folder XIVLauncher uses is the one the loader needs.</p><h2 class="wp-block-heading">Step 3: Check for multiple installations</h2><p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">Other causes to check</h2><ul class="wp-block-list"><li>Antivirus quarantine: if the loader was quarantined, it may run partially or not at all. See <a href="https://xivalexander.net/xivalexander-antivirus-false-positive/">XivAlexander Antivirus False Positive</a> and verify the hash before restoring anything.</li><li>Outdated build after a patch: if the loader cannot attach after a patch, the cause may be opcode incompatibility, not path detection. See <a href="https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/">XivAlexander Not Working After a Patch</a>.</li><li>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.</li><li>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.</li></ul><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Why does the loader find the game sometimes but not others?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Should I reinstall the game?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Does Steam vs standalone matter?</h3><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>XivAlexander Antivirus False Positive: What to Do</title>
		<link>https://xivalexander.net/xivalexander-antivirus-false-positive/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:08:33 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-antivirus-false-positive/</guid>

					<description><![CDATA[Windows Defender and other antivirus programs frequently flag XivAlexander as suspicious, often with a generic label such as a trojan or injector. That is alarming to see, and it deserves a careful response rather than either panic or dismissal. The reason for the flag is well understood: XivAlexander injects a DLL into the game process...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">Windows Defender and other antivirus programs frequently flag XivAlexander as suspicious, often with a generic label such as a trojan or injector. That is alarming to see, and it deserves a careful response rather than either panic or dismissal. The reason for the flag is well understood: XivAlexander injects a DLL into the game process and hooks local network handling, and those techniques look, to a heuristic scanner, like the techniques malware uses. A heuristic flag is not a verdict that a file is malware, but it is also not proof that a file is clean. This guide shows how to tell the difference.</p><h2 class="wp-block-heading">Why the flag happens</h2><p class="wp-block-paragraph">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&#8217;s core behaviour, DLL injection into FFXIV, triggers heuristic detection by design. The project&#8217;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.</p><h2 class="wp-block-heading">The correct response, in order</h2><ul class="wp-block-list"><li>Do not run the file yet. If your antivirus quarantined it, leave it quarantined while you check.</li><li>Confirm you downloaded the stable release, v1.14.9.3, from the <a href="https://xivalexander.net/download/">download page</a>, using the GitHub release as the main channel. A file from an unknown re-upload deserves more suspicion, not less.</li><li>Verify the SHA-256 hash exactly as described in <a href="https://xivalexander.net/how-to-verify-xivalexander-sha256/">How to Verify XivAlexander SHA-256 After Download</a>. The expected value is c17be29dc81cf4c5a43954832a47133d4f3929688a2304ebb1525c15526de03a. If the hash does not match, delete the file and do not proceed.</li><li>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.</li><li>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.</li></ul><h2 class="wp-block-heading">What not to do</h2><p class="wp-block-paragraph">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.</p><h2 class="wp-block-heading">If the flag appears after a patch</h2><p class="wp-block-paragraph">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 <a href="https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/">XivAlexander Not Working After a Patch</a> is more likely than an antivirus explanation, and you should not use an exclusion to mask a compatibility failure.</p><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Does a flag mean XivAlexander is malware?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Should I submit the file to my antivirus vendor?</h3><p class="wp-block-paragraph">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.</p><h3 class="wp-block-heading">Can I avoid flags by using a different download source?</h3><p class="wp-block-paragraph">No. A mirror does not change how the tool behaves, and an unverified mirror adds risk. Use the GitHub release and verify the hash.</p><p class="wp-block-paragraph">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.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>XivAlexander Not Working After a Patch: Opcode Fixes</title>
		<link>https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/</link>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 15:08:11 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://xivalexander.net/xivalexander-not-working-after-patch-opcodes/</guid>

					<description><![CDATA[After a Final Fantasy XIV patch, XivAlexander often stops working, crashes, or simply does nothing. This is not a sign that your settings are wrong, and it is not fixed by reinstalling the same build. Patches change the game&#8217;s internal packet structures, known as opcodes. XivAlexander identifies game packets by those opcodes, so when they...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">After a Final Fantasy XIV patch, XivAlexander often stops working, crashes, or simply does nothing. This is not a sign that your settings are wrong, and it is not fixed by reinstalling the same build. Patches change the game&#8217;s internal packet structures, known as opcodes. XivAlexander identifies game packets by those opcodes, so when they change, the tool can no longer recognise the packets it needs to adjust. Until the tool is updated for the new patch, it cannot work reliably, and forcing it is likely to make things worse.</p><h2 class="wp-block-heading">Step 1: Confirm the base game works</h2><p class="wp-block-paragraph">Launch FFXIV without XivAlexander and confirm the game itself runs. If the base game fails, fix the game first. If the base game works but the tool does not, you have isolated the problem to the tool and the patch, which is the expected situation. Do not skip this step: many patch-day reports turn out to be game update failures, launcher issues, or server maintenance, not tool failures.</p><h2 class="wp-block-heading">Step 2: Turn off autoload and test portable mode</h2><p class="wp-block-paragraph">If you use autoload, turn it off, as described in <a href="https://xivalexander.net/how-to-uninstall-xivalexander/">How to Uninstall XivAlexander Completely</a>, and restart the game. Then test the tool in portable mode, if at all. If portable mode also fails, the build is incompatible with the new patch, and no configuration change will fix that. If portable mode works but autoload does not, the fault is in the autoload setup, not the patch itself; see <a href="https://xivalexander.net/xivalexander-autoload-not-working/">XivAlexander Autoload Not Working</a>. Recording which of these cases you are in will save you from reinstalling the wrong thing.</p><h2 class="wp-block-heading">Step 3: Wait for, and verify, the update</h2><p class="wp-block-paragraph">Check the <a href="https://xivalexander.net/download/">download page</a> and the GitHub releases page for a new stable release or an updated opcode definition that explicitly supports the new patch. Download the new stable release, verify its hash following <a href="https://xivalexander.net/how-to-verify-xivalexander-sha256/">How to Verify XivAlexander SHA-256 After Download</a>, and test it in portable mode before re-enabling autoload. Do not copy old opcode definitions onto a new patch, do not edit opcode files by hand unless you understand exactly what you are doing, and do not install a testing build as a permanent solution. A testing build may appear sooner, but it is not the stable release, and it should not be presented or treated as one.</p><h2 class="wp-block-heading">What not to do after a patch</h2><ul class="wp-block-list"><li>Do not reinstall the same old build repeatedly. Reinstalling does not change opcodes.</li><li>Do not downgrade the game to keep an old tool working. Game version and tool version must match.</li><li>Do not run two latency tools at once in the hope that one will compensate for the other. That creates unpredictable timing and hides the real fault.</li><li>Do not disable your antivirus or firewall as a patch fix. If the tool worked before the patch and fails after it, the cause is the patch, not your security software, unless the antivirus quarantined a new file, which is covered in <a href="https://xivalexander.net/xivalexander-antivirus-false-positive/">XivAlexander Antivirus False Positive</a>.</li></ul><h2 class="wp-block-heading">If you need to play before an update appears</h2><p class="wp-block-paragraph">Play without the tool. That is the correct interim answer, even if it is unsatisfying. Your rotation will feel different at high ping, because animation lock will again be extended by the round-trip, but the game itself will be stable, and you will not be running an incompatible injection against a new client. Use the waiting time to check your network setup, since a better route still helps even without the tool, and re-read <a href="https://xivalexander.net/how-to-check-if-xivalexander-is-working/">How to Check If XivAlexander Is Working</a> so you can test the update properly when it arrives.</p><h2 class="wp-block-heading">Frequently asked questions</h2><h3 class="wp-block-heading">Does every patch break XivAlexander?</h3><p class="wp-block-paragraph">No. Minor patches may leave opcodes unchanged, in which case the tool keeps working. Major patches are far more likely to break it. Test after every patch rather than assuming.</p><h3 class="wp-block-heading">Can I update opcodes myself?</h3><p class="wp-block-paragraph">The project provides opcode definitions for supported versions. Manually editing them for an unsupported patch is expert work with a high chance of error. For most players, waiting for an official update is the right choice.</p><h3 class="wp-block-heading">How do I know an update supports my patch?</h3><p class="wp-block-paragraph">The release notes or update announcement should state the supported game version explicitly. If it does not, treat it as unconfirmed and test in portable mode.</p><p class="wp-block-paragraph">Patch breakage is a normal part of using a tool that depends on game internals. The players who handle it best are the ones who test the base game first, turn autoload off, wait for a verified stable update, and play without the tool in the meantime.</p><p class="wp-block-paragraph">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.</p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
