How to Update XivAlexander After a FFXIV Patch
Most XivAlexander failures follow the same pattern: a FFXIV patch lands, the tool stops working or the game crashes, and the player tries to force the old setup to work. That rarely helps, because patches change the internal structures and memory addresses the tool relies on, known as opcodes. When opcodes change, the tool can no longer identify the packets it needs to adjust, and no amount of reinstalling the same old build will fix that. The correct update process is slower than reinstalling, but it is the only one that reliably works.
Step 1: Back up before the patch, not after
Before a major patch, back up your XivAlexander folder, including the configuration file. A backup lets you restore your settings if an update resets them, and it gives you a known-good copy to compare against. Do not back up by copying the game folder, and do not rely on a backup of the old build to run on the new patch; the backup is for settings, not for forcing old code onto new game data. If you use autoload, note how it is configured before the patch, so you can turn it off cleanly if the new patch needs testing first.
Step 2: Test the base game first
After the patch, launch FFXIV without XivAlexander and confirm the game itself works. This single step separates a game problem from a tool problem, and it saves a great deal of wasted diagnosis. If the base game crashes or fails to update, fix that first. Only when the base game runs normally should you test XivAlexander. If the tool then fails, read XivAlexander Not Working After a Patch before changing anything else.
Step 3: Check for a new stable release or opcode update
Check the download page and the GitHub releases page for a new stable release that supports the new patch. Download the new stable release, verify its hash as described in How to Verify XivAlexander SHA-256 After Download, and extract it to a fresh folder rather than overwriting your old folder in place. Copy your backed-up configuration into the new folder only if the configuration format has not changed; if you are unsure, start with the default configuration and reapply your settings by hand. Do not install a testing build as a shortcut. A testing build may support the new patch earlier, but it is not the stable release, and using it for everyday play trades one risk for another.
Step 4: Re-test in portable mode
Test the new build in portable mode first, even if you normally use autoload. Run the game, attach the loader, and check weaving on a training dummy as described in How to Check If XivAlexander Is Working. Only after portable mode works should you re-enable autoload, and if autoload fails while portable mode works, the fault is in the autoload configuration, not in the new build. See XivAlexander Autoload Not Working for that case. If the new build also fails, wait for a further update rather than downgrading the game or forcing old opcode definitions onto the new patch.
Frequently asked questions
How long after a patch should I wait?
There is no fixed timetable. Wait until a stable release or an opcode update that explicitly supports the new patch is available, and verify it before you rely on it.
Can I keep playing with the old build until an update appears?
If the old build does not work on the new patch, no. Remove autoload, play without the tool, and wait. Forcing it risks crashes and gives you no reliable weaving benefit.
Should I delete my old folder?
Keep the old folder until the new build works, then you may remove it. Do not keep two autoload configurations active at once.
Patch-day discipline is simple: base game first, new stable build second, portable test third, autoload last. Players who follow that order spend patch day playing; players who reinstall the old build repeatedly spend it troubleshooting.
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.
