Ultimate Guide To Exporting Equipped Gear Sets In FFXI GearSwap

To instantly export your currently equipped gear set in Final Fantasy XI, input the command //gs export into your game chat window or console. This processes your character's active equipment packets and saves a pre-formatted Lua table directly to your local Windower addons folder under the GearSwap data export path. From there, you can copy the structural arrays directly into your job-specific configuration files for immediate automated swapping.

Technical Prerequisites and Preparation Checklist

Before attempting to export your equipped items from Final Fantasy XI, you must ensure your Windower environment, directory permissions, and in-game inventory states are correctly aligned. GearSwap relies on active packet parsing to determine what your character is wearing. If your local files are set to read-only, or if your character is in a transition state (such as zoning or mid-cast), the export tool will fail to write the necessary Lua data.

Essential Tools and Requirements

• Active Windower 4 or Windower 5 Installation: You must have the Windower launcher installed and fully updated to run the GearSwap helper library.
• GearSwap Addon Enabled: Ensure the GearSwap addon is toggled on within your Windower launcher library or loaded manually via the console.
• Physical Inventory Storage Rules: The items you wish to export must be actively equipped on your character. Items residing in your Mog Safe, Storage, or Locker cannot be exported unless they are in your active inventory, Wardrobes (1 through 8), or Case/Sack and currently resting on your character model.
• Admin-Level Local Directory Access: Your operating system must grant read and write permissions to the Windower directory, especially the subfolders containing configuration data.
• High-Quality Text Editor: To inspect and implement the exported files, utilize a structured text editor such as Notepad++ or Visual Studio Code set to recognize Lua syntax scripting.

Step-by-Step GearSwap Export Workflow

The process of converting your active in-game gear into clean, structured programming code requires precise execution. Follow these detailed steps to capture your current setup, locate the resulting files, and integrate them into your automated macros.

Step 1: Equipping Your Target Gear Set

Manually equip every piece of gear you wish to capture in your set. You can do this using the native Final Fantasy XI equipment menu, in-game macros, or Equipset configurations. Ensure that every slot—including your main weapon, sub-weapon, ranged weapon, ammo, head, neck, left ear, right ear, body, hands, left ring, right ring, back, waist, legs, and feet—is populated exactly as you want it represented in your code.

Pro-Tip: If you are exporting a set that relies on specific augmented stats, such as those obtained via Odyssey, Escha/Reisenjima, or Ambuscade, make sure the item is fully updated in your inventory. GearSwap reads the specific item ID and its associated extdata packet to record these augments.

Step 2: Executing the Console Command

Open your in-game chat interface and type your command. If typing directly into the standard chat bar, prepend the command with two forward slashes. If you are typing directly into the Windower console (accessed by pressing the tilde key on your keyboard), omit the slashes.

To run the default export, type: //gs export

To run the command directly through the Windower console, type: gs export

For advanced control over the output formatting, you can append specific parameters. For instance, if you prefer an XML output instead of a Lua table format, type: //gs export xml

Once you press Enter, you will see a confirmation message in your game chat log indicating that the export process was successful and displaying the generated filename.

Warning: Do not move your character, change gear, or zone during the brief window when the command is executing. Doing so can cause packet fragmentation, resulting in missing slots or a corrupt export file.

Step 3: Locating Your Exported Files

Once the command is executed, GearSwap saves the file on your local hard drive. Navigate to your main Windower installation folder. The standard pathing structure is as follows:

*C:\Program Files (x86)\Windower4\addons\GearSwap\data\export*

Within this directory, you will find files named according to your character's name, the date, and the time the export occurred. The file format will look similar to: CharacterName_YYYY_MM_DD_HHMMSS.lua

If you exported using the XML parameter, the file extension will be .xml instead of .lua.

Step 4: Integrating the Exported Set into Your Job Lua

Open the newly created export file with your preferred text editor. You will see a structured Lua table containing all sixteen equipment slots mapped to the exact items you wore during the export.

Highlight the entire block of code starting from the opening curly brace to the closing curly brace. Copy this block of text. Open your active job-specific file, such as Warrior.lua or WhiteMage.lua, located inside your GearSwap data directory. Locate the appropriate set block, such as your idle set or your weapon skill set, and paste the copied table inside the desired variable block. Save your job file and reload GearSwap in-game by typing //gs reload to apply your changes.

