Installing Teamcraft in Linux

linux_teamcraft.md

FLATPAK are not supported!

Choosing your WINE

XIVLauncher community has two wine "supported".

1. unofficial-wine-xiv-git https://github.com/rankynbass/unofficial-wine-xiv-git/releases

2. wine-ge-xiv https://github.com/rankynbass/wine-ge-xiv/releases

Both works just fine but we gotta some work to do.

Wayland

Unfortunately as of time being, at least in my machine, it simply wasn't possible to run Teamcraft in Wayland.

The problem is not that Teamcraft didn't work, it did, but just would not render anything inside the window. Maybe your experience will be different than mine, you could try, don't get your hopes too high at the moment.

Setup

Use official wine (right up this moment its 9.5), either staging or not. For some reason both mentioned before have problems to setup our prefix.

With the official wine (staging or not) we prepare our prefix.

1. Delete or rename your old one in ~/.xlcore/wineprefix.
2. Install FFXIV Teamcraft with WINEPREFIX=~/.xlcore/wineprefix wine /path/to/ffxiv-teamcraft-Setup-<version>.exe and close as soon as the teamcraft starts successfully.
3. Execute WINEPREFIX=~/.xlcore/wineprefix /path/to/chosen/wine/bin/wineboot -u. Example: WINEPREFIX=~/.xlcore/wineprefix ~/.xlcore/compatibilitytool/beta/unofficial-wine-xiv-wayland-9.5.1/bin/wineboot -u.
4. Setup XIVLauncher to use the chosen wine. Settings -> Wine -> Change to Custom -> set the path to /path/to/chosen/wine/bin/
5. Check which Sync you'll be using. ESYNC or FSYNC, keep in mind your choice.

Launching

After saving the settings and updating the prefix we are ready to go.

1. If you have ESYNC enabled, you should add WINEESYNC=1 before the next command. If you have FSYNC then WINEFSYNC=1.
2. Start Teamcraft:
   • WINEESYNC: WINEESYNC=1 WINEPREFIX=~/.xlcore/wineprefix/ /path/to/chosen/wine/bin/wine ~/.xlcore/wineprefix/drive_c/users/$USER/AppData/Local/ffxiv-teamcraft/FFXIV\ Teamcraft.exe
   • WINEFSYNC: WINEFSYNC=1 WINEPREFIX=~/.xlcore/wineprefix/ /path/to/chosen/wine/bin/wine ~/.xlcore/wineprefix/drive_c/users/$USER/AppData/Local/ffxiv-teamcraft/FFXIV\ Teamcraft.exe
3. Login
4. Start FFXIV
5. Login as usual

Beware

If you rely on some patch that the chosen wine uses I do not guarantee that they will work following these steps, do it at your own risk.

I've got the TeamCraft app running just fine under Wayland using Rankynbass's unofficial-wine-xiv-staging-ntsync-10.10, but packet capture still does not work for me.

Update: I managed to get packet capture working. Their Discord server has troubleshooting instructions which basically involve verifying that the client is receiving packets at all, but assuming you are:

• Go to Settings, Desktop, then click the buttons to Reset ignored characters and Reset linked characters.
• Restart TC.
• Go to the Inventory page and click the button to Reset all inventories.
• In game, use the right-click menu (or appropriate controller button) to Sort or Unsort your inventory. You may use Unsort to return your inventory to its previous state once you're done linking. Make sure at least one item moves as you do this.
• This should trigger a popup to select your character in TC.
• Once it's selected, teleport to a new zone. *It MUST be an entirely different zone than the one you are currently in -- for example, Limsa to Eulmore -- and will not work if you use aethernet teleports within the same zone.

Also for anyone using the fish shell, I made a simple command alias for launching TeamCraft:

function teamcraft
    set -lx WINESYNC 1 
    set -lx WINEPREFIX $HOME/.xlcore/wineprefix/ 
    set -lx WINE $HOME/.xlcore/compatibilitytool/wine/unofficial-wine-xiv-staging-ntsync-10.10/bin/wine
    set -lx TEAMCRAFT_EXE $HOME/.xlcore/wineprefix/drive_c/users/$USER/AppData/Local/ffxiv-teamcraft/FFXIV\ Teamcraft.exe
    $WINE $TEAMCRAFT_EXE
end

If you aren't using a custom Wine, you'll probably want to replace the WINE path with this:

$HOME/.xlcore/compatibilitytool/wine/wine-xiv-staging-fsync-git-10.8.r0.g47f77594-nolsc/bin/wine

