tommadness

> However, without the pid sharing commands, [Steam] will never detect when the game (and launcher) closes, and [the Steam library shortcut for XIVLauncher] will remain in the "Running" state...

Due to how Flatpak sandboxes processes, there is nothing we can really do about that. You will need the non-Flatpak version of Steam to use XIVLauncher.

I said you need the non-Flatpak *Steam*. Native vs Flatpak XIVLauncher doesn't matter in this case.

> Also facing this issue on Archlinux, installed xivlauncher-bin from AUR and have gnome-keyring isntalled but it won't store my secrets. Are you positive the gnome-keyring daemon is running and...

You can open `/home/deck/.xlcore/launcher.ini` in the text editor of your choice to change `IsIgnoringSteam` manually

This happens every time we update XIVLauncher. This is the reason we don't update it unless absolutely necessary. It's a false positive, either make exceptions or remove MalwareBytes entirely.

XLCore has its own setting for what wine binary to use. It will not mess up your native wine. It also keeps its managed wine versions to its own .xlcore/compattool...

Windows has a mostly-undocumented limit to the number of credentials stored in Windows Credential Manager. This is where we securely store your username and password. Try clearing out some old...

Your game files are broken. Disable auto login, right click the Login button, and select "Repair game files". If you use TexTools to apply mods, **do not reapply those mods...

Yes, that's a path from the compiling environment. It's how compiled .NET programs report errors. Repair indexes have not been updated for Dawntrail yet. This is expected.