GearSwap Command Parameters and Export Options

Different situations require different data formatting. Depending on whether you are building a new Lua file from scratch, updating an older Spellcast XML file, or cataloging your entire wardrobe for inventory management, you should customize your export command.

The following table compares the different command variations available within the GearSwap engine and lists their corresponding output structures and primary use cases.

Troubleshooting Common GearSwap Export Failures

Even seasoned players occasionally encounter situations where the export command fails to generate files, leaves out critical stats, or throws errors. Understanding the root cause of these system issues is key to maintaining a smooth gameplay experience.

Scenario 1: Command Returns "Command Not Found" or Nothing Happens

• Root Cause: The GearSwap addon is either not loaded into your Windower environment, or your game client is suffering from a disconnected hook. This often occurs after a major game update when Windower files have not yet been re-anchored to the updated game client executable.
• Actionable Fix: Verify that GearSwap is active by typing //lua load gearswap in your chat bar. If the system returns an error stating the addon does not exist, open your Windower launcher and make sure GearSwap is toggled on under the Addons tab. If it is already enabled, perform a clean reinstall of the addon files through the launcher to fix corrupted hooks.

Scenario 2: Exported Files Do Not Display Item Augments

• Root Cause: The local item database (resources) in your Windower folder is outdated, or the specific item uses a dynamic extdata format that GearSwap's parser failed to read due to server-to-client packet delays.
• Actionable Fix: Force-refresh your client's inventory status by sorting your inventory bag using the in-game sort feature. Ensure you run the export command while standing completely still in a low-congestion zone (such as your Mog House or a low-population area like West Ronfaure) to ensure packets are received cleanly. Additionally, make sure your Windower resources files are fully updated to the latest version.

Scenario 3: The Export Directory is Empty and No File is Generated

• Root Cause: The Windows operating system is blocking Windower from writing files to your hard drive, typically because the game is installed in the protected C:\Program Files (x86) directory and Windower was not launched with elevated privileges.
• Actionable Fix: Right-click your Windower executable file and select "Run as Administrator." Alternatively, move your entire Windower installation folder out of the protected Program Files directory to a user-controlled root directory such as *C:\Windower* to bypass strict OS-level write restrictions.

Scenario 4: Export Command Triggers Lua Console Crash Errors

• Root Cause: A conflict between your currently loaded job script and the core GearSwap libraries. If your active job Lua has syntax errors or infinite loops running in its self-update loops, it can freeze the rendering thread of the addon when it attempts to call an export function.
• Actionable Fix: Unload your active job script by typing //gs user unload in the chat box, leaving only the raw GearSwap addon engine running. Once the custom user script is unloaded, run your //gs export command again. The core engine will successfully capture your gear without your custom script interfering.

Frequently Asked Questions

Why does my exported gear set look different than what I am visually wearing in-game?

This occurs when you have Style Lock active. Style Lock projects an aesthetic appearance over your character while allowing you to wear completely different items for stats. The GearSwap export command reads your actual system packets representing your real stats and active attributes, completely ignoring your current visual Style Lock projection.

Can I export my gear while utilizing the Windower Dev build?

Yes. However, the command lines and directories for Windower 5 or dev builds may differ slightly. In newer versions, configuration files are structured under different subdirectories. Be sure to check your specific build's console logs to confirm the precise path where files are being written.

How do I export my inventory from all storage bags at once?

The export command only writes your currently equipped gear. If you want to dump your entire inventory, wardrobes, and storage bags into a readable document, you should use the Windower addon called Itemizer or the dedicated inventory dump tools rather than GearSwap's export system.

Do I need to manually add commas and formatting when pasting my export into a Lua?

No. The default export command formats the gear sets with precise Lua table syntax, including bracketed slot names, capitalized item strings, and trailing commas. You can directly copy the code from the export file and paste it straight between the curly braces of any valid GearSwap set container.

Optimize Your FFXI Gameplay

Take complete control of your character's potential by integrating your freshly exported gear configurations into premium, automated job scripts. By mastering your GearSwap variables and maintaining organized profiles, you ensure peak performance across every high-tier battle inside Vana'diel.