Getting Started With FFXIV Modifications
FFXIV is a game that runs on a modified version of Square Enix's proprietary Lumin engine, and the modding scene around it has grown substantially over the past few years. The ecosystem works differently than what you'd find in Skyrim or Fallout because of how the game loads its assets and communicates with servers. I spent about three years working through the technical side of this after my first installation broke my game client entirely during the Endwalker expansion push. The foundation here is FFXIV Mod Manager (FFXIVModLoader), which intercepts asset loading before the game processes it. This is different from traditional modding where you overwrite game files directly. The loader injects custom .pak files into the resource pipeline. You download the loader, place it in your FFXIV root directory alongside game.exe, and run it once to register. After that, any mods you drop into the Mods folder get loaded automatically on launch. The main mod types you will encounter are texture replacements, character model swaps, UI overhauls, and quality-of-life plugins that use the Dalamud framework. Each category operates differently behind the scenes. Texture packs replace .iff files inside the game's archived resources. Character models swap out skeleton and geometry data. UI mods modify overlay render calls. QoL plugins inject into CDLLs through Dalamud's hook system.
I ran into a specific problem about eight months ago where a custom texture pack would load fine at 1080p but cause the game to crash at 1440p with a memory access violation. The crash log pointed to an offset calculation error in the texture streaming system. The workaround was straightforward once I figured it out. I needed to enable the lowMemoryMode flag in the mod manager's config file and reduce the texture resolution scaling to 0.75. That stopped the crashes without noticeably degrading visual quality on my setup. I also had to exclude one particular character model mod that was using uncompressed PNGs instead of the normal DXT5 format, which was eating VRAM unnecessarily. One thing most people miss is that Dalamud plugins are not mods in the traditional sense. They are compiled Cassemblies that hook into the game's internal methods. This means they can read and modify game state in ways pure asset replacements cannot. A plugin like XIV Combo can trigger abilities based on cooldown timers. Another one, Inventory Note, lets you tag items with labels. These require Dalamud to be installed first, which the mod manager usually handles automatically. But here is the catch: some Dalamud plugins check your game client version against their own version matrix, and if they are out of date, they simply will not load. You have to keep them updated manually or use the Dalamud updater plugin. Another counter-intuitive point is that more mods does not always mean a better experience. I have seen people stack twelve texture packs, four model swaps, and six UI mods and then wonder why the game stuttered during raids. The rendering pipeline has a limit on how many custom asset bundles it can stream per frame. When that limit is exceeded, you get frame hitches that look exactly like server lag but are actually asset GC pressure. The practical solution is to keep your active mod count under six for textures and under three for model replacements. UI mods are cheaper on performance since they do not add geometry or texture memory, so you can run more of those safely.
Installation Walkthrough
Download the latest version of FFXIVModLoader from the official GitHub repository. The link is github.com/ffxivmodloader/FFXIVModLoader. Extract the contents into your FFXIV installation directory, which is typically something like C:\Program Files (x86)\Square Enix\FINAL FANTASY XIV - A Realm Reborn. Run the loader executable once. It will create a Mods folder and a configuration file in the same directory. For Dalamud, the loader handles this automatically on first run. It downloads the appropriate version for your game client. If you prefer manual control, you can download it separately from github.com/goatcorp/Dalamud. The manual method gives you better visibility into what is being installed and allows you to pin versions if a newer release breaks compatibility with your current patch. Mods themselves come from several sources. The primary hub is ffxiv-datamining.github.io for raw asset files, and gitlab.com/xivapi/mod-manager for packaged mods with dependency resolution. Third-party sites like Nexus Mods also host community submissions. Download a mod package, extract it into your Mods folder, and restart the game. The mod manager logs all loaded mods to a text file in the installation directory. Check that file if something does not appear to be working.
Get the Full Details
Common Pitfalls
The biggest issue users run into is version mismatch between the game patch and the mod. Square Enix updates FFXIV roughly every two weeks, and each update can change asset offsets, UI layouts, and internal structures. A texture pack that worked on patch 6.5 may break entirely on 7.0 because the UI coordinates it references no longer exist. Always check the mod's last updated date and look for version-specific notes in the description. Another frequent problem is conflicting mods that target the same asset. If two different texture packs both replace the same leather armor set, the loader picks one at random based on alphabetical order of the folder name. There is no built-in priority system unless you use the config file to explicitly enable or disable specific mods. I learned this the hard way when two lighting mods created a conflicting shadow pass that made outdoor areas look washed out. Disabling one of them in the config resolved it immediately. Dalamud plugins face a different problem. They can break when Square Enix patches their anti-tamper measures or changes API signatures. Plugins like XivChatText or Bagan may stop working between major patches and require the developer to update them. During that window, which can last anywhere from a few hours to two weeks, you simply cannot use those plugins until a compatible version ships.
Performance Impact
A typical mod setup adds roughly 200 to 500 megabytes of additional VRAM usage depending on texture resolutions. Character model swaps can add another 100 to 300 megabytes because they often include higher-poly geometry. UI mods are negligible at under 50 megabytes total. If you are running on a card with less than 8GB of VRAM, you should avoid high-resolution texture packs and stick to 1080p scaling at most. Frame rates generally drop by 5 to 15 percent with a moderate mod load, mostly due to increased asset streaming overhead. The hit is more noticeable during cutscenes and city areas where the game streams dense geometry and custom textures simultaneously. In combat, the impact is smaller because the GPU is already saturated by standard rendering work.
Maintenance Routine
Run this check every time a new game patch drops. Open the mod manager, verify which mods show red warning markers indicating incompatibility. Update Dalamud plugins through the plugin installer. Clear the mod cache by deleting the contents of the Cache folder in the installation directory. This forces the loader to rebuild its asset index and prevents stale references from causing crashes. The cache rebuild usually takes two to four minutes depending on your drive speed. If the game fails to launch after a patch, the first thing to try is disabling all mods and launching clean. If it starts normally, re-enable mods in small batches until you isolate the culprit. This is faster than checking individual mod compatibility pages, which are often outdated within days of a patch release.