Hi! Thank you for writing this guide, I'm new to using Linux & Wine and found it easy to follow. Using the steps from your guide, I can also vouch for Teamcraft working (with packet capture!) under Wayland using unofficial-wine-xiv-staging-10.10.

function teamcraft
    set -lx WINESYNC 1 
    set -lx WINEPREFIX $HOME/.xlcore/wineprefix/ 
    set -lx WINE $HOME/.xlcore/compatibilitytool/wine/unofficial-wine-xiv-staging-ntsync-10.10/bin/wine
    set -lx TEAMCRAFT_EXE $HOME/.xlcore/wineprefix/drive_c/users/$USER/AppData/Local/ffxiv-teamcraft/FFXIV\ Teamcraft.exe
    $WINE $TEAMCRAFT_EXE
end

Loving that alias. One small change I did was the actual execution line so it freed up my terminal:
nohup $WINE $TEAMCRAFT_EXE > /dev/null & disown

Wish I could figure out how to get a shortcut to actually work, but the alias is still a pretty good thing to have.

Edit: hah, figured that part out. I just used the shortcut made and coupling with the alias modified the .desktop file:

[Desktop Entry]
Comment[en_US]=Collaborative crafting made easy
Comment=Collaborative crafting made easy
Exec=fish -c teamcraft
GenericName[en_US]=
GenericName=
Icon=D894_FFXIV Teamcraft.0
MimeType=
Name[en_US]=FFXIV Teamcraft
Name=FFXIV Teamcraft
Path=
StartupNotify=true
StartupWMClass=
Terminal=true
TerminalOptions=
Type=Application
X-KDE-SubstituteUID=false
X-KDE-Username=

Thanks all who kept helping others. I should get to write a guide for at least a Steam method.

The truth is I wanted to migrate my system to another Distro due to some issues I had with Arch and have not yet done with updates. Hence this guide was written when Wine 9 was still current version.

XIVLauncher version I will do later, I don't want to install 3 different Dotnet runtimes for one program (resulting in 500+ MBits just for that). So for now I will try to at least do for Steam.

I got it working on Fedora 43 by using the system wine. I had to use winetricks to install dotnet 4.5 and ignore all the warnings it throws. After that I needed to change the windows version from server 2003 for some reason to 7. Then I followed from step 2 onward.

I packet capture and inventory tracking working on Kubuntu 25.10, KDE Plazma 6.4.5 with Wayland! I used wintricks to install the .NET version needed and changed the system back to Win7. The main thing I had to do that's not mentioned here is make a new teamcraft.desktop file in ~/.local/share/applications that I could pin to the taskbar to click to launch, as the one that's automatically made will be edited by wine, removing the WINEFSYNC=1 and custom wine bin.

Desktop file (Replace $USER with your username)

#!/usr/bin/env xdg-open
[Desktop Entry]
Name=FFXIV Teamcraft (Real)
Comment=Collaborative crafting made easy
Type=Application
StartupNotify=true

Exec=env WINEPREFIX="/home/flames5123/.xlcore/wineprefix" WINEFSYNC=1 /home/$USER/.xlcore/compatibilitytool/beta/unofficial-wine-xiv-staging-10.10/bin/wine "C:\\users\\$USER\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\FFXIV Teamcraft\\FFXIV Teamcraft.lnk"

Path=/home/$USER/.xlcore/wineprefix/drive_c/users/flames5123/AppData/Local/ffxiv-teamcraft
Icon=101C_FFXIV Teamcraft.0
StartupWMClass=FFXIV Teamcraft.exe

Also unofficial-wine-xiv-git was causing coredumps on my setup so I use the XIVLauncher managed version.

Is there any reason it has to be installed to the same wine prefix? trying to do that is causing my launcher to error out hard.

Is there any reason it has to be installed to the same wine prefix? trying to do that is causing my launcher to error out hard.

The prefix is basically a mini Windows the game runs in. In order for packet capture to work, TC needs to talk to the game and that takes place within the prefix. If you didn't care for that you could run it standalone, but at that point you're better off using the web version and saving the installation trouble.

Is there any reason it has to be installed to the same wine prefix? trying to do that is causing my launcher to error out hard.

The prefix is basically a mini Windows the game runs in. In order for packet capture to work, TC needs to talk to the game and that takes place within the prefix. If you didn't care for that you could run it standalone, but at that point you're better off using the web version and saving the installation trouble.

ok wasn't sure if the prefix was what enabled the packet capture or the specific wine binary.

part of the problem is i'm trying to set this all up on an atomic OS so I can't install system packages.